Community:SummerOfCode07: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
Projects with a confirmed mentor and approved by the Mozilla project SoC administrator will be moved to [[SummerOfCode07]]. Potential students should look at that page to find project ideas for which we'd like submissions.


Just getting started with brainstorming for ideas, and building a suggested project list for this year.
==Ground Rules==


For information on project from last year see http://wiki.mozilla.org/Community:SummerOfCode06
* '''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.
 
==Suggestion List==
 
[http://wiki.mozilla.org/Community:SummerOfCode06 Last year' ideas]
 
Please use this general format for submitting ideas.
{| border="1" cellpadding="3" width="100%" valign="top"
|- align="center"
| style="background-color: #efefef;" | '''Title'''
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc'''
| style="background-color: #efefef;" | '''Reporter'''
| style="background-color: #efefef;" | '''Mentor(s)'''
| style="background-color: #efefef;" | '''Comments'''
|-
| valign="top" |
| valign="top" |
| valign="top" |
| valign="top" |
| valign="top" |
|-
|}

Revision as of 13:51, 12 March 2007

Projects with a confirmed mentor and approved by the Mozilla project SoC administrator will be moved to SummerOfCode07. Potential students should look at that page to find project ideas for which we'd like submissions.

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.

Suggestion List

Last year' ideas

Please use this general format for submitting ideas.

Title Abstract - links to details/bugs/etc Reporter Mentor(s) Comments