Changes between Version 41 and Version 42 of SummerOfCodeOrgApplication
- Timestamp:
- Mar 29, 2013, 6:50:53 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SummerOfCodeOrgApplication
v41 v42 24 24 25 25 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 toattract new developers to our project and its26 We apply once more as we hope to implement new features in MacPorts 27 and attract new developers to our project and its 28 28 community. With new feature additions and enhancements to our 29 29 components (e.g. our GUI), we hope to become more user-friendly for … … 39 39 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.:: 40 40 {{{#!div class="compact" 41 MacPorts has taken part multiple times in the program since 2007 and42 greatly appreciates those contributions.Most of our students completed43 their projects successfully . We had previous GSoC students coming back41 MacPorts has participated multiple times since 2007. 42 Most of our students completed 43 their projects successfully, and we greatly appreciate those contributions. We had previous GSoC students coming back 44 44 as mentors in the following years; for example, our backup administrator 45 45 was a student for our organization back in GSoC 2011. … … 72 72 What criteria did you use to select the mentors? Please be as specific as possible.:: 73 73 {{{#!div class="compact" 74 Criteria for mentors is based on the mentor’svisible experience in the75 MacPorts internals. Since Tcl/Tk with namespaces will confuse new76 people,having mentors that know their way around is key to successfully74 Criteria for mentors is based on visible experience in the 75 MacPorts internals. Since Tcl/Tk with namespaces is likely to be new territory for newcomers, 76 having mentors that know their way around is key to successfully 77 77 planning our projects and guiding students to completion. 78 78 … … 96 96 What is your plan for dealing with disappearing students? Please be as specific as possible.:: 97 97 We require contact information from our students as part of the 98 application. Students shouldreport their progress to their mentor98 application. Students will report their progress to their mentor 99 99 at least once a week, via whichever communication medium works best 100 for both. We know from past experiences that a student can just101 disappear without anynotice, but if this happens we will not let100 for both. We know from past experiences that a student can 101 disappear without notice, but if this happens we will not let 102 102 them pass the midterm or final evaluation. We will make this clear 103 103 from the start, and students will be urged to maintain regular … … 106 106 What is your plan for dealing with disappearing mentors? Please be as specific as possible.:: 107 107 {{{#!div class="compact" 108 First of all, our mentors from the past years will be aroundto assist109 new mentors 'introduction to the program. This will ensure that mentors108 Our mentors from the past years will be available to assist 109 new mentors’ introduction to the program. This will ensure that mentors 110 110 know what is expected from them. 111 111 … … 115 115 116 116 We’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. 117 about progress and problems of their students, allowing for a clean failover to 118 another mentor. This also helps with setting expectations and making evaluations. 120 119 121 120 Projects will usually have multiple mentors, to provide redundancy if 122 121 one disappears. If a student cannot reach any of their mentors, they 123 122 should contact an organization administrator, who will have more contact 124 information. If somehowthat fails, they should post to the development125 mailing list, to send peopleafter myself and the backup admin.123 information. If that fails, they should post to the development 124 mailing list, to send others after myself and the backup admin. 126 125 }}} 127 126 … … 131 130 application, via IRC or on our mailing list. During the application 132 131 phase we will refine and discuss proposals with other developers. In the 133 program, students participate in thenormal development process: They132 program, students participate in our normal development process: They 134 133 get their own Subversion branch to work on, all their commits are 135 134 publicly viewable, and any member of the MacPorts community can provide … … 140 139 of open source development. 141 140 142 As we let students work as one of the organization’s developers, we look141 As we let students work as one of the project’s developers, we look 143 142 forward to their continued development of MacPorts after GSoC concludes. 144 143 Like any other developer, they will get regular commit privileges to