From: Amit Kucheria <amit.kucheria@verdurent.com>
To: Jameson Rollins <jrollins@finestructure.net>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch-next branch
Date: Mon, 11 Oct 2010 22:40:52 +0300 [thread overview]
Message-ID: <AANLkTimNeN_2xJWTvKrR+AhKsyj46Ti75bjaVLx8-hrf@mail.gmail.com> (raw)
In-Reply-To: <87pqvgr1u5.fsf@servo.finestructure.net>
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@gmail.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. The
> 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. As 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
next prev parent reply other threads:[~2010-10-11 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 18:45 notmuch-next branch Felipe Contreras
2010-10-11 18:53 ` Servilio Afre Puentes
2010-10-11 18:55 ` Kristoffer Ström
2010-10-11 19:01 ` Jameson Rollins
2010-10-11 19:11 ` Servilio Afre Puentes
2010-10-11 19:40 ` Amit Kucheria [this message]
2010-10-11 20:00 ` Jameson Rollins
2010-10-11 20:10 ` Jed Brown
2010-10-11 21:32 ` Jesse Rosenthal
2010-10-12 10:46 ` Sebastian Spaeth
2010-10-11 21:17 ` Felipe Contreras
2010-10-12 23:19 ` Carl Worth
2010-10-13 1:02 ` David Bremner
2010-10-13 7:35 ` Sebastian Spaeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimNeN_2xJWTvKrR+AhKsyj46Ti75bjaVLx8-hrf@mail.gmail.com \
--to=amit.kucheria@verdurent.com \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).