--- /dev/null
+Return-Path: <cworth@cworth.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 961A0431FBD\r
+ for <notmuch@notmuchmail.org>; Wed, 3 Feb 2010 19:05:51 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.864\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.864 tagged_above=-999 required=5\r
+ tests=[ALL_TRUSTED=-1.8, AWL=-0.065, BAYES_50=0.001] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id lMGzpNF3Y3GP; Wed, 3 Feb 2010 19:05:50 -0800 (PST)\r
+Received: from yoom.home.cworth.org (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 72806431FAE;\r
+ Wed, 3 Feb 2010 19:05:50 -0800 (PST)\r
+Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
+ id 26629254181; Thu, 4 Feb 2010 16:05:50 +1300 (NZDT)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: martin f krafft <madduck@madduck.net>, notmuch@notmuchmail.org\r
+In-Reply-To: <20100125213231.GB15987@lapse.rw.madduck.net>\r
+References: <87my083mgh.fsf@SSpaeth.de> <87d4148s2c.fsf@lillypad.riseup.net>\r
+ <4B595D3A.1030901@SSpaeth.de> <87636u34lw.fsf@SSpaeth.de>\r
+ <87d411zvz8.fsf@yoom.home.cworth.org>\r
+ <20100125213231.GB15987@lapse.rw.madduck.net>\r
+Date: Wed, 03 Feb 2010 19:05:42 -0800\r
+Message-ID: <87ock5punt.fsf@yoom.home.cworth.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha1; protocol="application/pgp-signature"\r
+Subject: Re: [notmuch] Git feature branch\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 04 Feb 2010 03:05:51 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Tue, 26 Jan 2010 10:32:31 +1300, martin f krafft <madduck@madduck.net> w=\r
+rote:\r
+> I discussed this with Carl at LCA a bit and ideally we should come\r
+> up with a way to relieve Carl of the bottleneck burden (obviously\r
+> without stealing away his dictator hat ;)\r
+\r
+Sounds great! Let's keep working together and find ways to help our\r
+community work together. And I really appreciate all the help!\r
+\r
+> I think it would make sense to move the mainline to git.debian.org\r
+> for now, or another place where everyone can easily get an account.\r
+> As alternatives I propose repo.or.cz. I'd prefer to stay away from\r
+> commercial services like Github.\r
+\r
+I'm glad to help make things work on notmuchmail.org directly. I don't\r
+have a problem giving out shell access to people who want to help set\r
+things up the way we want. (And prototyping things elsewhere is fine\r
+too.)\r
+\r
+> Once we're there, how about copying the branch structure from\r
+> Git development[0]:\r
+>=20\r
+> maint/ =E2=80=94 the stable release\r
+> master/ =E2=80=94 the stablising head\r
+> next/ =E2=80=94 testing branch\r
+> pu/ =E2=80=94 patch integration branch (proposed updates)\r
+\r
+I'm not a fan of this scheme, (or maybe I've just never quite understood\r
+it).\r
+\r
+When I first encountered this scheme, (when first using git), it was\r
+never clear to me what branch I should actually run or test as a\r
+user. Nor was it obvious which branches would be regularly rebased or\r
+not---nor which branches had features being discussed on the mailing\r
+list.\r
+\r
+Here are some of my thoughts:\r
+\r
+Instead of "maint" I'd much rather just have branches that are named\r
+directly after the stable releases being maintained. We've done this\r
+with the cairo repository with branch names like "1.2", "1.4", "1.6",\r
+etc. That way it's very clear what the branch represents and it's\r
+possible to have multiple concurrent "live" maintenance branches. But of\r
+course, until we actually have releases, this doesn't really matter. :-)\r
+\r
+I want to maintain a branch myself, (where I'm the only person pushing\r
+to the branch). [This is different than what I've done with the cairo\r
+repository where we have all core maintainer's pushing to a central\r
+repository. I'm intentionally trying something new here.]\r
+\r
+Obviously, that branch that I maintain is currently called "master", but\r
+I wouldn't mind (and might actually prefer) to have it be called\r
+"~cworth" or so. Though we have the problem that we need "master" to\r
+point to *something*.\r
+\r
+Beyond that, I'm quite happy to have any number of branches similarly\r
+maintained by any other individuals. I want to get things setup so that\r
+those will be hosted and listed alongside my branch on\r
+notmuchmail.org. And I'll be happy to accept pull requests from\r
+people. I expect to find people naturally gravitating to "ownership" or\r
+particular portions of the code, where I will gain a lot of trust for\r
+particular maintainers over the code they own.\r
+\r
+> What patch tracking workflow should we adopt? Keep sending patches\r
+> to the mailing list\r
+\r
+I definitely like the patches on the list. I find that with notmuch, I\r
+can maintain a queue of outstanding patches very effectively, (meaning,\r
+that the queue is usable and doesn't forget even if I do get very far\r
+behind like I am currently).\r
+\r
+> master or pu (or even maint/next), as appropriate? Use the Debian\r
+> bug tracker? Use Sebastian's Roundup instance? Set up a patch queue\r
+> manager on notmuchmail.org? Use patchwork [1]?\r
+\r
+I'm personally not interested in any system that requires me to push any\r
+additional buttons outside of notmuch and git itself. I am interested in\r
+tools that can generate reports and help provide visibility into\r
+things. So patchwork fixed to automatically notice when patches are\r
+merged would be interesting. Also interesting would be support for\r
+publishing my notmuch-based queue of patches to a web page.\r
+\r
+=2DCarl\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iD8DBQFLajmH6JDdNq8qSWgRAiidAJ4jY7ZpsNbySAMM+6tFj6u/Som2BACgg5CN\r
+QRhMik8h8NIBQS51+Wq5slI=\r
+=cthl\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
projects / notmuch-archives.git / commitdiff