Reps/SOPs/Swag Requests: Difference between revisions

Revision as of 09:43, 21 March 2012

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.

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 (swag request form) and Pierros/William assign the bug to an owner

Whiteboard: Reviewer Assigned

Step 2:

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

Questions to as yourself when reviewing a swag order

how does the Event Wiki page (ie. good description, mozilla specific activities, clear info on how this event will be documented, advertised etc)
what type of event is it? (eg. consumer event vs. tech event)
what type of attendees are expected? (eg. young attendees vs. old attendees; technical vs. non-technical)
what is out existing stock of swag (eg. are we running out of a particular item?)
are shipment costs going to be sky-high? (eg. 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? (eg. 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? (eg. people constantly asking for the same swag in a region - Reps are encouraged to use their swag "wisely" and safe some for future events)
Has this rep been filing his Monthly Reports regularly?

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:

The Rep receives and informs you on the bug or the package is lost in translation :P

Whiteboard: Order Delivered or Lost in Space

@@ Line 1: / Line 1: @@
 {{Remonav}}
-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.
+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.
 {{Admon/important |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}}
@@ Line 7: / Line 7: @@
 == Step 1 ==
-Mozilla Rep has submitted a swag request ([https://bugzilla.mozilla.org/form.reps.swag swag request form]) and Pierros/William assign bug to owner
+Mozilla Rep has submitted a swag request ([https://bugzilla.mozilla.org/form.reps.swag swag request form]) and Pierros/William assign the bug to an owner
 Whiteboard: '''Reviewer Assigned'''
@@ Line 13: / Line 13: @@
 == Step 2: ==
-Owner asseses the bug to see if it makes sense to ship swag requested (ie. consults with council, checks stock inventory etc...)
+Owner assesses 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)
-* Assessment of recent Monthly Reports by the requester
-* Assessment of Event Wiki page (mozilla specific info, detailed info etc)
+=== Questions to as yourself when reviewing a swag order ===
+* how does the Event Wiki page (ie. good description, mozilla specific activities, clear info on how this event will be documented, advertised etc)
+* what type of event is it? (eg. consumer event vs. tech event)
+* what type of attendees are expected? (eg. young attendees vs. old attendees; technical vs. non-technical)
+* what is out existing stock of swag (eg. are we running out of a particular item?)
+* are shipment costs going to be sky-high? (eg. 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? (eg. 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? (eg. people constantly asking for the same swag in a region - Reps are encouraged to use their swag "wisely" and safe some for future events)
+* Has this rep been filing his Monthly Reports regularly?
 Whiteboard: '''Reviewing Order'''
 == Step 3: ==
-If the request is approved, the owner makes the order via the [https://intlstore.mozilla.org/swag/?page=newrequest internal swag store] and specifies the swag store order ID in the bug<
+If the request is approved, the owner makes the order via the [https://intlstore.mozilla.org/swag/?page=newrequest 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: ==
@@ Line 39: / Line 40: @@
 Whiteboard: '''Order Shipped'''
 == Step 5: ==
-Requestee has the package in his hands or the package is lost in translation :P
+The Rep receives and informs you on the bug or the package is lost in translation :P
 Whiteboard: '''Order Delivered''' or '''Lost in Space'''