Reps/SOPs/Swag Requests: Difference between revisions
Konstantina (talk | contribs) No edit summary |
Konstantina (talk | contribs) No edit summary |
||
Line 20: | Line 20: | ||
# '''Type of the event''' | # '''Type of the event''' | ||
#*Community meetings | #*Community meetings | ||
#* Inter Community Meet ups ( eg. Arabic Mozilla Meetup) | |||
#* Moz Coffee | #* Moz Coffee | ||
#* [https://wiki.mozilla.org/ReMo/SOPs/MozCoffee Moz Coffee] | |||
#* Project Specific Hackathons (App days, L10n Marathons, QA Marathons) | #* Project Specific Hackathons (App days, L10n Marathons, QA Marathons) | ||
#* Talks-Presentations | #* Talks-Presentations | ||
Line 27: | Line 29: | ||
#* Booth in a conference | #* Booth in a conference | ||
#* Mozilla Tour | #* Mozilla Tour | ||
#* Special events | #* Special events | ||
# '''Connection to the 2014 goals''' | # '''Connection to the 2014 goals''' | ||
Line 41: | Line 42: | ||
#*selective = swag is only distributed to a selected type of attendee based on person's contribution to the project | #*selective = swag is only distributed to a selected type of attendee based on person's contribution to the project | ||
#* mix = combination of free for all and selective | #* mix = combination of free for all and selective | ||
===Swag Metrics and general info based on the event type=== | |||
#'''Community Meetings and Inter-community Meet-ups'' | |||
Community meetings don't need regular swag, we encourage ,however, the local communities, to produce their own local swag for awareness. | |||
#'''Moz Coffee''' | |||
#*Up to 20 people (max) | |||
#*Metrics | |||
engaging contributors-->sucess scenario 10% of the attendees (sign-ups) POST-EVENT | |||
awareness of the Mozilla mission/projects --> 100% | |||
Attendance-->70% of the estimated attendees showing up POST-EVENT | |||
# '''Project Specific Hackathons''' | |||
Attendance up to 100 | |||
Metrics | |||
set a measurable goal (eg. 10 articles to be translated, 5 apps etc) | |||
L10n, SUMO, App days -->up to 80% of the original goal (?? what do you mean "original goal" ? )-->the rep set a goal of translating articles/ creating apps we should track if he met that goal POST-EVENT | |||
QA run 80-100% of the goal tests POST-EVENT | |||
Attendance-->70% | |||
Contributor engagement--0-10% (0% if the attendees are all Mozillians) POST-EVENT | |||
Awareness of the specific project and how it works (tools, procedures) | |||
#'''Talks-Presentations''' | |||
General Info | |||
what is the talk about | |||
attendance up to 250 | |||
Metrics | |||
contributors--> 15% POST-EVENT | |||
New users fans--> 70% | |||
attendance 70% POST-EVENT | |||
Awareness of the Mozilla mission/projects --> 100% | |||
#'''WoMoz Events''' | |||
up to 20 people | |||
Metrics | |||
Same metrics with talks | |||
specific presentation about the WoMoz Community and women in technology | |||
#''' Talks in conferences/bigger events''' | |||
link of the conference | |||
schedule of the conference | |||
attendance: no limit (ask the reps to indicate of the last years conference attendance according to the organizers) | |||
Metrics | |||
contributors (0-10%) (0 cause attendees may not only interested in Mozilla Projects) POST-EVENT | |||
Fans/users (0-20 %) | |||
Awareness of the project | |||
Online link of the presentation (video is preferable) | |||
Attendance 10% of the conference (or less for huge events) 50 % for smaller events POST-EVENT | |||
#'''Booth in a conference''' | |||
same special requirements with Talk in conferences | |||
evidence that Mozilla will have a booth there | |||
Metrics | |||
Interaction and visibility--> attract 60% of the conference attendees POST-EVENT | |||
contributors-->0-5% of the attendees POST-EVENT | |||
Users/Fans--> 20% | |||
Awareness of Mozilla project/missions | |||
#''' Mozilla Tour''' | |||
Schedule of the cities, universities that will be visited | |||
attendees-->depending of the number of places visited | |||
Metrics | |||
contributors 2-10% | |||
fans/users 40% | |||
Awareness of the Mozilla project/Mission | |||
Line 86: | Line 151: | ||
Whiteboard: '''Request Rejected''' | Whiteboard: '''Request Rejected''' | ||
Status: ''' RESOLVED WON'T FIXED''' | Status: ''' RESOLVED WON'T FIXED''' | ||
== Step 4: == | == Step 4: == | ||
Revision as of 19:01, 14 April 2014
Main | Join | Procedures (SOPs) | Leadership (Resources) | Meetings | Website | FAQ
The Swag request form is an essential tool of the Mozilla Reps program. Never under-estimate the power of swag :) It is used extensively by Mozilla Reps that organize and/or participate in conferences. Mentors and Council members are given Swag Requests Handling rights (Bugzilla rights and swag system account) based on load of requests, by the council.
Step 1
Mozilla Rep has submitted a swag request (swag request form). The swag request is automatically assigned to Konstantina (bug owner)
Step 2:
Owner assesses the bug to see if it makes sense to ship swag requested (ie. consults with council, checks stock inventory etc...)
Whiteboard: Reviewing Order Status: ASSIGNED
General Info that must be included in the event page
- Type of the event
- Community meetings
- Inter Community Meet ups ( eg. Arabic Mozilla Meetup)
- Moz Coffee
- Moz Coffee
- Project Specific Hackathons (App days, L10n Marathons, QA Marathons)
- Talks-Presentations
- WoMoz Events
- Talks in conferences/bigger events
- Booth in a conference
- Mozilla Tour
- Special events
- Connection to the 2014 goals
- Event's length (hours, all day)
- Bug related to the event
- General info
- topic of the rep's talk
- where it is happening
- Agenda
- Expected size of audience
- Type of swag distribution at events
- free for all = anyone can swing by and pick up some swag
- selective = swag is only distributed to a selected type of attendee based on person's contribution to the project
- mix = combination of free for all and selective
Swag Metrics and general info based on the event type
- 'Community Meetings and Inter-community Meet-ups
Community meetings don't need regular swag, we encourage ,however, the local communities, to produce their own local swag for awareness.
- Moz Coffee
- Up to 20 people (max)
- Metrics
engaging contributors-->sucess scenario 10% of the attendees (sign-ups) POST-EVENT awareness of the Mozilla mission/projects --> 100% Attendance-->70% of the estimated attendees showing up POST-EVENT
- Project Specific Hackathons
Attendance up to 100 Metrics set a measurable goal (eg. 10 articles to be translated, 5 apps etc) L10n, SUMO, App days -->up to 80% of the original goal (?? what do you mean "original goal" ? )-->the rep set a goal of translating articles/ creating apps we should track if he met that goal POST-EVENT QA run 80-100% of the goal tests POST-EVENT Attendance-->70% Contributor engagement--0-10% (0% if the attendees are all Mozillians) POST-EVENT Awareness of the specific project and how it works (tools, procedures)
- Talks-Presentations
General Info what is the talk about attendance up to 250 Metrics contributors--> 15% POST-EVENT New users fans--> 70% attendance 70% POST-EVENT Awareness of the Mozilla mission/projects --> 100%
- WoMoz Events
up to 20 people Metrics Same metrics with talks specific presentation about the WoMoz Community and women in technology
- Talks in conferences/bigger events
link of the conference schedule of the conference attendance: no limit (ask the reps to indicate of the last years conference attendance according to the organizers) Metrics contributors (0-10%) (0 cause attendees may not only interested in Mozilla Projects) POST-EVENT Fans/users (0-20 %) Awareness of the project Online link of the presentation (video is preferable) Attendance 10% of the conference (or less for huge events) 50 % for smaller events POST-EVENT
- Booth in a conference
same special requirements with Talk in conferences evidence that Mozilla will have a booth there Metrics Interaction and visibility--> attract 60% of the conference attendees POST-EVENT contributors-->0-5% of the attendees POST-EVENT Users/Fans--> 20% Awareness of Mozilla project/missions
- Mozilla Tour
Schedule of the cities, universities that will be visited attendees-->depending of the number of places visited Metrics contributors 2-10% fans/users 40% Awareness of the Mozilla project/Mission
Questions to ask yourself when reviewing a swag order
- How does the Event page look? (i.e. good description, Mozilla specific activities, promising means of documentation, promotions etc.)
- What type of event is it? (e.g. consumer event vs. tech event)
- Are the metrics measurable (e.g number of new contributors to be engaged)
- What type of attendees are expected? (e.g. young attendees vs. old attendees; technical vs. non-technical)
- What is out existing stock of swag (e.g. are we running out of a particular item?)
- Are shipment costs going to be sky-high? (e.g. sending 10 lanyards to Kazakhstan costs more than sending 100 t-shirts to Germany)
- What type of swag would be better suited for this region? (e.g. some regions despise or love specific swag, like pens in Africa or lanyards in Germany <3)
- How often has this Reps requested swag in the past? (e.g. people constantly asking for the same swag in a region - Reps are encouraged to use their swag "wisely" and save some for future events)
- Has this rep been filing his Monthly Reports regularly?
- How many days we have for shipping the swag?
Examples of typical quantities you should distribute
Event type: FOSS conference Audience type: FOSS advocates, developers, geeks Expected attendance: 100 Will there be a Mozilla booth?: Yes # bracelets: 50 (most people love bracelets but end up never wearing them so give to people who wear them :) # stickers: 200 (stickers are always super popular - usually order as many as you have participants) # lanyards: 25 (lanyards are super popular but expensive - use them wisely) # buttons: 50 (buttons are heavy and expensive - use them wisely) # pens: 50 (in some countries, pens are SUPER popular :) # tshirts: 5 (get different sizes + should be given for free as a prize or award - do not distribute randomly) # horizontal banner: 1 (if Rep doesn't already have one) # pop-up banner: 1 (if Rep doesn't already have one) # tablecloth: 1 (if Rep doesn't already have one)
Step 3:
If the request is approved, the owner cc's Jennifer Balaco so she can process the request via Staples. Whitebord: Order Processed
If the request is rejected, the owner informs Mozilla Rep that his/her request has been rejected
Whiteboard: Request Rejected Status: RESOLVED WON'T FIXED
Step 4:
Tracking Number is obtained through shipping vendor and bug is updated by the owner to include tracking number
Whiteboard: Order Shipped
Step 5:
The Rep receives and informs you on the bug or the package is lost in translation :P
Whiteboard: Order Delivered or Lost in Space Status: RESOLVED FIXED