All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status update for grub 2 developments?
Date: Sat, 23 Jun 2007 22:19:49 +0200	[thread overview]
Message-ID: <200706232219.49349.okuji@enbug.org> (raw)
In-Reply-To: <87odj6mxs6.fsf@xs4all.nl>

On Saturday 23 June 2007 18:38, Marco Gerards wrote:
> Bean <bean123@126.com> writes:
> > On Sat, Jun 23, 2007 at 06:10:10PM +0200, Marco Gerards wrote:
> >> The best thing, according to most people working on GRUB (from what I
> >> can tell) is a bug tracking system combined with something that tracks
> >> tasks, what people are interested on, descriptions of how tasks should
> >> be performed, etc.  That is something I like as well.
> >
> > I notice that savannah has a bug tracking system, but it's filled with
> > stuff from GRUB Legacy, maybe grub2 should have a tracking system of its
> > own.
>
> Yes.  The question is what it will be.

No. I never recommend using external resources. Even though the bug tracker on 
Savannah sucks, it is more or less usable. You can add a new field with which 
you can indicate whether your version is legacy or 2.

People often tend to think about software quality, but the really important 
thing in services is the maintenance. It is surely easy to set up a server, 
but it is very tough to maintain such a server for years (especially without 
being paid), dealing with hardware and software failures, answering silly 
questions, taking care of vulnerabilities, and so on.

gnu.org is maintained. It is financially supported. Even if the software is 
far from the best, you should use it. If you are not satisfied, improve 
savane rather than going away.

You might want to think of another web site. But is there any good alternative 
to savannah, from the viewpoint of functions as well as software freedom? And 
is there any good reason that we, a part of the GNU project, would like to 
abandone savannah and move away to anything else?

Please consider my words carefully, before proposing not using savannah.

(The wiki is exceptional, but as you might know, I was working on implementing 
wiki support in savane some years ago, but I could not finish it due to lack 
of time. If anybody can finish it, I would be happy to throw away our own 
wiki site, and move to savannah.)

Okuji



  reply	other threads:[~2007-06-23 20:19 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
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 [this message]
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=200706232219.49349.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.