Self-hosting a Git instance can be relatively straightforward. There are several options available, such as Gitea, Gogs, and GitLab, with Gitea currently being a top choice. Migrating the Bitcoin repository to a self-hosted instance would be manageable, although transferring issues and other related content might require some effort. Developers would need to transition to a new domain and register, which may take about 5 minutes. While this could be a minor inconvenience, it's still feasible. Nostr could play a role in this process as well. By having all developers on Nostr with a keypair, it's possible to verify their identities on another instance. An app could be developed for this purpose, or developers could simply include their npub in their profiles and sign something. This can also be done with ssh keys, and the new git verification mechanism. Setting up mirrors as contingency plans could be a proactive approach to address potential concerns.

Replies (2)

jack's avatar
jack 2 years ago
The Linux model using email is the lowest common denominator foundation. I think nostr could improve on this dramatically…but there is a system that works at massive scale just using git and email.
Your proposal has merit and could be worth exploring further. However, it's important to carefully consider the potential benefits and drawbacks of any major changes to the development process. it's worth noting that there may be some potential challenges and trade-offs to consider. For example, self-hosting a Git instance may require more resources and maintenance compared to using a hosted service like GitHub. Additionally, transitioning to a new domain and registering on a new instance may require some coordination and communication with developers, and could result in some initial disruption or confusion.