Confirmed users, Bureaucrats and Sysops emeriti
421
edits
Contribute/Coding/Mentoring: Difference between revisions
→The Mentor's Role
| Line 50: | Line 50: | ||
* Be judicious in what bugs, as well as what contributors, you agree to mentor. You are not obliged to mentor any particular contributor, but it is a real commitment. Do not hesitate to look up prior work if you need to make a decision. | * Be judicious in what bugs, as well as what contributors, you agree to mentor. You are not obliged to mentor any particular contributor, but it is a real commitment. Do not hesitate to look up prior work if you need to make a decision. | ||
* Return emailed questions promptly: within 24 hours *at most*. Engagement falloff is measurably worse after 1 day and dramatically worse after three. If possible, establish "office hours" on IRC during which you agree to be available to answer that contributor's questions. | * Return emailed questions promptly: within 24 hours *at most*. Engagement falloff is measurably worse after 1 day and dramatically worse after three. If possible, establish "office hours" on IRC during which you agree to be available to answer that contributor's questions. You can create a mail to manage mentored bugmail specifically: [ http://www.joshmatthews.net/blog/2013/12/you-are-receiving-this-mail-because-you-are-mentoring-this-bug/ see here ]. | ||
* Follow up with contributors who seem to be off track or losing interest. It you go two weeks without hearing from a contributor on a mentored bug, there is no shame in putting it back in the common pool. | * Follow up with contributors who seem to be off track or losing interest. It you go two weeks without hearing from a contributor on a mentored bug, there is no shame in putting it back in the common pool. | ||
=== Following Up === | === Following Up === | ||