[MacPorts] SummerOfCodeOrgApplication modified

[MacPorts]

Page "SummerOfCodeOrgApplication" was changed by raimue at macports.org
Diff URL: <https://trac.macports.org/wiki/SummerOfCodeOrgApplication?action=diff&version=28>
Revision 28
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCodeOrgApplication
=========================================================================
--- SummerOfCodeOrgApplication (version: 27)
+++ SummerOfCodeOrgApplication (version: 28)
@@ -26,7 +26,7 @@
 
 === Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===
 
-MacPorts has taken part in the program since 2007 and greatly appreciates those contributions. Most of our students completed their projects successfully. Once we even had a previous GSoC student as a mentor in our team, which is great.
+MacPorts has taken part multiple times in the program since 2007 and greatly appreciates those contributions. Most of our students completed their projects successfully. We had previous GSoC students coming back as mentors in the following years. For example, our backup administrator for this year was a student for our organization back in GSoC 2011.
 
 === If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006. ===
 
@@ -35,6 +35,7 @@
  * 2009: 2/2
  * 2010: 3/3
  * 2011: 3/3
+
 === What is the URL for your ideas page? ===
 
 http://trac.macports.org/wiki/SummerOfCode
@@ -49,7 +50,7 @@
 
 === Does your organization have an application template you would like to see students use? If so, please provide it now. ===
 
-[wiki:SummerOfCodeApplicationTemplate]
+Yes, this can be found in our wiki at https://trac.macports.org/wiki/SummerOfCodeApplicationTemplate
 
 === What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
 
@@ -63,13 +64,13 @@
 
 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 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.
+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, 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.
 
-As we let students work as one of the organization's developers, we are looking forward to their continued development of MacPorts even after the program concludes. They will be treated like any other developer, which means they get regular 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.
+As we let students work as one of the organization's developers, we are looking forward to their continued development of MacPorts even after the program concludes. They will be treated like any other developer, which means they get regular commit privileges to help the project as they see fit. This also provides an introduction to future work. The success of this method can be seen as multiple students returned as mentors in the following years.
 
 === If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===
 
@@ -81,8 +82,8 @@
 
 === Is there anything else you would like to tell the Google Summer of Code program administration team? ===
 
-Thanks for hosting the Google Summer of Code program again this year!
+Thanks for hosting another instance of Google Summer of Code! The MacPorts Project would really be glad to take part in this program once again this year.
 
 === Backup organization administrator ===
 
-William Siegrist, link_id: wsiegrist
+Clemens Lang, link_id: ?
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/SummerOfCodeOrgApplication>
MacPorts <http://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'SummerOfCodeOrgApplication' page.
If it was not you, please report to .