canmove, Confirmed users
7,088
edits
Contribute/Pilots: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
'''Finding:''' Having someone drive participation matters and we are able to intentionally deepen existing communities as well as broaden participation opportunities to new areas. | '''Finding:''' Having someone drive participation matters and we are able to intentionally deepen existing communities as well as broaden participation opportunities to new areas. | ||
'''Next steps:''' David is working with key teams that have low leverage, such as Firefox OS engineering, to identify people who can drive community building plans. | |||
==Contribution Pathways== | ==Contribution Pathways== | ||
| Line 32: | Line 34: | ||
'''Finding:''' Having clear contribution pathways and visibility into the health of those pathways matters and this becomes more important as we grow bigger. | '''Finding:''' Having clear contribution pathways and visibility into the health of those pathways matters and this becomes more important as we grow bigger. | ||
'''Next steps:''' We are putting plans together to get data about contribution pathways so that we can analyze what's working and where the roadblocks are (see below for more information about data plans). | |||
==Systems and Data== | ==Systems and Data== | ||
| Line 40: | Line 44: | ||
** Summary: There is very limited bandwidth in Webdev for monitoring contributions and issuing badges, so the Webdev Stewards created a way to automatically track relevant contribution activities on Mozilla's sites and to send that data directly to [http://badges.mozilla.org badges.mozilla.org]. | ** Summary: There is very limited bandwidth in Webdev for monitoring contributions and issuing badges, so the Webdev Stewards created a way to automatically track relevant contribution activities on Mozilla's sites and to send that data directly to [http://badges.mozilla.org badges.mozilla.org]. | ||
** Outcome: There are now [https://blog.mozilla.org/creative/2013/03/07/community-design-update-we-have-new-webdev-badges/ badges being issued to people who contribute to Mozilla's web sites] that are being issued without requiring any time from Webdev team members. | ** Outcome: There are now [https://blog.mozilla.org/creative/2013/03/07/community-design-update-we-have-new-webdev-badges/ badges being issued to people who contribute to Mozilla's web sites] that are being issued without requiring any time from Webdev team members. | ||
* Pilot: Building coding contribution dashboards | * Pilot: Building coding contribution dashboards | ||
** Summary: Josh Matthews and Seif Lofty created [https://docs.google.com/spreadsheet/ccc?key=0ApOXjgdvXthCdG9UY09MejgzSHNzN3dCQ0t2U01RRnc#gid=0 some] [https://docs.google.com/spreadsheet/ccc?key=0AiMUukRUspH3dFd1Q3U0SjltbzdVT0FBUEdQbFFMVGc#gid=0 prototypes] of dashboards that show activity of contributors involved with coding projects. | ** Summary: Josh Matthews and Seif Lofty created [https://docs.google.com/spreadsheet/ccc?key=0ApOXjgdvXthCdG9UY09MejgzSHNzN3dCQ0t2U01RRnc#gid=0 some] [https://docs.google.com/spreadsheet/ccc?key=0AiMUukRUspH3dFd1Q3U0SjltbzdVT0FBUEdQbFFMVGc#gid=0 prototypes] of dashboards that show activity of contributors involved with coding projects. | ||
** Outcome: This data allows the Coding Stewards to do things they hadn't been able to do before, such as put together a survey that could be sent to people who had started to contribute but didn't end up being successful. | ** Outcome: This data allows the Coding Stewards to do things they hadn't been able to do before, such as put together a survey that could be sent to people who had started to contribute but didn't end up being successful. | ||
* Pilot: Gathering contribution data | |||
** Summary: Josh, Pierros, Liz and Ricky are working on a [[Blackhole|prototype]] to gather contribution data from different systems into one place so that information is easily available to be accessed and analyzed. | |||
** Outcome: The initial work done on this is showing that we'll be able to build dashboards more quickly than before and it will give us a more holistic look at contributions than the current limited set of dashboards. | |||
'''Finding:''' Having the appropriate tools and data is essential for community builders to be effective and to make smart use of the limited time teams have to devote to community building. | '''Finding:''' Having the appropriate tools and data is essential for community builders to be effective and to make smart use of the limited time teams have to devote to community building. | ||
| Line 70: | Line 74: | ||
'''Finding:''' There is definitely a demand for learning more about community building and we have been able to create material that has been helpful and to identify ways to deliver this in a scalable way. | '''Finding:''' There is definitely a demand for learning more about community building and we have been able to create material that has been helpful and to identify ways to deliver this in a scalable way. | ||
'''Next steps:''' We are creating a second version of the [[Contribute/Workshops|community building workshops]] that will be easier for people to interact with and will be easier for people to deliver to their own teams and communities. | |||
==Recognition== | ==Recognition== | ||
| Line 84: | Line 90: | ||
'''Finding:''' Recognition efforts have been happening in an ad hoc way and we have been able to identify ways to make recognition efforts easier to implement and more effective. | '''Finding:''' Recognition efforts have been happening in an ad hoc way and we have been able to identify ways to make recognition efforts easier to implement and more effective. | ||
'''Next steps:''' We are pulling together documentation about best practices into a [[Contribute/Recognition|Recognition Guide]] that can be easily shared with teams. | |||