Google Code-in is open to tasks related with user interface. Are you in?
-------- Original Message -------- Subject: Google Code-in: are you in? Date: Thu, 10 Oct 2013 10:51:21 -0700 From: Quim Gil qgil@wikimedia.org To: Wikimedia developers wikitech-l@lists.wikimedia.org
Google Code-in has been announced:
http://www.google-melange.com/gci/homepage/google/gci2013
This is about 13-17 year old students performing tasks that can be isolated and a skilled contributor would complete in a couple of hours. The tasks mjust have a mentor and can be related to code, documentation, outreach, QA or UX. Participants get one point for each task completed and they can complete as many as they can between 18 November and 6 January.
Wikimedia can apply thanks to our participation on GSoC 2013. The deadline is 28 October. Only 10 organizations will be accepted.
I think we should apply. Main reasons:
* The definition of a Code-in task fits very well with our ideal definition of an annoying little bug: https://www.mediawiki.org/wiki/Annoying_little_bugs
* The typical Code-in participant needs what most potential new contributor also need from us: an insightful landing page, straight connections to first tasks and friendly community support.
* Just like GSoC / OPW, it is a good chance for non-primetime projects to raise their hands, get some help and hopefully some new contributors.
* Good exercise for first-time mentors, practicing for more co plex internship projects.
* Good exercise for any open source project, meaning just any MediaWiki / Wikimedia tech project.
But of course this will only work if many projects want to step in with a task and a mentor for it. So what do you think?
On 10/10/2013 11:00 AM, Quim Gil wrote:
Google Code-in is open to tasks related with user interface. Are you in?
An update:
We have already a good collection of UI related tasks at
https://www.mediawiki.org/wiki/Google_Code-In#User_Interface
Thank you Matma Rex, Nemo, Pau and Jorm for your help so far. This raw material is good enough for the current stage, but of course you or anybody else can keep adding tasks. The exercise of identifying these good tasks for newcomers is useful in any case.
According to the plan, we will apply by next Monday and we will know whether we have been selected as a participant organization on November 1. If we are selected we will have until November 18 to polish the descriptions of those tasks.
-------- Original Message -------- Subject: Google Code-in: are you in? Date: Thu, 10 Oct 2013 10:51:21 -0700 From: Quim Gil qgil@wikimedia.org To: Wikimedia developers wikitech-l@lists.wikimedia.org
Google Code-in has been announced:
http://www.google-melange.com/gci/homepage/google/gci2013
This is about 13-17 year old students performing tasks that can be isolated and a skilled contributor would complete in a couple of hours. The tasks mjust have a mentor and can be related to code, documentation, outreach, QA or UX. Participants get one point for each task completed and they can complete as many as they can between 18 November and 6 January.
Wikimedia can apply thanks to our participation on GSoC 2013. The deadline is 28 October. Only 10 organizations will be accepted.
I think we should apply. Main reasons:
- The definition of a Code-in task fits very well with our ideal
definition of an annoying little bug: https://www.mediawiki.org/wiki/Annoying_little_bugs
- The typical Code-in participant needs what most potential new
contributor also need from us: an insightful landing page, straight connections to first tasks and friendly community support.
- Just like GSoC / OPW, it is a good chance for non-primetime projects
to raise their hands, get some help and hopefully some new contributors.
- Good exercise for first-time mentors, practicing for more co plex
internship projects.
- Good exercise for any open source project, meaning just any MediaWiki
/ Wikimedia tech project.
But of course this will only work if many projects want to step in with a task and a mentor for it. So what do you think?