If your project needs gadgets or templates imported / adapted / fixed,
or other little technical tasks, and you have admins busy enough to do
the work but not to mentor it... this is your chance!
Google Code-in is a perfect program to bring technical help to your
projects. If you are interested read below, edit our Google Code-in wiki
page, or contact me directly.
-------- Original Message --------
Subject: Google Code-in: YES, WE ARE IN!
Date: Fri, 01 Nov 2013 09:06:29 -0700
From: Quim Gil <qgil(a)wikimedia.org>
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Wikimedia is one of the ten organizations selected to participate in
Google Code-in 2013! This means that on November 18 we will start having
hundreds of 13-17 year old students looking at Wikimedia tech tasks to
be completed.
The announcement:
http://google-opensource.blogspot.com/2013/11/mentoring-organizations-for-g…
Our GCI page:
https://www.mediawiki.org/wiki/Google_Code-In
If you are involved in FOSS Outreach Program for Women in any way you
can stop reading here. Otherwise, please stay with us. This program is a
very good opportunity to find fresh young helpers willing to complete
that little task that has been sitting in your ToDo list for too long.
WE NEED STRUCTURE
Andre Klapper and me are the Wikimedia org admins and we will take a lot
of dirty and boring work so the rest of you don't have to. However, we
won't be able to make it without meta-mentors.
META-MENTORS are seasoned contributors that have a good knowledge of the
relevant technologies, features and people involved in a specific area.
They are also mentors of some tasks in their areas, but their role
includes looking for more mentors that bring more tasks, and coordinate
with them. GCI organizations get an average of 150-200 tasks completed
during the program. You see the need for a distributed structure that
scales.
GCI has five areas:
* Code (proposing MatmaRex, helped by ?)
* Documentation/Training (guillom, helped by ?)
* Outreach/Research (?, helped by Quim - or the other way around)
* Quality Assurance (proposing Željko, helped by Andre)
* User Interface (Pau and Jorm)
Please, help substituting question marks with names.
WE NEED MENTORS BRINGING TASKS
The deal is simple: join GCI as mentor and bring your little tasks (that
would take you 2-3 hours to complete). You need to describe the tasks
for a newcomer, linking to the resources needed to complete them. You
also need to be ready to answer the questions of the students assigning
your tasks to them.
We will have more specific instructions for mentors before the beginning
of the program.
WE NEED PEOPLE PROPOSING TASKS
Even if you can't mentor a specific task we still want to know about it.
All we need is a bug report with
gci2013
https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
added to its Whiteboard field to make it easy to track them. Please CC
the related meta-mentors, Andre and me.
Questions? Please ask and you will help us improving our documentation.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil