[Soc-coordination] Application to GCI / End Debian's delegation

[Ana Guerrero]

Hi!

With the application process opening in 2 days and not having enough
volunteers or having done anything about it (see forwarded email below),
the best is not applying for the code-in this year :(

On other news, the delegation for this year's GSoC finishes tomorrow [1].
I think everything is closed, if you have some email pending, ping
about it because it has been forgotten. If it is related to travel
reimbursement, it should go to SPI treasurer.

If you're interested in helping to run the program next year, this list
continues open to discuss improvements, suggestions and better ways
to do things in the next edition.


Thanks everybody,
Ana

[1] http://lists.debian.org/debian-devel-announce/2012/02/msg00006.html


----- Forwarded message from Stephanie Taylor <sttaylor at google.com> -----

From: Stephanie Taylor <sttaylor at google.com>
Sender: google-summer-of-code-mentors-list at googlegroups.com
To: Google Summer of Code Mentors List <google-summer-of-code-mentors-list at googlegroups.com>
Date: Mon, 15 Oct 2012 13:09:58 -0700
Subject: [GSoC Mentors] Application to be a GCI Mentoring Org - Things to Consider before the application
	process opens Oct 22nd
Message-ID: <CAEp7XcTj5PT9iowPdxF7TWgwBnmHuEK58j=+asaS9LFgMhiwZg at mail.gmail.com>

*Hi GSoC Mentors and Admins,

We’ve been receiving quite a few questions about the Google Code-in 2012
[0] contest and we wanted to give you some more information so your orgs
can start talking about whether you think the contest would be a good fit
for your organization and you can start thinking about your applications
and task list (one of the most important parts of your GCI application).

Important Upcoming Dates:
October 22, 2012 16:00 UTC - November 5, 2012 at 23:00 UTC - Orgs can go to
google-melange.com and the org admin can register and fill out the
application to be a mentoring organization for Google Code-in 2012.
November 12, 2012 - The 10 Mentoring organizations are announced for Google
Code-in 2012 and the orgs can start entering their tasks into the Google
system (the tasks will not be viewable to students until the contest opens
on Nov 26)
November 26, 2012 at 17:00 UTC - Google Code-in 2012 contest opens for
students.
<http://code.google.com/p/google-code-in/wiki/GCIMentorInformation2012>
Some Basics:
The new contest structure should make many things easier for your orgs (we
hope!).  We have listened to your suggestions and have made the following
changes:


   - Org admins can upload tasks throughout the contest.


   - We have eliminated all translation tasks.
   - No easy, medium or hard task classifications - Each org had different
   parameters for ranking something as easy/medium/hard so we have eliminated
   the classifications entirely and have asked that orgs base their tasks on
   things they think would take the average contributor about 2 hours to
   complete.
   - There will be 10 mentoring organizations this year (compared to 18
   last year).


   - Each Org will name 2 Grand Prize Winners for a total of 20 Grand Prize
   winners.


You can view more details on these changes on our Wiki page [2].

FAQ’s for Mentoring Orgs:
1)  How do we become a mentoring org for GCI 2012?
Organizations that have participated in any Google Summer of Code will be
able to apply to be a mentoring organization for Google Code-in 2012.  The
Application will open up to organizations on Monday, October 22nd at 9am
PST (16:00 UTC) and will close on Monday, November 5th at 3:00pm PST (23:00
UTC). We will send an email to this list on Monday, October 22nd with the
direct link for org admins to apply for Google Code-in 2012 on the Melange
program site.

2) We are used to working with the university students for Google Summer of
Code, what should we expect working with 13-17 year olds?
We won’t kid you, working with teengers can be demanding. It’s important
that your mentors/org be prepared to put the time in over the holidays
(including on weekends, etc.) to respond to questions and evaluate the
student’s tasks. If you do participate you will all have the satisfaction
of sharing your project and your passion for open source with a truly
inspiring group of young people, and getting them started in our community.

3)  How do we know if we would be a good fit with the younger developers?
Think about the types of tasks you have that you would want students to
work on.  When filling out your application you will need to link to your
task list of at least 5 tasks for each of the 5 categories (Coding,
Documentation/Training, Outreach/Research, Quality Assurance and User
Interface).  Your Proposed Tasks list is *very* important in helping us
determine which organizations we choose to be mentoring orgs for Google
Code-in 2012.

It is okay if your tasks lean more toward coding or documentation/training
or user interface, etc. but think about the types of tasks that you would
like the students to work on and remember while some of these students have
been coding since they were 5 others are new to coding or may have never
attempted coding before so having other types of tasks available to them is
necessary. The goal of Google Code-in is to introduce students to the world
of open source and to show them there are many ways to contribute to open
source projects.

4) What should we consider when applying to be a GCI org -- ie. what type
of time commitments are required to participate?
Reach out early and get a commitment from a primary org admin and at least
one backup org admin and then multiple mentors as each task will be
assigned a mentor in case the student has questions and ultimately to
review the task to decide if it has been successfully completed. The
contest starts November 26, 2012 and will end on January 14, 2013. This
time frame will cover many national and religious holidays so you will want
to assign people to cover the days of major holidays. If a mentor is
assigned to a task and is on vacation/away from their computer for an
extended period of time (more than 36 hours) then there needs to be another
mentor covering those tasks so when a student submits a task they won’t
have to wait a week until their mentor gets back to claim another task.
Students can only claim one task at a time so in the past they have gotten
very antsy when they haven’t heard back from their mentor within a
reasonable amount of time.

Google Code-in session at GSoC Mentor Summit
There will be a Google Code-in session at the GSoC Mentor Summit this
weekend. The session will be a good opportunity to ask questions of other
mentors and the Google Code-in administrators.

We will send out an email to this list next Monday (October 22nd) when we
open the program site for applications.

We hope your org will apply to be a part of Google Code-in 2012.

[0]  http://www.google-melange.com/
[1]  http://www.google-melange.com/gci/events/google/gci2012
[2]  http://code.google.com/p/google-code-in/wiki/GCIMentorInformation2012

Best,
Stephanie Taylor*

Stephanie Taylor | Open Source Programs, Google |  sttaylor at google.com |
650-214-1656

-- 
You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group.
To post to this group, send email to google-summer-of-code-mentors-list at googlegroups.com.
To unsubscribe from this group, send email to google-summer-of-code-mentors-list+unsubscribe at googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-summer-of-code-mentors-list?hl=en.


----- End forwarded message -----