[Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers

Milly Bitcoin milly at bitcoins.info
Thu Jun 18 15:13:41 UTC 2015

 >Impacts, yes, decider, no.  Multiple ACKs are required from developers 
who will not act if the community will disagree with the change.

 >The users ultimately choose by deciding which software to download, 
and that dictates the range of choices available.

That is what I mean by a cultish reply.  Just saying the users 
ultimately decide is not an adequate explanation of the situation. You 
are talking hard fork if someone doesn't like it.  If 10% of the users 
don't like there is nothing they can do unless they want to operate an 
altcoin.  You are not going to resolve anything by repeating these types 
of replies that really have no applicability in the real world.  The 
person who approves the pull request (no matter what the process is 
beforehand) is effectively the decider.

Also, as pointed out, there is no real process in place.   Making 
offhand statements that "multiple ACKs are required" without describing 
a real process just sends people down a rat hole like this block size 
debate.  Providing these (non) answers instead of developing a real 
process is why there is so much contention now.


More information about the bitcoin-dev mailing list