Reps/SOPs/Council onboarding

This page describes the process to on board new Council members.

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 project lead will send them an email:

Subject: Welcome to the Council!

Hello new council fellows,

I'm [Name], 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

When?

The onboarding of new Council members entails practical training on the tools and processes of the Reps Council and mentorship from former Council members, the program lead and other leaders at Mozilla.

The process starts from the day after the election results. The new council members will receive practical training on lasts for 3 weeks and this SOP outlines most of the practical training.

The mentorship process will last longer with former council members budding up with new council members. Mozilla leaders will also be involved in the mentorship of new and existing Council members.

Week 1

Each new Council member is assigned a council buddy, who will help him/her understand and navigate the Council responsibilities. will be one of outgoing Council members or a former Council if needed.
Council chair will meet in video with new members and explain their responsibilities and tools, buddies will help with this.

Training meeting agenda

Communications

Alias and Council list
- How to filter emais.
  - 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
- https://wiki.mozilla.org/ReMo/Meetings#Bi-weekly_Council_Meetings
- Be on the next one (mandatory)
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".
New council see how things work and the work-flow.
Buddies will answer any question to new Council.

Week 3

Admin gives permissions on the portal to new and revoke to old ones.
New council 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 alias and list.
- 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.