public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: Move tasks to bugzilla
Date: Mon, 18 Feb 2013 16:19:00 -0000	[thread overview]
Message-ID: <87bobhd27o.fsf@fleche.redhat.com> (raw)

I'd like to propose changing how we manage our task list.

Rather than have it on the wiki, I think we should file each task as a
bug in bugzilla.  We would add an "archer" tag to each task.

Then, we could replace the current list on the wiki with a bugzilla
query.

I think this would be somewhat better since it would give us a way to
track who is working on which archer task; and also let us more easily
"accept" existing bugs into archer (by just adding the tag).  This would
also give us a built-in spot to discuss any particulars of a given task,
and a simple way to indicate task dependencies (and even priorities if
we care).

Some of our tasks are a bit vague for a PR; but the vague ones aren't
really tasks so much as long-term goals or wishes.  Those could remain
on the wiki.

Any comments?

Tom

                 reply	other threads:[~2013-02-18 16:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87bobhd27o.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).