Changes between Version 36 and Version 37 of SummerOfCodeOrgApplication


Ignore:
Timestamp:
Mar 22, 2013, 12:24:11 AM (12 years ago)
Author:
larryv (Lawrence Velázquez)
Comment:

editing

Legend:

Unmodified
Added
Removed
Modified
  • SummerOfCodeOrgApplication

    v36 v37  
    1212
    1313 Describe your organization.::
    14     MacPorts was created in 2002 and is a ports collection and packaging system for OS X. We have an ever-growing collection of ports (currently over 16500), 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 OS X, making it a primary interface between OS X and the rest of the open source world.
     14    MacPorts is a ports collection and packaging system for OS X. Created in 2002 as DarwinPorts, we have an ever-growing collection of ports (currently over 16500), many of which accept multiple configuration variants. MacPorts is one of the primary means of building and installing open source software on OS X, making it an important interface between OS X and the rest of the open source world.
    1515
    1616 Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?::
    17     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 and further increase the quality of our packages. Some big goals this year are minimizing MacPorts' dependency on Xcode since we can now provide pre-built binaries and Apple now provides a standalone compiler installer and improvements to the dependency resolution.
     17    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 and further increase the quality of our packages. Some big goals this year are improvements to dependency resolution and minimizing MacPorts' dependency on Xcode (since we now provide pre-built binaries, and Apple now provides standalone CLI tools).
    1818
    1919 Has your organization participated in past Google Summer of Codes? (yes/no)::
     
    2222 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.::
    2323    {{{#!div class="compact"
    24 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.
     24MacPorts 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.
    2525
    2626* 2007: 2 pass / 1 fail
     
    6565First 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.
    6666
    67 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.
     67A disappearing mentor has occurred once, when we also had a disappearing student. When the mentor disappeared, another mentor—who soon after actually became a MacPorts manager—stepped in to cover.
    6868
    6969We'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.