[bisq-network/proposals] Host downloads on self-managed server (#72)

Devin Bileck notifications at github.com
Mon Feb 11 07:56:08 UTC 2019

> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

# Summary
Rather than hosting downloads on GitHub (https://github.com/bisq-network/bisq/releases), I am proposing we host them on a self-managed server. This will be additional work on our part to manage the server and maintain the downloads, but potentially worth while in the end.

# Rationale
Hosting downloads on a server that we (a trusted contributor) has full control over will be beneficial in the following ways:

- **Eliminate trust in GitHub.** Not only do we currently trust that GitHub downloads don't become compromised, but also that they don't start censoring downloads or access to the project in general. This seems like a centralized point of failure. However, hosting source code on GitHub (or any centralized service for that matter) should be less of a concern as if there are any interruptions the impact should be minimal and not disruptive to the end users - only a disruption to development.

- **Ability to switch version control providers with minimal end-user impact.** If at some point we decide to switch to another version control service provider, all existing (outdated) client applications will still be checking for updates from GitHub since the URL is hard-coded.

- **Provide deterministic source zips/tarballs.** As is done with Bitcoin Core and stated on their GitHub releases page (https://github.com/bitcoin/bitcoin/releases), we should recommend to not use the source download links provided by GitHub but rather our own files which should be generated deterministically.

# Responsibility
We will either need a new role or utilize an existing role (and contributor) to take on this responsibility. I believe the [Bisq Maintainer](https://github.com/bisq-network/roles/issues/63) role would make sense since they handle the release process.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190210/9b6f2a7c/attachment.html>

More information about the bisq-github mailing list