Contribute/Recruiting

Stewards

Vivien Jin and Kimber Schlegelmilch
Please note that this plan is mainly for College Recruiting

Identify Community

Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?

A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons.

Suggestion: Use the mozillians.org contributor directory to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the Mozillians dashboard will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.

Define Contribution Opportunities

Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?

A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for 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 could speak about our various teams and projects.

Attend conferences + interview -

Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.

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.