From: maximilian attems <janitor@sternwelten.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] bugzilla instead of TODO?
Date: Tue, 06 Jul 2004 12:33:03 +0000 [thread overview]
Message-ID: <20040706123303.GF1639@sputnik.stro.at> (raw)
In-Reply-To: <200407051644.i65GioRE022762@p-chan.krl.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
hello,
On Mon, 05 Jul 2004, Don Koch wrote:
> Is there any reason not to use bugzilla in place of a todo list?
> It would, at least:
> 1. make it easier to find out who, if anyone, is working on a todo item,
> 2. make it easier to assign oneself to an item,
> 3. make it easier to add items and
> 4. make it easier for the "powers that be" to prioritize items.
>
> These are, after all, bugs. Not necessarily show-stoppers, but bugs
> nonetheless. I was thinking of a separate, k-j bugzilla and not use
> the existing bugzilla.kernel.org copy if you want to keep things
> separate.
>
hmm there was a kj wiki for more than a year,
but the usage was _quite_ moderate..
(Randy may tell more, he did all the updates there).
a bugzilla is even more managment overhead,
don't think it will just fly.
the bonus of the TODO file is the quick
overview: it's really easy to pick up a new task.
thanks to that kj gets more easily new contributors.
the cvs todo file is quite easy to update,
just check it out and send a diff to the
list and it get updated. (we've seen nice
updates the last month :)
use of bugzilla.kernel.org is encouraged,
there are very active bug owner there.
why duplicate that effort?
a++ maks
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-07-06 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 16:44 [Kernel-janitors] bugzilla instead of TODO? Don Koch
2004-07-06 12:33 ` maximilian attems [this message]
2004-07-07 12:34 ` maximilian attems
2004-07-07 13:11 ` Anupam Kapoor
2004-07-07 15:19 ` Randy.Dunlap
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=20040706123303.GF1639@sputnik.stro.at \
--to=janitor@sternwelten.at \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.