Changes between Version 41 and Version 42 of SummerOfCodeOrgApplication


Ignore:
Timestamp:
Mar 29, 2013, 6:50:53 AM (11 years ago)
Author:
larryv (Lawrence Velázquez)
Comment:

11th hour editing

Legend:

Unmodified
Added
Removed
Modified

  • SummerOfCodeOrgApplication

    v41 v42  
    2424
    2525 Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?::
    26     We apply once more as we hope to implement new features in MacPorts.
    27     We also intend to attract new developers to our project and its
     26    We apply once more as we hope to implement new features in MacPorts
     27    and attract new developers to our project and its
    2828    community. With new feature additions and enhancements to our
    2929    components (e.g. our GUI), we hope to become more user-friendly for
    … …  
    3939 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.::
    4040    {{{#!div class="compact"
    41 MacPorts has taken part multiple times in the program since 2007 and
    42 greatly appreciates those contributions. Most of our students completed
    43 their projects successfully. We had previous GSoC students coming back
     41MacPorts has participated multiple times since 2007.
     42Most of our students completed
     43their projects successfully, and we greatly appreciate those contributions. We had previous GSoC students coming back
    4444as mentors in the following years; for example, our backup administrator
    4545was a student for our organization back in GSoC 2011.
    … …  
    7272 What criteria did you use to select the mentors? Please be as specific as possible.::
    7373        {{{#!div class="compact"
    74 Criteria for mentors is based on the mentor’s visible experience in the
    75 MacPorts internals. Since Tcl/Tk with namespaces will confuse new
    76 people, having mentors that know their way around is key to successfully
     74Criteria for mentors is based on visible experience in the
     75MacPorts internals. Since Tcl/Tk with namespaces is likely to be new territory for newcomers,
     76having mentors that know their way around is key to successfully
    7777planning our projects and guiding students to completion.
    7878
    … …  
    9696 What is your plan for dealing with disappearing students? Please be as specific as possible.::
    9797    We require contact information from our students as part of the
    98     application. Students should report their progress to their mentor
     98    application. Students will report their progress to their mentor
    9999    at least once a week, via whichever communication medium works best
    100     for both. We know from past experiences that a student can just
    101     disappear without any notice, but if this happens we will not let
     100    for both. We know from past experiences that a student can
     101    disappear without notice, but if this happens we will not let
    102102    them pass the midterm or final evaluation. We will make this clear
    103103    from the start, and students will be urged to maintain regular
    … …  
    106106 What is your plan for dealing with disappearing mentors? Please be as specific as possible.::
    107107    {{{#!div class="compact"
    108 First of all, our mentors from the past years will be around to assist
    109 new mentors' introduction to the program. This will ensure that mentors
     108Our mentors from the past years will be available to assist
     109new mentors’ introduction to the program. This will ensure that mentors
    110110know what is expected from them.
    111111
    … …  
    115115
    116116We’ve made it a rule that mentors will communicate among each other
    117 about progress and problems of the student, ensuring a clean failover to
    118 another mentor. This also helps with evaluation judgement and gauging
    119 expectations.
     117about progress and problems of their students, allowing for a clean failover to
     118another mentor. This also helps with setting expectations and making evaluations.
    120119
    121120Projects will usually have multiple mentors, to provide redundancy if
    122121one disappears. If a student cannot reach any of their mentors, they
    123122should contact an organization administrator, who will have more contact
    124 information. If somehow that fails, they should post to the development
    125 mailing list, to send people after myself and the backup admin.
     123information. If that fails, they should post to the development
     124mailing list, to send others after myself and the backup admin.
    126125}}}
    127126
    … …  
    131130application, via IRC or on our mailing list. During the application
    132131phase we will refine and discuss proposals with other developers. In the
    133 program, students participate in the normal development process: They
     132program, students participate in our normal development process: They
    134133get their own Subversion branch to work on, all their commits are
    135134publicly viewable, and any member of the MacPorts community can provide
    … …  
    140139of open source development.
    141140
    142 As we let students work as one of the organization’s developers, we look
     141As we let students work as one of the project’s developers, we look
    143142forward to their continued development of MacPorts after GSoC concludes.
    144143Like any other developer, they will get regular commit privileges to