1 Return-Path: <cworth@cworth.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 503664196F0
\r
6 for <notmuch@notmuchmail.org>; Mon, 3 May 2010 12:06:06 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5
\r
12 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01]
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id wLRl0GD8Nn0Z; Mon, 3 May 2010 12:06:05 -0700 (PDT)
\r
17 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 5A951431FC1;
\r
19 Mon, 3 May 2010 12:06:05 -0700 (PDT)
\r
20 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
21 id 15216568DED; Mon, 3 May 2010 12:06:05 -0700 (PDT)
\r
22 From: Carl Worth <cworth@cworth.org>
\r
23 To: Jameson Rollins <jrollins@finestructure.net>,
\r
24 David Bremner <bremner@unb.ca>, Notmuch Mail <notmuch@notmuchmail.org>
\r
25 Subject: Re: bug tracking
\r
26 In-Reply-To: <87wrvrzqca.fsf@servo.finestructure.net>
\r
27 References: <87d3xr8p6m.fsf@servo.finestructure.net>
\r
28 <87wrvz2xt5.fsf@convex-new.cs.unb.ca>
\r
29 <87sk6icbh2.fsf@yoom.home.cworth.org>
\r
30 <87wrvrzqca.fsf@servo.finestructure.net>
\r
31 User-Agent: Notmuch/0.3-7-g2baa576 (http://notmuchmail.org) Emacs/23.1.1
\r
33 Date: Mon, 03 May 2010 12:06:04 -0700
\r
34 Message-ID: <87ocgwkdpf.fsf@yoom.home.cworth.org>
\r
36 Content-Type: multipart/signed; boundary="=-=-=";
\r
37 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
38 X-BeenThere: notmuch@notmuchmail.org
\r
39 X-Mailman-Version: 2.1.13
\r
41 List-Id: "Use and development of the notmuch mail system."
\r
42 <notmuch.notmuchmail.org>
\r
43 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
44 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
45 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
46 List-Post: <mailto:notmuch@notmuchmail.org>
\r
47 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
48 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
50 X-List-Received-Date: Mon, 03 May 2010 19:06:06 -0000
\r
53 Content-Transfer-Encoding: quoted-printable
\r
55 On Wed, 28 Apr 2010 08:58:13 -0400, Jameson Rollins <jrollins@finestructure=
\r
57 > Issues are raised on the mailing list, because there's no where else to
\r
58 > raise them (other than irc, where they're not actually logged). But
\r
59 > there's currently no way to track issues. We can't tell if they've been
\r
60 > dealt with, and we have no way of browsing through them. Folks who send
\r
61 > issues to the list have no feedback that their issue has even been
\r
64 Right. I agree with all of these points.
\r
66 I wasn't trying to claim that what we are currently doing is sufficient.
\r
68 What I was trying to say is that our new "bug tracking system"
\r
69 (which I agree that we do need) would ideally involve as little change
\r
70 to my workflow as possible.
\r
72 Here's a rough sketch along the lines of something that I would like:
\r
74 1. Particular messages could be tagged as indicating a bug.
\r
76 I can do this for my own private use now, but we need better
\r
77 visibility of that. Such as publication of "unresolved bugs" to a
\r
80 2. Users could indicate that an email they are sending indicates a
\r
83 Perhaps an extra header would cause the mail to automatically
\r
84 acquire a tag when I incorporated it.
\r
86 3. I could tag bug messages as "resolved" or "invalid" or whatever.
\r
88 Again, as in (1) for this to be useful we need a new way for users
\r
89 to get visibility to these tag manipulations. And I'd also like to
\r
90 have some associations between git commits and bug resolution.
\r
92 It looks to me like the ability to share tags, (and then the ability to
\r
93 turn a notmuch search into a web page) would go a long way toward giving
\r
94 us a "bug tracker". Since we already want both of those features
\r
95 *anyway* I think we should definitely pursue this.
\r
97 In the meantime, if people want to explore existing bug trackers, I
\r
98 would be fine with adopting something sane.
\r
100 > Saying that issues sent to the list are usually followed by a "thanks,
\r
101 > pushed" implies that only issues that include patches are acknowledged.
\r
102 > While I certainly appreciate that this is a Free software project and
\r
103 > that users should be encouraged to contribute, I don't think it's wise
\r
104 > to imply that "only issues with patches will be acknowledged". I think
\r
105 > that all users should be encouraged to report issues, even those that
\r
106 > are not capable or currently able to supply patches.
\r
108 You're absolutely right. I wasn't trying to imply that. I just meant
\r
109 that I'm already following up via email on any reported issue. This
\r
110 could be "I've committed a fix for this bug" just as much as "I've
\r
111 committed your patch".
\r
113 > > My primary metric for adopting a new issue tracker is "how little extra
\r
114 > > work will I have to do to use this compared to what I'm already
\r
115 > > doing?". That's a lot more important to me than how the system stores
\r
118 > I don't think I agree that that's the right question to ask. We're
\r
119 > currently not tracking issues at, particularly ones not accompanied by
\r
120 > patches, so I claim that we have to do something different. Doing
\r
121 > nothing at all leaves us with a continued problem.
\r
123 But I *am* tracking things. The only real problems are:
\r
125 1. People don't have visibility into my tracking efforts
\r
127 2. We can't collaborate on the tracking efforts.
\r
129 So I think the various tag-sharing prototypes being worked on right now
\r
130 are extremely interesting.
\r
135 Content-Type: application/pgp-signature
\r
137 -----BEGIN PGP SIGNATURE-----
\r
138 Version: GnuPG v1.4.10 (GNU/Linux)
\r
140 iD8DBQFL3x6c6JDdNq8qSWgRAnlZAJ0fGQ0xZOgVL+JKhvpfUFPUjO07yACfc3pd
\r
141 Gy+psv1o8e4q98VQPOamZug=
\r
143 -----END PGP SIGNATURE-----
\r
projects / notmuch-archives.git / blob