From MozillaWiki
Jump to: navigation, search
Ambox outdated.png 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.


Stacy Martin, Alex Fowler and Ben Simon

Policy Contribute Group

Meetings every other Wednesday at 11 am pacific.

Action Plan




Potential Contributors

Active Contributors

Core Contributors

Background Information

Note: this background information came from initial discussions are a Privacy community building plan and will not necessarily be relevant to a more broadly scoped Policy community building plan.

Identify Community

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

A: As far as I know, our team has only paid staff. I received one contributor inquiry through the Student Reps program, but when I responded back, I didn't receive a response.

Suggestion: Use the 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: No, this is a great idea though and I will work on putting something together.

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?

A: Privacy is complex, but there are some industry resources, such as the International Association of Privacy Professionals, as well as several blogs, including our own. I can create a list of resources someone could use to learn about privacy. Also, on our team there are technical and non-technical projects. For example, someone more technical might want to contribute to Do Not Track.

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?

A: We are a small team, so my goal would be to bring in one contributor and then look at growing from there. I have talked to Alex about reaching out to privacy professionals through the International Association of Privacy Professionals (IAPP) and also through colleges with compliance or ethics programs. I would measure how many times we've reached out and through how many channels.

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.