canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,104
edits
Events/Global Strategy 2011: Difference between revisions
Jump to navigation
Jump to search
→Mozilla Wide
| Line 8: | Line 8: | ||
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! | 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? | * How do we decide what events we attend/support? | ||
** United front to contributors | ** United front to contributors | ||
** | ** Need common decision-tree to measure against event requests | ||
** Define roles. A task force and defined responsibilities. | ** Define roles. A task force and defined responsibilities. | ||
** Common schedule (consider internal for planning vs. external for marketing) | ** Common schedule and calendar (consider internal for planning vs. external for marketing) | ||
** Common practices around sponsorship | ** Common practices around sponsorship | ||
** Participant coordination. Knowing who's attending what, how to max time there. | ** Participant coordination. Knowing who's attending what, how to max time there. | ||
| Line 62: | Line 62: | ||
* Which group is responsible for each category? | * Which group is responsible for each category? | ||
* Who identifies as Mozillian? Sometimes the community doesn't realize they have capacity / already doing something active. | * 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=== | ||
| Line 73: | Line 76: | ||
* Communication channels | * Communication channels | ||
* Mozilla Spaces | * Mozilla Spaces | ||
* | * Event agreements, making sure they respect our values and our users | ||
* Feedback mechanisms | * Feedback mechanisms | ||
** For event attendees and organizers (did you reach your goals, was it worth it, etc) | ** 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=== | ||