From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Google SOC 2008
Date: Wed, 27 Feb 2008 10:46:05 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.02.27.10.46.05@cox.net> (raw)
In-Reply-To: 47C4A08C.3040708@gentoo.org
joshua jackson <tsunam@gentoo.org> posted 47C4A08C.3040708@gentoo.org,
excerpted below, on Tue, 26 Feb 2008 15:28:12 -0800:
> Rémi Cardona wrote:
>> joshua jackson a écrit :
>>> 2) We need mentors, so far confirmed I have: Diego and Saleem
>>
>> What kind of work is involved there? I wouldn't mind being a mentor but
>> I'd like to know a bit more about what's expected from a "good" mentor.
> There's a few requirements. Being decent in a language or multiple
> languages would certainly be a plus, as the students are writing code.
> having someone writing something in C or C++ when you've never touched
> it wouldn't exactly work out that well obviously.
>
> Having time to interact with the student as well. [snip]
I saw some discussion earlier about the possibility/goal of having backup
mentors as well. Someone that would keep familiar enough with what's
going on to step in if the primary mentor has "things" happen and isn't
as available as they intended to be, but (unless the two team as true co-
mentors) wouldn't need to do the detail code reviewing, performance
auditing, or whatever, unless those "things" /did/ happen to the primary
mentor.
IOW, someone to keep the whole project afloat if something does happen to
the primary mentor/gentoo-contact-point. If I'm not mistaken, the
original comment I read suggesting this pointed out that there had been a
need for a backup mentor for at least one project, that had ended up not
going much of anywhere because there wasn't one. Such a run of events
would certainly be a shame, both for Gentoo and for the student in
question, so if it can be avoided...
Of course, with only two mentors (now possibly three) volunteered so far,
that's not so practical, but perhaps there are some who would prefer to
avoid primary mentorship if possible, but wouldn't mind doing it if it
becomes necessary to avoid /dev/null-ing the project.
It's also possible some would be available as co-mentors.
So anyone qualified and interested, I'm sure it'll help both Gentoo and
the student you backup- or co-mentor. =8^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-27 10:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 18:32 [gentoo-dev] Google SOC 2008 joshua jackson
2008-02-26 23:13 ` Rémi Cardona
2008-02-26 23:28 ` joshua jackson
2008-02-27 2:57 ` Alec Warner
2008-02-27 10:46 ` Duncan [this message]
2008-02-27 8:42 ` Fabian Groffen
2008-02-27 10:46 ` Roy Marples
2008-02-27 12:29 ` Fabian Groffen
2008-02-27 13:56 ` Roy Marples
2008-02-27 14:21 ` Fabian Groffen
2008-02-27 21:04 ` Roy Marples
2008-02-28 11:22 ` Roy Marples
2008-02-28 11:25 ` Fabian Groffen
2008-03-03 13:36 ` Roy Marples
2008-03-03 14:53 ` Fabian Groffen
2008-03-03 15:50 ` Michael Haubenwallner
2008-03-03 16:04 ` Roy Marples
2008-03-03 15:58 ` Roy Marples
2008-02-27 19:11 ` [gentoo-dev] MESA i965 SUPPORT PLEASE! Mateusz Mierzwinski
2008-02-27 19:47 ` Chris Gianelloni
2008-02-27 19:49 ` Chris Gianelloni
2008-02-28 7:37 ` Mateusz Mierzwinski
2008-02-28 9:58 ` Rémi Cardona
2008-02-27 10:50 ` [gentoo-dev] Google SOC 2008 Damian Florczyk
2008-02-28 16:02 ` Marius Mauch
2008-02-29 13:08 ` JoseAlberto
2008-02-29 17:24 ` Alec Warner
2008-03-02 15:58 ` Luca Barbato
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=pan.2008.02.27.10.46.05@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox