I have done a good deal of mentored bugs as well as mentoring new Mozillians (gsoc, interns, employees) on their journey. I would like to share a few things which I have found that make things easier. Most of this might seem like common sense, but I find it so easy to overlook little details and forget things.
- When filing a bug (or editing an existing one), make sure to include:
- Link(s) to getting started with the code base (cloning, building, docs, etc.)
- Clear explanation of what is expected in the bug
- A general idea of where the problematic code is
- What testing should look like
- How to commit a patch
- A note of how best to communicate and not to worry about asking questions
- Avoid shorthand and acronyms!
- Spend a few minutes via IRC/Email getting to know your new friend, especially timezones and general schedule of availability.
- Make it a priority to do quick reviews and answer questions – nothing is more discouraging when you have 1 thing to work on and you need to wait for further information.
- It is your job to help them be effective – take the time to explain why coding styles and testing are important and how it is done at Mozilla.
- Make it clear how their current work plays a role in Mozilla as a whole. Nobody likes to work on something that is not valued.
- Granting access to Try server (or as a contributor to a git repository) really make you feel welcome and part of the team, consider doing this sooner than later. With this comes the responsibility of teaching them how to use their privileges responsibly!
- Pay attention to details- forming good habits up front go a long way!
With those things said, just try to put yourself in the shoes of a new Mozillian. Would you want honest feedback? Would you want to feel part of the larger community?
Being a good mentor should be rewarding (the majority of the time) and result in great Mozillians who people enjoy working with.
Lets continue to grow Mozilla!
3.1415926535897932384626433... 