__NOTOC__
== Purpose Overview ==
ReMo will provide The program provides a simple framework and structured framework specific tools to informhelp Mozilla Reps be the eyes, assist ears and support voice of Mozilla. Anyone who is passionate and knowledgeable about Mozilla volunteers and who want is ready to become official representatives of Mozilla in their regiondive deeper into the project can sign-up to the program. They will be known as The Mozilla Reps (program helps push responsibility and authority to the edges, making it much easier for volunteers organize and/or MozReps)attend events, recruit and mentor new contributors, and support their local communities better.
A Mozilla Rep will have agrees to take on the following responsibilities:
* '''represent''' Mozilla in their country/region
* '''build on''' and '''support''' existing/future local community efforts and programs
* '''inspire''', '''recruit''' and '''support''' new contributors
* '''support''' and '''mentor''' future Mozilla Reps* '''document''' clearly all their his/her activities
== Anti-Purpose An "open" and "structured" program ==
Here are some things ReMo specifically aims '''NOT''' The Mozilla Reps program is open to do anyone who is:
* replace or undermine efforts by existing communities '''passionate''' about the Mozilla Project* '''knowledgeable''' of the Mozilla volunteers around the world to recruit new contributorsorganization, its mission, its products and its community* become a top-down ambassador program run exclusively by '''willing''' to communicate to as many people as possible and keen to inspire people to contribute to Mozilla staff
== Characteristics of Although anyone can sign-up to become a Mozilla Rep, that doesn't mean you automatically become a Mozilla Rep after submitting your application. Because Mozilla Reps are entrusted with new responsibilities and special tools to manage budgets, events and swag, each application is carefully reviewed by the ReMo program ==Mozilla Rep council and each applicant, if shortlisted, must pass a short a short interview before offically becoming a Mozilla Rep.
* open to EVERYONE but rigorous membership process* community-driven (once === ReMo has reached mature stage)* vertical distribution of responsibilities* structured and well documented* meritocratic* regular monitoring/assessment of activityApplication Process ===
== Who can be Anyone applying to become a Mozilla Rep? ==goes through three easy steps before officially becoming a Rep. To learn more, click [[ReMo/Application_Process|here]].
Anyone who is:== ReMo Tools ==
* '''passionate''' about the Mozilla Project* '''knowledgeable''' of the Mozilla organizationTo make it easier, its missionfaster and more efficient to organize/participate in events, its products obtain sponsorship for Mozilla-related travel and its community* '''willing''' order/customize swag, Mozilla Reps have access to communicate to as many people as possible a specific set of tools and keen to inspire people to contribute to Mozillaresources.
== ReMo Website = Budget request form ===
ReMo If a Mozilla Rep wants to request sponsorship to attend a conference, request a specific budget to organize a community event, or request reimbursement for a previsously approved activity, all the Mozilla Rep needs to do is fill out a special form which will be based on specific infrastructure reviewed by the Mozilla Reps council (see below) and approved/rejected within a dynamic websiteweek.
More info on can be found on our [[ReMo/Website|Website planning page]]=== Swag request form ===
=== Use Cases If a Mozilla Rep wants to request swag, all the Mozilla Rep needs to do is fill out a special form which will be reviewed by the Mozilla Reps council (see below) and User Tasks ===approved/rejected within a week.
A list of most common use cases and user tasks for ReMo:=== Events Toolkit ===
* Apply Various printable and downloadable materials exist to become a help Mozilla Reps spread the word about Mozilla Rep (once application sent, each applicant will go through a simple but rigorous screening process)* Log in with your ReMo LDAP account and start updating your profile* See / Browse through various Events happening near him* Add events to ReMo calendar and become owner educate people about specific areas of these events* Use ReMo ticketing system to request swag or sponsorship for events* Peruse ReMo file repository for slide decksthe project. '''Print collateral, presentation templates, printable materials (ie. posters, flyers, stickers)* Represent Mozilla at events* Customize slide decks and order swag videos are available for your community * Customize and order your download [[ReMo business card* Regularly update your ReMo profile with recent activities (ie. events, presentations, contributions etc../Toolkit|here]]'''.)* Mentor recent Mozilla Reps and monitor their progress* See other ReMo activities through the ReMo planet* Add his blog on ReMo planet
{{Admon/note | Note | Please add more usage scenarios!}}== ReMo Events ==
== Schedule ==See [[ReMo/Events_Calendar|ReMo Events Calendar]]
The aim is to have 25 ReMo test-pilots (all veteran Mozilla contributors) signed up to test the platform by end of Q1 2011 == Structure and have ReMo officially roll out some time in Q2 2011Governance ==
The detailed timeline and status Mozilla Reps program is a community-driven program that will create a global network of hundreds of Mozilla Reps by the end of project components can be found at [[ReMothe year. The following organizational structure will ensure that the program runs efficiently, in a participative/Phase_1_Plan|Phase 1 Plan]]collaborative way and in total transparency.
=== Summary Plan ===To learn more about the structure and governance of the program, click [[ReMo/Structure_Governance|here]].
A summary plan is available that contains details on the thinking behind ReMo as well as the structure of the program.== Resources ==
It can be found === ReMo Planning Wiki ===
* Ver 1.0 [https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.0.pdf here]* Ver 1.1 [https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.1.pdf here]* Ver 1.5 [https:The Mozilla Reps program is a work in progress and constantly evolving//wikiimproving thanks to its open and participatory nature.mozilla.org/File:Remo_brownbagAll Mozilla Reps are actively encouraged to participate in the design and planning of the program by regularly checking and updating the '''ReMo Planning Wiki'''.pdf here (Brown Bag presentation)]
== Outreach = Mozilla Reps SOPs ===
Documenting Mozilla Reps are involved in variety of processes and procedures, called SOPs, that ensure that the project, sharing it program works smoothly and gathering as much feedback as possible in a consistent way. An SOP (Standard Operating Procedure) is critical to the successful design a written document or instruction detailing all steps and implementation activities of ReMoa process or procedure. Tools and resources that will help to communicate ReMo to Mozillians and the public in general can be found on our [[ReMo/outreachSOPs|OutreachAll Mozilla Reps SOPs are described here]] page.
== Contact ==
In order the initial phase of the Mozilla Reps program, if you have a specific question or if you just want to communicate throughout learn more about the planning and deploying stage program, make sure to contact either one of ReMo, we the project leads: * William Quiviger is project lead (william [at] mozilla [dot] com)* Pierros Papadeas is assistant project lead (pierros [at] mozilla [dot] com) You're also strongly encouraged to reach out to other Mozilla Reps for any questions you may have created several communication channelsor ideas you may want to share:
* '''IRC''' You can join us on these channels on irc.mozilla.org
** [https://lists.mozilla.org/listinfo/reps-general Reps-general] General mailing list of Mozilla Reps
** [https://lists.mozilla.org/listinfo/reps-webdev Reps-webdev] WedDev and Infrastructure planning and building mailing list
Make sure you join our frequent [[ReMo/Meetings|meetings]] too!
== Project leads ==
* William Quiviger is project lead (william [at] mozilla [dot] com)
* Pierros Papadeas is assistant project lead (pierros [at] mozilla [dot] com)
