canmove, Confirmed users
868
edits
Contribute/Best Practices: Difference between revisions
no edit summary
Jennierose (talk | contribs) No edit summary |
|||
| (26 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
This page documents best practices about how to help new people get involved with Mozilla. | This page documents best practices about how to help new people get involved with Mozilla. | ||
==Local Community Best Practice Sessions== | |||
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 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] | |||
==Provide Recognition== | ==Provide Recognition== | ||
| Line 24: | Line 33: | ||
* Ask someone to download a nightly build if they're interested in testing | * Ask someone to download a nightly build if they're interested in testing | ||
* 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 join a bug triage project: [[Bugmasters/Projects]] | |||
==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. [[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 33: | 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 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 43: | Line 62: | ||
* [http://creative.mozilla.org/challenges/8 Design Challenges] | * [http://creative.mozilla.org/challenges/8 Design Challenges] | ||
* Swag at events | * Swag at events | ||
==Offer Support== | |||
Volunteers may need some help in order to help you. You may want to consider if there are specific needs that a volunteer may need help with in order to be effective. | |||
Examples: | |||
* The [[Mobile/Testdrivers_Program|Mobile Test Driver]] program offering loaner phones to people to test Mobile Firefox | |||
* Providing a headset to both employees and volunteers so they can participate in video team calls | |||
==Host Events== | ==Host Events== | ||
| Line 54: | Line 82: | ||
* [http://jgoulie.blogspot.com/2011/04/mozilla-stanford-university-for-open.html Open Source Bootcamp] | * [http://jgoulie.blogspot.com/2011/04/mozilla-stanford-university-for-open.html Open Source Bootcamp] | ||
== | ==Run a Contest== | ||
Consider running a contest to encourage contributor participation. Examples: | |||
* [https://blog.mozilla.org/addons/2011/12/22/amo-editors-new-years-challenge/ AMO Editor Challenge] - A short review queue is key to a good add-on development experience. In this contest, the volunteer editor who reviewed the most add-ons during the contest period won a MacBook Air. The contest resulted in the queues being [https://blog.mozilla.org/addons/2012/02/16/the-review-queues-are-empty/ empty for the first time]. | |||
* [https://blog.mozilla.org/addons/2012/04/24/tell-us-about-your-favorite-add-on-for-a-chance-to-win-one-of-three-android-tablets/ Favorite Add-ons Contest] - This was a great way to get users to encourage add-on developers and tell them how indispensable their contributions are. | |||
==Clarify Ownership== | ==Clarify Ownership== | ||
Consider having a very clear understanding of people's roles and of what they own to avoid situations where opportunities are missed when people assume someone else will | Consider having a very clear understanding of people's roles and of what they own to avoid situations where opportunities are missed when people assume someone else will take care of it. | ||
Everyone in Mozilla shares the responsibility of bringing new people into the project, but that's not to say there aren't specific areas that need to be owned by specific people. | |||
Examples: | |||
* Who in your project makes a point of staying in an IRC channel to answer questions people may have? | |||
* 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.)? | |||
Put those roles and contact information for ownership onto the main wiki page for your project or module. | |||
==Create a New User Flow== | |||
Consider mapping out how someone interested in your project can find out about contribution opportunities and how to start working on a project. Wiki pages and blog posts are important parts of this, but how will people find those and what should they do next if they're interested? | |||
==Don't Get Discouraged== | ==Don't Get Discouraged== | ||
| Line 71: | 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]] | |||