Google Summer of Code/Application 2022 - Revision history

Firespeaker: /* Mentors */

2022-02-21T15:31:39Z

Mentors

Firespeaker: /* Ideas list */

2022-02-21T14:34:15Z

Ideas list

Firespeaker: /* Mentors */

2022-02-21T14:33:11Z

Mentors

Popcorndude: /* Mentors */ add people who agreed to mentor on irc

2022-02-21T13:20:29Z

Mentors: add people who agreed to mentor on irc

Popcorndude: /* Mentors */

2022-02-21T13:11:20Z

Mentors

Xavivars: /* Mentors */

2022-02-21T13:03:28Z

Mentors

Xavivars: /* Mentors */

2022-02-21T11:49:25Z

Mentors

Xavivars: /* Mentors */

2022-02-21T07:05:01Z

Mentors

Xavivars at 07:04, 21 February 2022

2022-02-21T07:04:17Z

Xavivars: /* Mentors */

2022-02-21T07:02:21Z

Mentors

@@ Line 94: / Line 94: @@
 * nlhowell
 * Sevilay
+* Hèctor (if relevant project)
 (add your names here!)

@@ Line 81: / Line 81: @@
 === Ideas list ===
-(url)
+https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code
 === Mentors ===

@@ Line 92: / Line 92: @@
 * Unhammer
 * nlhowell
+* Sevilay
 (add your names here!)

@@ Line 90: / Line 90: @@
 * Marc Riera
 * Daniel Swanson
+* Unhammer
+* nlhowell
 (add your names here!)

@@ Line 89: / Line 89: @@
 * Xavi Ivars
 * Marc Riera
+* Daniel Swanson
 (add your names here!)

@@ Line 86: / Line 86: @@
 (How many Mentors does your Organization have available to participate in this program?)
-- Jonathan, ... (add your names here!)
+* Jonathan
-- Xavi Ivars
+* Xavi Ivars
+(add your names here!)
 === Program Retention Survey ===

@@ Line 70: / Line 70: @@
 === How will you get your GSoC contributors involved in your community during GSoC? ===
-First, we encourage all prospective contributors to visit our IRC channel (freenode.net#apertium) 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, contributors 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 contributors 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 contributors on a daily basis and give them suggestions and advice when they get stuck.
+First, we encourage all prospective contributors to visit our IRC channel (irc.oftc.net#apertium) 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, contributors 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 contributors 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 contributors on a daily basis and give them suggestions and advice when they get stuck.
 === Anything else we should know? (optional) ===