canmove, Confirmed users
868
edits
Contribute/Best Practices: Difference between revisions
no edit summary
Vineelreddyp (talk | contribs) |
Jennierose (talk | contribs) No edit summary |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 5: | Line 5: | ||
Local community leaders have been sharing their best practices at the [[Grow|Grow Mozilla meetings]] and the videos and slides from those are available here. | Local community leaders have been sharing their best practices at the [[Grow|Grow Mozilla meetings]] and the videos and slides from those are available here. | ||
* Mozilla Tunisia [http://mozilla-tunisia.org/growmozilla/growmozilla/#/ slides] | |||
* Mozilla Kenya ([https://wiki.mozilla.org/images/c/c9/Mozilla_kenya_best_pracrices.pdf slides from presentation at Grow Mozilla discussion on April 4, 2013]) | * Mozilla Kenya ([https://wiki.mozilla.org/images/c/c9/Mozilla_kenya_best_pracrices.pdf slides from presentation at Grow Mozilla discussion on April 4, 2013]) | ||
* Mozilla Hispano ([ | * Mozilla Hispano ([https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=SSeny16mxmV449Q video of Grow Mozilla discussion on Dec. 13, 2012]) (note to add start time in video) | ||
** Blogpost [ http://www.nukeador.com/09/12/2011/organizing-a-mozilla-community/ about organizing a Mozilla community] | ** Blogpost [http://www.nukeador.com/09/12/2011/organizing-a-mozilla-community/ about organizing a Mozilla community] | ||
==Provide Recognition== | ==Provide Recognition== | ||
| Line 33: | Line 34: | ||
* Ask someone to grab a download button if they're interested in marketing | * Ask someone to grab a download button if they're interested in marketing | ||
* Ask someone to do copy edits to a web / documentation page | * Ask someone to do copy edits to a web / documentation page | ||
* Ask someone to join a bug triage project: [[Bugmasters/Projects]] | |||
==Create a | ==Create a Task of Medium Complexity== | ||
Not every task needs to be bite-size. It's perfectly fine for a contributor to want to work on something more complicated, they just need to be given the tools to do so effectively. [http://www.joshmatthews.net/blog/2011/09/making-bugs-more-attractive-for-other-people-to-fix/ Mentored bugs] are great ways of introducing contributors to more complex bugs in a non-intimidating fashion. | Not every task needs to be bite-size. It's perfectly fine for a contributor to want to work on something more complicated, they just need to be given the tools to do so effectively. [[Good first bug]]s are tagged in Bugzilla, but still need quite a bit of setup before a beginning contributor can get started. And more difficult bugs tend to have mentors; [http://www.joshmatthews.net/blog/2011/09/making-bugs-more-attractive-for-other-people-to-fix/ Mentored bugs] are great ways of introducing contributors to more complex bugs in a non-intimidating fashion. | ||
When you’re marking a bug as being good for another person to work on, please take a few moments to dump your investigative work in the bug. Function names, MXR links, steps to reproduce, explanations of the problem and how it can be solved: these are the stepping stones that allow a contributor to start looking into how to solve the problem without waiting to get in contact with you. Tagging something as a mentored bug will feed it into [[BugsAhoy]]. | |||
==Reach Out== | ==Reach Out== | ||
| Line 46: | Line 50: | ||
* If you see someone in Bugzilla with 'New to Bugzilla' next to their name, send them an email | * If you see someone in Bugzilla with 'New to Bugzilla' next to their name, send them an email | ||
* If you haven't seen anything from an existing contributor in a while, get in touch and ask if they are being blocked by anything | * If you haven't seen anything from an existing contributor in a while, get in touch and ask if they are being blocked by anything | ||
* A quick way of seeing if a new contributor has been active in Bugzilla is to | * A quick way of seeing if a new contributor has been active in Bugzilla is to google for "site:bugzilla.mozilla.org user@domain.tld" | ||
* You can also check a bugzilla user activity report with a user's email: https://bugzilla.mozilla.org/page.cgi?id=user_activity.html | |||
==Offer Incentives== | ==Offer Incentives== | ||
| Line 96: | Line 101: | ||
* Who in your project keeps documentation and relevant wiki pages up to date? | * Who in your project keeps documentation and relevant wiki pages up to date? | ||
* Who in your project gets the word out about contribution opportunities and knows about different channels available (newsletters, promos, snippets, feeds, lists, etc.)? | * Who in your project gets the word out about contribution opportunities and knows about different channels available (newsletters, promos, snippets, feeds, lists, etc.)? | ||
Put those roles and contact information for ownership onto the main wiki page for your project or module. | |||
==Create a New User Flow== | ==Create a New User Flow== | ||
| Line 108: | Line 115: | ||
So that's all to say, don't get discouraged :) | So that's all to say, don't get discouraged :) | ||
[[Category: Contribute]] [[Category: CBT]] | |||