Contribute/Best Practices: Difference between revisions

Contribute/Best Practices (view source)

175 bytes added , 10 May 2013

m

Confirmed users

2,816

edits

@@ Line 38: / Line 38: @@
 ==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]].