Dear all, as you know, "Google Code-In is a contest for pre-university students (e.g., high school and secondary school students) with the goal of encouraging young people to participate in open source.". Google Code-In works "with open source organizations", such as Apertium, "each of whom will provide a list of tasks to be completed by student contestants. Tasks can be anything an organization needs help with, from bug fixes, to writing code, to user experience research, to writing documentation. The contest takes place entirely online."
Apertium has been part one of the Google Code-In organizations every year since its inception in 2010. Note that only about 10 organizations are part of it every year: it's a very exclusive club. We need more Apertium developers to become involved. If we succeed in our application, which has to go in before November 10, there will be hundreds of tasks and hundreds of participants, eager to get feedback on their work by email or on IRC. GCI 2014 [1] will run between December 1 and January 18. We need you to: *Propose tasks that you can mentor*. We have hundreds of unfinished tasks left over from other GCIs. You could easily mentor some of these. But you can propose tasks of a similar size that may help our project. Think of teenager-level, a-few-days tasks that can help that part of Apertium where you are working. You can look at task descriptions (and the interaction with students) in previous editions [2,5] by typing Apertium in the Organization field. We also keep task descriptions in the Apertium wiki [6], and this is where you could propose new tasks. When proposing a task, think about how long the tasks take to be reviewed or explained, and how easy it will be for other people to review work. Note that having a good task page at application time increases our chances of being part of GCI this year. *Actually mentor tasks*: this means being available to discuss tasks with student, evaluate the results, and make sure results are made available in our repository. This means you have to read your email often for notifications and ideally hang around on our IRC channel, although this is not entirely necesssary. Tasks can have more than one mentor. *Volunteer to administer*: there is some work involved in making tasks available through the Mélange site: importing them, classifying them, making sure they have a description. I hope I haven't forgotten anything: past mentors and admins, please add or correct. I look forward to hearing from you. Mikel L. Forcada interim president of the Apertium Project Management Committee [1] http://www.google-melange.com/gci/homepage/google/gci2014 [2] http://www.google-melange.com/gci/tasks/google/gci2010 [3] http://www.google-melange.com/gci/tasks/google/gci2011 [4] http://www.google-melange.com/gci/tasks/google/gci2012 [5] http://www.google-melange.com/gci/tasks/google/gci2013 [6] http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in -- Mikel L. Forcada E-mail: m...@dlsi.ua.es Departament de Llenguatges Phone: +34-96-590-9776 i Sistemes Informàtics also +34-96-590-3772. UNIVERSITAT D'ALACANT Fax: +34-96-590-9326, -3464 E-03071 ALACANT, Spain. URL: http://www.dlsi.ua.es/~mlf
------------------------------------------------------------------------------
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
