Confirmed users, Bureaucrats and Sysops emeriti
803
edits
Stewards/User Engagement: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? | Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? | ||
A: | A: In many cases, yes. We can identify the localizers who work on Firefox & You and Firefox Affiliates. We may need to identify key contributors to the Army of Awesome. | ||
Suggestion: Use the [http://www.mozillians.org 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. | Suggestion: Use the [http://www.mozillians.org 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. | ||
*Suggested tags: Firefox & You, Firefox Affiliates | |||
=Define Contribution Opportunities= | =Define Contribution Opportunities= | ||
| Line 15: | Line 17: | ||
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities? | Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities? | ||
A: | A: Yes and we are putting that 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. | 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. | ||
| Line 23: | Line 25: | ||
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing? | Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing? | ||
A: | A: The user engagement wiki https://wiki.mozilla.org/Engagement/User_Engagement as well as the interested in marketing auto-responder (Chelsea sends follow-up notes to promising submissions and the directs them to the right person within Mozilla) | ||
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. | 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. | ||
| Line 31: | Line 33: | ||
Q: What goals does your team have for bringing in new contributors and how can you measure if you are successful? | Q: What goals does your team have for bringing in new contributors and how can you measure if you are successful? | ||
A: | A: Need to firm up numbers, but can record #of affiliates, #of newsletter localizers, #of participants in Army of Awesome, #of follow ups to the marketing autoresponder | ||
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. | 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. | ||