On Mon, 25 Jan 2010 16:46:43 -0800, sebastian at 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 ? 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100127/297ea735/attachment.pgp>