{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-05-07\n📝 Original message:On Thu, May 07, 2015 at 04:05:41PM +0200, Mike Hearn wrote:\n\u003e \u003e One thing is the Bitcoin core project where you could argue that the 5\n\u003e \u003e committers decide (I don't know why Wladimir would have any more\n\u003e \u003e authority than the others).\n\u003e \u003e\n\u003e \n\u003e Because he is formally the maintainer.\n\nI quite liked Wladimir's description of what someone with the ability\nto merge pull requests into Bitcoin Core is:\n\n    @orionwl github.com/bitcoin/bitcoin repository admin, or maybe just \"janitor\"\n\n-https://twitter.com/orionwl/status/563688293737697281\n\nIn any case, we can't force people to run Bitcoin Core - an unpopular\npatch that fails to reach consensus is a strong sign that it may not get\nuser acceptance either - so we might as well accept that centralized\nauthority over the development process isn't going to fly and deal with\nthe sometimes messy consequences.\n\nLike I said, you're welcome to fork the project and try to get user\nacceptance for the fork.\n\n-- \n'peter'[:-1]@petertodd.org\n000000000000000013e67b343b1f6d75cc87dfb54430bdb3bcf66d8d4b3ef6b8\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150507/cd705b97/attachment.sig\u003e"}