Contribute/Coding/Mentoring

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.

Good Mentored Bugs

There are three parts to a successful mentored bug: a clear initial description of the problem, clear expectations on the part of the both the mentor and contributor, and a cooperative working relationship as the bug is resolved.

Clear Requirements

Above and beyond what normally makes up a good bug description, a good mentored bug should include:

- A broad description of what an acceptable solution to the bug would look like, in particular including the testing/validation requirements the contributor would need to land a fix. - If possible, a [ http://dxr.mozilla.org/mozilla-central/source/ link to DXR] or other relevant repo where the bug resides. - If possible, links to prior art - similar bugs in Bugzilla, similar tests in the tree.

The Contributor's Role

We want the contributor's participation in mentored bugs to be a good experience that's the start of a long-term relationship.

- For mentored bugs, it is generally expected that you've your development environment set up, and that you have made some contributions to the Mozilla codebase before. Few mentored bugs, if any, will be good first bugs.

- Regular communication with your mentor is important; your mentor needs confidence that the bug is moving in a good direction, and