Revision 1 as of 2017-09-01 16:41:28
added "#language en"
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
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 interns 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 an intern to judge whether they want 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 applicants, 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 if you have already mentored a project before, but it is very recommended. Secondary mentors do not need to be as knowledgeable as the first one in the project, but they should be available to help the intern if they are 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 interns do not have as much experience as the mentor.
What the intern will learn: At least 2-3 lines telling the applicants the skills they will develop and how they will improve Debian. Do not focus on the technologies, rather use something that could motivate the prospective interns to take on your project.
Application tasks: some test tasks that you want your applicants to complete during the application process. This helps us make sure the applicants are motivated to do the project, and to assess mentor/intern communication during the application step.
Related projects: links to some existing projects that are related.