From: micah anderson <micah@riseup.net>
To: sebastian@sspaeth.de, notmuch@notmuchmail.org
In-Reply-To: <960df8f6a8a08f2ca3aceef5a216d691.squirrel@webmail.sspaeth.de>
References: <87my083mgh.fsf@SSpaeth.de> <87d4148s2c.fsf@lillypad.riseup.net>
	<4B595D3A.1030901@SSpaeth.de> <87636u34lw.fsf@SSpaeth.de>
	<87d411zvz8.fsf@yoom.home.cworth.org>
	<20100125213231.GB15987@lapse.rw.madduck.net>
	<960df8f6a8a08f2ca3aceef5a216d691.squirrel@webmail.sspaeth.de>
Date: Wed, 27 Jan 2010 11:24:15 +1300
Message-ID: <87wrz4fqsw.fsf@lillypad.riseup.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha512; protocol="application/pgp-signature"
Subject: Re: [notmuch] Git feature branch
Precedence: list

--=-=-=

On Mon, 25 Jan 2010 16:46:43 -0800, sebastian@sspaeth.de wrote:
> > I think it would make sense to move the mainline to git.debian.org
> > for now, or another place where everyone can easily get an account.
> > As alternatives I propose repo.or.cz. I'd prefer to stay away from
> > commercial services like Github.

I too prefer to stay away from commercial,non-free services like GitHub.
Gitorious (http://www.gitorious.org/) is a great service, similar to
Github, but with added freedom.

Currently the git repository is at git://notmuchmail.org/git/notmuch
which seems like a fine location for it, but perhaps I missed the
motivation for switching to a centralized repository with the added
overhead of giving people access to commit?

Couldn't all of this be done without moving the existing git repository
(don't forget that transition is a cost)? Those who wish to put together
these proposed branches go ahead and do so, publishing those wherever
they like (git.debian.org, gitorious, their own hosted git repositories,
or even github) and then Carl can just add those as remotes as he sees
fit.

> > What patch tracking workflow should we adopt? Keep sending patches
> > to the mailing list and have a few people who integrate them into
> > master or pu (or even maint/next), as appropriate? Use the Debian
> > bug tracker? Use Sebastian's Roundup instance? Set up a patch queue
> > manager on notmuchmail.org? Use patchwork [1]?

Personally, I've found mailing lists that have patches sent to them
tends to totally kill the list for anything else. It seems a bit weird
to use Debian's bug tracker for a non-Debian native program (but using
it for the Debian package of notmuch does make sense). I am not so
familiar with Roundup, patch queue trackers or patchwork to have
anything to say about those.

micah

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCgAGBQJLX2uQAAoJEIy/mjIoYaeQu50P/22TEB8ovPSvCQSEllIUxHFA
uMYz0Pwd0Il8xtKhxo7exHhhcoYyCgFmIp/m/PUChgAtRAQ0kzWyiLXcO8mlge6n
MrhKhaOnyVo8Jsos0Lm0VSRC6IDlge1H47dcvRj86lBaRdThagnxjGLy0iOBqGbf
4QgiRjoijzMsXUMSAV0byD/XW7lS4wW3vu9pLx/IVkNWM0sCS6/xE35D8F1WInr0
Ol5Io6pV3GsBuxERJoSujgJ3H8+6OjX4I0TB2lRNaPuRCuKK2/Vr3RzP8upwxoes
NB7FqtXNk/owN/RaTFUYCV3Jk+Lrgp3ny8sVbXDBoviWIDHpThg5wnVN91BMIJRX
HnDR2ib4fakCAtxI60G6wwJVtRbCLd0gI/yoC7nhog9Y82jAqBye8eeO63mvPQeJ
SplClJXh57H1GXJqtz2Nvtv5nAQFcdIvb+hTDSoyMeRMa0Mv57bRW6S3Gwmmrygx
SWFGdb1pFugXWspuJd/Q1JKba49545Sg3Wsofz9gL6xNZ99Tf6G76sTKAKRF/F4D
XCy1ESUGTyBTkSrRxHAKlD0d3vOy6r26T+4LITkTBOGuZnGq3CzP9ynt3xMW+0H3
HNyIQqKGWbCxwwNq5D7zR3lEf+aCGulVhuRgyZxlBgr15hoY14onMlO8uBqfLSSo
qlYxj4c2W81ZPu1iXMYE
=x9yZ
-----END PGP SIGNATURE-----
--=-=-=--