rich1.0npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58njumphttps://nostr.ae📅 Original date posted:2015-06-24 📝 Original message: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 at 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 at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150624/5eae6595/attachment-0001.html>