Reps/SOPs/Swag Requests

Main | Join | Procedures (SOPs) | Leadership (Resources) | Meetings | Website | FAQ

Swag request is an essential tool of the Mozilla Reps program. It is used extensively by Mozilla Reps that organize and/or participate in conferences. Mentors and council members will be given Swag Requests Handling rights (Bugzilla rights and swag system account) based on load of requests, by the council.

Keep bugs tidy
Please make sure that within the process the swag bug is up to date with the progress and reflects the steps as noted below

Step 1

Mozilla Rep has submitted a swag request and Pierros/William assign bug to owner

Whiteboard: Owner Assigned

Step 2:

Owner asseses the bug to see if it makes sense to ship swag requested (ie. consults with council, checks stock inventory etc...)

Swag request assessment criteria

• existing stock in inventory
• type of event (eg. consumer event vs. tech event)
• type of attendees (eg. young attendees vs. old attendees; technical vs. non-technical)
• probably shipment costs (eg. sending 10 lanyards to Kazakhstan costs more than sending 100 t-shirts to Germany)
• type of swag per region (eg. some regions despise or love specific swags, like pens in Africa <3)
• Repetition of swag for specific region (eg. people constantly asking for the same swag in a region)

Whiteboard: Reviewing Order

Step 3:

If the request is approved, the owner makes the order via the internal swag store and specifies the swag store order ID in the bug<

If the request is rejected, the owner informs Mozilla Rep that his/her request has been rejected

Whiteboard: Order Processed or Request Rejected

Step 4:

Tracking Number is obtained through shipping vendor and bug updated to include UPS tracking number

Whiteboard: Order Shipped

Step 5:

Requestee has the package in his hands or the package is lost in translation :P

Whiteboard: Order Delivered or Lost in Space