OLD PAGE, DON'T USE
PLEASE USE SummerOfCode2014/Projects INSTEAD
All the project descriptions should follow the following template.
Title of the project
Description of the project: At least 8-10 lines describing what the project is about; it is really important to have a good description if you want to attract students who are interested by the idea. This does not need to be a very technical description, but something that stirs interest and is complete enough to allow a student to judge whether s/he wants to work on the particular project or not. It does not need to be a complete road map either and does not need to explain all the tiny details and whatnot -- the mentor can tell that to interested students, or they can work out the exact details together.
Confirmed Mentor: Name of the mentor
How to contact the mentor: (mail, IRC, etc)
Confirmed co-mentors: It is not compulsory to have co-mentors, but it is a good idea. Secondary mentors do not need to be as knowledgeable as the first one in the project, but they should be available to help the student if s/he is stuck and the main mentor is busy / not available.
Deliverables of the project:
Desirable skills: Skills that the student has or is willing to develop. Remember, the students do not have as much experience as the mentor.
What the student will learn: At least 2-3 lines telling the students the skills they develop and how they will improve Debian. Do not focus on the technologies, rather use something that could motivate the prospective student to take your project.
Projects with confirmed mentors
Please keep this section clear of project ideas without confirmed mentors, to avoid any confusion for prospective students. Such projects should be published in the next section.
Projects ideas without confirmed mentors
Please find mentors for those projects. If no confirmed mentor shows up before the student application period starts, the project will not happen.