Google Summer of Code/Application 2019 - Revision history

Francis Tyers: /* How many potential mentors have agreed to mentor this year? */

2019-02-05T06:02:23Z

How many potential mentors have agreed to mentor this year?

Francis Tyers: /* How will you keep mentors engaged with their students? */

2019-02-04T17:02:58Z

How will you keep mentors engaged with their students?

Francis Tyers: /* How many potential mentors have agreed to mentor this year? */

2019-02-04T16:55:41Z

How many potential mentors have agreed to mentor this year?

Francis Tyers: /* How many potential mentors have agreed to mentor this year? */

2019-02-04T16:26:13Z

How many potential mentors have agreed to mentor this year?

Francis Tyers: /* How many potential mentors have agreed to mentor this year? */

2019-02-04T02:40:53Z

How many potential mentors have agreed to mentor this year?

Francis Tyers: /* Long Description */

2019-02-04T02:33:12Z

Long Description

Francis Tyers: /* Where does your source code live? */

2019-02-04T02:32:02Z

Where does your source code live?

Francis Tyers: /* How many potential mentors have agreed to mentor this year? */

2019-02-04T01:17:49Z

How many potential mentors have agreed to mentor this year?

Francis Tyers: /* How many potential mentors have agreed to mentor this year? */

2019-02-04T01:02:04Z

How many potential mentors have agreed to mentor this year?

Mlforcada: /* Why does your org want to participate in Google Summer of Code? */

2019-02-03T17:10:42Z

Why does your org want to participate in Google Summer of Code?

@@ Line 82: / Line 82: @@
 * Memduh
 * Sardana
+* Unhammer
 == How will you keep mentors engaged with their students? ==

← Older revision		Revision as of 17:02, 4 February 2019
Line 86:		Line 86:


	We select our mentors among very active developers, with long-term commitment to this 13-year-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 most of them have been embedded in our community for ~~yers~~. However, there is always the possibility that some problem comes up, so we also assign back-up mentors to all students, in many cases more than one back-up. If a mentor cannot continue for whatever reason, one of the backup co-mentors will take over, and one of the three organisation administrators (themselves experienced GSoC mentors) will take on the role of second backup mentor.		We select our mentors among very active developers, with long-term commitment to this 13-year-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 most of them have been embedded in our community for years. However, there is always the possibility that some problem comes up, so we also assign back-up mentors to all students, in many cases more than one back-up. If a mentor cannot continue for whatever reason, one of the backup co-mentors will take over, and one of the three organisation administrators (themselves experienced GSoC mentors) will take on the role of second backup mentor.

	== How will you help your students stay on schedule to complete their projects? ==		== How will you help your students stay on schedule to complete their projects? ==

@@ Line 81: / Line 81: @@
 * Sevilay
 * Memduh
+* Sardana
 == How will you keep mentors engaged with their students? ==

@@ Line 80: / Line 80: @@
 * Sushain
 * Sevilay
+* Memduh
 == How will you keep mentors engaged with their students? ==

@@ Line 79: / Line 79: @@
 * Mikel
 * Sushain
+* Sevilay
 == How will you keep mentors engaged with their students? ==

@@ Line 45: / Line 45: @@
 Apertium uses a language-independent specification, to allow for the ease of contributing to Apertium, more efficient development, and enhancing the project's overall growth.
-At present, Apertium has released more than 40 stable language pairs, delivering fast translation with reasonably intelligible results. Being an open-source project, Apertium provides tools for potential developers to build their own language pair and contribute to the project.
+At present, Apertium has released more than 40 stable language pairs, delivering fast translation with reasonably intelligible or excellent results depending on the language pair. Being an open-source project, Apertium provides tools for potential developers to build their own language pair and contribute to the project.
 == Application Instructions ==

← Older revision		Revision as of 02:32, 4 February 2019
Line 119:		Line 119:

	[http://github.com/apertium http://github.com/apertium] (and some of it still in [http://sf.net/projects/apertium http://sf.net/projects/apertium])		[http://github.com/apertium http://github.com/apertium] (and some of it still in [http://sf.net/projects/apertium http://sf.net/projects/apertium])


			[[Category:Google Summer of Code\|Application 2019]]

@@ Line 74: / Line 74: @@
 == How many potential mentors have agreed to mentor this year? ==
+* Fran
+* Jonathan
+* Mikel
 == How will you keep mentors engaged with their students? ==

@@ Line 72: / Line 72: @@
 Apertium loves less-resourced languages and GSoC gives an opportunity for computer-literate students speaking them to generate FOS language technologies for them.
 Apertium will gain: more students getting to know FOS software and the ethos that comes with it, contributing to it and, very especially students who are passionate about languages and computers.
-This part does not fit:
-GSoC has allowed Apertium to open many new avenues of development over the last years. GSoC 2019 will give Apertium a unique opportunity to concentrate on the most successful and the most promising paths, and the ideas page reflects this.
 == How many potential mentors have agreed to mentor this year? ==