Mailing list w/ gatekeeper(s)

["Eric S. Raymond" <esr@thyrsus.com>]

From: Richard Stallman <rms@gnu.org>
> Subject: Re: What a modern collaboration toolkit looks like
> To: Gregory Collins <greg@maptuit.com>
> Cc: emacs-devel@gnu.org
> Message-ID: <E1JCJmu-0003ks-TE@fencepost.gnu.org>
> Content-Type: text/plain; charset=ISO-8859-15
> 
>     3. Mailing list w/ gatekeeper(s)
>     ---------------------------------
>     This is how mercurial manages its own development. Proposed changes are
>     sent in patch form to a mailing list, which is dedicated to the
>     discussion and review of such patches. The central repository is
>     read-only except for a small set of integrators. When a change has been
>     reviewed + tested, an integration crew member pulls the patch from email
>     into the central tree.
> 
>     This is the approach I'd suggest for emacs (and it's the one we
>     instituted for the project I maintain at my workplace). The main
>     advantages:
> 
> I would be willing to try it, or a compromise between this and #1,
> which would mean a larger number of people who can commit directly
> to the main repository.

I agree with the "compromise between this and #1".  That is what
I would recommend.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>