|
|
| Line 1: |
Line 1: |
| = Winter Of Security 2017 =
| |
| [[File:WinterOfSecurity_logo_light_horizontal.png|right|500px]]
| |
| The Winter of Security (MWOS) is a program organized by [[Security|Mozilla's Security teams]] to involve students with Security projects. Students who have to perform a semester project as part of their university curriculum can apply to one of the MWOS project. Projects are guided by a Mozilla Adviser, and a University Professor. Students are graded by their University, based on success criteria identified at the beginning of the project. Mozilla Advisers catch up weekly with students, typically via video chat, and provide ongoing mentorship for the projects.
| |
|
| |
|
| Projects are focused on building security tools, and students are expected to write code which must be released as Open Source. Universities are free to specify their own requirements to projects, such as written reports. Mozilla does not influence the way grades are allocated, but advisers will provide any information professors need in order to grade their students.
| |
|
| |
| Note on language: English is required for code comments and documentation, but not for interactions between students and advisers. Advisers who speak the same language as their students are encouraged to interact in that language.
| |
|
| |
| Contact us on [[IRC|irc.mozilla.org]] in the '''#security''' channel if you have questions.
| |
|
| |
| == Selection process ==
| |
|
| |
| Projects are assigned to groups of students. Groups are defined by the universities, and can be of any size between 1 and 4 students. The selection process is open to all students in undergraduate/license and graduate/master programs. A group applies to up to 3 projects by submitting an application that contains:
| |
| * the names of the projects the team is applying to
| |
| * team introduction and motivation (max 1000 characters)
| |
| * presentation of the university program (max 500 characters)
| |
| * short description of each team member (skills, interest, ...) (max 500 character for each team member)
| |
| * links to relevant resources (university website, resumes, ...)
| |
|
| |
| Applications will be accepted from Monday 14th August. (Link to application form will be posted here then).
| |
|
| |
| == Timeline ==
| |
|
| |
| We will be opening the program for applications on August 14th, closing the application process on September 15th, and announcing results on September 30th.
| |
|
| |
| The students and their professor can decide on the timeline, and make sure that it fits well with other classes.
| |
| Ideally, projects should not take more than 6 months from start to finish.
| |
|
| |
| Mozilla advisors will be available weekly on video (Vidyo, Google Hangout or Skype) to discuss progress and roadblocks, and provide help. Professors can set intermediary deadlines if needed, and have complete control over the grading of their students.
| |