From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z5ZH0-0002uD-G3 for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 12:50:26 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.172 as permitted sender) client-ip=209.85.212.172; envelope-from=laanwj@gmail.com; helo=mail-wi0-f172.google.com; Received: from mail-wi0-f172.google.com ([209.85.212.172]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z5ZGz-0003VQ-Cj for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 12:50:26 +0000 Received: by wicgi11 with SMTP id gi11so12724245wic.0 for ; Thu, 18 Jun 2015 05:50:19 -0700 (PDT) X-Received: by 10.180.72.179 with SMTP id e19mr30014195wiv.53.1434631819382; Thu, 18 Jun 2015 05:50:19 -0700 (PDT) Received: from amethyst.visucore.com (dhcp-089-098-228-253.chello.nl. [89.98.228.253]) by mx.google.com with ESMTPSA id s10sm12139373wjy.35.2015.06.18.05.50.18 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 18 Jun 2015 05:50:18 -0700 (PDT) Date: Thu, 18 Jun 2015 14:50:17 +0200 From: "Wladimir J. van der Laan" To: Pieter Wuille Message-ID: <20150618125016.GA7611@amethyst.visucore.com> References: <55828737.6000007@riseup.net> <20150618111407.GA6690@amethyst.visucore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -1.2 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.4 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z5ZGz-0003VQ-Cj Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2015 12:50:26 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, Jun 18, 2015 at 02:29:42PM +0200, Pieter Wuille wrote: > On Thu, Jun 18, 2015 at 1:14 PM, Wladimir J. van der Laan > wrote: > > > Like in any open source project there is lots of decision making ability > > for code changes. I'd say look at the changelog for e.g. 0.11 > > https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md#0110-change-log, > > or follow pull requests for a while, to see how many decisions about > > changes are made from day to day. No, I'm not sitting on my hands, and so > > is none of the other contributors that you'd like to get rid of. > > > > The analogy goes further even. Even though I disagree with some of the > changes you're making, I respect Mike's (and anyone's) right to make a fork > of Bitcoin Core. That's how open source works: if people disagree with > changes made or not made, they can maintain their own version. However: Sure. According to github, there exist 4890 forks of the bitcoin/bitcoin repository. Forking the code is perfectly fine in itself, that doesn't even need to be said, it's how open source works. Make your changes, run your own version, contribute back the changes (or not). And I never had a problem with Bitcoin-XT while it was just a patch-set with no consensus changes. But a controversial hard fork of the chain is something else completely. Wladimir -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCgAGBQJVgr5LAAoJEHSBCwEjRsmm5mMH/0yLGGQQefRVdmM/nJZ60b/z iTCUUzY4eLL67FRC6pqGA18RdUt4Etl4wEqvgXH/B9mWIAM2yQD/jnxutYrEIoBT 8Jyd1OhmmKF8MN5/uE7JNPivIuHs0ioF+qTxlbdElpVZ2NodVotznbTvuqJgXUFb c9Et5L5n7g55uPzDt+MSV5iBDJaMiBAnZA00aTLGmYmNXxcy7xBwCFX3dDij8krv 0+zdpNNAKm85k1rG2jHCM+0onu+TOIur03pPd5OZktgr18P6UvAQ6A59yAkGgFai 4l6VVNJ40g3PzItGQ7wsKZ8s/qG5LlcEppxMlG6CX1dIDpxbrwx2aJmeNjwSLKQ= =LbA3 -----END PGP SIGNATURE-----