Confirmed users, Bureaucrats and Sysops emeriti
421
edits
Contribute/Coding/Mentoring: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This page is intended to describe what makes up a good Mentored Bug, and to clarify expectations around what constitutes a good bug-mentoring relationship. | This page is intended to describe what makes up a a good first bug, a good Mentored Bug, and to clarify expectations around what constitutes a good bug-mentoring relationship. | ||
= Good First Bugs = | |||
The challenge of a "good first bug" is only peripherally about the bug itself. The focus, for a new contributor, should be on getting your development environment set up and learning how to navigate Mozilla's contribution process. There are some [https://developer.mozilla.org/en-US/docs/Introduction excellent documents on MDN] to help you get started, and the #introduction IRC channel exists just to help people getting started as contributors. | |||
A good, ahem, good first bug includes an extremely narrow scope, clear hardware and platform requirements, and prompt reviewer followup. | |||
=== Narrowly Scoped === | |||
An ideal first bug is very well understood and extremely narrow in scope, possibly as little as one line, and the bug description should have a [http://dxr.mozilla.org/mozilla-central/source/ DXR link to the relevant code] in the bug description. No dependencies. | |||
=== Clear External Requirements === | |||
If any external requirements exist - A particular OS or OS version, hardware, language facility (C++, Regular expressions, Taiwanese, whatever that means) anything else - that information should be specified in the whiteboard or comments. | |||
=== Reviewer Followup === | |||
We know for a fact that the single biggest influence on contributor retention is response time. Contributors whose contribution is acknowledged within the first two days - even if it is only to thank the contributor and say when it will be reviewed - will generally return to make a second contribution; wait two weeks, and they will not. Please follow up first-bug submissions promptly, and successful reviews with a note about what this contributor might want to work on next. | |||
= Good Mentored Bugs = | = Good Mentored Bugs = | ||