From: joshua jackson <tsunam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Google SOC 2008
Date: Tue, 26 Feb 2008 15:28:12 -0800 [thread overview]
Message-ID: <47C4A08C.3040708@gentoo.org> (raw)
In-Reply-To: <47C49D22.1090409@gentoo.org>
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.
>
> Thanks,
>
> Rémi
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. They are getting paid
as are we as an organization, so helping them and giving them idea's is
needed. Touching base and making sure they are still progressing on
their projects. Its summer...but they are being paid to work so it is a
job as I hope as a mentor you would take a similar approach as well.
Basically you act as a technical boss/mentor/leader to someone.
One area I'm working on for this year is goals within the overall goal
that can be implemented hopefully even if the project isn't fully
finished before the end of the project.
For the mentor it won't be a full time commitment but having time to
talk with/help someone with their project and explain how to implement
this feature or get this information from Gentoo's system would take
some time.
As a warning some people come on board with excellent programming
ability that you don't need to do much with/for. Some well its their
first real jump into programming and need more attention. I plan on
having a few additional questions for the Gentoo related applications to
help define that kind of thing and hope to get people together in such a
way.
As well a few of the people who are helping run it have agreed to help
poke/get updates from the mentors and step in and help in whatever way
possible to the students as well. Basically, we want as many projects to
succeed as possible and become a daily tool or vastly improved tools as
possible. Its certainly something that is possible.
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-26 23:28 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 [this message]
2008-02-27 2:57 ` Alec Warner
2008-02-27 10:46 ` [gentoo-dev] " Duncan
2008-02-27 8:42 ` [gentoo-dev] " 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=47C4A08C.3040708@gentoo.org \
--to=tsunam@gentoo.org \
--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