MozillaWiki

Events/Global Strategy 2011: Difference between revisions

Page Discussion

Events/Global Strategy 2011 (view source)

Revision as of 18:58, 17 May 2011

2,485 bytes added ,  17 May 2011
→‎Shared Infrastructure
 
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
{{Admon/important | Planning | This is a planning page under active development. Edit furiously! }}


== Mozilla Wide==
== Mozilla Wide==
===Preamble===
Mozilla is engaged in a broad range of events that target many audiences and outcomes. Until now, there has not be a deliberate effort to develop an overarching events strategy and ensure that the energies invested in events are effective, impacting, and harmonious across the organization. To the extent there can be shared infrastructure, resources, and other assets across the organization, these should be explored and built.
In an effort to describe possible shared tools and workflow improvements towards greater efficiency and impact, the following document is a '''DRAFT'''. It's a strawman to begin the conversation. There's much to revise and improve. Let's dig in!
===Framing Questions and Principles===
* How do we decide what events we attend/support?
** United front to contributors
** Need common decision-tree to measure against event requests
** Define roles. A task force and defined responsibilities.
** Common schedule and calendar (consider internal for planning vs. external for marketing)
** Common practices around sponsorship
** Participant coordination. Knowing who's attending what, how to max time there.
===Shared Goals===
===Shared Goals===
* Offer '''new entry points to Mozilla''' projects and people -- to participants in a global effort to keep the web open.
* Offer '''new entry points to Mozilla''' projects and people -- to participants in a global effort to keep the web open.
Line 7: Line 23:
* Leverage and '''extend our reach''' internationally and beyond targeted geographies and domains
* Leverage and '''extend our reach''' internationally and beyond targeted geographies and domains
* '''Improve web tools''' and products and increase their usage
* '''Improve web tools''' and products and increase their usage
* '''Teaching people''' about open technologies so that when designers and developers pick technologies, the open ones are top of mind.


===Event Matrix===
===Event Matrix===
Line 17: Line 34:
! scope="col" | Established User Community
! scope="col" | Established User Community
! scope="col" | Core Contributors
! scope="col" | Core Contributors
|-
! scope="row" | Value to Participants
|Learn about and build web tools that scratch their itches.
|Share knowledge and solve cutting edge issues
|Connect with fellow contributors and shape projects
|-
|-
! scope="row" | Small
! scope="row" | Small
|e.g. Hackasaurus Hackjams
|e.g. Hackasaurus Hackjams
|e.g. MozPub
|e.g. MozPub
|e.g. Community Meetups
|e.g. Local Community Meetups
|-
|-
! scope="row" | Medium
! scope="row" | Medium
|e.g. Buttercamp  
|e.g. Buttercamp  
|e.g. Design Jams
|e.g. Design Jams
|e.g. Team Offsites
|e.g. Inter-Community Meetups
|-
|-
! scope="row" | Large
! scope="row" | Large
Line 34: Line 56:
|-
|-
|}
|}
Questions/Suggestions:
* Settle on terms for audience types. Difference in usage of "users", "contributors", etc.
* This matrix is focused on our events. Need one for events we sponsor. Weights in size/audience, etc and determines priority.
* Which group is responsible for each category?
* Who identifies as Mozillian? Sometimes the community doesn't realize they have capacity / already doing something active.
* How Mozilla delivers involvement for events that we attend / sponsor
* How to determine priorities based on size, audiences
* Category / strategy for meetups during larger events (i.e. a Mozilla gathering within another conf)


===Shared Infrastructure===
===Shared Infrastructure===
* Calendars
* Calendars
** Christian has prototype
* Wikis
* Wikis
** https://wiki.mozilla.org/Events
* [[ReMo/Tools_and_Resources|Request forms]]
* [[ReMo/Tools_and_Resources|Request forms]]
** Speaker (we have one through press team)
** Conference sponsorship
** Travel sponsorship to speak/represent on behalf of Mozilla
* Communication channels
* Communication channels
* Mozilla Spaces
* Event agreements, making sure they respect our values and our users
* Feedback mechanisms
** For event attendees and organizers (did you reach your goals, was it worth it, etc)
* Existing tools
** lanyrd: Call out who's self-identified Mozillians. Conversation planned with the company.
** speaker rate = rating for talks


===Shared Resources===
===Shared Resources===
* ReMo
* ReMo
* Program assets (slides, print materials, videos, etc). [[ReMo/Toolkit|ReMo]]
* Program assets (slides, print materials, videos, etc). [[ReMo/Toolkit|ReMo]]
* Videos of talks Mozillians have given
* Event toolkits
* Event toolkits
* Content Modules
* Content Modules
* Speaker Bureau
** Listing of people who can talk about different subjects. (Shannon)
* Budget?
* Budget?
** Costs: How much do events cost Mozilla? Not just sponsorship, but people hours, travel time, travel, etc.
** Organization-wide budget pool. (Should all be in "6300 Events & Sponsorship" bucket.)
* Badges or awards for participating and speaking at an event as incentive
 


===Shared Branding===
===Shared Branding===
* Policies on joint branding. "Mozilla first."
* Policies on joint branding, such as showing affiliation and connections across events by using the Mozilla name in addition to the event name. For example, Mozilla Buttercamp or Mozilla Inter-Community Meet-up.


===Shared Metrics===
===Shared Metrics===
Line 62: Line 112:
* # of "Sparklez" (connections made at an event)
* # of "Sparklez" (connections made at an event)


==MoCo Events Strategy==
==Drumbeat Events Strategy==
===Background===
Mozilla and community organizers have iterated on a [https://drumbeat.org/en-US/events/ number of Drumbeat events] hosted in several cities. Now, with months of experience and feedback under our belt, we're taking our event strategy to the next level.
 
Over the past years, Mozilla has organized or participated in a wide variety of events. These events range from casual contributor meetup in a pub to an international (-day gathering of 700 Mozila staff and non=paid staff. Two categories of events stand out:
* events that aim to strengthen and build community (eg. Mozilla Summit, Inter-Community Meetups, Mozilla Camps etc...)
* events that aim to inform and educate about the Mozilla Project (eg. JSConf, CeBIT, FOSDEM, FISOL etc...)
 
Geographically, events have taken place all over the globe, most events have taken place in Europe.
 
Teams across the organization have been participating and/or organizing their events outside any clear global strategy or framework, often with little coordination with other teams. This page aims to outline a proposed global strategy moving forward.
 
===Strategy Overview===
 
The aim, moving forward, is to have a much more structure approach towards events and define a clear events strategy for 2011 and beyond.
 
==MoFo Events Strategy==
 
===Strategy Overview===
 
Mozilla and community organizers have iterated on a [https://drumbeat.org/en-US/events/ number of events] hosted in several cities. Now, with months of experience and feedback under our belt, we're taking our event strategy to the next level.
 
'''Events propel action through convening.'''


We're focusing on live events because we believe that by working together in a shared space, we can achieve more. Ideas emerge in realtime, conversations evolve, new connections are made. Because sometimes, despite all the ways we can collaborate together over vast distance, '''we can get more done f2f.'''
We're focusing on live events because we believe that by working together in a shared space, we can achieve more. Ideas emerge in realtime, conversations evolve, new connections are made. Because sometimes, despite all the ways we can collaborate together over vast distance, we can get more done f2f.  


But that means being deliberate and strategic about what events can accomplish and how all of these small pieces, loosely joined, can make the Web better.
Key to the strategy are: 1) growing a leadership circle and 2) deploying a scale of action along event sixes and templates.


===Action through convening===
Read more and add feedback: https://wiki.mozilla.org/Drumbeat/events/strategy


* Events offer '''new entry points''' to Mozilla projects and people -- to participants in a global effort to keep the web open
==Mozilla Engagement Events Strategy==
* Through shared action, we can '''improve web tools''' that benefit many groups -- artists, educators, businesses, activists, students -- anyone really, who uses the web.
Over the past years, Mozilla has organized or participated in a wide variety of events. These events range from casual contributor meetups in a pub to a large international 5-day gatherings of 700 Mozilla staff and non-paid staff.  
* We are all the makers of the web. And while we conduct much of our making online, often we can '''teach, learn, and build''' better in a shared space.


===Scale of Action===
Two categories of events stand out:
* events that aim to inspire, strengthen and build community (eg. Mozilla Summit, Inter-Community Meetups, Mozilla Camps etc...)
* events that aim to inspire, inform and educate about the Mozilla Project (eg. JSConf, CeBIT, FOSDEM, FISOL etc...)


====[[Events/Small|Small]]====
Geographically, events have taken place all over the globe, but most events have taken place in Europe. Teams across the organization have been participating and/or organizing their events outside any clear global strategy or framework, often with little coordination with other teams, hence, this strawman.
* frequent microevents. solving one discrete problem and bringing together a small, focused audience.  
* easy, lightweight organization


====[[Events/Medium|Medium]]====
Read more and add feedback to the Mozilla Engagement Events Strategy brainstorm: https://wiki.mozilla.org/Events/2011/Events_Strategy_Brainstorm
* workshops, hackfests, and regional meet-ups involving more participants with complexer and more diverse problem set to address.  
* more organizational involvement from staff and community.


====[[Events/Large|Large]]====
==Questions==
* annual heavy weights that draw in more numbers and accelerate many projects across a number of topics.  
How do we decide what events we attend/support?
* intense involvement from staff and community.
'''Needs:'''
** Common toolset to measure against event requests
** Define roles. A task force and defining responsibilities.
** Common schedule (Internal for planning vs. External for marketing)
Stormypeters
Confirmed users
172

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/302647...309675"