public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <grant@g2.ces.clemson.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] bug/issue tracker requirements
Date: Wed, 28 Nov 2001 15:43:04 -0500	[thread overview]
Message-ID: <20011128154304.A19215@g2.ces.clemson.edu> (raw)
In-Reply-To: <20011128202031.DCA3E159C4@chiba.3jane.net>

I'm absolutely the wrong person to put this topic together, but
I'll give it a stab anyway.

User requirements:
  1. Simple to add a bug, an ebuild or a patch, or a feature request.
  2. Current bugs/whatever easily displayed, preferably by priority
  3. Search system for bugs/whatever
  4. Responses, whether by developers or other users, nicely threaded.

My own opinion is that being able to easily scan the current bugs/to-dos
is very important, which is why I put (2) above (3).  I'm reasonably 
agnostic over whether the submission interface should be via web,
e-mail, or both.  I like the way that roundup keeps a list of everybody
who has commented on a particular bug/to-do and sends an e-mail to 
everybody on that list whenever a bug/to-do is updated.  I assume the
other bug trackers do something similar.

Dev requirements:
  1. All of the above user requirements.  Hey, we'll use it most!
  2. Ability to own a bug/to-do, set the priority, label it complete, etc.
  3. Probably lots of other things that I can't think of right now.

Now if somebody who actually uses one of these things would take up this
thread. . ..

-g2boojum-
-- 
___________________________________________________________________
|     Grant Goodyear                  |  The Secrets of Physics:   |
|     Dept. of Chemistry - Clemson U  |1. Add zero.                |
|     Clemson, SC  29634              |2. Multiply by one.         |
|-------------------------------------|3. Expand in a Taylor series|
|e-mail: goodyea@clemson.edu          |4. Integrate by parts.      |
|www:bernacchi.chem.uh.edu/~grant     |5. Fourier transform.       |
|                                     |6. Add auxiliary variables  |
|_____________________________________|____________________________|
 


      reply	other threads:[~2001-11-28 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 20:16 [gentoo-dev] drobbins puts the kibosh on bugtracker talk Daniel Robbins
2001-11-28 20:20 ` Damon M. Conway
2001-11-28 20:43   ` Grant Goodyear [this message]

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

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

  git send-email \
    --in-reply-to=20011128154304.A19215@g2.ces.clemson.edu \
    --to=grant@g2.ces.clemson.edu \
    --cc=gentoo-dev@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox