(Document Whiteboard status flags) |
(Warning added) |
||
| (22 intermediate revisions by 4 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}} | ||
| Line 4: | Line 6: | ||
= Joining = | = Joining = | ||
[[File:Reps-Onboarding-Process.png|650px|frameless|center|Onboarding process]] | |||
While the Mozilla Reps program is open to all, becoming a Mozilla Reps involves a short but rigorous application process to make sure those interested are motivated and ready to take on a leadership role within the Mozilla community. | While the Mozilla Reps program is open to all, becoming a Mozilla Reps involves a short but rigorous application process to make sure those interested are motivated and ready to take on a leadership role within the Mozilla community. You can find all criteria regarding a Reps application on the [[ReMo/Application_Process/Selection_Criteria|Selection Criteria page]]. | ||
'''During the Onboarding period and the various steps, if there is no reply from the applicants in a range of three weeks on the ticket, the application will be closed also if approved.''' | |||
In the second half of 2016 we came to the edges of our possibilities to assign all new Reps to new mentors and having a quality onboarding experience. In 2020, we changed the Webinar to a Teachable course with a similar structure as the Webinar. We did that to ensure that information can be easily updated. We are currently using the Teachable course to make the on-boarding part easier, as well as working on Coaching materials and new coaching training to on-board new coaches. The Teachable course is divided to 3 sub - courses. You can find more about Teachable courses in the [[Reps/Webinar/Teachable | Teachable page]]. | |||
In the second half of 2016 we came to the edges of our possibilities to assign all new Reps to new mentors and having a quality onboarding experience. We are currently using | |||
== | = Step 1 - Submit application = | ||
You can find all criteria regarding your Reps application on the [[ReMo/Application_Process/Selection_Criteria|Selection Criteria page]]. Please read that to make sure your application fulfills all requirements. Next, fill out and submit the [https://bugzilla.mozilla.org/form.reps.mentorship MozillaReps application form]. We require all applicants to have at least [ReMo/SOPs/Vouching one vouch] from another Rep in the application bug. We would recommend including 3 vouches, but we value quality over quantity. Once these vouches have been verified by the Onboarding team, you will be put in the queue to be screened. | |||
== Whiteboard status for applications == | |||
'''Missing Info''': Application has obviously missing information based on Application Criteria | |||
'''Pending References''': Application hasn't gotten any references yet | |||
'''Next screening round''': Planned to be screened in next application round | |||
[[ | = Step 2 - Screening = | ||
Based on the selection criteria the onboarding team will screen the pending applications regularly. Currently, we are planning to run this screening every 2 weeks. This means that if you don't hear back from us within 3 weeks, we missed the application and ask you to write a mail to the [[ReMo/Council|Reps Council]] reminding us. Qualifying applicants will be marked as "Teachable" to be included in the next round of the Webinar. Applicants that do not show a strong track record will be rejected with an appropriate explanation and their application will be closed. | |||
'''Initial actions in the application:''' | '''Initial actions in the application:''' | ||
* Initial check according to the [ | * Initial check according to the [ReMo/Application_Process/Selection_Criteria Selection Criteria] | ||
* To make it easier, the following text is posted to give background on why there is an additional vouch necessary on the Reps application | * To make it easier, the following text is posted to give background on why there is an additional vouch necessary on the Reps application | ||
<blockquote> | <blockquote> | ||
@X, @Y: You have been added as a voucher for this application | @X, @Y: You have been added as a voucher for this application. The vouch here is for the Reps application at hand, not general participation within Mozilla. | ||
We would like to know more from you about the following questions regarding the applicant: | We would like to know more from you about the following questions regarding the applicant: | ||
* How has the applicant impacted the community you are working in? | * How has the applicant impacted the community you are working in? | ||
* How would you qualify the applicant’s skill regarding | * How would you qualify the applicant’s skill regarding mobilizing the communities the applicant has been working with? | ||
If you don’t feel comfortable vouching for the applicant or think the applicant is not ready for Reps yet, it’s fine to not answer these questions at all. | If you don’t feel comfortable vouching for the applicant or think the applicant is not ready for Reps yet, it’s fine to not answer these questions at all. | ||
| Line 42: | Line 52: | ||
Information about the screening process can be found at [[ReMo/Webinar/Screening]]. | Information about the screening process can be found at [[ReMo/Webinar/Screening]]. | ||
The final decision will be communicated to the applicant according to the [https://wiki.mozilla.org/ReMo/SOPs/Mentoring/Screening#Step_2:_Assessment Screening documentation] and further steps are taken for the | The final decision will be communicated to the applicant according to the [https://wiki.mozilla.org/ReMo/SOPs/Mentoring/Screening#Step_2:_Assessment Screening documentation] and further steps are taken for the Teachable part if accepted. | ||
= Step 3 - Teachable = | |||
Once an applicant is accepted, we ask them to complete the 3 Teachable sub-courses | |||
Check [[Reps/Webinar/Teachable]] for Teachable related content.''' | |||
== | == Whiteboard status for applications == | ||
'''Onboarding Teachable''': Application was screened and accepted. The applicant is now in the phase to do the Teachable steps. | |||
= Step 4 - Orientation period = | |||
* Return the Mozilla Rep Agreement signed and sent by email | * Return the Mozilla Rep Agreement signed and sent by email | ||
* Council | * Council adds Rep to the Reps group on the Community Portal | ||
* Council subscribes Rep to | * Add the Reps to the queue to get a mentor | ||
* Council subscribes Rep to Reps mailing list | |||
* Creation of Bugzilla account (if they don't have one already) | * Creation of Bugzilla account (if they don't have one already) | ||
Once these steps are done, the [[ReMo/SOPs/Mentoring/Orientation]] Period starts. The Orientation Period will last 3 months, to make sure that Reps are well fitted for their responsibilities. Reps will need to create Reports on the Reps Portal to document their work. The Reps Council will decide who will proceed to being an official Rep after those 3 months according to the submitted reports. | Once these steps are done, the [[ReMo/SOPs/Mentoring/Orientation]] Period starts. The Orientation Period will last 3 months, to make sure that Reps are well fitted for their responsibilities. Reps will need to create Reports on the Reps Portal to document their work. The Reps Council will decide who will proceed to being an official Rep after those 3 months according to the submitted reports. | ||
== Whiteboard status for applications == | |||
'''Agreement not signed ( | '''Agreement not signed (Teachable)''': Agreement needs to be signed by applicant and NDA invite accepted on people.mozilla.org | ||
'''Orientation Period ( | '''Orientation Period (Teachable)''': Applicant is now in the Orientation Period | ||
= Tools used in the Webinar workflow = | |||
* | * Teachable | ||
* Bugzilla for applications | * Bugzilla for applications | ||
* | * people.mozilla.org | ||
* eMail for coordination | * eMail for coordination | ||
* | * Community portal for the Reps profile | ||
* Wiki for information about SOPs | * Wiki for information about SOPs | ||
[[Category:Remosop]] | [[Category:Remosop]] | ||
Latest revision as of 19:27, 29 September 2023
Warning: With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.
Main | Join | Procedures (SOPs) | Leadership (Resources) | Meetings | Website | FAQ
Joining
While the Mozilla Reps program is open to all, becoming a Mozilla Reps involves a short but rigorous application process to make sure those interested are motivated and ready to take on a leadership role within the Mozilla community. You can find all criteria regarding a Reps application on the Selection Criteria page. During the Onboarding period and the various steps, if there is no reply from the applicants in a range of three weeks on the ticket, the application will be closed also if approved.
In the second half of 2016 we came to the edges of our possibilities to assign all new Reps to new mentors and having a quality onboarding experience. In 2020, we changed the Webinar to a Teachable course with a similar structure as the Webinar. We did that to ensure that information can be easily updated. We are currently using the Teachable course to make the on-boarding part easier, as well as working on Coaching materials and new coaching training to on-board new coaches. The Teachable course is divided to 3 sub - courses. You can find more about Teachable courses in the Teachable page.
Step 1 - Submit application
You can find all criteria regarding your Reps application on the Selection Criteria page. Please read that to make sure your application fulfills all requirements. Next, fill out and submit the MozillaReps application form. We require all applicants to have at least [ReMo/SOPs/Vouching one vouch] from another Rep in the application bug. We would recommend including 3 vouches, but we value quality over quantity. Once these vouches have been verified by the Onboarding team, you will be put in the queue to be screened.
Whiteboard status for applications
Missing Info: Application has obviously missing information based on Application Criteria
Pending References: Application hasn't gotten any references yet
Next screening round: Planned to be screened in next application round
Step 2 - Screening
Based on the selection criteria the onboarding team will screen the pending applications regularly. Currently, we are planning to run this screening every 2 weeks. This means that if you don't hear back from us within 3 weeks, we missed the application and ask you to write a mail to the Reps Council reminding us. Qualifying applicants will be marked as "Teachable" to be included in the next round of the Webinar. Applicants that do not show a strong track record will be rejected with an appropriate explanation and their application will be closed.
Initial actions in the application:
- Initial check according to the [ReMo/Application_Process/Selection_Criteria Selection Criteria]
- To make it easier, the following text is posted to give background on why there is an additional vouch necessary on the Reps application
@X, @Y: You have been added as a voucher for this application. The vouch here is for the Reps application at hand, not general participation within Mozilla.
We would like to know more from you about the following questions regarding the applicant:
- How has the applicant impacted the community you are working in?
- How would you qualify the applicant’s skill regarding mobilizing the communities the applicant has been working with?
If you don’t feel comfortable vouching for the applicant or think the applicant is not ready for Reps yet, it’s fine to not answer these questions at all.
Thanks in advance,
<name of Council member>
on behalf of the Onboarding Team and the Reps Council
Screening after application is completely filled out: Information about the screening process can be found at ReMo/Webinar/Screening.
The final decision will be communicated to the applicant according to the Screening documentation and further steps are taken for the Teachable part if accepted.
Step 3 - Teachable
Once an applicant is accepted, we ask them to complete the 3 Teachable sub-courses
Check Reps/Webinar/Teachable for Teachable related content.
Whiteboard status for applications
Onboarding Teachable: Application was screened and accepted. The applicant is now in the phase to do the Teachable steps.
Step 4 - Orientation period
- Return the Mozilla Rep Agreement signed and sent by email
- Council adds Rep to the Reps group on the Community Portal
- Add the Reps to the queue to get a mentor
- Council subscribes Rep to Reps mailing list
- Creation of Bugzilla account (if they don't have one already)
Once these steps are done, the ReMo/SOPs/Mentoring/Orientation Period starts. The Orientation Period will last 3 months, to make sure that Reps are well fitted for their responsibilities. Reps will need to create Reports on the Reps Portal to document their work. The Reps Council will decide who will proceed to being an official Rep after those 3 months according to the submitted reports.
Whiteboard status for applications
Agreement not signed (Teachable): Agreement needs to be signed by applicant and NDA invite accepted on people.mozilla.org
Orientation Period (Teachable): Applicant is now in the Orientation Period
Tools used in the Webinar workflow
- Teachable
- Bugzilla for applications
- people.mozilla.org
- eMail for coordination
- Community portal for the Reps profile
- Wiki for information about SOPs