Changes between Version 18 and Version 19 of SummerOfCodeOrgApplication

Timestamp:

Mar 11, 2010, 6:44:08 PM (14 years ago)

Author:

nerdling (Jeremy Lavergne)

Comment:

--

SummerOfCodeOrgApplication

@@ -53 +53 @@
 === What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
 
-Our mentors are active developers from the community. Most of the mentors proposed ideas we list on our ideas page and are therefore familiar with the topics. We will make sure that the mentor for a specific project will have the necessary knowledge in the particular problem domain. Our organization administrator already took this job in 2009 and has experience as mentor/co-mentor in 2008/2009.
+Our mentors are active developers from the community. Most of the mentors proposed ideas we list [SummerOfCode#Tasks on our ideas page] and are therefore familiar with the topics. We will make sure that the mentor for a specific project will have the necessary knowledge in the particular problem domain. Our organization administrator is a veteran GSoC admin from 2009 and has experience as mentor/co-mentor in 2008/2009.
 
 === What is your plan for dealing with disappearing students? ===
 
-We require contact information from our students as part of the application. Students should report at least once a week their progress to their mentor. We leave it open which communication medium to be used as student and mentor should use what works best for both. We know from past experiences that a student can just disappear without any absence notice, but if this happens we will not let them pass midterm or the evaluation at the end. Of course we will make this clear from the very beginning of the program and students will be urged to maintain regular communication.
+We require contact information from our students as part of the application. Students should report their progress to their mentor at least once a week. We leave it open which communication medium to be used as student and mentor should use what works best for both. We know from past experiences that a student can just disappear without any notice, but if this happens we will not let them pass the midterm or final evaluation. Of course we will make this clear from the very beginning of the program and students will be urged to maintain regular communication.
 
 === What is your plan for dealing with disappearing mentors? ===
 
-First of all our mentors from the past years will be around to assist new mentors introduction to the program. This will ensure that mentors are aware what is expected from them.
+First of all our mentors from the past years will be around to assist new mentors' introduction to the program. This will ensure that mentors know what is expected from them.
 
-A disappearing mentor never really happened in the past for us, but there will always be other people to help out. Usually we try to assign more than one mentor to a project. If the student cannot reach any of their mentors, they should contact the organization administrator which will have more contact informations. The mentors will communicate among each other about progress and problems of the student, so that it would be possible for another mentor to take over.
+A disappearing mentor has not happened to us, but in the event it happens there will always be other people to help out, usually by  assigning more than one mentor to a project. If the student cannot reach any of their mentors, they should contact the organization administrator which will have more contact information. The mentors will communicate among each other about progress and problems of the student, so that it would be possible for another mentor to take over.
 
 === What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
 
-We like to make contact with our students even before they submit their application per IRC or on the mailing list. During the application phase we will refine and discuss the proposal with other developers. In the program, students are held to the normal development process. They get their own branch to work on, but any commits are visible to the whole community. Anybody can express their critique on the student's work as replies to the commit system's emails, as we also do in general development. Also for specific milestones in their roadmap, we like to see status reports to the public development mailing list. By requiring communication with other people than their respective mentor, we encourage them to work with the spirit of open source development.
+We like to make contact with our students even before they submit their application, via IRC or on our mailing list. During the application phase we will refine and discuss the proposal with other developers. In the program, students are held to the normal development process. They get their own svn branch to work on, and any commits are visible to the whole community. This way anybody can express their critique on the student's work as replies to the commit system's emails, as we also do in general development. Also for specific milestones in their roadmap, we like to see status reports to the public development mailing list. By requiring communication with other people than their respective mentor, we encourage them to work with the spirit of open source development.
 
 === What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===
 
-As we let students work as one of the organization's developers, we are looking forward to their continued development of MacPorts. They will be treated as any other developer, which gives them commit privileges to help the project as they see fit. This also provides an introduction to future work. In the past we have successfully motivated a student to do mentoring for us.
+As we let students work as one of the organization's developers, we are looking forward to their continued development of MacPorts. They will be treated as any other developer, which gives them commit privileges to help the project as they see fit. This also provides an introduction to future work. This can be seen in our successful motivation of a student to return as a mentor for us.
 
 === Is there anything else you would like to tell the Google Summer of Code program administration team? ===