[devel at bb.net] Google Summer of Code 2016
Dustin J. Mitchell
dustin at buildbot.net
Sat Feb 13 18:06:52 UTC 2016
Quick bump: we're still looking for more mentors for this year's Google
Summer of Code. We'd love to have some of our former mentors re-join us
this year, or welcome new mentors. I'm happy to answer any questions you
might have about mentoring.
Dustin
On Wed, Feb 10, 2016 at 9:34 AM, Dustin J. Mitchell <dustin at buildbot.net>
wrote:
> For the last five years, Buildbot has participated in the Google Summer of
> Code, mentoring students while they work on development projects. Let's do
> it again!
>
> Here's what we need:
>
> 1. A co-administrator
>
> Administrators represent the organization to google, helping handle
> student applications, keeping students and mentors on track during the
> year, and handling any situations that come up during the year (e.g.,
> failing a student.. it happens).
>
> I'll be co-administering again this year (unless we get two eager
> co-administrators!), but Google wisely requires two co-admins.
>
> 2. Mentors
>
> Each mentor works directly with one student (typically two mentors to a
> student; see below), helping them either with the organizational bits like
> keeping to a schedule and measuring progress; or with the technical aspects
> of the Buildbot codebase. You don't have to be an expert Buildbot hacker
> to mentor!
>
> 3. Feedback from previous years
>
> We've had a number of mentors over the years, and aside from welcoming you
> back for 2016, I'd love feedback from you on how we might run things
> differently this year. One question I'm particularly interested in is
> this: is it useful to keep the two-mentors-per-student ratio, or should we
> try one-to-one?
>
> Applications are due on the 19th, so we'll be drafting our application at
> the next Tuesday 16:30UTC meeting in #buildbot.
>
> Let us know how you can help!
>
> Dustin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20160213/7f6eb290/attachment.html>
More information about the devel
mailing list