Reps: Difference between revisions

Jump to navigation Jump to search

Reps (view source)

Revision as of 23:59, 24 February 2011

1,032 bytes removed ,  24 February 2011
Undo revision 286808 by Ppapadeas (talk)
(Undo revision 286808 by Ppapadeas (talk))
Line 1: Line 1:
<table class="wikitable" style="float: right;">
{| class="wikitable" style="float: right;"
<tr>
| bgcolor="00FF00" | Pre-Planning
<td bgcolor="00FF00"> Pre-Planning
|-
</td></tr>
| bgcolor="#CC3300" | '''Planning'''
<tr>
|-
<td bgcolor="#CC3300"> <b>Planning</b>
| bgcolor="cyan" | Deploying
</td></tr>
|-
<tr>
| bgcolor="cyan" | Live
<td bgcolor="cyan"> Deploying
|}
</td></tr>
 
<tr>
 
<td bgcolor="cyan"> Live
 
</td></tr></table>
{{Admon/important | Draft | This is a draft outline of an upcoming program. Edit furiously! }}
<p><br />
ReMo is the code name for the '''Mozilla Representatives Program''', a program that aims to empower and support volunteer Mozillians who want to be “official” Mozilla representatives in their region/locale.
</p><p><span class="fck_mw_template">{{Admon/important | Draft | This is a draft outline of an upcoming program. Edit furiously! }}</span>
[[Image:Remo_skaff_2.png|350px|thumb|right|We are building this! Join Us!]]
ReMo is the code name for the <b>Mozilla Representatives Program</b>, a program that aims to empower and support volunteer Mozillians who want to be “official” Mozilla representatives in their region/locale.
== Purpose ==
<img src="/images/thumb/9/9f/Remo_skaff_2.png/350px-Remo_skaff_2.png" _fck_mw_filename="Remo skaff 2.png" _fck_mw_location="right" _fck_mw_width="350" _fck_mw_type="thumb" alt="" class="fck_mw_frame fck_mw_right" />
 
</p>
ReMo will provide a simple and structured framework to inform, assist and support Mozilla volunteers who want to become official representatives of Mozilla in their region. They will be known as Mozilla Reps (or MozReps).
<h2> Purpose </h2>
 
<p>ReMo will provide a simple and structured framework to inform, assist and support Mozilla volunteers who want to become official representatives of Mozilla in their region. They will be known as Mozilla Reps (or MozReps).
A Mozilla Rep will have the following responsibilities:
</p><p>A Mozilla Rep will have the following responsibilities:
 
</p>
* '''represent''' Mozilla in their region and have a clear understanding of Mozilla in her/his local tech/social/cultural context
<ul><li> <b>represent</b> Mozilla in their region and have a clear understanding of Mozilla in her/his local tech/social/cultural context
* '''promote''' the Mozilla Project and our mission
</li><li> <b>promote</b> the Mozilla Project and our mission
* '''build''' on existing contributor-building efforts and programs
</li><li> <b>build</b> on existing contributor-building efforts and programs
* '''inspire''', '''recruit''' and '''support''' new contributors
</li><li> <b>inspire</b>, <b>recruit</b> and <b>support</b> new contributors
* '''mentor''' future Mozilla Reps
</li><li> <b>mentor</b> future Mozilla Reps
 
</li></ul>
== Anti-Purpose ==
<h2> Anti-Purpose </h2>
 
<p>Here are some things ReMo specificly aims <b>NOT</b> to do&nbsp;:  
Here are some things ReMo specificly aims '''NOT''' to do :  
</p>
 
<ul><li> replace or undermine efforts by existing communities of Mozilla volunteers around the world to recruit new contributors
* replace or undermine efforts by existing communities of Mozilla volunteers around the world to recruit new contributors
</li><li> become a top-down ambassador program run exclusively by Mozilla staff
* become a top-down ambassador program run exclusively by Mozilla staff
</li></ul>
 
<h2> Characteristics of the ReMo program </h2>
== Characteristics of the ReMo program ==
<ul><li> open to EVERYONE but rigorous membership process
 
</li><li> community-driven (once ReMo has reached mature stage)
* open to EVERYONE but rigorous membership process
</li><li> vertical distribution of responsibilities
* community-driven (once ReMo has reached mature stage)
</li><li> structured and well documented
* vertical distribution of responsibilities
</li><li> meritocratic
* structured and well documented
</li><li> regular monitoring/assessment of activity
* meritocratic
</li></ul>
* regular monitoring/assessment of activity
<h2> Who can be a Mozilla Rep? </h2>
 
<p>Anyone who is:
== Who can be a Mozilla Rep? ==
</p>
 
<ul><li> <b>passionate</b> about Mozilla Project  
Anyone who is:
</li><li> <b>knowledgeable</b> of the Mozilla organization, its mission and its products
 
</li><li> <b>willing</b> to communicate all those, to as many people as possible
* '''passionate''' about Mozilla Project  
</li></ul>
* '''knowledgeable''' of the Mozilla organization, its mission and its products
<h2> ReMo Website </h2>
* '''willing''' to communicate all those, to as many people as possible
<p>In order to accommodate the needs of this program, infrastructure and outreach website is needed.  
 
</p><p>More info on <a href="ReMo/Website">Website planning page</a>
== ReMo Website ==
</p>
 
<h3> Use Cases and User Tasks </h3>
In order to accommodate the needs of this program, infrastructure and outreach website is needed.  
<p>A list of most common use cases and user tasks for ReMo:
 
</p>
More info on [[ReMo/Website|Website planning page]]
<ul><li> Apply to become a Mozilla Rep (once application sent, each applicant will go through a simple but rigorous screening process)
 
</li><li> Log in with your ReMo LDAP account and start updating your profile
=== Use Cases and User Tasks ===
</li><li> See / Browse through various Events happening near him
 
</li><li> Add events to ReMo calendar and become owner of these events
A list of most common use cases and user tasks for ReMo:
</li><li> Use ReMo ticketing system to request swag or sponsorship for events
 
</li><li> Peruse ReMo file repository for slide decks, presentation templates, printable materials (ie. posters, flyers, stickers)
* Apply to become a Mozilla Rep (once application sent, each applicant will go through a simple but rigorous screening process)
</li><li> Represent Mozilla at events
* Log in with your ReMo LDAP account and start updating your profile
</li><li> Customize and order swag for your community  
* See / Browse through various Events happening near him
</li><li> Customize and order your ReMo business card
* Add events to ReMo calendar and become owner of these events
</li><li> Regularly update your ReMo profile with recent activities (ie. events, presentations, contributions etc...)
* Use ReMo ticketing system to request swag or sponsorship for events
</li><li> Mentor recent Mozilla Reps and monitor their progress
* Peruse ReMo file repository for slide decks, presentation templates, printable materials (ie. posters, flyers, stickers)
</li><li> See other ReMo activities through the ReMo planet
* Represent Mozilla at events
</li><li> Add his blog on ReMo planet
* Customize and order swag for your community  
</li></ul>
* Customize and order your ReMo business card
<p><span class="fck_mw_template">{{Admon/note | Note | Please add more usage scenarios!}}</span>
* Regularly update your ReMo profile with recent activities (ie. events, presentations, contributions etc...)
</p>
* Mentor recent Mozilla Reps and monitor their progress
<h2> Schedule </h2>
* See other ReMo activities through the ReMo planet
<p>The aim is to have 25 ReMo test-pilots (all veteran Mozilla contributors) signed up to test the platform by end of Q1 2011 and have ReMo officially roll out some time in Q2 2011
* Add his blog on ReMo planet
</p><p>The detailed timeline and status of project components can be found at <a href="ReMo/Phase 1 Plan">Phase 1 Plan</a>
 
</p>
{{Admon/note | Note | Please add more usage scenarios!}}
<h3> Summary Plan </h3>
 
<p>A summary plan is available that contains details on the thinking behind ReMo as well as the structure of the program.
== Schedule ==
</p><p>It can be found  
 
</p>
The aim is to have 25 ReMo test-pilots (all veteran Mozilla contributors) signed up to test the platform by end of Q1 2011 and have ReMo officially roll out some time in Q2 2011
<ul><li> Ver 1.0 <a href="https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.0.pdf">here</a>
 
</li><li> Ver 1.1 <a href="https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.1.pdf">here</a>
The detailed timeline and status of project components can be found at [[ReMo/Phase_1_Plan|Phase 1 Plan]]
</li></ul>
 
<h2> Outreach </h2>
=== Summary Plan ===
<p>Content and resources made to communicate initially ReMo to the rest of Mozilla and the public in general can be found on our <a href="ReMo/outreach">Outreach</a> page.
 
</p><p><br />
A summary plan is available that contains details on the thinking behind ReMo as well as the structure of the program.
</p>
 
<h2> Contact </h2>
It can be found  
<p>In order to communicate throughout the planning and deploying stage of ReMo, we have created several communication channels:
 
</p>
* Ver 1.0 [https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.0.pdf here]
<ul><li> <b>IRC</b> You can join us on these channels on irc.mozilla.org
* Ver 1.1 [https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.1.pdf here]
<ul><li> #remo General Channel for ReMo (will be used as our main one)
 
</li><li> #remo-dev Channel on planning and deploying ReMo
== Outreach ==
</li></ul>
 
</li><li> <b>Mailing List</b> (stay tuned for that)
Content and resources made to communicate initially ReMo to the rest of Mozilla and the public in general can be found on our [[ReMo/outreach|Outreach]] page.
</li></ul>
 
<p>Bi-weekly meetings on IRC will be held at three different times to encourage everyone to share ideas, thoughts and suggestions as ReMo planning moves forward:
 
</p>
== Contact ==
<ul><li> <b>IRC bi-weekly meetings in #remo</b>
 
<ul><li> Europe, Middle East and Afria: Thursdays at 18:00 UTC (next one Thursday 3 March)
In order to communicate throughout the planning and deploying stage of ReMo, we have created several communication channels:
</li><li> Asia and Pacific: Thursdays at 09:00 UTC (next one Thursday 3 March)  
 
</li><li> North America and Latin America: Thursdays at 23:00 UTC (next one Thursday 3 March)
* '''IRC''' You can join us on these channels on irc.mozilla.org
</li></ul>
** #remo General Channel for ReMo (will be used as our main one)
</li></ul>
** #remo-dev Channel on planning and deploying ReMo
<h2> Resources </h2>
* '''Mailing List''' (stay tuned for that)
<ul><li> William Quiviger is project lead
 
</li><li> Pierros Papadeas is assistant project lead
Bi-weekly meetings on IRC will be held at three different times to encourage everyone to share ideas, thoughts and suggestions as ReMo planning moves forward:
</li><li> WebDev needs:
* '''IRC bi-weekly meetings in #remo'''
<ul><li> TBD
** Europe, Middle East and Afria: Thursdays at 18:00 UTC (next one Thursday 3 March)
</li></ul>
** Asia and Pacific: Thursdays at 09:00 UTC (next one Thursday 3 March)  
</li><li> Design needs:
** North America and Latin America: Thursdays at 23:00 UTC (next one Thursday 3 March)
<ul><li> We'll need someone to help design ReMo logo and ReMo collateral (ie. tshirt, bags, business cards etc...)
 
</li></ul>
== Resources ==
</li><li> Legal needs:  
 
<ul><li> TBD
* William Quiviger is project lead
</li></ul>
* Pierros Papadeas is assistant project lead
</li></ul>
* WebDev needs:
** TBD
* Design needs:
** We'll need someone to help design ReMo logo and ReMo collateral (ie. tshirt, bags, business cards etc...)
* Legal needs:  
** TBD
Ppapadeas
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,783

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/286810"

Navigation menu