From: Thomas Schwinge <tschwinge@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Google Summer of Code 2007
Date: Tue, 13 Mar 2007 23:39:44 +0100 [thread overview]
Message-ID: <20070313223944.GF31291@fencepost.gnu.org> (raw)
In-Reply-To: <87bqix82r8.fsf@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Hello!
On Tue, Mar 13, 2007 at 06:36:11PM +0100, Marco Gerards wrote:
> "Yoshinori K. Okuji" <okuji@enbug.org> writes:
> > 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.
One note on that: it seems that this year a much smaller number of GNU
(sub)projects are going to take part. Compare
<http://gnu.org/software/soc-projects/ideas-2006.html> to
<http://gnu.org/software/soc-projects/ideas.html>. (Of course, not
everything may be in place yet -- like to Hurd's tasks are still
missing...) So it might be that the participating GNU (sub)projects
might get more students to work on tasks like they got last year. Or it
may not.
> > 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.
It may be hard for students (also for capable ones) to come up with
suitable tasks, if they don't have any guide lines. So, I think it's
helpful to publish quite a number of ideas. _Then_, the students can
still modify them as it suits them.
> Last year it looked like the number of projects assigned and the number of
> mentors a project had, had a certain relation. Of course, because
> GRUB is a part of the GNU project, this relation might not be true for
> GRUB. And this is mainly based on rumors from last year... Perhaps
> people can confirm this?
I can't really support that statement, but then, I only know the number
of the GNU project.
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2007-03-13 22:42 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
2007-03-13 17:36 ` Marco Gerards
2007-03-13 22:39 ` Thomas Schwinge [this message]
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=20070313223944.GF31291@fencepost.gnu.org \
--to=tschwinge@gnu.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.