Contribute/Recruiting
|
THIS PAGE MAY BE OUTDATED |
| This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution until this flag has been lifted. Help by editing the article, or discuss its contents on the talk page. |
Contents
Stewards
Vivien Jin and Kimber Schlegelmilch
Please note that this plan is mainly for College Recruiting
Identify Community
Paid Staff on the University Recruiting Team: Kimber, Jill, and Vivien
Volunteers: our intern alumni
Define Contribution Opportunities
Please note that the opportunities offered by the University Recruiting Team will be seasonal, mostly happening between September and March, with a much stronger need in the Fall.
Support Recruitment Activities
1. Intern Alumni or Student Rep: up to 4 positions available to build Mozilla presence at new universities (Oxford, Cambridge, INSA Lyon, and University Politehnica of Bucharest).
2. Mozilla Evangelists: We would love contributors to help host workshops, take on the role of technical evangelists during campus events, facilitate tech talks at universities, act as a mentor for university capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and can speak knowledgeably about our various teams and projects.
3. Mozilla Reps: help us identify new talent at conferences and hackathons, and help identify key rigorous courses at the university level
Strengthen our online presence
1. We need one Web Developer (perhaps a Web Designer) to give college.mozilla.org a new look
2. We need one web Administrator to maintain our web content and keep it interactive (bug of the month, algorithms problems, organize online competing events)
Map Contribution Paths
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities.
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy.
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?
- create some sort of process for new contributors to get up to speed with our college recruiting needs
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.
Establish Goals and Metrics
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?
We don't have any external participation for our team at this point.
Goals for Q1:
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)
2) Identify what opportunities would be available for the Student Reps
3) Identify location of potential contributors
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)
5) Identify Student Reps for our tier1 universities
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.
