MIME-Version: 1.0
In-Reply-To: <87pqvgr1u5.fsf@servo.finestructure.net>
References: <AANLkTimes1ndLhOxJupDh72h1MRR0q28wu7mjAeCOzVu@mail.gmail.com>
	<87pqvgr1u5.fsf@servo.finestructure.net>
Date: Mon, 11 Oct 2010 22:40:52 +0300
Message-ID: <AANLkTimNeN_2xJWTvKrR+AhKsyj46Ti75bjaVLx8-hrf@mail.gmail.com>
Subject: Re: notmuch-next branch
From: Amit Kucheria <amit.kucheria@verdurent.com>
To: Jameson Rollins <jrollins@finestructure.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: notmuch@notmuchmail.org
Precedence: list

On Mon, Oct 11, 2010 at 10:01 PM, Jameson Rollins
<jrollins@finestructure.net> wrote:
> On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras <felipe.contreras@gm=
ail.com> wrote:
>> I think many people agree notmuch mainline has been rather slow. So
>> I'm proposing to have notmuch-next branch, either on github or
>> gitorious (please vote).
>>
>> More than one person should have write access to this repo, but some
>> guidelines should be in place. I propose that patches should be
>> signed-off-by at least another person in the mailing list before
>> pushing. It would be nice if this is how the mainline branch works,
>> but we don't need to wait for that to happen. We need to vote on who
>> are the people to have write access.
>
> I think this generally sounds like a fine idea, but I don't see why we
> need a single central repo that multiple people need access to. =A0The
> whole point of git is to allow for distributed development without need
> for a central repo.

While distributed development is good, it would be nice for users to
be able to clone one git repo instead of tracking 5 different trees.
And more users typically means more robust software.

It would also make it easier to merge patches back into notmuch-master
if it ever takes off again.

> In this case, folks can just merge the patches they're interested in
> into a "next" branch in their own personal repos, publish them where
> ever they want, and then every body can just keep their "next" branches
> synced with each other. =A0As consensus is reached, the next release will
> emerge.

Everyone can still maintain their own trees. Patches can go into the
'-next' repo only after being ack'ed by 1-2 active developers on the
mailing list. Meanwhile they bake in personal trees.

/Amit