I've been thinking of having the Wikidata mobile skin use CSS3 animations
instead of jQuery and adding a two column layout for tablets.
I think this shouldn't take more than a few hours each and I'm pretty sure
I'm capable enough to help students along if they'd like to pick this task
up. Is this something that I could propose for GCI?
On Fri, Nov 1, 2013 at 9:48 PM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
Woohoo! Everybody prepare your bugs and feature reqs
for bite-sized work
units!
-- brion
On Friday, November 1, 2013, Quim Gil wrote:
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-**google-code.html<
http://google-opensource.blogspot.com/2013/11/mentoring-organizations-for-g…
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<
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<
http://www.mediawiki.org/wiki/User:Qgil>
______________________________**_________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<
https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l