Google Code-in/Application 2016
- Why does your organisation want to participate in Google Code-in 2016?
- How has your organisation prepared for Google Code-in 2016?
We have four organisation administrators: Francis Tyers, Jonathan North Washington, Mikel L. Forcada and Kevin Brubeck Unhammer.
We have around 15 mentors who will be taking part. They are from a variety of time zones, from CST (UTC-6) to MSK (UTC+4).
- In which years did your organisation participate in Code-In?
2009 (GSoC only), 2010 (GSoC and GCI), 2011 (GSoC and GCI), 2012 (GSoC and GCI), 2013 (GSoC and GCI), 2014 (GSoC and GCI),
- In which years did your organisation participate in Google Summer of Code?
2009 (GSoC only), 2010 (GSoC and GCI), 2011 (GSoC and GCI), 2012 (GSoC and GCI), 2013 (GSoC and GCI), 2014 (GSoC and GCI),
- How many mentors have agreed to participate?
- Fran
- Jonathan
- Flammie
- Joonas
- Kvld
- Vin-ivar
- Sushain
- Unhammer
- Memduh
- zfe
- Tino
- Trond
- Mikel Forcada
- wei2912
- Kira
- How do you plan to deal with any holidays or vacations mentors may have planned during the contest period?
In addition to these mentors, there will be plenty of help available to students as there are always Apertium developers hanging out on the Apertium IRC channel. For most of our mentors, hanging out on the Apertium IRC channel, hacking, and helping other developers hack is a lot of what we do in our free time, because we do it for fun. For those of us that work, the 'holidays' are really when we are most active in Apertium.
It is also worth noting that our mentors come from a diverse range of countries which have different holiday traditions (e.g. mentors in the US and England celebrate Christmas on the 25th December, while in Turkey Christmas is not celebrated and in Russia it is celebrated on the 7th January).
- How do you plan to deal with unresponsive mentors?
In past Google Code-Ins our organisation has had a good record in responding in time to students. But, if for some reason a mentor becomes unresponsive (in our experience, it would have to be either task overload or 'force majeure'!), administrators will be on call to reassign the task to another mentor or evaluate it themselves. One difference this year is that we will ensure that each task has at least two mentors who are qualified to evaluate it, this will reduce the possibility of task overload.
- We would like to see 25 example tasks.
- Common task information [Short instructions or tips to be displayed on every task. May include limited Markdown. Example
- See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions.]
- Common task information [link]
