[MacPorts] SummerOfCodeOrgApplication modified

[MacPorts]

Page "SummerOfCodeOrgApplication" was changed by larryv at macports.org
Diff URL: <https://trac.macports.org/wiki/SummerOfCodeOrgApplication?action=diff&version=42>
Revision 42
Comment: 11th hour editing
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCodeOrgApplication
=========================================================================
--- SummerOfCodeOrgApplication (version: 41)
+++ SummerOfCodeOrgApplication (version: 42)
@@ -23,8 +23,8 @@
     world.
 
  Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?::
-    We apply once more as we hope to implement new features in MacPorts.
-    We also intend to attract new developers to our project and its
+    We apply once more as we hope to implement new features in MacPorts
+    and 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 OS X user and further increase the quality of our
@@ -38,9 +38,9 @@
 
  If you answered “yes” to the question above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year.::
     {{{#!div class="compact"
-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
+MacPorts has participated multiple times since 2007.
+Most of our students completed
+their projects successfully, and we greatly appreciate those contributions. We had previous GSoC students coming back
 as mentors in the following years; for example, our backup administrator
 was a student for our organization back in GSoC 2011.
 
@@ -71,9 +71,9 @@
 
  What criteria did you use to select the mentors? Please be as specific as possible.::
         {{{#!div class="compact"
-Criteria for mentors is based on the mentor’s visible experience in the
-MacPorts internals. Since Tcl/Tk with namespaces will confuse new
-people, having mentors that know their way around is key to successfully
+Criteria for mentors is based on visible experience in the
+MacPorts internals. Since Tcl/Tk with namespaces is likely to be new territory for newcomers,
+having mentors that know their way around is key to successfully
 planning our projects and guiding students to completion.
 
 Rainer was previously a GSoC mentor, and as a MacPorts manager he brings
@@ -95,18 +95,18 @@
 
  What is your plan for dealing with disappearing students? Please be as specific as possible.::
     We require contact information from our students as part of the
-    application. Students should report their progress to their mentor
+    application. Students will report their progress to their mentor
     at least once a week, via whichever communication medium 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
+    for both. We know from past experiences that a student can
+    disappear without notice, but if this happens we will not let
     them pass the midterm or final evaluation. We will make this clear
     from the start, and students will be urged to maintain regular
     communication.
 
  What is your plan for dealing with disappearing mentors? Please be as specific as possible.::
     {{{#!div class="compact"
-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
+Our mentors from the past years will be available to assist
+new mentors’ introduction to the program. This will ensure that mentors
 know what is expected from them.
 
 A disappearing mentor has occurred once, when we also had a disappearing
@@ -114,15 +114,14 @@
 actually became a MacPorts manager—stepped in to cover.
 
 We’ve made it a rule that mentors will communicate among each other
-about progress and problems of the student, ensuring a clean failover to
-another mentor. This also helps with evaluation judgement and gauging
-expectations.
+about progress and problems of their students, allowing for a clean failover to
+another mentor. This also helps with setting expectations and making evaluations.
 
 Projects will usually have multiple mentors, to provide redundancy if
 one disappears. If a student cannot reach any of their mentors, they
 should contact an organization administrator, who will have more contact
-information. If somehow that fails, they should post to the development
-mailing list, to send people after myself and the backup admin.
+information. If that fails, they should post to the development
+mailing list, to send others after myself and the backup admin.
 }}}
 
  What steps will you take to encourage students to interact with your project's community before, during and after the program?::
@@ -130,7 +129,7 @@
 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 proposals with other developers. In the
-program, students participate in the normal development process: They
+program, students participate in our normal development process: They
 get their own Subversion branch to work on, all their commits are
 publicly viewable, and any member of the MacPorts community can provide
 feedback by replying to the commit system’s emails. We also like
@@ -139,7 +138,7 @@
 people other than their mentors, we encourage them to work in the spirit
 of open source development.
 
-As we let students work as one of the organization’s developers, we look
+As we let students work as one of the project’s developers, we look
 forward to their continued development of MacPorts after GSoC concludes.
 Like any other developer, they will get regular commit privileges to
 help the project as they see fit; this also provides an introduction to
-------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 .