Contribute/Documentation: Difference between revisions
No edit summary |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| 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: Most of our most-active contributors are in Mozillians.org, tagged with either "mdn" or "developer documentation". We also recognize "significant" recent contributions in a bi-weekly "State of Docs" post on Hacks.mo. | ||
=Define Contribution Opportunities= | =Define Contribution Opportunities= | ||
| Line 15: | Line 13: | ||
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. For example, we have a [https://developer.mozilla.org/Project:en/Documentation_Wishlist Documentation Wishlist] on MDN. Also, we have [http://beta.elchi3.de/doctracker/#list=fx&version= a tool that tracks Firefox bugs with documentation impacts]. And we tag articles that need help, such as [https://developer.mozilla.org/Special:Tags?tag=NeedsTechnicalReview NeedsTechnicalReview] and [https://developer.mozilla.org/Special:Tags?tag=NeedsEditorialReview NeedsEditorialReview]. | ||
=Map Contribution Paths= | =Map Contribution Paths= | ||
| Line 27: | Line 23: | ||
'''Note:''' If you're interested in contributing to end-user documentation for Firefox, look under the [[Stewards/Support|Support]] area. | '''Note:''' If you're interested in contributing to end-user documentation for Firefox, look under the [[Stewards/Support|Support]] area. | ||
# [https://developer.mozilla.org/Special:UserRegistration Create an account on MDN]. Don't use a valuable password, because it will be emailed to you (platform limitation, sorry!). | |||
# See [https://developer.mozilla.org/Project:en/How_to_Help How to help] and [https://developer.mozilla.org/Project:en/Getting_started Getting started] for starting points. | |||
# Edit articles that need help. Look for tags like NeedsTechnicalReview or NeedsExample. Once the page is fixed, remove the tag. | |||
# Join the [http://www.mozilla.org/about/forums/#dev-mdc dev-mdc] forum (as a mailing list, Usenet group or Google group) for news and announcements, and drop into the #devmo channel on irc.mozilla.org for real-time help. | |||
=Establish Goals and Metrics= | =Establish Goals and Metrics= | ||
Q: | 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: | A: | ||
Possible metrics: | |||
* People who attempt to create an account on MDN | |||
** # of BrowserID confirmation emails sent for MDN | |||
** # of people who click confirmation link sent for MDN | |||
** # of BrowserID confirmations completed for MDN | |||
** # of new BrowserID logins on MDN (may be existing BrowserID users) | |||
* % of new accounts who make an edit immediately (<2 hours) | |||
* % of new account who make an edit soon (<7 days) | |||
* % of new accounts who edit their profile page(s) | |||
* # of new MDN accounts who also subscribe to dev-mdc (correlated with BrowserID) or join #devmo (measure how??) | |||
* Of people who created accounts N months ago, look for patterns in contributions and drop-offs. | |||
Latest revision as of 16:05, 11 May 2012
Steward
Janet Swisher
Identify Community
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?
A: Most of our most-active contributors are in Mozillians.org, tagged with either "mdn" or "developer documentation". We also recognize "significant" recent contributions in a bi-weekly "State of Docs" post on Hacks.mo.
Define Contribution Opportunities
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
A: Yes. For example, we have a Documentation Wishlist on MDN. Also, we have a tool that tracks Firefox bugs with documentation impacts. And we tag articles that need help, such as NeedsTechnicalReview and NeedsEditorialReview.
Map Contribution Paths
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
A:
Note: If you're interested in contributing to end-user documentation for Firefox, look under the Support area.
- Create an account on MDN. Don't use a valuable password, because it will be emailed to you (platform limitation, sorry!).
- See How to help and Getting started for starting points.
- Edit articles that need help. Look for tags like NeedsTechnicalReview or NeedsExample. Once the page is fixed, remove the tag.
- Join the dev-mdc forum (as a mailing list, Usenet group or Google group) for news and announcements, and drop into the #devmo channel on irc.mozilla.org for real-time help.
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:
Possible metrics:
- People who attempt to create an account on MDN
- # of BrowserID confirmation emails sent for MDN
- # of people who click confirmation link sent for MDN
- # of BrowserID confirmations completed for MDN
- # of new BrowserID logins on MDN (may be existing BrowserID users)
- % of new accounts who make an edit immediately (<2 hours)
- % of new account who make an edit soon (<7 days)
- % of new accounts who edit their profile page(s)
- # of new MDN accounts who also subscribe to dev-mdc (correlated with BrowserID) or join #devmo (measure how??)
- Of people who created accounts N months ago, look for patterns in contributions and drop-offs.