All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status update for grub 2 developments?
Date: Mon, 18 Jun 2007 18:40:47 +0300	[thread overview]
Message-ID: <4676A77F.8030702@nic.fi> (raw)
In-Reply-To: <20070618133204.GA30651@aragorn>

Robert Millan wrote:
> On Mon, Jun 18, 2007 at 12:22:47PM +0200, adrian15 wrote:
>>> Ideas are welcome where to store this information are also welcome :).
>>> We would need to track requirements for features on component level.
>>> More automated the better.
>> Can we use the bugs system maybe?
>> A friend of mine uses trac ( http://trac.edgewall.org/ ) and he likes it 
>> a lot. I do not know if it fits our needs.
> 
> We have a bug system in Savannah, but it's occupied by GRUB Legacy.  I guess
> this is why we're not using it?

Bug tracker isn't exactly a tool I was looking for :). With tweaks and
meta bugs some task could be done with it. But I would prefer something
else that savannah's bug tracking facility.

Trac has a bit more features, though I am not familiar enough with it.

Joomla's tracker is a bit more what I was thinking about. It handles
tasks quite nicely. Has task dependency support. It can store files in
tasks so drafts being developed could be stored there. Later specs could
then be stored on Wiki or in doc storage. There is also some reporting
tools... Though they could be a bit better... perhaps anonymous users
just don't see them.

http://joomlacode.org/gf/project/joomla/tracker/



  reply	other threads:[~2007-06-18 15:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 12:47 status update for grub 2 developments? Vesa Jääskeläinen
2007-06-17 13:34 ` Robert Millan
2007-06-18  2:52 ` Ashok kumar
2007-06-18 10:22 ` adrian15
2007-06-18 13:32   ` Robert Millan
2007-06-18 15:40     ` Vesa Jääskeläinen [this message]
2007-06-19 12:13       ` adrian15
2007-06-19 15:13         ` Vesa Jääskeläinen
2007-06-19 12:08     ` adrian15
2007-06-23 12:57 ` Marco Gerards
2007-06-23 14:31   ` Bean
2007-06-23 14:50     ` Marco Gerards
2007-06-24  4:22       ` Bean
2007-06-24 11:47         ` Bean
2007-07-22 12:42           ` Marco Gerards
2007-06-23 14:52     ` Marco Gerards
2007-06-23 15:59       ` Bean
2007-06-23 16:10         ` Marco Gerards
2007-06-23 16:23           ` Bean
2007-06-23 16:38             ` Marco Gerards
2007-06-23 20:19               ` Yoshinori K. Okuji
2007-07-01 17:49     ` adrian15
2007-06-25 18:41       ` Bean
2007-06-26  4:13   ` Ashok kumar
2007-07-22 14:31     ` Marco Gerards

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=4676A77F.8030702@nic.fi \
    --to=chaac@nic.fi \
    --cc=grub-devel@gnu.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.