This page is for submitting ideas for Summer of Code projects for 2009.
Ground Rules
- Be specific. It's hard to understand the impact of, or the size of, vague proposals.
- Consider size. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
- Do your research. Support the idea with well-researched links.
- Don't morph other people's ideas. If you have a related idea, place it next to the existing one, or add a comment.
- Insert only your own name into the Mentor column, and then only if you are willing to take on the responsibility. Potential mentors sign up here.
- Check back regularly. The administrators may have questions about your idea that you will need to answer.
(More thoughts on making a good list)
Suggestion ListMozilla Platform
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Firefox
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Thunderbird
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Calendar
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Camino
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
SeaMonkey
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Bugzilla
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
L10n
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Firefox Support (Sumo)
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|
Rhino
| Title
|
Abstract - links to details/bugs/etc
|
Reporter
|
Mentor(s)
|
Comments
|