Google Code-in/Application 2013 - Revision history

Francis Tyers at 15:34, 28 October 2013

2013-10-28T15:34:49Z

Mlforcada at 11:02, 28 October 2013

2013-10-28T11:02:56Z

Mlforcada at 11:02, 28 October 2013

2013-10-28T11:02:34Z

Mlforcada at 10:43, 28 October 2013

2013-10-28T10:43:25Z

Mlforcada at 10:43, 28 October 2013

2013-10-28T10:43:10Z

Mlforcada: First draft in for Fran to finish up

2013-10-27T08:03:20Z

First draft in for Fran to finish up

Mlforcada at 08:02, 27 October 2013

2013-10-27T08:02:19Z

Mlforcada at 07:44, 27 October 2013

2013-10-27T07:44:00Z

Mlforcada at 07:43, 27 October 2013

2013-10-27T07:43:33Z

Mlforcada at 07:42, 27 October 2013

2013-10-27T07:42:21Z

@@ Line 1: / Line 1: @@
-(First draft in by --[[User:Mlforcada|Mlforcada]] 08:03, 27 October 2013 (UTC))
+(Second draft in by [[User:Francis Tyers|Francis Tyers]] 15:34, 28 October 2013 (UTC))
 ;Organisation id*
-* Apertium
+* apertium
 ;Organisation name*
@@ Line 25: / Line 25: @@
 ;Veteran/New*
-* Veteran (2010, 2011, 2012)
+* Veteran
 ;Backup Admin*
+jnw
-mikel.forcada@gmail.com
 ;Why would you organisation like to participate in Google Code-in 2013?*
@@ Line 51: / Line 51: @@
 ;What programming languages does your organisation use?*
+* C++, Python, Java, Bash, HTML, Javascript, XML
-* C/C++, Java, Python, perl, Apertium's internal XML formats for grammatical transformation rules and dictionaries
 ;What is the main development mailing list for your organisation? This question will be shown to students who would like to get more information about applying to your organisation for Google Code-in 2013. If your organisation uses more than one list, please make sure to include a description of the list so students know which to use.*
 * apertium-stuff@lists.sourceforge.net (general list: most traffic here)
-* apertium-dev@lists.sourceforge.net (some involved development discussions may move on to this one)
 * apertium-turkic@lists.sourceforge.net (for discussions relating to Turkic-language development)
@@ Line 65: / Line 64: @@
 ;Please tell us about how your organisation has prepared for Google Code-in, including what (and how many) mentors and organisation administrators have agreed to help, what your schedule and response time will be during the holidays (and otherwise during the contest period) and how you plan to deal with unresponsive mentors.*
-(Fran had a text about this, but I want to have something just in case --[[User:Mlforcada|Mlforcada]] 07:44, 27 October 2013 (UTC))
+We have two organisation administrators, Francis Tyers and Jonathan North Washington. Fran is going to be unemployed during November and December, so he'll be able to dedicate himself full-time to it.
-* Currently we have more than 60 tasks, and many of the tasks listed refer generically to "a language pair" of which there are dozens. Therefore, there will be plenty of tasks available to students.
-* Currently the following mentors (and two admins) have already signed up, but we are actively recruiting mentors for language-pair tasks among the (dozens of) language-pair developers in the project:
+We have around 10 mentors who will be taking part. They are from a variety of time zones, from CST (UTC-6) to MSK (UTC+4).
-** Bernard Chardonneau
-** Miquel Esplà
+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 list, 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.  In past Google Code-Ins our organisation has had no problem to respond in time to students.
-** Mikel L. Forcada (backup admin)
-** Xavi Ivars
+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.
-** Fulup Jakez
-** Juan Antonio Pérez-Ortiz
+Last year at one point we were asked to come up with more tasks because the number of tasks in one area had got quite low. This year we will be on the ball to make sure that this does not happen.
-** Jim O'Regan
-** Ilnar Salimzyan
-** Felipe Sánchez-Martínez
-** Francis M. Tyers (admin)
-** Kevin Unhammer
-** Nikant Vohra
-** Jonathan N. Washington
-* 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 the mentors listed above, hanging out on the Apertium IRC list, hacking and helping other developers hack is what we do most of the free time we have, because we do it for fun. For those of us that work, the 'holidays' are really when we are most active in Apertium. In past Google Code-Ins our organisation has had no problem to respond in time to students.
-* If for some reason (in our experience, it would have to be either task overload or 'force majeure'!) a mentor becomes unresponsive, administrators will be on call to reassign the task to another mentor.
 ;Please include a link to the logo you would like to use if your org is chosen as a mentoring org for 2013. This allows us to post the logos of the GCI 2013 mentoring orgs as soon as we announce them on November 1, 2013.*
-* [http://xixona.dlsi.ua.es/apertium.png http://xixona.dlsi.ua.es/apertium.png]
+* [http://apertium.org/apertium65.png http://apertium.org/apertium65.png]
 [[Category:Google Code-in|Application 2013]]

@@ Line 68: / Line 68: @@
 * Currently we have more than 60 tasks, and many of the tasks listed refer generically to "a language pair" of which there are dozens. Therefore, there will be plenty of tasks available to students.
-* Currently 12 mentors (and two admins) have already signed up, but we are actively recruiting mentors for language-pair tasks among the (dozens of) language-pair developers in the project:
+* Currently the following mentors (and two admins) have already signed up, but we are actively recruiting mentors for language-pair tasks among the (dozens of) language-pair developers in the project:
 ** Bernard Chardonneau
 ** Miquel Esplà

@@ Line 74: / Line 74: @@
 ** Xavi Ivars
 ** Fulup Jakez
+** Juan Antonio Pérez-Ortiz
 ** Jim O'Regan
 ** Ilnar Salimzyan

@@ Line 68: / Line 68: @@
 * Currently we have more than 60 tasks, and many of the tasks listed refer generically to "a language pair" of which there are dozens. Therefore, there will be plenty of tasks available to students.
-* Currently 9 mentors (and two admins) have already signed up, but we are actively recruiting mentors for language-pair tasks among the (dozens of) language-pair developers in the project:
+* Currently 12 mentors (and two admins) have already signed up, but we are actively recruiting mentors for language-pair tasks among the (dozens of) language-pair developers in the project:
 ** Bernard Chardonneau
 ** Miquel Esplà

@@ Line 73: / Line 73: @@
 ** Mikel L. Forcada (backup admin)
 ** Xavi Ivars
+** Fulup Jakez
 ** Jim O'Regan
 ** Ilnar Salimzyan
+** Felipe Sánchez-Martínez
 ** Francis M. Tyers (admin)
 ** Kevin Unhammer
+** Nikant Vohra
 ** Jonathan N. Washington
 * 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.

← Older revision		Revision as of 08:03, 27 October 2013
Line 1:		Line 1:
			(First draft in by --[[User:Mlforcada\|Mlforcada]] 08:03, 27 October 2013 (UTC))

	;Organisation id*		;Organisation id*

@@ Line 63: / Line 63: @@
 ;Please tell us about how your organisation has prepared for Google Code-in, including what (and how many) mentors and organisation administrators have agreed to help, what your schedule and response time will be during the holidays (and otherwise during the contest period) and how you plan to deal with unresponsive mentors.*
-(Fran had a text about this ----~~)
+(Fran had a text about this --[[User:Mlforcada|Mlforcada]] 07:44, 27 October 2013 (UTC))
 ;Please include a link to the logo you would like to use if your org is chosen as a mentoring org for 2013. This allows us to post the logos of the GCI 2013 mentoring orgs as soon as we announce them on November 1, 2013.*