Confirm
550
edits
Changes
Add "dropping out of Council" section
* Provide guidance for Mozilla Reps
The 7 volunteers sitting on the council are elected by existing Mozilla Reps for 12-month terms depending on their previous term (if any) as a Council member.
Archive of previous Eligibility and criteria based on [https://remo.etherpad.mozilla.org/camp2012-governance initial meetings] are [[ReMo/Council/Elections/Archives|here]] .
You can find out the history of the council and more info [[ReMo/Council/History|'''here''']].
You can find the list of the current Council members '''[https://reps.mozilla.org/people/#/group/council/ here]'''. To contact the Council, please send an email to '''reps-council@mozilla.com'''.
<onlyinclude>
{| class="wikitable" width=100%
* Konstantina/Nuke will assign the current chair person to the above alias
Members of the Council have specific tasks to complete and responsibilities to agree to once they join the Council, including:
* Be in contact and reply within 72h (exceptions when absence is announced) to Council threads
* Notify the Council at least 1 month before of their anticipated absence
* Find another Council member who agrees to cover for them while they're absent, including mentoring of Reps, budget reviews and participation at meetings ''NB: if a Council member realises that they must be absent from the program for more than 1 month, then the Council must be notified as soon as possible in order to find a permanent replacement. ''
The [[Reps/Peers|Reps Peers]] are responsible to hold Council accountable to their tasks.
* Every Council member should participate (not only reading) in discussions happening on Discourse and the Council alias
* Every current/future Council member should agree to use Github for sharing updates and activities
* Every Council member should give a small update after every quarter summarizing their work (mostly OKR related)
* OKRs should not be published later than 3 weeks into the quarter
* Council should ask Peers actively for feedback - Peers can however give feedback without a specific ask - feedback doesn’t need to be on a working document, this can also be in the middle of a discussion in Discourse. The Council members ask Peers for feedback for strategic parts of their working documents once Council reviews those as well. Feedback can of course be asked already before that if valuable (e.g. “what do you think of this direction?”). Council members can also give feedback to Peers whenever they see fit.
* Council can define a “bridge person” (does not by default mean the current council chair) that interacts with Peers on a regular basis if Council decides to do so
* Council Updates in the Reps Weekly Call should be distributed among the Council members so it’s not always the same person doing the update. This should be decided async by the Council before the call. The Peers advice this to be done as an action item during prior Council call.
* Council member should fill out the timeline for the OKRs they are responsible for to identify possible resource problems (vacations, day job, …). OKRs with identified shortcomings in resourcing should have at least one other Council member supporting.
* Peers give context of previous discussions/incidents in day-to-day discussions where needed
* Peers are heavily involved in strategic discussions around the Reps Program and are always part of strategic discussions
In case you want to contact the council for questions/inquiries or suggestions you should use one of the following channels:
* reps-council@mozilla.com email alias
To make sure that this is in compliance with our voting, the first person to be asked to step in will be the one Rep voted most, but not making the cut in the previous elections. If 4 spots were open, we will ask the 5th in the voting ranking to take on this new responsibility. If this person does not want to step up, it’s up to the Module Owner to decide on a replacement for the rest of the term. If the remaining time of the resigning Rep’s term is less than 3 months, the Module Owner can decide to nominate another Rep who has been on Council before to decrease the onboarding overhead.
