Reps/SOPs/Council onboarding: Difference between revisions

← Older edit

Reps/SOPs/Council onboarding (view source)

Revision as of 19:33, 29 September 2023

1,007 bytes removed , 29 September 2023

Warning added

Seburo

313

edits

@@ 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}}
-This page describes the process to on board new Council members.
+The onboarding of new Council members entails practical training on the tools and processes of the Reps Council. Onboarding is done by the staff members of the Reps Council. Outgoing Council members help through the buddy system.
-==Who?==
-Project lead will be in charge of leading the efforts, with the help of the Council.
-==How?==
-Once the Council elections are over and new Council members are elected, the Chair will send them an email:
-<pre>
-Subject: Welcome to the Council!
-Hello new council fellows,
-I'm [Name], the current Council chair, welcome to the Reps Council. In order to brief and give you a small training regarding your new responsibilities as Council Members I would like to set up a meeting with you.
-Please let me know [dates/times] work for you.
-Regards
-</pre>
-==When?==
+The process starts from the day after the election results. The new Council members will receive practical training which lasts for 3 weeks and this SOP outlines most of the practical training.
-On boarding starts from the day after the election results and lasts for 3 weeks.
+All specific tasks can be found in the [[Reps/Council/Elections#Election_Schedule|Elections Timeline]].
 ===Week 1===
-* Each new Council member is assigned to a "buddie", who will help him during the whole on boarding process. This buddie will be one of outgoing Council members or a former Council if needed.
+* The Council staff appointees will meet in video with new members and explain their responsibilities and tools.
-* Council chair will meet in video with new members and explain their responsibilities and tools, buddies will help with this.
-====Training meeting agenda====
+====Operation Training meeting agenda====
 '''Communications'''
-* Alias and Council list
+* Discourse Council alias inbox
-** How to filter emais.
+* GitHub
-*** https://wiki.mozilla.org/Bugzilla:FAQ:Filtering_Bugzilla_Email_In_Gmail
-*** http://hearsum.ca/blog/how-to-not-get-spammed-by-bugzilla/
-*** from:(bugzilla-daemon@mozilla.org) to:(reps-council@mozilla.com,)
-*** to:(reps-council@mozilla.com) -{bugzilla-daemon@mozilla.org}
-*** https://wiki.mozilla.org/ReMo/Tools_and_Resources/Workflow#Council
-* Trello board.
-** https://trello.com/b/aqQ8cgqz/mozilla-reps
-** How does it work? Show some examples.
-** Admin to invite them to board
 * Subscribe to governance
 ** https://www.mozilla.org/hacking/module-ownership.html
 ** https://lists.mozilla.org/listinfo/governance
-* Bi-weekly meetings
+* Weekly meetings
-** https://wiki.mozilla.org/ReMo/Meetings#Bi-weekly_Council_Meetings
+** https://wiki.mozilla.org/ReMo/Meetings#Remo_Council_Weekly_Meetings
 ** Be on the next one (mandatory)
-* What's the council chair?
+* What's the Council Chair?
 ** https://wiki.mozilla.org/ReMo/Council#Council_Chair
-'''Budget and voting processes'''
-* https://wiki.mozilla.org/ReMo/SOPs/Budget#Filtering_phase
-* How council votes on the portal? When?
-** Discussion and voting phases.
-*** Day 1: Discussion email: Review, and add your comment IN the voting page.
-*** (If changes to the budget are needed, these should be commented on the bug ASAP by any Council member)
-*** Day 3: Voting email: Review other Councils comments and vote.
-*** Day 6: Voting ends.
-*** Day 7: Council assigned to the bug updates the bug with comments.
-*** https://wiki.mozilla.org/ReMo/SOPs/Budget#Council_Member_Assignment_for_budgets_OVER_.24500_USD
-*** Extensions.
 ===Week 2===
-* New council added to mailing list and alias, just as "lurkers".
+* Each new Council member paired with a council buddy, who will help them understand and navigate the Council responsibilities. The buddy will be one of the outgoing Council members or a former Council member.
-* New council see how things work and the work-flow.
+* New Council added to Council Alias Discourse Inbox, so that they can understand what happens on that list and have access to older conversations.
-* Buddies will answer any question to new Council.
+* New Council members get permissions for everything they need.
+* New Council members can see see how things work and the workflow.
+* Buddies will answer any questions new Council members might have and bring them up to speed about ongoing projects.
 ===Week 3===
-* Admin gives permissions on the portal to new and revoke to old ones.
+* Admin adds members on the Community Portal group and revokes permissions of the outgoing members.
-* New council on boarded and start to fulfill their role completely.
+* New Council is on-boarded and start to fulfill their role completely.
-* Buddies still support any question new council may have.
+* At the end of this week former Council is removed from the Discourse Alias.
-* At the end of this week former Council is removed from alias and list.
+* New Council gets announced on Reps Blog.
-** Chair emails former Council announcing their duties are over as Council members.
-** Chair emails new members and reps-general announcing the new ones start their duties.
 [[Category:remosop]]