The case for privatizing Bitcoin Core

The discourse on the decentralization of Bitcoin Core development, as reflected in the recent email exchanges, delves into the nuances and implications of shifting towards a more private development model versus maintaining or slightly modifying the current structure. The conversation initiated with a speculative stance on transitioning Bitcoin Core into a source-available project. This model would entail development occurring privately, with the source code being released concurrently with reproducible binary versions. Concerns highlighted include the potential increase in the burden of producing educational and historical content, which is presently leveraged by the broader technical community. Additionally, this shift could significantly raise the barriers for grassroots onboarding to the project, making it almost imperative for newcomers to engage through established development organizations.

Notwithstanding, the focus shifts to the proposition of a private Bitcoin Core repository complemented by a public mirror. This setup would allow for developer engagement in public comment threads on pull requests and issue reporting while retaining the option to recede into the privacy of the repository for focused work. The concept appears more favorable albeit questions around its practicality and the possible introduction of churn remain unanswered, especially concerning the integration of public comments within the private threads without duplication.

Another aspect touched upon is the office culture and the quest for a balanced platform that mitigates the extremes of unmoderated public discussions and entirely private dialogues within the confines of a developer organization's offices. While online fora disruptions drive some discussions into office spaces, the intrinsic benefits of in-person interactions cannot be overlooked. Moreover, the premise that creating a public mirror would reduce brigading, although it might confine it to specific threads, seems contradictory to the openness of public commenting avenues.

The underlying problem statement acknowledges the dangerous misconception that the Bitcoin Core Github repository exerts undue control over Bitcoin, sometimes leading to political pressures and legal threats against developers. Emphasizing the distinction between Bitcoin's decentralized nature and Bitcoin Core's centralized governance is crucial. The proposed structural changes, aimed at disentangling these perceptions, are viewed as considerably disruptive compared to the potential benefits. The need for a collective response from Bitcoin Core contributors to mitigate social attacks without altering the project's structure is underscored.

In conclusion, while the idea of privatizing certain aspects of Bitcoin Core development is not outright dismissed, the current project structure is deemed sufficient. The emphasis lies on addressing social attacks through non-tolerance policies rather than a comprehensive overhaul of the development framework.