Personal tools

ReMo/Council

From MozillaWiki

Jump to: navigation, search

Remo logo horizontal.png Main | Join | People | Events | Tools & Resources | SOPs | Meetings | SIGs | Website | Planning | FAQ


The Mozilla Reps Council is the governing body of the Mozilla Reps Program. It provides the general vision of the program and oversees day-to-day operations globally. Currently, 7 volunteers and 2 paid staff sit on the council. Its specific duties and functions are to:

  • provide a governance and support structure to assist Mozilla Reps worldwide
  • oversee global Rep activities
  • oversee global budget /swag management for events
  • represent Mozilla Reps interests within the Mozilla organization
  • nominate Mozilla Reps mentors
  • resolve disputes
  • provide guidance for Mozilla Reps


Election/Designation of Council Members

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.

Elections are held every 6 months for 4 or 3 positions that are open. (see Council History) Eligibility and criteria based on previous meetings are:

  • Nominee should be a current Mozilla Reps Mentor
  • Bug responsiveness of under 48 hours
  • Commitment to bi-weekly meetings, usually on weekends
  • Availability to travel
  • Proficiency in English is required
  • Minimum 2 years experience contributing to the (Mozilla) project is a plus

For more information on the Mozilla Reps election process, click here.

Council History

You can find out the history of the council and more info here.

Council Members

You can find the list of the current Council members here. To contact the Council, please send an email to reps-council@mozilla.com.

Council Chair

On November 1st, 2012, the Mozilla Reps Council began designating a chairperson to help make the council work more efficiently and effectively. The "Council Chair" is designated a rotating 2-month basis and has the following responsibilities:

  • chair council meetings
  • send meeting reminders to the council
  • create meeting agenda and gather agenda items from all members
  • share meeting minutes and follow-up on action items with designated owners
  • be co-spokesperson with Council Comms Lead at the organizational level (eg. team meetings, offsites, town hall meetings, mailing lists)
  • keep overall program goals and objectives in check and ensure that everything is on track
  • update Mozilla Reps Module peers every 2 weeks with current issues at reps-peers@mozilla.com

The Council chair can be reached at reps-chair@mozilla.com

Schedule for the period of Nov 2012 - July 2014 :

  • November 2012: Majken Connor
  • December 2012: Regnard Raquedan
  • January 2013: Gloria Meneses
  • February 2013: William Quiviger (replacing William "FuzzyFox" Duyck)
  • March 2013: Pierros Papadeas
  • April 2013: Melek Jebnoun
  • May 2013: Melek Jebnoun
  • June 2013: Ioana Chiorean
  • July 2013: Ioana Chiorean
  • August 2013: Soumya Deb
  • September 2013: Soumya Deb
  • October 2013: Bob Reyes
  • November 2013 Bob Reyes
  • December 2013: Majda Nafissa Rahal
  • January 2014: Majda Nafissa Rahal
  • February 2014: Nikos Roussos
  • March 2014: Nikos Roussos
  • April 2014: Sayak Sarkar
  • May 2014: Sayak Sarkar
  • June 2014: Guillermo Movia
  • July 2014: Guillermo Movia

Tasks and Responsibilities of Council Members

Members of the Council have specific tasks to complete and responsibilities to agree to once they join the Council, including:

  • individually guide/mentor Mozilla Rep applicants in their region if assigned an applicant by William or Pierros
    • contact applicant via email (council designates mentor based on region/number)
    • schedule a short IRC meeting the same week for a short interview
    • give Go/No-Go after consulting with council and performing background check
      • in case of a No-Go, inform applicant via email about decision
      • in case of Go: inform applicant of next steps via email
    • guide applicant through process of signing and returning the Mozilla Reps Agreement, creating wiki profile, subscribing to mailing list and providing walk-through of main ReMo Tools and SOPs
  • participate in short bi-weekly IRC meetings to discuss overall status and roadmap of the program
  • attend ReMo work week(s) to meet in person, brainstorm and discuss future of the program (NB: no date or location have been determined nor has any budget been allocated yet so stay tuned for that)
  • provide mentorship and guidance to Mozilla Rep mentors and Mozilla Reps

Council Leave of Absence

If a Council member must step away from the program and cannot fulfill his/her duties (eg. vacation), then the Council must do the following:

  • 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 (s)he 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.

Contact the Council

In case you want to contact the council for questions/inquiries or suggestions you should use one of the following channels:

  • #remo-council IRC channel
  • reps-council@mozilla.com email alias