Changes between Version 32 and Version 33 of SummerOfCodeOrgApplication

Timestamp:

Mar 21, 2013, 7:02:30 PM (11 years ago)

Author:

nerdling (Jeremy Lavergne)

Comment:

--

SummerOfCodeOrgApplication

@@ -15 +15 @@
 
  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 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.
+    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 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. The big goal this year is to minimize MacPorts' dependency on Xcode since we can now provide pre-built binaries and Apple now provides a standalone compiler installer.
 
  Has your organization participated in past Google Summer of Codes? (yes/no)::
@@ -22 +22 @@
  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 as mentors in the following years. For example, our backup administrator for this year was a student for our organization back in GSoC 2011.
+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 was a student for our organization back in GSoC 2011.
 
 * 2007: 2 pass / 1 fail
@@ -50 +50 @@
 
  What criteria did you use to select the mentors? Please be as specific as possible.::
-    Our mentors are active developers from the community. Most of the mentors proposed ideas we list [SummerOfCode#Tasks on our ideas page] and are therefore familiar with the topics. We will make sure that the mentor for a specific project will have the necessary knowledge in the particular problem domain. Our organization administrator has served in this job for two years already and also has experience as a previous mentor/co-mentor.
+        {{{#!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 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 implemented many new features in the base code. He can also be influential in helping get people setup for editing tcl/tk if they're new to it, since he went through it! Clemens took backup admin when I moved from mentor to admin when Rainer was too busy 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/tk namespaces.
+}}}
 
  What is your plan for dealing with disappearing students? Please be as specific as possible.::
@@ -59 +65 @@
 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 occurred once, when we also had a disappearing student. When the mentor disappeared, another mentor—who sooner after 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 clean a clean failover to another mentor. This also helps with evaluation judgement and gauging expectations.
+
+In the event a mentor disappears 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 an organization administrator which will have more contact information, and if somehow that fails the mailing list to send people after myself and the backup admin.
 }}}