unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: David Bremner <bremner@unb.ca>,
	Jameson Rollins <jrollins@finestructure.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: bug tracking
Date: Mon, 26 Apr 2010 11:31:05 -0700	[thread overview]
Message-ID: <87sk6icbh2.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87wrvz2xt5.fsf@convex-new.cs.unb.ca>

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

On Thu, 22 Apr 2010 14:37:26 -0300, David Bremner <bremner@unb.ca> wrote:
> It was thinking along these lines that got me to make the following list
> 
>  http://www.cs.unb.ca/~bremner/blog/posts/git-issue-trackers/

I'm not sure what it is you think of as a "git-based issue tracker". Or
rather, I'm not sure if we have the same ideas about what would make a
git-based issue tracker interesting.

> If people think the general concept of a distributed bug tracker is
> worthwhile, I'm willing to investigate a more.  Feel free to cc

For me, having an issue tracker be git-based might help with what really
matters, but wouldn't necessarily.

One realization is that since we have distributed code, we necessarily
have distributed bug state. (The bugs that exist in my repository are
distinct from the bugs that exist in your repository.) So if bug state
can follow the way code moves, then that is interesting.

For example, if dme commits a fix and marks "issue #217 closed" with
that fix, then I'd like my repository of bugs to also know to close that
issue when I later merge his fix.

To me, that's really a user-interface issue, more than a storage
issue. I don't care if the issue tracker stores its state in a git
database. But I do care that it be able to watch what we are already
doing, (creating git commits and sharing them), in order for us to
easily track state.

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.

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.

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.

-Carl

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

  reply	other threads:[~2010-04-26 18:31 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 [this message]
2010-04-26 18:42     ` Arvid Picciani
2010-04-28 12:58     ` Jameson Rollins
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=87sk6icbh2.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=bremner@unb.ca \
    --cc=jrollins@finestructure.net \
    --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).