DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=DFOeo4u9PW7N/U4sRq/fFs7OLD5bYDXYe4RKcn0Pb1IBqyye5pgCb6H/sIMmzSPlbJ
	ZsmaK4KqSMzJG+QBCxciWGAG1Hp5XdyD1sOprVcraeF46L4fve7fb8ZtUZdbNyWTDZzm
	03jDYPQP7zQSXS2NpxV49Ii3m7Ajb7dHpCj0k=
MIME-Version: 1.0
Date: Mon, 11 Oct 2010 21:45:47 +0300
Message-ID: <AANLkTimes1ndLhOxJupDh72h1MRR0q28wu7mjAeCOzVu@mail.gmail.com>
Subject: notmuch-next branch
From: Felipe Contreras <felipe.contreras@gmail.com>
To: notmuch@notmuchmail.org
Content-Type: text/plain; charset=UTF-8
Precedence: list

Hi,

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.

Also, we need to agree which patches to start with and how. One
proposal would be to propose and vote here, another would be to resend
them and wait for signed-off-by's.

What do you think?

-- 
Felipe Contreras