Difference between revisions of "Google Code-in/Application 2016"
| Line 1: | Line 1: | ||
;Why does your organisation want to participate in Google Code-in 2016? |
;Why does your organisation want to participate in Google Code-in 2016? |
||
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. |
|||
There are three main reasons that Apertium wants to participate in Google Code-in again: First of all |
|||
the project really benefits, we get a lot out of it in terms of code, documentation, new ideas and |
|||
new resources. Our web site runs on code produced during GCI, and students who work with us have |
|||
even published academic papers in international conferences. So, we benefit. Secondly, Apertium is a project that focuses a lot on marginalised languages. GCI gives us a chance of getting in touch with the next generation of speakers, and showing them how they can help their languages develop and give them some esteem. Language shift (abandoning one's language after perceiving it is not useful for wider spheres of communication) often occurs at this age, and if we can show young language users that their language is useful, and other people care, and there is no barrier for its use in the 'electronic' space, then that might give it more chance of survival. |
|||
;How has your organisation prepared for Google Code-in 2016? |
;How has your organisation prepared for Google Code-in 2016? |
||
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! |
|||
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? |
;In which years did your organisation participate in Code-In? |
||
| Line 38: | Line 32: | ||
# wei2912 |
# wei2912 |
||
# Kira |
# Kira |
||
# Jaipal |
|||
;How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? |
;How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? |
||
Latest revision as of 21:03, 29 October 2016
- Why does your organisation want to participate in Google Code-in 2016?
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 2016?
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!
- 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
- Jaipal
- 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 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]
