MIME-Version: 1.0
In-Reply-To: <201108102032.00373.andyparkins@gmail.com>
References: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com>
	<CAJNQ0stfYFN2YCGq-be5D-XW+81ZkVVM_jHHonSy2OHsNyN1Cw@mail.gmail.com>
	<CABsx9T059A+RtJ-Mc8XCX6m3dyF23WZ5jraBLGt1=hvSGn14kg@mail.gmail.com>
	<201108102032.00373.andyparkins@gmail.com>
Date: Wed, 10 Aug 2011 15:57:29 -0400
Message-ID: <CA+8xBpdCtYQkKwQZzZY2PsHm=+BrhD4TdoKqoAVoa7R0W9YkRw@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Andy Parkins <andyparkins@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Change to multiple executables?
Precedence: list

On Wed, Aug 10, 2011 at 3:32 PM, Andy Parkins <andyparkins@gmail.com> wrote=
:
> People get itches and they want to scratch them. =A0They aren't paid, so =
they
> don't necessarilly want to turn up and be told which part they _should_ b=
e
> working on. =A0The choice is not "bug fix that Gavin wants" or "new featu=
re
> that New Developer wants", it is "New Feature" or nothing.

This is true -- though there is value to having a list of "things we
think people should focus on" for the motivated, and for new people
interested in tackling a project, but not sure what project to tackle.

>> there would be less pressure to help with the boring bug-fixing and
>> testing of the bug-fix branch, which I think would be bad.
>
> That pressure might be relieved if the community were able to grow a bit,
> and people felt they had a personal investment. =A0That means loosening t=
he
> reigns a bit; and perhaps a development branch would be the way to do tha=
t
> while not compromising code quality.

A centrally managed development branch on bitcoin/bitcoin.git is not
the way to do it, however.  See the description of linux-next, in my
previous email, for a more distributed method which can easily be
layered on top of the existing bitcoin dev structure by any motivated
volunteer(s).

Think distributed.  :)  The community does not need Linus's help
(linux-next) or Gavin's help (bitcoin-next) to do this.  linux-next
became so widely used and useful that Linus requires almost all
changes to be first staged in linux-next.

--=20
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com