Google Summer of Code/Application 2016 - Revision history

Tino Didriksen: /* How many potential mentors have agreed to mentor this year? */

2016-02-18T16:23:19Z

How many potential mentors have agreed to mentor this year?

2016-02-15T09:01:10Z

Application instructions

2016-02-15T09:00:19Z

Long Description

2016-02-15T06:30:23Z

Thanks Raveesh and Jonathan!

2016-02-11T08:22:27Z

How many potential mentors have agreed to mentor this year?

2016-02-11T08:22:10Z

Google+ URL (optional)

2016-02-10T20:58:18Z

How will you keep mentors engaged with their students?

2016-02-10T17:16:38Z

2016-02-10T17:16:09Z

2016-02-10T17:15:07Z

If your org has applied for GSoC before but not been accepted, select the years:

@@ Line 92: / Line 92: @@
 * --[[User:Mlforcada|Mlforcada]] ([[User talk:Mlforcada|talk]]) 18:05, 10 February 2016 (CET)
 * --[[User:Unhammer|unhammer]] ([[User talk:Unhammer|talk]]) 09:22, 11 February 2016 (CET)
+* --[[User:Tino Didriksen|Tino Didriksen]] ([[User talk:Tino Didriksen|talk]]) 17:23, 18 February 2016 (CET)
 ==How will you keep mentors engaged with their students?==

@@ Line 46: / Line 46: @@
 # Be appropriate: Demonstrate you have a knowledge of Apertium, how it works and the problem it has that you'd like to solve.
 # Have a plan: Three months may seem like a long time, but it isn't. Provide a weekly plan with dates and deliverables. Leave time for getting familiar with the platform — ideally before, or in the community bonding period — and for documentation. If you plan to work on a language pair, make yourself familiar with testvoc and other quality controls, and factor those in. If you know of any breaks or absences beforehand, mention them and plan around them.
-# Get in contact ASAP!: We get lots of proposals: only a few are good. Contact your potential mentor as soon as possible: send your proposal to the mailing list, ask for feedback, and refine your application based on feedback. If you are remembered, you are more likely to be picked.
+# Get in contact ASAP!: We get lots of proposals: only a few are good. Contact your potential mentor as soon as possible: send your proposal to the mailing list, hang out on IRC, ask for feedback, and refine your application based on feedback. If you are remembered, you are more likely to be picked.
 #Read the Ideas Page! If you find yourself asking 'do you have any Java/Python/Fortran/x86 assembler projects...' -- you didn't read the ideas page. Read the ideas page.

@@ Line 33: / Line 33: @@
 ==Long Description==
-Apertium is a free/open-source machine translation platform, initially aimed at related-language pairs (such as Spanish–Catalan)  but which has been expanded to deal with more divergent language pairs (such as English-Catalan). The platform provides
+Apertium is a free/open-source machine translation platform, initially aimed at related-language pairs (such as Spanish–Catalan)  but which has been expanded to deal with more divergent language pairs (such as English-Catalan and even Basque→English). The platform provides
 # a language-independent machine translation engine
 # tools to manage the linguistic data necessary to build a machine translation system for a given language pair and
-# linguistic data for a growing number of language pairs.
+# linguistic data for a growing number of languages and language pairs
 =Proposals=

@@ Line 99: / Line 99: @@
 We select our mentors among very active developers, with long-term commitment to this decade-old project — they are people we know well and whom we have met face-to-face at conferences, workshops or even in daily life; some of them teach and do research at universities or work at companies using Apertium.
-For this reason, it is quite unlikely for mentors to disappear, since all of the mentors are known to us. However, there is always the possibility that some problem comes up, so we also assign backup mentors to all students, in many cases more than one backup. If a mentor cannot continue for whatever reason, one of the backup co-mentors will take over, and one of the organisation administrators will take on the role of second backup mentor.
+For this reason, it is quite unlikely for mentors to disappear, since of them are well embedded in our community. However, there is always the possibility that some problem comes up, so we also assign backup mentors to all students, in many cases more than one backup. If a mentor cannot continue for whatever reason, one of the backup co-mentors will take over, and one of the organisation administrators will take on the role of second backup mentor.
 ==How will you help your students stay on schedule to complete their projects?==

@@ Line 93: / Line 93: @@
 It would be nice to have every mentor sign here:
 * --[[User:Mlforcada|Mlforcada]] ([[User talk:Mlforcada|talk]]) 18:05, 10 February 2016 (CET)
+* --[[User:Unhammer|unhammer]] ([[User talk:Unhammer|talk]]) 09:22, 11 February 2016 (CET)
 ==How will you keep mentors engaged with their students?==

@@ Line 71: / Line 71: @@
 ==Google+ URL (optional)==
+https://plus.google.com/+ApertiumOrg
 ==Twitter URL (optional)==

@@ Line 146: / Line 146: @@
 * 2008
-== (another question I cannot add)==
+== (another question I cannot add due to Spam filtering)==
 We are not new, but we were not selected for 2015 after 6 years of participation.

@@ Line 147: / Line 147: @@
 We are not new, but we were not selected for 2015 after 6 years of participation.
-Spam filtering does not let me add the remaining sections --[[User:Mlforcada|Mlforcada]] ([[User talk:Mlforcada|talk]]) 18:10, 10 February 2016 (CET)
 ==Are you part of a foundation/umbrella organization?==