Canmove, confirm, emeritus
1,783
edits
Changes
Added Module documentation
The Mozilla Reps governance structure is broken down into 3 bodies, each with specific duties and functions. Aligning with Mozilla Governance structure we also have a Module with Owner and Peers
<div style="float:right;background-color:white;margin:10px;">[[File:Remo_structure_draft_5.png|600px]]</div>
The Mozilla Reps Council is the program's 9-member governing body and its members are elected. The Council is tasked to ensure that the Mozilla Reps program runs smoothly, oversees the governance and finances of the program and serves as an advisory body within the Mozilla organisation.
'''Learn more about the Council [[ReMo/Council|here]]'''.
Mozilla Rep mentors play a crucial part in the success of the program. Mentors provide mentorship and guidance to Reps to ensure that Reps are successful and fulfilling their responsbilities. Mentors are also responsible for reviewing monthly reports, budget requests and swag requests filed by their Reps.
'''Learn more about mentors [[ReMo/Mentors|here]]'''
Reps are deeply passionate Mozillians who represent Mozilla in their country or region and are committed to educating and empowering people to support the Mozilla mission and contribute to the project. As Reps, they are the eyes, ears and voice of Mozilla on the ground and support their local communities with a specific set of tools and resources they are equipped with.
''NB: in the initial phase of the Mozilla Reps program, members of the provisional council were designated by the ReMo project leads (William and Pierros) based on a specific different criteria, notably on geographic location and on the member's level of participation in early brainstorms of the program. Now that the Mozilla Reps has reached mature stage, an election/designation or rotation system has been introduced to select the next members of the Mozilla Reps Council, going forward.''
== Mozilla Reps Module ===== Module Owner === '''Role''' The "module owner" is the person to whom leadership of the module's work has been delegated. Module owner is not a tyrant. He/she is chartered to make decisions with input from the community and in the best interests of the community. The owner and peers of the Module Ownership module will get involved if controversy develops and cannot be resolved otherwise. Mozilla Reps specific roles include: * Holding the Mozilla Reps Council accountable for their actions.* Provide historical background on issues and decisions to the council.* Appointing Peers, making sure that historical councils are represented to the extend possible.* Being the point person for general questions/concerns about about the program as a whole and how it fits within the Mozilla project.* Criteria and selection: see [https://www.mozilla.org/hacking/module-ownership.html here] === Module Peers ==='''Role'''Peers possess many of the qualities of a good module owner and compliment and advise his/her actions see [https://www.mozilla.org/hacking/module-ownership.html here] for more details * Criteria and selection: see [https://www.mozilla.org/hacking/module-ownership.html here] === Communication between Module Owner/Peers and Council ===Module Owner and Peers might need (or be asked) to communicate with Reps Council. The following guidelines apply: * The Council can request Module Owner/Peers opinion, intervention, action or feedback on a particular issue. This should be done by either explicitly mentioning @peers on reps-council alias or list, or by sending an email to reps-peers@mozilla.com with [Ask] in subject.* Module Owner and Peers are monitoring all council (and reps) communications and might want to intervene to provide guidance or for conflict resolution. This communication needs to be coordinated/surfaced by the Module Owner. == Beyond the Mozilla Reps Program ===
Mozilla Reps Council members are, by definition, experienced and accomplished Mozilla volunteers who have a deep commitment to the project. As such, the Mozilla Reps Council should logically participate in strategic decision-making within the organization to represent the interests of regional volunteer communities at large.
Mozilla Reps is still a relatively new program so our focus has until recently been to define the best growth path for Reps within the program (ie. Rep --> Mentor --> Council Member). Now that the program is reaching maturity, we have been spending more time exploring a growth path for Reps beyond the program and into higher circles of leadership. Stay tuned for regular updates on this.
