[MacPorts] SummerOfCodeOrgApplication modified

[MacPorts]

Changed page "SummerOfCodeOrgApplication" by snc at macports.org from 129.137.206.15*
Page URL: <http://trac.macports.org/wiki/SummerOfCodeOrgApplication>
Diff URL: <http://trac.macports.org/wiki/SummerOfCodeOrgApplication?action=diff&version=18>
Revision 18

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCodeOrgApplication
=========================================================================
--- SummerOfCodeOrgApplication (version: 17)
+++ SummerOfCodeOrgApplication (version: 18)
@@ -6,15 +6,15 @@
 
 === Describe your organization. ===
 
-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.
+MacPorts is a ports collection and packaging system for Mac OS X. We have an ever-growing collection of ports (currently over 5600), many of which accept multiple configuration variants. MacPorts is one of the primary means by which open source software is compiled for and installed onto Mac OS X, making it 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? ===
 
-We apply again as we hope to get new features implemented in MacPorts. We also intend to attract new developers to our project and its community. With new feature additions and enhancements to our components (e.g. our GUI) we hope to become more user-friendly for the average Mac OS X user.
+We apply again as we hope to implement new features in MacPorts. We also intend to attract new developers to our project and its community. With new feature additions and enhancements to our components (e.g. our GUI) we hope to become more user-friendly for the average Mac OS X user.
 
 === Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===
 
-MacPorts is taking part in the program since 2007 and greatly appreciates those contributions. Most of our students completed their projects successfully. Last year we even had a previous GSoC student as a mentor in our team, which is great.
+MacPorts has taken part in the program since 2007 and greatly appreciates those contributions. Most of our students completed their projects successfully. Last year we even had a previous GSoC student as a mentor in our team, which is great.
 
 === 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. ===
 
@@ -56,21 +56,21 @@
 
 === 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 do their regular reports.
+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.
 
 === 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.
+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.
 
 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.
 
 === 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 hold 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 emails, as we also do it 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 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.
 
 === What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===
 
-As we let students work in the usual way of the organization's developers, we are looking forward to them sticking to MacPorts. They will be treated as any other developer, which gives them a good introduction for future work. In the past we also successfully motivated a previous 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. In the past we have successfully motivated a student to do mentoring for us.
 
 === Is there anything else you would like to tell the Google Summer of Code program administration team? ===
 

-------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 .