community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulrich Stärk <>
Subject Re: [GSoC Mentors Announce] Google Summer of Code 2013
Date Fri, 15 Feb 2013 15:23:57 GMT
That's quite accurate and corresponds with my experience in the last two years.

I expect to put in a bit more this year as I want to tidy up our websites a bit.


On 15.02.2013 15:57, Ross Gardler wrote:
> Others are likely reading this and wondering if they have the cycles to be
> an admin. So here's my experience, other admins may have slightly different
> experiences.
> The admin is very busy in the run up to and selection process (easily 5
> hours a week, for a few weeks - shared between admins). This is promoting
> the activity, updating website, answering questions, filling forms and
> monitoring Googles mentor mail list Once underway the admin role goes down
> to about half an hour a week (each admin). This is monitoring the mentor
> list and communicating things back. Around mid-term there are a couple of
> weeks at about 5 hours (shared between admins). This is the same monitoring
> but there is more to do now, like chase missing student reports etc. Then
> back to the 1 hour per week monitoring work. Finally in the wrap up a few
> more weeks at 5 hours per week (chasing missing reports, blogs, data
> collection, feedback to PMC chair for board report etc.)
> Sometimes there is a burst of activity when a mentor or student is having a
> problem. Usually this will fit in the time estimates above. However, once
> every couple of years there is something more serious that requires careful
> investigation. This can take an addition 5-10 hours depending on the case.
> It's these kinds of things that will usually draw on those hovering on the
> sidelines to help out if necessary.
> Ross
> On 15 February 2013 13:58, Suresh Marru <> wrote:
>> On Feb 15, 2013, at 4:24 AM, Ulrich Stärk <> wrote:
>>> Chris,
>>> thanks for the heads up.
>>> Folks, I'd like us to get started with this ASAP. The application period
>> hasn't started yet but we
>>> need to get the word out to our projects and have them collect ideas.
>>> I've got some cycles and would volunteer as the org admin again. Any
>> others?
>> Hi Uli,
>> I am willing to help co-ordinate and I will be mentoring project as well.
>> I do not know the time commitments for admins. So I will not sign up for
>> official admin, but will be mostly around to help you guys as needed.
>> Suresh
>>> Also I think we should look at our procedures and discuss if anything
>> needs to be improved. One
>>> thing is the "who goes to the mentor summit" discussion we had last
>> year. Historically these were
>>> the org admins. I was there last year as one of the org admins but I
>> would have liked it if there
>>> was one of the mentors as well because I missed some insights into the
>> actual mentoring. I'm
>>> therefore proposing that this year we send at least one mentor. We'll
>> have to establish criteria for
>>> chosing a mentor to send but I could think of tying this to additional
>> effort put into the program
>>> such as mentoring more than one student or creating publicity with blog
>> posts about the projects
>>> they are mentoring.
>>> Thoughts?
>>> Uli
>>> On 11.02.2013 21:22, Mattmann, Chris A (388J) wrote:
>>>> Guys FYI.
>>>> From: Carol Smith <<>>
>>>> Reply-To: "<mailto:
>>>" <
>>>> Date: Monday, February 11, 2013 11:02 AM
>>>> To: "<mailto:
>>>" <
>>>> Subject: [GSoC Mentors Announce] Google Summer of Code 2013
>>>> Hi GSoC mentors and org admins,
>>>> We've announced that we're doing Google Summer of Code 2013 [1]. Yay!
>>>> If you would like to help spread the word about GSoC, we have
>> presentations [2], logos [3], and flyers [4] for you to use. Please host
>> meetups, tell your friends and colleagues about the program, go to
>> conferences, talk to people about the program, and just generally do all
>> the awesome word-of-mouth stuff you do every year to promote the program.
>>>> The GSoC calendar, FAQ, and events timeline have all been updated with
>> this year's important dates, so please refer to those for the milestones
>> for this year's program. NB: the normal timeline for the program has been
>> modified for this year. You'll probably want to examine the dates closely
>> to make sure you know when important things are happening.
>>>> Please consider translating the presentations and/or flyers into your
>> native language and submitting them directly to me to post on the wiki.
>> Localization for our material is integral to reaching the widest possible
>> audience around the world. If you decide to translate a flyer, please fill
>> out our form to request a thank you gift for your effort. [5]
>>>> If you decide to host a meetup, please email me to let me know the
>> date, time, and location so I can put it on the GSoC calendar. Also,
>> remember to take pictures at your meetup and write up a blog post for our
>> blog using our provided template for formatting [6]. If you need
>> promotional items for your attendees, please fill out our form [7] to
>> request some; we're happy to send some along. We can provide up to about 25
>> pens, notebooks, or stickers and/or a few t-shirts. Please keep in mind,
>> though, that shipping restrictions and timeline vary country-to-country;
>> request items early to make sure they get there on time! If you have
>> questions about hosting meetups, please see the section in our FAQ [8].
>>>> Please also consider applying to participate as an organization again
>> this year or maybe joining as a mentor for your favorite organization if
>> they are selected this year.
>>>> We rely on you for your help for the success of this program, so thank
>> you in advance for all the work you do!
>>>> [1] -
>>>> [2] -
>>>> [3] -
>>>> [4] -
>>>> [5] -
>>>> [6] -
>>>> [7] -
>>>> [8] -
>>>> Cheers,
>>>> Carol
>>>> --
>>>> You received this message because you are subscribed to the Google
>> Groups "Google Summer of Code Mentors Announce List" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to<mailto:
>>>> Visit this group at
>>>> For more options, visit

View raw message