[MacPorts] SummerOfCodeOrgApplication modified

Fri Mar 29 00:19:47 PDT 2013

Page "SummerOfCodeOrgApplication" was changed by larryv at macports.org
Diff URL: <https://trac.macports.org/wiki/SummerOfCodeOrgApplication?action=diff&version=46>
Revision 46
Comment: reformat
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCodeOrgApplication
=========================================================================

--- SummerOfCodeOrgApplication (version: 45)
+++ SummerOfCodeOrgApplication (version: 46)
@@ -26,25 +26,24 @@
 
  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
-    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
-    packages. Some big goals this year are improving dependency
-    resolution and minimizing MacPorts’ dependency on Xcode (since we
-    now provide pre-built binaries, and Apple now provides standalone
-    CLI tools).
+    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 packages. Some big goals
+    this year are improving dependency resolution and minimizing
+    MacPorts’ dependency on Xcode (since we now provide pre-built
+    binaries, and Apple now provides standalone CLI tools).
 
  Has your organization participated in past Google Summers of Code? (yes/no)::
     Yes.
 
  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 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.
+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.
 
 * 2007: 2 pass / 1 fail
 * 2008: 2 pass / 2 fail
@@ -73,23 +72,23 @@
 
  What criteria did you use to select the mentors? Please be as specific as possible.::
         {{{#!div class="compact"
-Criteria for mentors is based on visible experience in the
-MacPorts internals. Since Tcl 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.
+Criteria for mentors is based on visible experience in the MacPorts
+internals. Since Tcl 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
 great experience in our base code. Clemens was a GSoC student, and after
 completion of his project has stayed with us and worked extensively on
-MacPorts base. He can also be helpful in getting
-newcomers setup for developing in Tcl, since he went
-through it! Clemens assumed the backup administrator role when I moved from mentor to admin
-last year, and we’ve kept that structure this
-year. Lawrence is also contributing greatly to our base code,
-specifically ensuring packages are built with compilers they “support”.
-This is very helpful as some packages still don’t build right on Clang,
-or have legacy issues with old Apple GCC. His efforts allow MacPorts to
-switch out compilers based on their version for a given package.
+MacPorts base. He can also be helpful in getting newcomers setup for
+developing in Tcl, since he went through it! Clemens assumed the backup
+administrator role when I moved from mentor to admin last year, and
+we’ve kept that structure this year. Lawrence is also contributing
+greatly to our base code, specifically ensuring packages are built with
+compilers they “support”. This is very helpful as some packages still
+don’t build right on Clang, or have legacy issues with old Apple GCC.
+His efforts allow MacPorts to switch out compilers based on their
+version for a given package.
 
 All these mentors fill our desire to have people knowledgeable of
 navigating our base code, which uses Tcl.
@@ -97,33 +96,33 @@
 
  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 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
-    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.
+    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 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"
-Our mentors from the past years will be available to assist
-new mentors’ introduction to the program and ensure that mentors
-know what is expected from them.
+Our mentors from the past years will be available to assist new mentors’
+introduction to the program and ensure that mentors know what is
+expected from them.
 
 A disappearing mentor has occurred once, when we also had a disappearing
 student. When the mentor disappeared, another mentor—who soon after
 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 their students, allowing for a clean failover to
-another mentor. This also helps with setting expectations and making evaluations.
+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 that fails, they should post to the development
-mailing list, to send others 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?::
-------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 .
