Confirm
550
edits
Changes
Adjust from quarterly to half-year
* Participate in the Open Innovation monthly meetings (monthly)
* Shape and give feedback on the Community Development OKRs (Objectives and Key Results) (every quarterhalf year)
* Participate on the Reps weekly Call (weekly)
* Interview Mozilla Corporation and Mozilla Foundation board members (once or twice per year)
* Shape Reps program quarterly half-yearly and yearly - via the Reps OKRs (in the beginning of each half year and quarterly)
* Implement OKRs depending on strategy
* Lead the monthly Newsletter Team (monthly)
* Introduce new Reps to the program (quarterly)
* Give feedback and overview the Activate campaign strategy (monthly)
* Decide on the Reps program budget allocation (quarterlyhalf-yearly)
* Lead community feedback and connect it with Mozilla leadership
* Lead the re-commitment process (quarterly)
== Documentation ==
* Every Council member should give a small update after every quarter half year summarizing their work (mostly OKR related)
* Every Council member should create issues to document their work in the Reps GitHub repository and keep them up to date
* Decisions should be recorded in the voting tool by creating votings as this better facilitates async voting. Votings in person can be conducted without voting if enough votes can be gathered.
* Finished working documents should lead to a post on Discourse to update Reps
* Where applicable, feedback should be gathered before starting a working document to gather Reps feedback and to inform them about what the Council member is gonna work on
* OKRs should not be published later than 3 weeks into the quarterhalf-year
== Asking for Peers feedback ==
* 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.
* OKRs and responsibilities should be equally distributed by taking into consideration bandwidth and availability of the council members.
* OKRs should have high priority, other business (except conflict resolution and top priority incidents) should be planned for the future (next quarter half-year OKRs for example)
* Council members should work together on the OKRs, provide timely feedback to not block each other
* 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.
