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: Google Summer of Code 2007
Date: Tue, 13 Mar 2007 17:44:21 +0100	[thread overview]
Message-ID: <200703131744.22340.okuji@enbug.org> (raw)
In-Reply-To: <87veh571ya.wl@dekkers.cx>

On Tuesday 13 March 2007 13:38, Jeroen Dekkers wrote:
> Well I can always be hit by a bus or anything like that. But I hope it
> won't be necessary.

Last year, real procedures were always taught only to primary mentors, but not 
to backup mentors, IIRC. Hollis, weren't they? So I thought, then what is the 
meaning of having a backup mentor?

> We should come up with a idea list today, because tomorrow Google will
> begin accepting applications. I think we should just start with
> http://www.gnu.org/software/grub/grub-soc.html and remove the project
> I did last summer. I think all the other tasks still need to be
> done. New ideas are welcome too of course.

I agree. And this needs to be informed to the gnu's list, because what Google 
will see is the GNU's list but not ours.

http://www.gnu.org/software/soc-projects/ideas.html

> Personally I think one of the important things we have to do is making
> GRUB2 a suitable replacement for GRUB Legacy. This means implementing
> all the features from GRUB Legacy that GRUB2 doesn't have yet, making
> sure that the installer and other tools are all in a good state,
> etc. It's a bit difficult to make a task out of that, but IMHO it's
> time that GRUB2 gets ready for production use.

I fully agree, but I am afraid that this kind of task should be done by 
long-term contributors rather than newcomers, and SoC is not very suitable. 

The term of SoC is really short. IMO, it is long enough to implement some 
clear, straightforward and visible feature, but not for vague, complicated 
and tiresome work.

Anyway, our list just shows examples. Students are free to propose new ideas. 
In addition, we can obtain only one student from the past experience. If we 
are unlucky, we can get zero. So I think it is better not to bloat the list 
too much, but rather expect that students would think of something 
interesting themselves.

Okuji



  reply	other threads:[~2007-03-13 16:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 17:17 Google Summer of Code 2007 Yoshinori K. Okuji
2007-03-06 10:44 ` Johan Rydberg
2007-03-06 17:07   ` Thomas Schwinge
2007-03-06 17:56     ` Er Zapito
2007-03-06 21:49     ` Jeroen Dekkers
2007-03-10 21:38       ` Jeroen Dekkers
2007-03-12 17:45         ` Yoshinori K. Okuji
2007-03-13 12:38           ` Jeroen Dekkers
2007-03-13 16:44             ` Yoshinori K. Okuji [this message]
2007-03-13 17:36               ` Marco Gerards
2007-03-13 22:39                 ` Thomas Schwinge
2007-03-15 10:26               ` Jeroen Dekkers
2007-03-21  4:02                 ` Yoshinori K. Okuji
2007-03-14  1:52             ` Brandon Sho
2007-03-14 11:14               ` Marco Gerards
2007-03-19  4:38                 ` Brandon Sho
2007-03-07 13:45 ` Marco Gerards
     [not found] <200703151705.l2FH53LC032672@correoredir01.dinaserver.com>
2007-03-19  8:11 ` adrian15
  -- strict thread matches above, loose matches on Subject: below --
2007-02-25  7:59 Shawn O. Pearce
2007-02-27 20:47 ` Johannes Schindelin
2007-02-28  8:42 ` Andy Parkins
2007-02-28  9:03   ` Matthieu Moy
2007-03-02 20:36     ` Johannes Schindelin
2007-02-28  9:35 ` Raimund Bauer
2007-02-28 15:39   ` Brian Gernhardt
2007-02-28 15:47     ` Shawn O. Pearce
2007-02-28 16:00       ` Brian Gernhardt
2007-03-01  2:08 ` Jakub Narebski
2007-03-01  8:03   ` Matthieu Moy
2007-03-01 21:34   ` Shawn O. Pearce
2007-03-04 22:10     ` Martin Langhoff

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=200703131744.22340.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.