1,079
edits
Difference between revisions of "Summer of Code/Application/2007"
Jump to navigation
Jump to search
Summer of Code/Application/2007 (view source)
Revision as of 14:55, 7 March 2007
, 14:55, 7 March 2007Changed section levels (to separate the actual application from the draft texts); added placeholds for the missing parts of the application
(Rearrange application) |
(Changed section levels (to separate the actual application from the draft texts); added placeholds for the missing parts of the application) |
||
| Line 49: | Line 49: | ||
* Project leads -- we currently have three, and they all are also represented in one of the above categories, but besides this organize and coordinate things, make decisions, solve disputes etc. (as one would expect) | * Project leads -- we currently have three, and they all are also represented in one of the above categories, but besides this organize and coordinate things, make decisions, solve disputes etc. (as one would expect) | ||
This structure enables us to be highly productive in a team of about 30 currently active developers (out of an all time pool of well over 60), who work together on a codebase exceeding 600,000 LOC. In addition we have many non-developer contributors, and a huge and highly active community. We are among the most active projects hosted on sourceforge.net -- well over 100,000 monthly downloads and ~9 millions project web hits per month speak for themselves, we think. | |||
=== What we hope to gain === | |||
TODO Q2 | |||
=== Our mentors === | |||
TODO Q12 & Q13 | |||
=== How we will deal with participants 'missing in action' === | |||
TODO Q14 & Q15 | |||
=== Integrating students with the community === | |||
TODO Q16 & Q17 | |||
=== 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? | |||
| Line 58: | Line 86: | ||
TODO: Answer the questions/points listed on http://code.google.com/support/bin/answer.py?answer=60303&topic=10727 | TODO: Answer the questions/points listed on http://code.google.com/support/bin/answer.py?answer=60303&topic=10727 | ||
== Abstract == | === Abstract === | ||
== Introduction == | === Introduction === | ||
* scummvm description and purpose (Q1) | * scummvm description and purpose (Q1) | ||
* scummvm hierachy | * scummvm hierachy | ||
| Line 67: | Line 95: | ||
LoC, # devs (active & all time), # ports, downloads (Q1) | LoC, # devs (active & all time), # ports, downloads (Q1) | ||
= | === SoC Participation Application === | ||
== SoC Participation Application == | |||
* participation statement. (Q3,4) | * participation statement. (Q3,4) | ||
* - what will scummvm gain? (Q2) | * - what will scummvm gain? (Q2) | ||
| Line 80: | Line 105: | ||
lively and large team interacting though mailing lists and irc. makes turnaround time between a question raised and possible answers very small. | lively and large team interacting though mailing lists and irc. makes turnaround time between a question raised and possible answers very small. | ||
== Mentors == | === Mentors === | ||
* Short bios for _sev, Fingolfin, Jubanka. (Q12,13) | * Short bios for _sev, Fingolfin, Jubanka. (Q12,13) | ||
In particular, we do not need a "normal" CV, we need something to support we can mentor students, eg. great familiarity with code etc, students (if applicable), actively helping new devs. trying to answer (Q13) implicitly. | In particular, we do not need a "normal" CV, we need something to support we can mentor students, eg. great familiarity with code etc, students (if applicable), actively helping new devs. trying to answer (Q13) implicitly. | ||
| Line 86: | Line 111: | ||
briefly reiterate each mentor's expertise. | briefly reiterate each mentor's expertise. | ||
== When things go wrong == | === When things go wrong === | ||
* Students. (Q14) | * Students. (Q14) | ||
* > Communication breakdown seldom occurs abruptly. Usually, a student losing interest will keep an ever lowering profile. The mentors will regularly query for status (at least once a week). When the student is in trouble, the mentros will go to lengths to support the student actively. The tasks will be planned ahead by the mentor, with informal interim reports (maybe) and milestones. Of course there may be RL problems prohibiting the continuation of the task (unpredictable). | * > Communication breakdown seldom occurs abruptly. Usually, a student losing interest will keep an ever lowering profile. The mentors will regularly query for status (at least once a week). When the student is in trouble, the mentros will go to lengths to support the student actively. The tasks will be planned ahead by the mentor, with informal interim reports (maybe) and milestones. Of course there may be RL problems prohibiting the continuation of the task (unpredictable). | ||
| Line 93: | Line 118: | ||
=== Draft === | ==== Draft ==== | ||
This section presents the overall strategy used to prevent students and mentors from dropping out of their tasks. | This section presents the overall strategy used to prevent students and mentors from dropping out of their tasks. | ||
=== Students === | ==== Students ==== | ||
There are two main reasons for a student to stop participating in the assigned task: | There are two main reasons for a student to stop participating in the assigned task: | ||
Loss of interest, and unforeseen difficulties. | Loss of interest, and unforeseen difficulties. | ||
| Line 116: | Line 141: | ||
Hopefully, this case will be identified through the frequent student-mentor communication. | Hopefully, this case will be identified through the frequent student-mentor communication. | ||
=== Mentors === | ==== Mentors ==== | ||
Of the two above mentioned cases, only the case of unpredictable circumstances, unrelated to the project, applies to the mentors. | Of the two above mentioned cases, only the case of unpredictable circumstances, unrelated to the project, applies to the mentors. | ||
When a mentor anticipates a period of unavailability, the student will be referred to another mentor and the administrator will be notified. | When a mentor anticipates a period of unavailability, the student will be referred to another mentor and the administrator will be notified. | ||
The students can always turn to the very active irc channel for both general and specific inquiries. | The students can always turn to the very active irc channel for both general and specific inquiries. | ||
Mentors will internally update their status, so no students get left alone if a mentor drops out. | Mentors will internally update their status, so no students get left alone if a mentor drops out. | ||