[MacPorts] SummerOfCodeOrgApplication modified

[MacPorts]

Changed page "SummerOfCodeOrgApplication" by raimue at macports.org from 131.188.30.102*
Page URL: <http://trac.macports.org/wiki/SummerOfCodeOrgApplication>
Diff URL: <http://trac.macports.org/wiki/SummerOfCodeOrgApplication?action=diff&version=12>
Revision 12
Comment: Add some sentences and some points

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCodeOrgApplication
=========================================================================
--- SummerOfCodeOrgApplication (version: 11)
+++ SummerOfCodeOrgApplication (version: 12)
@@ -9,6 +9,8 @@
 MacPorts is a ports collection and packaging system for Mac OS X. We have a growing number of about 5600 ports currently, many of which accept multiple variants. MacPorts is one of the primary means by which open source software is compiled for and installed onto Mac OS X, and is thus a primary interface between Mac OS X and the rest of the open source world.
 
 === Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? ===
+
+...
 
 === Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===
 
@@ -54,11 +56,30 @@
 
 === 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 know from past experiences that a student can just disappear without a 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 aware that they are required to report back.
+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 aware that they are required to report regularly.
 
 === What is your plan for dealing with disappearing mentors? ===
+
+First of all our mentors from the past years will be around to introduce new mentors to the program. This will ensure that mentors are aware 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. If the student cannot reach their mentor, they should contact the organization administrator which will have more contact informations from them. As mentors are communicating among each other progress and problems of the students will be shared.
+
 === What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
+
+...
+ * Normal development process
+ * Own branch, but fully visible to community
+ * Comments from other developers to their commits
+ * Mailing list status reports?
+...
+
 === What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===
+
+...
+
 === Is there anything else you would like to tell the Google Summer of Code program administration team? ===
+
+...?
+
 === Backup organization administrator ===
 (required)

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on SummerOfCodeOrgApplication. If it was not you, please
report to .