Changes between Version 15 and Version 16 of SummerOfCodeOrgApplication
- Timestamp:
- Mar 11, 2010, 4:23:54 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SummerOfCodeOrgApplication
v15 v16 11 11 === Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? === 12 12 13 We apply again as we hope to get new features implemented in MacPorts. Also we intend to attract new developers to our project and its community. 14 15 ... 16 * MacPorts as interface between Mac OS X and the Linux/BSD Open Source world 17 ... 13 We apply again as we hope to get new features implemented 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 Mac OS X user. 18 14 19 15 === Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. === … … 61 57 === What is your plan for dealing with disappearing students? === 62 58 63 We require contact information from our students as part of the application. Students should report at least once a week their progress to their mentor. We leave it open which communication medium to be used as student and mentor should use what works best for both. We know from past experiences that a student can just disappear without any absence notice, but if this happens we will not let them pass midterm or the evaluation at the end. Of course we will make this clear from the very beginning of the program and students will be aware that they are required to report regularly.59 We require contact information from our students as part of the application. Students should report at least once a week their progress to their mentor. We leave it open which communication medium to be used as student and mentor should use what works best for both. We know from past experiences that a student can just disappear without any absence notice, but if this happens we will not let them pass midterm or the evaluation at the end. Of course we will make this clear from the very beginning of the program and students will be urged to do their regular reports. 64 60 65 61 === What is your plan for dealing with disappearing mentors? === … … 67 63 First of all our mentors from the past years will be around to introduce new mentors to the program. This will ensure that mentors are aware what is expected from them. 68 64 69 A disappearing mentor never really happened in the past for us, but there will always be other people to help out. If the student cannot reach their mentor, they should contact the organization administrator which will have more contact informations from them. As mentors are communicating among each other progress and problems of the students will be shared.65 A disappearing mentor never really happened in the past for us, but there will always be other people to help out. Usually we try to assign 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 informations. 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. 70 66 71 67 === What steps will you take to encourage students to interact with your project's community before, during and after the program? === 72 68 73 ... 74 * Requirements of contacting us before submitting an application 75 * Normal development process 76 * Own branch, but fully visible to community 77 * Comments from other developers to their commits 78 * Mailing list status reports? 79 ... 69 We like to make first contact with our students even before they submit their application. During the application phase we will refine and discuss the proposal with other developers. In the program, students are hold to the normal development process. They get their own branch to work on, but any commits are visible to the whole community. Anybody can express their critique on the student's work as replies to the commit emails, as we also do it in general development. Also for specific milestones in their roadmap, we like to see status reports to the public development mailing list. 80 70 81 71 === What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===