Re: bug tracking

diff --git a/a3/278f96929cdd51b2ece7543d03d724b68595a8 b/a3/278f96929cdd51b2ece7543d03d724b68595a8
new file mode 100644 (file)
index 0000000..e4f286f
--- /dev/null
+++ b/a3/278f96929cdd51b2ece7543d03d724b68595a8
@@ -0,0 +1,110 @@
+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 4D7DE4196F0\r
+       for <notmuch@notmuchmail.org>; Mon, 26 Apr 2010 11:31:06 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.89\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5\r
+       tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01]\r
+       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 dLp2EeYPHs8s; Mon, 26 Apr 2010 11:31:05 -0700 (PDT)\r
+Received: from yoom.home.cworth.org (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 6E37D431FC1;\r
+       Mon, 26 Apr 2010 11:31:05 -0700 (PDT)\r
+Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
+       id 274ED568DEC; Mon, 26 Apr 2010 11:31:05 -0700 (PDT)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: David Bremner <bremner@unb.ca>,\r
+       Jameson Rollins <jrollins@finestructure.net>,\r
+       Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: bug tracking\r
+In-Reply-To: <87wrvz2xt5.fsf@convex-new.cs.unb.ca>\r
+References: <87d3xr8p6m.fsf@servo.finestructure.net>\r
+       <87wrvz2xt5.fsf@convex-new.cs.unb.ca>\r
+User-Agent: Notmuch/0.2-202-g01ec4d3 (http://notmuchmail.org) Emacs/23.1.1\r
+       (i486-pc-linux-gnu)\r
+Date: Mon, 26 Apr 2010 11:31:05 -0700\r
+Message-ID: <87sk6icbh2.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
+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: Mon, 26 Apr 2010 18:31:06 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Thu, 22 Apr 2010 14:37:26 -0300, David Bremner <bremner@unb.ca> wrote:\r
+> It was thinking along these lines that got me to make the following list\r
+>=20\r
+>  http://www.cs.unb.ca/~bremner/blog/posts/git-issue-trackers/\r
+\r
+I'm not sure what it is you think of as a "git-based issue tracker". Or\r
+rather, I'm not sure if we have the same ideas about what would make a\r
+git-based issue tracker interesting.\r
+\r
+> If people think the general concept of a distributed bug tracker is\r
+> worthwhile, I'm willing to investigate a more.  Feel free to cc\r
+\r
+For me, having an issue tracker be git-based might help with what really\r
+matters, but wouldn't necessarily.\r
+\r
+One realization is that since we have distributed code, we necessarily\r
+have distributed bug state. (The bugs that exist in my repository are\r
+distinct from the bugs that exist in your repository.) So if bug state\r
+can follow the way code moves, then that is interesting.\r
+\r
+For example, if dme commits a fix and marks "issue #217 closed" with\r
+that fix, then I'd like my repository of bugs to also know to close that\r
+issue when I later merge his fix.\r
+\r
+To me, that's really a user-interface issue, more than a storage\r
+issue. I don't care if the issue tracker stores its state in a git\r
+database. But I do care that it be able to watch what we are already\r
+doing, (creating git commits and sharing them), in order for us to\r
+easily track state.\r
+\r
+It seems to me that almost all issues of interest are already raised on\r
+this mailing list, and later followed up with a message from me, (along\r
+the lines of "thanks, this is pushed"). So I'd be happy with a system\r
+that relied on an email interface as well.\r
+\r
+What I don't want is something that would make me go push buttons in a\r
+web form in addition to the "git push" and sending of email that I'm\r
+already doing.\r
+\r
+My primary metric for adopting a new issue tracker is "how little extra\r
+work will I have to do to use this compared to what I'm already\r
+doing?". That's a lot more important to me than how the system stores\r
+its data.\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
+iD8DBQFL1dvp6JDdNq8qSWgRAmRfAJ9fKbiHW3Xjz38vVIdqr/yQZ7DvcACgj+Xy\r
+xKYh9x+GbkonSH4oZSGTKHQ=\r
+=5Wng\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r