Google Summer of Code/Application 2020 - Revision history

Firespeaker: /* Apertium profile (we have to provide one) */

2021-02-17T15:51:13Z

Apertium profile (we have to provide one)

Firespeaker: Undo revision 73131 by Firespeaker (talk)

2021-02-17T15:33:00Z

Undo revision 73131 by Firespeaker (talk)

Firespeaker: /* Application */

2021-02-17T15:32:32Z

Application

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

2020-02-08T20:46:18Z

How many potential mentors have agreed to mentor this year?

Firespeaker: /* How will you keep students involved with your community after GSoC? */

2020-02-05T03:28:15Z

How will you keep students involved with your community after GSoC?

Firespeaker: /* How will you get your students involved in your community during GSoC? */

2020-02-05T03:18:52Z

How will you get your students involved in your community during GSoC?

Firespeaker: /* How will you help your students stay on schedule to complete their projects? */

2020-02-05T03:16:37Z

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

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

2020-02-05T02:57:05Z

How will you keep mentors engaged with their students?

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

2020-02-05T02:51:57Z

How many potential mentors have agreed to mentor this year?

Firespeaker: /* Has your org been accepted as a mentor org in Google Summer of Code before? */

2020-02-04T18:47:44Z

Has your org been accepted as a mentor org in Google Summer of Code before?

@@ Line 62: / Line 62: @@
 Mailing list:  https://lists.sourceforge.net/lists/listinfo/apertium-stuff
+General email: apertium-contact@lists.sourceforge.net
 = Application =

@@ Line 104: / Line 104: @@
 Yes: 2009-2014, 2016-2019
-=== If your org has applied for GSoC before but not been accepted, select the years: ===
 == For each year your organization has participated, provide the counts of successful and total students. ==

@@ Line 104: / Line 104: @@
 Yes: 2009-2014, 2016-2019
+=== If your org has applied for GSoC before but not been accepted, select the years: ===
 == For each year your organization has participated, provide the counts of successful and total students. ==

@@ Line 82: / Line 82: @@
 * Aléssio
 * Daniel (tentative)
+* Sevilay
+* Tommi
 == How will you keep mentors engaged with their students? ==

@@ Line 97: / Line 97: @@
 == How will you keep students involved with your community after GSoC? ==
-We have found that the following has helped us have quite a high retention rate in previous years: Helping students out publishing papers for conferences, or assisting with academic work. Organising workshops (such as FreeRBMT) or courses (such as http://goo.gl/jzre7e) where students can present their work to the wider community. Encouraging students to get involved in mentoring themselves, through the Google Code-In programme. Passing on information about MSc and PhD positions, and academic and other grants.
+We have found that the following has helped us have quite a high retention rate in previous years: Helping students out publishing papers for conferences, or assisting with academic work.  Organising workshops (such as FreeRBMT) or courses (such as http://goo.gl/jzre7e) where students can present their work to the wider community.  Encouraging students to themselves get involved in mentoring, through the Google Code-In programme. Passing on information about MSc and PhD positions, and academic and other grants.
 == Has your org been accepted as a mentor org in Google Summer of Code before? ==

@@ Line 93: / Line 93: @@
 == How will you get your students involved in your community during GSoC? ==
-First, we encourage all of our students to visit our IRC channel (#apertium @ freenode.net) as often as possible, even before the start of the program, since that would help them find a suitable mentor and a useful project that they can work on. We advice them strongly to read our Wiki pages and manuals, use our system, try to break it and fix it, and finally tell us about it. As a result, students get familiar with Apertium before the coding period starts, which increases their chances of ending up with a successful project. In addition, we define coding challenges for each of the proposed projects, which serve both as an entry task, and as a means for getting our students familiar with Apertium and involved in our community in the early stages of the program. Finally, during the coding stage, we are available to talk to our students on a daily basis and give them suggestions and advice when they get stuck.
+First, we encourage all of our students to visit our IRC channel (#apertium @ freenode.net) as often as possible, even before the start of the program, since that will help them find a suitable mentor and a useful project that they can work on.  We advise them strongly to read our wiki pages and manuals, use our system, try to break it and fix it, and finally tell us about it.  As a result, students get familiar with Apertium before the coding period starts, which increases their chances of ending up with a successful project.  In addition, we define coding challenges for each of the proposed projects, which serve both as an entry task, and as a means for getting our students familiar with Apertium and involved in our community in the early stages of the program.  Finally, during the coding stage, we are available to talk to our students on a daily basis and give them suggestions and advice when they get stuck.
 == How will you keep students involved with your community after GSoC? ==

@@ Line 89: / Line 89: @@
 == How will you help your students stay on schedule to complete their projects? ==
-Apertium only accepts applications with a well-defined weekly schedule, with clear milestones and deliverables and, if possible, with a section on risk management (risks, their probability, their severity, and mitigating actions). Applications should also plan for holidays, exams, and other absences. Students will be encouraged to let us know if they need to reschedule or take a break if needed. Students may also need consultation when they are stuck, or personal matters interfere with their work: we will, as we have in the past, try our best to reach out for them, be open and friendly, and provide as much support as we can to help them out. We've been students too! Detailed scheduling will avoid both mentors and students wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), they will be contacted by the administrators. If silence persists, their task will be frozen and we will report to Google, to proceed according to the rules of GSoC.
+Apertium only accepts applications with a well-defined weekly schedule, with clear milestones and deliverables and, if possible, with a section on risk management (risks, their probability, their severity, and mitigating actions). Applications should also plan for holidays, exams, and other absences. Students will be encouraged to let us know if they need to reschedule or take a break if needed. Students may also need consultation when they are stuck, or personal matters interfere with their work: we will, as we have in the past, try our best to reach out for them, be open and friendly, and provide as much support as we can to help them out. We've been students too! Detailed scheduling will avoid both mentors and students wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), the student will be contacted by the administrators. If silence persists, their task will be frozen and we will report to Google, to proceed according to the rules of GSoC.
 == How will you get your students involved in your community during GSoC? ==

@@ Line 85: / Line 85: @@
 == How will you keep mentors engaged with their students? ==
+We select our mentors among very active developers, with long-term commitment to this 16-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 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? ==