Re: Patches, Developers and Training

diff --git a/1f/c4eb2df7a181fc53c94434a5566f1f948fcef7 b/1f/c4eb2df7a181fc53c94434a5566f1f948fcef7
new file mode 100644 (file)
index 0000000..fac5081
--- /dev/null
+++ b/1f/c4eb2df7a181fc53c94434a5566f1f948fcef7
@@ -0,0 +1,89 @@
+Return-Path: <bremner@unb.ca>\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 DAE8E429E25\r
+       for <notmuch@notmuchmail.org>; Wed, 14 Sep 2011 03:34:20 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\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 SFb+ipjpHFC4 for <notmuch@notmuchmail.org>;\r
+       Wed, 14 Sep 2011 03:34:19 -0700 (PDT)\r
+Received: from tempo.its.unb.ca (tempo.its.unb.ca [131.202.1.21])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id F1EB9431FB6\r
+       for <notmuch@notmuchmail.org>; Wed, 14 Sep 2011 03:34:18 -0700 (PDT)\r
+Received: from zancas.localnet\r
+       (fctnnbsc36w-156034073093.pppoe-dynamic.High-Speed.nb.bellaliant.net\r
+       [156.34.73.93]) (authenticated bits=0)\r
+       by tempo.its.unb.ca (8.13.8/8.13.8) with ESMTP id p8EAYCC3020624\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO);\r
+       Wed, 14 Sep 2011 07:34:13 -0300\r
+Received: from bremner by zancas.localnet with local (Exim 4.76)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1R3mnE-0001EY-G7; Wed, 14 Sep 2011 07:34:12 -0300\r
+From: David Bremner <david@tethera.net>\r
+To: Martin Owens <doctormo@gmail.com>,\r
+       Notmuch developer list <notmuch@notmuchmail.org>\r
+Subject: Re: Patches, Developers and Training\r
+In-Reply-To: <1315968415.2201.8.camel@delen>\r
+References: <1315968415.2201.8.camel@delen>\r
+User-Agent: Notmuch/0.8 (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Wed, 14 Sep 2011 07:34:12 -0300\r
+Message-ID: <87obyno1jv.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\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: Wed, 14 Sep 2011 10:34:21 -0000\r
+\r
+On Tue, 13 Sep 2011 22:46:55 -0400, Martin Owens <doctormo@gmail.com> wrote:\r
+> \r
+> I'm not sure what the exact process is, but I imagine you're using some\r
+> kind of tool similar to launchpad's merge request functionality that\r
+> allows you to see branches for merging (or in this case patches).\r
+> \r
+\r
+We're not really using any system, which is part of the problem, but to\r
+be honest probably only a small part of the problem. The real underlying\r
+problem is that Carl has able to devote notmuch time to notmuch lately,\r
+and we have not adapted to that.\r
+\r
+The good news is that some technical solution might help a little.  If\r
+you were keen to work on a bug tracking system, that would be great in\r
+my view.  Currently I think most of the patch tracking state is\r
+contained in tags in Carl's mailbox.  If you start at\r
+id:"87boya98sf.fsf@gogo.home" you can find some discussion about tag\r
+sharing. I personally think this is the way forward, although I'm\r
+agnostic about the implementation details.  It occured to me that a\r
+simpler (?) system might to use git to merge a shared set of tags. Then\r
+issues of access control, merging, and reverting could be done with git.\r
+At least for me, that is quite comfortable.\r
+\r
+As for why not existing bug tracking system $X, I think from past\r
+discussions, we have agreed that having something that integrates well\r
+with notmuch is pretty much a requirement, at least for Carl. There is a\r
+patchwork instance limping along, but it seems to me to be roughly\r
+equivalent to "notmuch search subject:patch and notmuch"; i.e. we have\r
+that information already.\r
+\r
+David\r
+\r
+\r