--- /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 503664196F0\r
+ for <notmuch@notmuchmail.org>; Mon, 3 May 2010 12:06: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 wLRl0GD8Nn0Z; Mon, 3 May 2010 12:06:05 -0700 (PDT)\r
+Received: from yoom.home.cworth.org (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 5A951431FC1;\r
+ Mon, 3 May 2010 12:06:05 -0700 (PDT)\r
+Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
+ id 15216568DED; Mon, 3 May 2010 12:06:05 -0700 (PDT)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: Jameson Rollins <jrollins@finestructure.net>,\r
+ David Bremner <bremner@unb.ca>, Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: bug tracking\r
+In-Reply-To: <87wrvrzqca.fsf@servo.finestructure.net>\r
+References: <87d3xr8p6m.fsf@servo.finestructure.net>\r
+ <87wrvz2xt5.fsf@convex-new.cs.unb.ca>\r
+ <87sk6icbh2.fsf@yoom.home.cworth.org>\r
+ <87wrvrzqca.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.3-7-g2baa576 (http://notmuchmail.org) Emacs/23.1.1\r
+ (i486-pc-linux-gnu)\r
+Date: Mon, 03 May 2010 12:06:04 -0700\r
+Message-ID: <87ocgwkdpf.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, 03 May 2010 19:06:06 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Wed, 28 Apr 2010 08:58:13 -0400, Jameson Rollins <jrollins@finestructure=\r
+.net> wrote:\r
+> Issues are raised on the mailing list, because there's no where else to\r
+> raise them (other than irc, where they're not actually logged). But\r
+> there's currently no way to track issues. We can't tell if they've been\r
+> dealt with, and we have no way of browsing through them. Folks who send\r
+> issues to the list have no feedback that their issue has even been\r
+> acknowledged.\r
+\r
+Right. I agree with all of these points.\r
+\r
+I wasn't trying to claim that what we are currently doing is sufficient.\r
+\r
+What I was trying to say is that our new "bug tracking system"\r
+(which I agree that we do need) would ideally involve as little change\r
+to my workflow as possible.\r
+\r
+Here's a rough sketch along the lines of something that I would like:\r
+\r
+ 1. Particular messages could be tagged as indicating a bug.\r
+\r
+ I can do this for my own private use now, but we need better\r
+ visibility of that. Such as publication of "unresolved bugs" to a\r
+ web page.\r
+\r
+ 2. Users could indicate that an email they are sending indicates a\r
+ bug.\r
+\r
+ Perhaps an extra header would cause the mail to automatically\r
+ acquire a tag when I incorporated it.\r
+\r
+ 3. I could tag bug messages as "resolved" or "invalid" or whatever.\r
+\r
+ Again, as in (1) for this to be useful we need a new way for users\r
+ to get visibility to these tag manipulations. And I'd also like to\r
+ have some associations between git commits and bug resolution.\r
+\r
+It looks to me like the ability to share tags, (and then the ability to\r
+turn a notmuch search into a web page) would go a long way toward giving\r
+us a "bug tracker". Since we already want both of those features\r
+*anyway* I think we should definitely pursue this.\r
+\r
+In the meantime, if people want to explore existing bug trackers, I\r
+would be fine with adopting something sane.\r
+\r
+> Saying that issues sent to the list are usually followed by a "thanks,\r
+> pushed" implies that only issues that include patches are acknowledged.\r
+> While I certainly appreciate that this is a Free software project and\r
+> that users should be encouraged to contribute, I don't think it's wise\r
+> to imply that "only issues with patches will be acknowledged". I think\r
+> that all users should be encouraged to report issues, even those that\r
+> are not capable or currently able to supply patches.\r
+\r
+You're absolutely right. I wasn't trying to imply that. I just meant\r
+that I'm already following up via email on any reported issue. This\r
+could be "I've committed a fix for this bug" just as much as "I've\r
+committed your patch".\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
+>=20\r
+> I don't think I agree that that's the right question to ask. We're\r
+> currently not tracking issues at, particularly ones not accompanied by\r
+> patches, so I claim that we have to do something different. Doing\r
+> nothing at all leaves us with a continued problem.\r
+\r
+But I *am* tracking things. The only real problems are:\r
+\r
+ 1. People don't have visibility into my tracking efforts\r
+\r
+ 2. We can't collaborate on the tracking efforts.\r
+\r
+So I think the various tag-sharing prototypes being worked on right now\r
+are extremely interesting.\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
+iD8DBQFL3x6c6JDdNq8qSWgRAnlZAJ0fGQ0xZOgVL+JKhvpfUFPUjO07yACfc3pd\r
+Gy+psv1o8e4q98VQPOamZug=\r
+=+8ep\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
projects / notmuch-archives.git / commitdiff