1,079
edits
(Added link to PostgeSQL 'good advice' for student applications) |
(→Introduction: added SoC application template from application page) |
||
Line 18: | Line 18: | ||
The PostgrSQL folks have some real good | The PostgrSQL folks have some real good | ||
[http://www.postgresql.org/developer/summerofcodeadvice.html Advice to Students on Submitting SoC Applications]. We recommand all students interested in applying with us (or any other SoC project, for that matter) to read this. | [http://www.postgresql.org/developer/summerofcodeadvice.html Advice to Students on Submitting SoC Applications]. We recommand all students interested in applying with us (or any other SoC project, for that matter) to read this. | ||
=== Student application template === | |||
The following was adapted from the FreeBSD [http://www.freebsd.org/projects/summerofcode.html Proposal Guidelines]. | |||
* '''Name''' | |||
* '''Email''' | |||
* '''Project Title''' | |||
* '''Possible Mentor''' (optional) | |||
* '''Benefits to the ScummVM Community''' - a good project will not just be fun to work on, but also generally useful to others. | |||
* '''Deliverables''' - It is very important to list quantifiable results here e.g. | |||
** "Improve X modules in ways Y and Z." | |||
** "Write 3 new man pages for the new interfaces." | |||
** "Improve test coverage by writing X more unit/regression tests." | |||
** "Improve performance in FOO by X%." | |||
* '''Project Schedule''' - How long will the project take? When can you begin work? | |||
* '''Availability''' - How many hours per week can you spend working on this? What other obligations do you have this summer? | |||
* '''Bio''' - Who are you? What makes you the best person to work on this project? | |||
== Generic infrastructure tasks == | == Generic infrastructure tasks == |
edits