unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>, David Bremner <bremner@unb.ca>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: bug tracking
Date: Wed, 28 Apr 2010 08:58:13 -0400	[thread overview]
Message-ID: <87wrvrzqca.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87sk6icbh2.fsf@yoom.home.cworth.org>

[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]

Hi, Carl.  Thanks for the reply on this issue.  Please permit me counter
with a couple points.

On Mon, 26 Apr 2010 11:31:05 -0700, Carl Worth <cworth@cworth.org> wrote:
> It seems to me that almost all issues of interest are already raised on
> this mailing list, and later followed up with a message from me, (along
> the lines of "thanks, this is pushed"). So I'd be happy with a system
> that relied on an email interface as well.

Issues are raised on the mailing list, because there's no where else to
raise them (other than irc, where they're not actually logged).  But
there's currently no way to track issues.  We can't tell if they've been
dealt with, and we have no way of browsing through them.  Folks who send
issues to the list have no feedback that their issue has even been
acknowledged.

Saying that issues sent to the list are usually followed by a "thanks,
pushed" implies that only issues that include patches are acknowledged.
While I certainly appreciate that this is a Free software project and
that users should be encouraged to contribute, I don't think it's wise
to imply that "only issues with patches will be acknowledged".  I think
that all users should be encouraged to report issues, even those that
are not capable or currently able to supply patches.

> What I don't want is something that would make me go push buttons in a
> web form in addition to the "git push" and sending of email that I'm
> already doing.

I agree that purely web-based solutions are crappy.  But many now
include email interfaces as well.  In any event, this is why I was
suggesting one of the new distributed issue trackers that can live
inside the repo of the source code and integrate well with our/your
current workflow.  I just haven't used any of them to be able to vouch
for them.

> My primary metric for adopting a new issue tracker is "how little extra
> work will I have to do to use this compared to what I'm already
> doing?". That's a lot more important to me than how the system stores
> its data.

I don't think I agree that that's the right question to ask.  We're
currently not tracking issues at, particularly ones not accompanied by
patches, so I claim that we have to do something different.  Doing
nothing at all leaves us with a continued problem.

Anyway, thanks for the discussion.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2010-04-28 12:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 15:47 bug tracking Jameson Rollins
2010-04-22 17:37 ` David Bremner
2010-04-26 18:31   ` Carl Worth
2010-04-26 18:42     ` Arvid Picciani
2010-04-28 12:58     ` Jameson Rollins [this message]
2010-04-28 14:34       ` David Bremner
2010-04-29 17:48         ` Servilio Afre Puentes
2010-04-29 20:01           ` Mark Anderson
2010-05-03 19:44             ` Jesse Rosenthal
2010-05-03 19:06       ` Carl Worth
2010-05-03 19:32         ` Jesse Rosenthal
2011-01-13 14:43           ` Thomas Schwinge
2011-01-13 20:49             ` Jesse Rosenthal
2011-01-14 11:46               ` Andreas Amann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrvrzqca.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=bremner@unb.ca \
    --cc=cworth@cworth.org \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).