Reps/SOPs/Mentoring/Screening: Difference between revisions

Add note about Council screening + minor text updates
m (Fixed a minor issue in the mailto text)
(Add note about Council screening + minor text updates)
Line 2: Line 2:


__TOC__
__TOC__
{{Admon/note | Note | Currently screening is done by members of the Council, not mentors. However, the rest of the text still applies.}}


== Screening new applicants ==
== Screening new applicants ==
Line 40: Line 42:
=== Scenario A: You think this person is a strong candidate ===
=== Scenario A: You think this person is a strong candidate ===
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 must still interview this person to better understand their goals and how to support them.  Please follow the instructions in Scenerio B.
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 must still interview this person to better understand their goals and how to support them.  Please follow the instructions in Scenerio B.


=== Scenario B: More info/contact needed ===
=== Scenario B: More info/contact needed ===
Line 106: Line 106:


If you are convinced that, based on the information submitted by the applicant and/or on your personal experience with the applicant in the past, the applicant is not suitable to become a Mozilla Rep at this point, then contact the person and inform them that they are not yet ready to join the program. it's very important to explain to them that they can re-apply to the program later when they feel they have acquired enough experience. If you're hesitant, inform the council and ask for advice on what to do.  
If you are convinced that, based on the information submitted by the applicant and/or on your personal experience with the applicant in the past, the applicant is not suitable to become a Mozilla Rep at this point, then contact the person and inform them that they are not yet ready to join the program. it's very important to explain to them that they can re-apply to the program later when they feel they have acquired enough experience. If you're hesitant, inform the council and ask for advice on what to do.  
For suggested acceptance criteria please follow [[ReMo/Application_Process/Selection_Criteria]].


Email example: [mailto:example@domain.com?subject=Your%20Mozilla%20Rep%20application&body=Hi%20(name%20of%20applicant),%0A%0AThanks%20for%20applying%20to%20become%20a%20Mozilla%20Rep.%20Based%20on%20the%20information%20you%20submitted,the%20Mozilla%20Rep%20council%20agreed%20that%20it%20is%20too%20early%20for%20you%20to%20apply%20to%20the%20program.%20Mozilla%20Reps%20is%20a%20program%20for%20Mozilla%20volunteers%20who%20have%20been%20active%20for%20some%20time%20in%20the%20project%20and%20have%20demonstrated%20strong%20leadership%20in%20their%20community.%0A%0AWe%20encourage%20you%20to%20re-apply%20when%20you%20have%20gathered%20enough%20experience%20participating%20in%20the%20project.%0AIn%20the%20meantime,%20we%20encourage%20you%20to%20get%20in%20touch%20with%20(name%20of%20contact%20person%20of%20his/her%20local%20Mozilla%20community)%20to%20learn%20how%20to%20get%20involved.%0A%0AThanks%20very%20much%20for%20your%20interest%20in%20Mozilla.%0A%0A(your%20name)%0AMozilla%20Rep%20Mentor Click here to launch mail]
Email example: [mailto:example@domain.com?subject=Your%20Mozilla%20Rep%20application&body=Hi%20(name%20of%20applicant),%0A%0AThanks%20for%20applying%20to%20become%20a%20Mozilla%20Rep.%20Based%20on%20the%20information%20you%20submitted,the%20Mozilla%20Rep%20council%20agreed%20that%20it%20is%20too%20early%20for%20you%20to%20apply%20to%20the%20program.%20Mozilla%20Reps%20is%20a%20program%20for%20Mozilla%20volunteers%20who%20have%20been%20active%20for%20some%20time%20in%20the%20project%20and%20have%20demonstrated%20strong%20leadership%20in%20their%20community.%0A%0AWe%20encourage%20you%20to%20re-apply%20when%20you%20have%20gathered%20enough%20experience%20participating%20in%20the%20project.%0AIn%20the%20meantime,%20we%20encourage%20you%20to%20get%20in%20touch%20with%20(name%20of%20contact%20person%20of%20his/her%20local%20Mozilla%20community)%20to%20learn%20how%20to%20get%20involved.%0A%0AThanks%20very%20much%20for%20your%20interest%20in%20Mozilla.%0A%0A(your%20name)%0AMozilla%20Rep%20Mentor Click here to launch mail]
Line 200: Line 202:
Mozilla Reps Mentor
Mozilla Reps Mentor
</pre>
</pre>


=== Scenario E: Applicant did not finish the application process ===
=== Scenario E: Applicant did not finish the application process ===
Line 210: Line 211:
Bug Whiteboard : '''Scenario E'''
Bug Whiteboard : '''Scenario E'''


=== Suggested selection criteria ===
For suggested acceptance criteria please follow [[ReMo/Application_Process/Selection_Criteria]].
* how long has the applicant been involved in the Mozilla project
** Minimum: 6 months
** Bonus:  Years
* how knowledgeable is the applicant of the Mozilla Project, our mission and our values
** Minimum: Read the Mozilla Manifesto
** Bonus: Personal association with mission or values of mozilla
* Applicant blogs/posts about mozilla
** Minimum: One post
** Bonus: Already doing/done that
* Have Goals for participation in ReMo
** Minimum: One goal aligned with the program
** Bonus: Three or more goals aligned with the program
* Ability to publicly speak about mozilla
** Minimum: Be comfortable with that
** Bonus: Already done that in different audiences
* Involved in other community-driven projects?
** Minimum: At least one
** Bonus: Participation in open-source community
* is the applicant familiar with the different products Mozilla develops and different Mozilla initiatives (eg. Drumbeat, Firefox Identity etc..)
** Minimum: Know at least one other project except Firefox
** Bonus: Knows about upcoming projects and latest developments
* 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?
** Minimum: Willing to do that (and understand what it takes)
** Bonus: Already done that
* what would be his commitment period to the program? (3 months, 6months etc)
** Minimum: This year
** Bonus: No limit


== Step 3: Interviewing the applicant ==
== Step 3: Interviewing the applicant ==
Line 243: Line 217:
Bug Whiteboard : '''Meeting Scheduled'''
Bug Whiteboard : '''Meeting Scheduled'''


Make sure to keep the interview short and not too formal. Below,  are examples of questions you might want to ask the applicant.   
Make sure to keep the interview short and not too formal. Below,  are examples of questions you might want to ask the applicant. Please adopt those to the current needs of the Mozilla Reps program if necessary.   
* When and why did you first start contributing to the Mozilla project?
* 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?
* How much time do you spend contributing to the project every week on average?
Line 298: Line 272:


== Formally accepting the applicant into the program ==
== Formally accepting the applicant into the program ==
When the mentor feels his/her mentee is ready to become a Mozilla Rep and has sent his signed Mozilla Reps agreement (which should be forwarded to Rosana Ardila <rardila at mozilla.com> and Rubén Martín <rmartin at mozilla.com>) then the mentor must officially accept the applicant into the program by changing the applicant's status on bugzilla.  
When the mentor feels his/her mentee is ready to become a Mozilla Rep and has sent his signed Mozilla Reps agreement (which should be forwarded to Konstantina Papadea <kpapadea at mozilla.com>) then the mentor must officially accept the applicant into the program by changing the applicant's status on bugzilla.  


Bug Status : '''ASSIGNED'''<br>
Bug Status : '''ASSIGNED'''<br>
Confirmed users
555

edits