Reps/SOPs/Mentoring: Difference between revisions

Jump to navigation Jump to search

Reps/SOPs/Mentoring (view source)

Revision as of 08:27, 27 May 2011

5,158 bytes added ,  27 May 2011
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
Mentorship is an essential component of the Mozilla Reps program. It is the starting point for any Mozilla Rep. In the first phase of ReMo, the two project leads of ReMo, William Quiviger and Pierros Papadeas will be in charge of mentoring applicants who are shortlisted after filling out the Mozilla Reps application form. Mozilla Rep council members may also be asked to become mentors.
{{Remonav}}


== Mentoring during the application process ==
Mentorship is an essential component of the Mozilla Reps program. It is the starting point for any Mozilla Rep. In the first phase of ReMo, the two project leads of ReMo, William Quiviger and Pierros Papadeas will be in charge of mentoring applicants who are shortlisted after filling out the Mozilla Reps application form. Mozilla Rep council members may also be asked to become mentors.


Once an applicant has submitted his/her application form and has been selected for the next round, he/she is assigned a mentor.
{{Admon/important |Keep bugs tidy| Please make sure that withing the process the application bug is up to date with the progress and reflects the steps as noted below}}


The mentor will touch base with the applicant by email, briefly explain to him the next steps of the application process and set up an short interview on IRC with the applicant that same week (or when available).  
== Step 1: Being assigned an applicant ==
Once an applicant has submitted their application form, a bug is created on bugzilla that is triaged by William and Pierros. If this applicant has been selected for the next round, William and Pierros might assign this applicant to you, by assigning you the bug. If this is the case, you will receive an email informing you of this and will be able to access the bug.


=== IRC interview ===
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Screening'''


The IRC interview between mentor and applicant should not last more than 30 minutes and is informal. The aim of the interview is for the mentor to get to know the applicant and to ask the applicant specific questions to get a better feel of the applicant and of his/her motivations to join the program. This interview is critical in helping the mentor make a final decision on whether or not the applicant should be admitted into the Mozilla Reps program.
== Step 2: Gathering information about the applicant from the bug ==
The bug you've been assigned contains all the applicant submitted when applying. Read carefully through this information and decide whether or not you think this person is a good candidate to become a Mozilla Rep.


=== Post-interview decision and contact ===
== Step 3: First contact with the applicant ==


After the interview, the mentor will decide whether or not the applicant should be accepted into the program. If the mentor has some doubts, the mentor is strongly encourage to dicuss with the Mozilla Reps council to come to a speedy decision.  
=== Scenario A: You think this person is a strong candidate and doesn't need an interview ===
If you think that accepting him into the program is a no-brainer (either because you know the applicant already and/or you just know the person would be a fantastic Mozilla Rep), you can skip to Step 5.


Once the decision is made, the mentor must reach out to the applicant by email to inform him/her of the decision.
=== Scenario B: More info/contact needed ===
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Meeting Needed'''


=== Hand-holding period ===
If you think the person is a strong candidate but you would like to get to know him/her better, touch base with the applicant by email and set up an short interview on IRC with the him/her that same week (or when available).
 
Email example:
<pre>
Subject: Mozilla Rep application – next step
Hi [name of applicant],
Thanks for applying to become a Mozilla Rep program!
 
I'm [your name] and I will guide you through the rest of the application process .
I would like to set up a short chat interview with you on IRC this week to ask you a few questions.
 
Please let me know if you would be available at [suggest different times].
Thanks very much and look forward to speaking to you!
 
[your name]
Mozilla Rep Council Member
</pre>
 
=== Scenario C: Not a good candidate===
Bug Status : '''RESOLVED WONTFIX'''<br>
Bug Whiteboard :
 
If you think that, based on the information submitted by the applicant and/or on your personal experience with the applicant in the past, (s)he is not suitable to become a Mozilla Rep at this point, inform the council of your decision and make sure that there is no objection from anyone (NB: if the council is split on the applicant, a vote needs to be held). Then contact the person and inform them of the council's decision.
 
Email example:
<pre>
Subject: your Mozilla Rep application
Hi [name of applicant],
 
Thanks for applying to become a Mozilla Rep program Based on the information you submitted,
the Mozilla Rep council agreed that it is too early for you to apply to the program.
Mozilla Reps is a program for Mozilla volunteers who have been active for some time in the
project and have demonstrated strong leadership in their community.
 
We encourage you to re-apply when you have gathered enough experience participating in the project.
In the meantime, we encourage you to get in touch with [name of contact person of his/her local Mozilla community]
to learn how to get involved.
 
Thanks very much for your interest in Mozilla.
 
[your name]
Mozilla Rep Council Member
</pre>
 
 
=== Suggested selection criteria ===
* how long has the applicant been involved in the Mozilla project
* how knowledgeable is the applicant of the Mozilla Project, our mission and our values
* what are the applicant's main motivations to join ReMo
* do you feel this person would explain Mozilla well to a public audience?
* do you feel this person is genuinely interested in helping promote Mozilla ?
* is the applicant already involved in other community-driven projects?
* is the applicant familiar with the different products Mozilla develops and different Mozilla initiatives (eg. Drumbeat, Firefox Live etc..)
* nomination/recommendation from team leader, eg OpenMatt for drumbeat, maryc for marketing
* will the applicant be able to pull together his own resources at times even though if Mozilla is unable to provide? example: designing presentations, press releases, make own swag?
* what would be his commitment period to the program? (3 months, 6months etc)
* Open to work in collaboration
 
== Step 4: Interviewing the applicant on IRC ==
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Meeting Scheduled'''
 
Make sure to keep the interview short and not too formal. Here are examples of questions you might want to ask the applicant:
* when and why did you first start contributing to the Mozilla project?
* How much time do you spend contributing to the project every week on average?
* Are you comfortable speaking in public?
* Have you ever organised a community event before?
* Have you spoken to the press before?
* What would be the first project you'd work on if you became a MozillaRep?
 
== Step 5: Informing the applicant that there are accepted into the program ==
 
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Accepeted'''
 
If you think the interview went well and/or that applicant is clearly ready to become a Mozilla Rep, contact him/her by email to inform him of the good news, but also to explain the next steps.
 
Email example:
<pre>
Subject: You've been accepted to the Mozilla Rep program
 
Hi [name of applicant],
 
Thanks again for applying to become a Mozilla Rep program [and for taking the short interview (if applicable)].
I'm thrilled to inform you that the Mozilla Rep council's accepted you into the program :)
I've been assigned to be your program mentor meaning I'll be your main contact person for
the program if you have any questions or concerns.
I'll also help you get started and help monitor your activity in the program.
 
So let's get right down to business! Here are the next steps for you in order to become an official Mozilla Rep are:
• create a user profile (if you haven't already) on the ReMo wiki
• sign up (if you haven't already) to the ReMo mailing list
• sign and return to me by email the Mozilla Rep Agreement
• read through and get familiar with all the ReMo tools
• read through and get familiar with all the SOPs (if the links don't work, you can go here: https://wiki.mozilla.org/ReMo/SOPs)
 
As soon as we have received your signed Rep Agreement, you're all set!
 
Of course, if you have any questions, feel free to ask away :)
 
[your name]
Mozilla Rep Council member
</pre>
 
== Step 6: Hand-Holding Period ==
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Hand-holding period'''


If the applicant is approved to become a Mozilla Rep, his/her mentor should help him/her to get started. This period is called the "hand-holding" period where the mentor makes sure the new Mozilla Rep:
If the applicant is approved to become a Mozilla Rep, his/her mentor should help him/her to get started. This period is called the "hand-holding" period where the mentor makes sure the new Mozilla Rep:
Line 28: Line 140:
* asks all the questions they may have
* asks all the questions they may have


The hand-holding period should not last more than two weeks although each Mozilla Rep will be strongly encouraged to regularly liaise with their mentor.
The hand-holding period should not last more than two weeks although each Mozilla Rep will be strongly encouraged to regularly liaise with their mentors.
 
=== Selection criteria used by mentors for applicant approval ===


All Mozilla Rep mentors are required to consider specific criteria when making their decision on whether or not to admit an applicant into the Mozilla Reps program. The list of suggested selection criteria can be found [[ReMo/Application_Process/Selection_Criteria|here]].
== Step 7: End of process ==
Bug Status : '''RESOLVED FIXED'''<br>
Bug Whiteboard :
Ppapadeas
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,783

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/313288"

Navigation menu