Google Code-in/Application 2017
- Why does your organisation want to participate in Google Code-in 2017?
Firstly the project really benefits, we get a lot out of it in terms of code, documentation, ideas and resources. Our web site runs on code produced during GCI, and students who work with us have even published academic papers in international conferences. Secondly, Apertium is a project that focuses a lot on marginalised languages. GCI gives us a chance to get in touch with the next generation of speakers, and to show them how they can help their languages develop and give them some esteem.
- How has your organisation prepared for Google Code-in 2017?
We've put together an organisation team of four experienced mentors and admins. We've recruited 17 mentors, many of whom have been mentors in past GCIs and some of whom are past GSOC students. We've tried to get a range of mentors in different time zones, so our time zone spreads from UTC-6 to UTC+5. We've produced an updated task page and continue to solicit more ideas. We've also started personally preparing ourselves for the excitement!
- Prior Experience
- How many mentors have committed to participate?
- How do you plan to deal with any holidays or vacations mentors may have planned during the contest period?
In addition to our mentors, there will be plenty of help available to students as there are always Apertium developers hanging out on IRC. For most of our mentors, talking on IRC, hacking, and helping others 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.
- 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 be either task overload or 'force majeure'!), administrators will arrange for the task's evaluation either themselves or by another mentor. 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.