Mentors: Difference between revisions
Jump to navigation
Jump to search
(→Respond to contribution inquiries: Updated link to mentored bugs) |
|||
| (16 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
Help new people become active contributors | Help new people become active contributors (you can also [[Mozilla.org/Contribute/Coding | help at a higher level]]). | ||
= | =Mentor a specific bug= | ||
You can offer to mentor someone who wants to take on a specific bug, by adding your Bugzilla username to the bug's mentor field. | |||
You should also add a comment in the bug telling a new contributor:<br> | |||
* how to get started with this bug, | |||
* what a completed solution should look like, | |||
* pointers to relevant information, | |||
* if the bug is not trivial: | |||
** how hard the bug is, | |||
** what resources they may need to implement the fix. | |||
Finally, emailing a quick "thanks, ask me anything" to new contributors when they arrive will give them a warm fuzzy feeling, which we encourage. | |||
Setting the mentor field on a bug will make it searchable in Bugzilla, but will also make it available in the [[BugsAhoy|Bugs Ahoy]] site. | |||
= | * [https://bugzilla.mozilla.org/buglist.cgi?f1=bug_mentor&o1=isnotempty&resolution=---&query_format=advanced&list_id=10686903 List of current mentored bugs] | ||
* [http://www.joshmatthews.net/blog/2011/09/making-bugs-more-attractive-for-other-people-to-fix/ Making bugs more attractive for other people to fix] - a helpful blog post. | |||
** Note that we've switched from using the whiteboard for the mentor name to a proper field. | |||
<br> | |||
=Help a newbie on Bugzilla or IRC= | |||
There is a [https://bugzilla.mozilla.org/show_bug.cgi?id=648948 'New to Bugzilla' tag] next to people's names in Bugzilla who have just started using the system. Take a minute to answer a new user's question, provide a helpful pointer or just say something nice about how great it is they want to help. | |||
Hang out in the [irc://irc.mozilla.org/introduction #introduction channel] and answer questions from new community members interested in development. | |||
=Respond to contribution inquiries= | =Respond to contribution inquiries= | ||
| Line 19: | Line 32: | ||
The [http://www.mozilla.org/contribute Get Involved] page asks people to contact us if they have any questions about how to get involved with Mozilla. We are looking for people to handle responses for their project areas, which means: | The [http://www.mozilla.org/contribute Get Involved] page asks people to contact us if they have any questions about how to get involved with Mozilla. We are looking for people to handle responses for their project areas, which means: | ||
* send initial response | * send an [[Mozilla.org/Contribute/Canned_responses#Coding | initial response]], | ||
* followup if they | * followup if they don't respond back, | ||
* get them a first bug they'd be interested in | * get them a first bug they'd be interested in: | ||
* answering any questions they have | **[https://bugzilla.mozilla.org/buglist.cgi?f1=bug_mentor&o1=isnotempty&resolution=---&query_format=advanced mentored bugs], | ||
**[https://bugzil.la/kw:student-project&resolution=--- student-projects], | |||
**[https://bugzil.la/sw:%5Bgood%20first%20bug%5D&resolution=--- good first bugs], | |||
* answering any questions they have. | |||
Contact ''david at mozilla dot org'' to help. | |||
* [https://wiki.mozilla.org/Mozilla.org/Contribute/Point_people List of current point people] | |||
== Never miss a comment from contributor == | |||
* With {{bug|869989}} you can now use e-mail header and body footer to filter out bugmails from bugs you mentored. Read the bug for more detail, or [http://www.joshmatthews.net/blog/2013/12/you-are-receiving-this-mail-because-you-are-mentoring-this-bug/ an informative blog post]. | |||
=Other Mentor resources= | |||
* [https:// | * [https://gist.github.com/ygjb/4543418 Kitherder matching prototype] | ||
* [http://www.joshmatthews.net/mentorwatch/ Mentorwatch mentored bug dashboard] | |||
* [[Security/Mentorship|Security Mentorship docs]] | |||
* [http://mentorship.mozillareps.org/ Reps mentor dashboard] | |||
Latest revision as of 13:42, 9 July 2014
Help new people become active contributors (you can also help at a higher level).
Mentor a specific bug
You can offer to mentor someone who wants to take on a specific bug, by adding your Bugzilla username to the bug's mentor field.
You should also add a comment in the bug telling a new contributor:
- how to get started with this bug,
- what a completed solution should look like,
- pointers to relevant information,
- if the bug is not trivial:
- how hard the bug is,
- what resources they may need to implement the fix.
Finally, emailing a quick "thanks, ask me anything" to new contributors when they arrive will give them a warm fuzzy feeling, which we encourage.
Setting the mentor field on a bug will make it searchable in Bugzilla, but will also make it available in the Bugs Ahoy site.
- List of current mentored bugs
- Making bugs more attractive for other people to fix - a helpful blog post.
- Note that we've switched from using the whiteboard for the mentor name to a proper field.
Help a newbie on Bugzilla or IRC
There is a 'New to Bugzilla' tag next to people's names in Bugzilla who have just started using the system. Take a minute to answer a new user's question, provide a helpful pointer or just say something nice about how great it is they want to help.
Hang out in the #introduction channel and answer questions from new community members interested in development.
Respond to contribution inquiries
The Get Involved page asks people to contact us if they have any questions about how to get involved with Mozilla. We are looking for people to handle responses for their project areas, which means:
- send an initial response,
- followup if they don't respond back,
- get them a first bug they'd be interested in:
- answering any questions they have.
Contact david at mozilla dot org to help.
Never miss a comment from contributor
- With bug 869989 you can now use e-mail header and body footer to filter out bugmails from bugs you mentored. Read the bug for more detail, or an informative blog post.