Reps/SOPs/Mentoring: Difference between revisions

From MozillaWiki
< Reps‎ | SOPs
Jump to navigation Jump to search
(Warning added)
 
(113 intermediate revisions by 21 users not shown)
Line 1: Line 1:
{{Warning |1= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.|title= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.}}
{{Remonav}}
{{Remonav}}
Mozilla Reps recognizes that our primary goals are best reached through the support, encouragement, and empowerment of community through mentorship. Mentoring is a process for the informal transmission of knowledge, made possible through regular and supportive interaction.


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.
Being a Mozilla Reps mentor requires a familiarity with different tools and processes that the Council has put in place to better streamline the way Mozilla Reps can document their activities, request budgets for projects, order swag and interact with other Reps.
 
A mentor also serves as a coach, dedicated to helping their mentee’s personal development. This includes the following responsibilities:
{{Admon/important |Keep bugs tidy| Please make sure that within the process the application bug is up to date with the progress and reflects the steps as noted below}}
 
== 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.
 
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Screening'''
 
== 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.
 
== Step 3: First contact with the applicant ==
 
=== 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.
 
=== Scenario B: More info/contact needed ===
Bug Status : '''ASSIGNED'''<br>
Bug Whiteboard : '''Meeting Needed'''
 
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 .
*Be available for their mentees in a timely manner
I would like to set up a short chat interview with you on IRC this week to ask you a few questions.
*Organize regular coaching sessions with your mentees
*Be available for other Reps for coaching sessions which fit your specialized skills
**Example: If a mentor has a great experience in Goal Setting activities, other Reps might approach this mentor to learn more


Please let me know if you would be available at [suggest different times].
We encourage mentors to be as open to learning from their mentees, as they are to teaching, for the benefit and growth of both individuals and the program as a whole.
Thanks very much and look forward to speaking to you!


[your name]
__TOC__
Mozilla Rep Council Member
</pre>


{{hidden|Spanish version|
=How to Become a Mentor=
<pre>
Any interested official Rep can take the [[ReMo/Coaching/Training|Coaching Training]] and complete its requirements to be accepted as a mentor.
Asunto: Solicitud Mozilla Rep – Siguiente paso
Hola [nombre del solicitante],


¡Gracias por apuntarte al programa Mozilla Reps!
'''Please note: we are currently updating the Coaching training. If you wish to become a Mentor please email the Council so that we can keep track of those that are interested.
'''


Soy [tu nombre] y te guiaré a través del resto del proceso de solicitud.
=Mentors Role=
Me gustaría fijar una breve entrevista por chat contigo en IRC esta semana para preguntarte algunas cuestiones.


Por favor, hazme saber si estás disponible a las [sugiere diferentes horarios].
The Mentor role is one of support. This involves a number of responsibilities, such as guiding new Reps within the Program, offering advice and encouragement to their mentees and supporting them in staying active and engaged withing the Reps Program.


¡Muchas gracias y quedo a la espera de charlar contigo!
=Mentors Activities=


[tu nombre]  
*'''Mentors should have a general idea of how their mentees are doing and offer support as appropriate.''' To this end:
Mozilla Rep Council Member
**Mentors should  aim to '''organize at least one meeting a year with each mentee to touch base with them'''. This meeting could be used to discuss the plans of the mentee and also to establish what kind of support they need. [https://docs.google.com/document/d/1v7sRsJNsrmPkolfK_MuafgeDkm2HMQVFgnK8LwTmhoU/edit?usp=sharing A template for this meeting can be found here] and [https://docs.google.com/document/d/1iNAPzKVZz7Y66tacPYW4o9mL_RvFqlXRuVLJVO960c0/edit?usp=sharing here you can find more detailed suggestions on how to carry out the meeting].
</pre>
**Mentor '''should carry out regular communication with their mentees''' as established in the yearly meeting.
}}
**Mentors '''should be available to support their mentees with specific issues when they arise'''. The mentee should be able to reach their mentor through an agreed upon communication channel, and receive timely support.


=== Scenario C: Not yet ready for ReMo ===
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.
*'''Supporting new Reps''': Mentors have a very important role in supporting new Reps. New reps need more frequent guidance than other reps, a meeting at least every three months (and possibly more often)  is advised. [[Reps/SOPs/Mentoring/Orientation/Call|You can find more guidance on how to conduct a first orientation call here]].  


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,
*'''Mentors support the council in relating information about changes and important events in the Reps program to their mentees'''. You are encouraged to establish what are important updates that need to be communicated, but a member of the council will post in discourse and communicate during the mentors call if there are important updates we would like the mentors to pass on to their mentees
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.
''N.B. These are not information that are given uniquely to mentors, but we need mentors’ help to make sure that important information reaches their mentees.''
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.
=Communication Channels and Tools=


[your name]  
*People.mozilla.org. All mentors should have an updated profile and be in the [https://people.mozilla.org/a/mozilla-reps-mentor/ Mozilla Reps Mentor access group]
Mozilla Rep Council Member
</pre>


=== Suggested selection criteria ===
*Community Portal: all Mentors should have an updated profile and be in the [https://community.mozilla.org/en/groups/mozilla-reps-mentors/ Mozilla Reps group].
* 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 ==
*We have a [https://discourse.mozilla.org/c/reps/mentors/268 special Discourse category for mentors]. Make sure that you have access to it and that you are watching it.
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:
*[https://chat.mozilla.org/#/room/#reps-mentors:mozilla.org Mentors matrix room]: all mentors should have access to it. This is the place to talk with other mentors and ask questions.
* 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>
=Changing your mentor=
Bug Whiteboard : '''Accepted'''


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.
Normally the commitment for the 1:1 relationship is done for one year. After that year, the commitment can either be extended or the mentor can be changed. This allows to continue fruitful coaching sessions or to be assigned to a new mentor with a different skill set to broaden the horizon and skills of a Rep. If a mentor becomes inactive, mentors can be changed disregarding the 1 year commitment through the Reps Council.


Email example:
For more details about changing your mentor, check the [[ReMo/SOPs/Mentoring/Reassigning|Reassigning a Mentor page]].
<pre>
Subject: You've been accepted to the Mozilla Rep program


Hi [name of applicant],
=Mentor Assessment=


Thanks again for applying to become a Mozilla Rep program [and for taking the short interview (if applicable)].
There is a yearly feedback round for both mentors and mentees. This allows to identify strengths and weaknesses we can improve upon. This highly improves the quality of the coaching relationships.
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:
=Resigning=
• create a user profile (if you haven't already) on the ReMo wiki
If a mentor can no longer fulfill his/her duties as a mentor, the mentor must send an email to the Council or any of the [https://reps.mozilla.org/people/#/group/council/ Council Members] to resign and recommend a new mentor to replace him/her.
• 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!
=List of Mentors=


Of course, if you have any questions, feel free to ask away :)
You can find the [https://community.mozilla.org/en/groups/mozilla-reps-mentors full list of mentors on the Community Portal].


[your name]
=Council procedure=
Mozilla Rep Council member
The mentor onboarding require a Council member that follow the various steps:
</pre>


== Step 6: Hand-Holding Period ==
==Assigning==
Bug Status : '''ASSIGNED'''<br>
* Add new reps looking for a mentor to Coaching Open Assignment document
Bug Whiteboard : '''Hand-holding period'''
* Contact the Rep about the mentor that accepted to have him/her as mentee for an approval


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:
==Prepare mentors==
* The wannabe Mentor need to write to the council an email about the finished course on Teachable
  ''Note: The council is currently working on updating this procedure''


* [[ReMo/SOPs/User_Profile|creates a user profile]] on the ReMo wiki
* signs up to the [[ReMo#Contact|ReMo mailing list]]
* signs and returns the [https://wiki.mozilla.org/images/4/4b/Mozilla_Reps_Agreement.pdf Mozilla Reps Agreement]
* is briefed on the [[ReMo/Main#ReMo_Tools|ReMo tools]]
* is briefed on all the [[ReMo/SOPs|SOPs]]
* 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 mentors.
* Start with the training https://wiki.mozilla.org/ReMo/Coaching/Practice_Week


== Step 7: End of process ==
[[Category:Remosop]]
Bug Status : '''RESOLVED FIXED'''<br>
Bug Whiteboard :

Latest revision as of 19:26, 29 September 2023

Warning signWarning: With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.

MozRep-Final-Outline.png Main | Join | Procedures (SOPs) | Leadership (Resources) | Meetings | Website | FAQ


Mozilla Reps recognizes that our primary goals are best reached through the support, encouragement, and empowerment of community through mentorship. Mentoring is a process for the informal transmission of knowledge, made possible through regular and supportive interaction.

Being a Mozilla Reps mentor requires a familiarity with different tools and processes that the Council has put in place to better streamline the way Mozilla Reps can document their activities, request budgets for projects, order swag and interact with other Reps. A mentor also serves as a coach, dedicated to helping their mentee’s personal development. This includes the following responsibilities:

  • Be available for their mentees in a timely manner
  • Organize regular coaching sessions with your mentees
  • Be available for other Reps for coaching sessions which fit your specialized skills
    • Example: If a mentor has a great experience in Goal Setting activities, other Reps might approach this mentor to learn more

We encourage mentors to be as open to learning from their mentees, as they are to teaching, for the benefit and growth of both individuals and the program as a whole.

How to Become a Mentor

Any interested official Rep can take the Coaching Training and complete its requirements to be accepted as a mentor.

Please note: we are currently updating the Coaching training. If you wish to become a Mentor please email the Council so that we can keep track of those that are interested.

Mentors Role

The Mentor role is one of support. This involves a number of responsibilities, such as guiding new Reps within the Program, offering advice and encouragement to their mentees and supporting them in staying active and engaged withing the Reps Program.

Mentors Activities

  • Mentors should have a general idea of how their mentees are doing and offer support as appropriate. To this end:
    • Mentors should aim to organize at least one meeting a year with each mentee to touch base with them. This meeting could be used to discuss the plans of the mentee and also to establish what kind of support they need. A template for this meeting can be found here and here you can find more detailed suggestions on how to carry out the meeting.
    • Mentor should carry out regular communication with their mentees as established in the yearly meeting.
    • Mentors should be available to support their mentees with specific issues when they arise. The mentee should be able to reach their mentor through an agreed upon communication channel, and receive timely support.



  • Mentors support the council in relating information about changes and important events in the Reps program to their mentees. You are encouraged to establish what are important updates that need to be communicated, but a member of the council will post in discourse and communicate during the mentors call if there are important updates we would like the mentors to pass on to their mentees

N.B. These are not information that are given uniquely to mentors, but we need mentors’ help to make sure that important information reaches their mentees.

Communication Channels and Tools

  • Community Portal: all Mentors should have an updated profile and be in the Mozilla Reps group.
  • Mentors matrix room: all mentors should have access to it. This is the place to talk with other mentors and ask questions.


Changing your mentor

Normally the commitment for the 1:1 relationship is done for one year. After that year, the commitment can either be extended or the mentor can be changed. This allows to continue fruitful coaching sessions or to be assigned to a new mentor with a different skill set to broaden the horizon and skills of a Rep. If a mentor becomes inactive, mentors can be changed disregarding the 1 year commitment through the Reps Council.

For more details about changing your mentor, check the Reassigning a Mentor page.

Mentor Assessment

There is a yearly feedback round for both mentors and mentees. This allows to identify strengths and weaknesses we can improve upon. This highly improves the quality of the coaching relationships.

Resigning

If a mentor can no longer fulfill his/her duties as a mentor, the mentor must send an email to the Council or any of the Council Members to resign and recommend a new mentor to replace him/her.

List of Mentors

You can find the full list of mentors on the Community Portal.

Council procedure

The mentor onboarding require a Council member that follow the various steps:

Assigning

  • Add new reps looking for a mentor to Coaching Open Assignment document
  • Contact the Rep about the mentor that accepted to have him/her as mentee for an approval

Prepare mentors

  • The wannabe Mentor need to write to the council an email about the finished course on Teachable
 Note: The council is currently working on updating this procedure


Retrieved from "https://wiki.mozilla.org/index.php?title=Reps/SOPs/Mentoring&oldid=1248258"