Thunderbird/Documentation/2011ContribGoals
Contents
Goal Summary for Q1 2011
Goal | March 1 2011 |
3 KB contribs | 1 |
3 MDC contribs | 2 |
kitsune conversion | underway, on track |
streamlined processes | not started, post-kitsune |
Goal Summary for Q2 2011
- Documentation funnel
- Invitation to contribute should be prominent on every KB page when user is not logged in.
- After first-time user contributes to KB article, user gets a friendly thank-you note that encourages further involvement (assuming that user provided email address when they created their account).
Thunderbird Documentation Contributor Goals for 2011
A "contribution" consists of a single project, either a completely new article or a significant rewrite to an existing article. Editing and grammatical fixes don't really count (although a person who did a lot of small fixes would certainly count as a contributor).
General contribution notes
- Make it easy for people to contribute (be specific in our instructions regarding what needs to be done; offer a variety of small, manageable projects)
- Make sure that our project management / information architecture / infrastructure enables people to contribute effectively (usable wiki platforms; lightweight processes; access to help and encouragement)
- Make sure that contributors feel valued and recognized so that they continue to contribute
How do we get more people engaged?
Make it Easy
- Infrastructure: make it easy to use and robust
- Instructions: make it easy for users to find out what needs to be done; specific instructions
How do we make people in the community more effective?
- Improved information sharing: newsletter?
- Recognition: make sure that people feel valued
- Improve wiki platforms
Projects
Documentation Funnel
Present a single page that lists all the ways people can help. Within the documentation section make sure there are a variety of contribution projects to match various levels of technical expertise and areas of interest:
- contribute Knowledge Base articles
- work on the FLOSS Manual (or other third-party project)
- contribute a snippet
- extend the add-on tutorial
- etc
Implementation
- Q2 (after Sumomo moves to Kitsune)
- create the funnel page
- audit all the places where we ask for documentation help (blogs, wikis, corporate site); make sure these link to the funnel page
Infrastructure
Make sure that our infrastructure enables people to contribute effectively.
Implementation
- Q1: Switch to Kitsune wiki platform for Knowledge Base
- Q?: Switch to Kitsune wiki platform for MDC
Process
Make sure that our processes make it easy for people to contribute.
Implementation
- Q1: After switch to Kitsune wiki platform, revisit process for triggering knowledge base articles from Get Satisfaction topics.
- Q2: After switch to Kitsune, re-work comment section so that support requests are weeded out and KB article comments can be easily filtered to trigger KB article updates.
First-Time Contributors
Simple first-timer task (aka "the first hit"):
- User finds knowledge base article from web search, from link on support site, or from other site.
- User sees an invitation to contribute / edit article.
- User creates account then logs in.
- User edits article.
- User gets a friendly thank-you note that encourages further involvement.
Implementation
- Q2: Invitation should be prominent on every KB page when user is not logged in.
- Q2: After first-time user contributes to KB article, user gets a friendly thank-you note that encourages further involvement (assuming that user provided email address when they created their account).
Metrics
Knowledge Base contributors:
(or significant contributions of MDN-class material on non-Mozilla websites)
- 15 contributors
- Q1: 3
- Q2: 3
- Q3: 4
- Q4: 5
- 5 contributors who contribute more than 5 new articles or major re-writes
MDN contributors:
(or significant contributions of MDN-class material on non-Mozilla websites)
- 10 contributors
- Q1: 3
- Q2: 3
- Q3: 4
- Q4: 5
- 2 contributors who contribute more than 4 major pieces