> Code is accepted into the Bitcoin Core repo when it is likely that the community will accept a change.
This is very vague. It relies on implicit consensus by those performing the assessment of "when it is likely that the community will accept a change" (assessors). In reality, opinions of the assessors can vary wildly. This then leads to the decision ultimately being up to the assessors. So then, the question moves to: who gets to assess the community, and what is the vote threshold of assessors?
BIPs are accepted into BIP repo with a low "reasonable" threshold.
Code is accepted into the Bitcoin Core repo when it is likely that the community will accept a change.
There is no voting in the way you think. Devs commit changes the users will accept and use. Users "fire" developers by choosing different devs or different software.
Standard open source method.
On Jun 24, 2015 4:41 PM, "Raystonn" <raystonn@hotmail.com> wrote:I would like to start a civil discussion on an undefined, or at least unwritten, portion of the BIP process. Who should get to vote on approval to commit a BIP implementation into Bitcoin Core? Is a simple majority of these voters sufficient for approval? If not, then what is?
Raystonn
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
_______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
