Reps/SOPs/Swag Requests
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. Resource Reps 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 or Resource Rep has submitted a swag request (swag request form). The swag request is automatically assigned to Francesca (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
- Specific Hackathons (App days, L10n Marathons, QA Marathons)
- Talks-Presentations
- 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
General based on the event type
- Community Meetings and Inter-community Meet-ups
- that kind of meetup full-fills the need of the community member to discuss of the goals of their community. As such the agenda and the number of the participants is determined by the community
- Moz Coffee
- Attendance to 20 people (max)
- Project Specific Hackathons
- Talks-Presentations
- What is the talk about
- Attendance up to 250
- 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)
- Booth in a conference
- Same special requirements with Talk in conferences
- Evidence that Mozilla will have a booth there
- Mozilla Tour
- Schedule of the cities, universities that will be visited
- Attendees-->depending of the number of places visited
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?
Typical quantities you will receive based on your event type
Event Type - Swag | Bracelets | Stickers | Buttons | T-shirts | Lanyards | Tattoos |
---|---|---|---|---|---|---|
Community meetings | No need for swag, however we encourage the local communities to produce their local swag for awareness | |||||
Inter Community Meet ups ( eg. Arabic Mozilla Meetup) | ||||||
Moz Coffee | 10 | 20 | - | 2 | - | - |
Specific Hackathons (App days, L10n Marathons, QA Marathons) | 50% of the participants | 80% of the participants | 50% of the participants | up to 5 | - | 50 (if the participants are more than 60) |
Talks-Presentations | 40% of the participants | 80% of the participants | 50% of the participants | up to 5 | 10 | 50 |
Talks in conferences/bigger events | 20% of the participants | 60% of the participants | 15% of the participants | up to 5 | 10 | 15% of the participants |
Booth in a conference | 30% of the participants | 65% of the participants | 20% of the participants | up to 10 | 10 | 20% of the participants |
Mozilla Tour | 40% of the participants | 80% of the participants | - | up to 5 | - | 30% of the participants |
Special events | Depending on the needs of the event |
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
Step 6:
Swag Metrics, what your metrics should include,understanding if your event has been successful
- Community Meetings and Inter-community Meet-ups
- setting Goals for your community
- Moz Coffee
- Engaging Contributors-->success scenario 10% of the attendees (sign-ups)
- Awareness of the Mozilla mission/projects --> 100%
- Attendance-->70% of the estimated attendees showing up
- Project Specific Hackathons
- Set a measurable goal (eg. 10 articles to be translated, 5 apps etc)
- L10n, SUMO, App days -->up to 80% of the original goal
- Articles/ Creating apps
- QA run 80-100% of the goal tests
- Attendance-->70% of the estimated attendees showing-up
- Contributor engagement-->0-10% of the estimated attendees (0% if the attendees are all Mozillians)
- Awareness of the specific project and how it works (tools, procedures)
- Talks-Presentations
- Contributors--> 15% of the estimated attendees
- New users fans--> 70% of the estimated attendees
- Attendance--> 70% of the estimated attendees
- Awareness of the Mozilla mission/projects --> 100%
- Talks in conferences/bigger events
- Contributors (0-10%) of the estimated attendees(0 cause attendees may not only interested in Mozilla Projects)
- 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
- Booth in a conference
- Interaction and visibility--> attract 60% of the conference attendees
- Contributors-->0-5% of the attendees
- Users/Fans--> 20%
- Awareness of Mozilla project/Mission
- Mozilla Tour
- Contributors --> 2-10% of the estimated attendees
- Users/Fans--> 40% of the estimated attendees
- Awareness of the Mozilla project/Mission