Reps/SOPs/Budget/Process: Difference between revisions

Warning added
(new diagram)
(Warning added)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Warning |1= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.|title= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.}}
{{Remonav}}
{{Remonav}}
{{admon/important|Review Team take over Council's role to review budget request | As per 19 September 2016, The Review Team is taking over Council's role as a main reviewer in budget request. Please read thoroughly to get the idea of the new process}}


= Processing =
= Processing =
Line 7: Line 7:
The process of budget requests is made up of three distinct phases:
The process of budget requests is made up of three distinct phases:


1) Preliminary screening made by the Rep's mentor<br>
1) Preliminary screening made by the Rep's mentor if not filed by a Resource Team member
2) "Filtering" made by Budget Task Force and approves/rejects budget requests <$500 USD<br>
2) "Filtering" made by Review Team member and approves/rejects budget requests <$500 USD
3) The Review Team approves or rejects budget requests >$500 USD<br>
3) The Review Team approves or rejects budget requests >$500 USD
 


[[File:BudgetSOP.png|center | 800 px]]
[[File:BudgetSOP.png|center | 800 px]]


== Preliminary Screening ==
== Preliminary Screening (skip if filed by Resource Team member ==
=== Requesting Review using flags ===
=== Requesting Review using flags ===
* Bug wrangler assigns the bug to mentor
* Bug wrangler assigns the bug to mentor
Line 50: Line 49:
Bug wrangler will filter out those requests that are not considered relevant or appropriate. All remaining requests are then passed on to a Review Team member for final review and approval/rejection.
Bug wrangler will filter out those requests that are not considered relevant or appropriate. All remaining requests are then passed on to a Review Team member for final review and approval/rejection.


*If remo-review is + then the bug wrangler assigns the bug conditionally :
*If remo-review is + or filed by a Resource Team member then the bug wrangler assigns the bug conditionally :
** If budget request is <500 USD then it is assigned to a regional Review Team member
** If budget request is <500 USD then it is assigned to a regional Review Team member


     Bug Status : ASSIGNED
     Bug Status : ASSIGNED
     Bug Whiteboard : Review team assigned
     Bug Whiteboard : Review Team assigned
     Set remo-approval flag to ?
     Set remo-approval flag to ?


Line 60: Line 59:


     Bug Status : ASSIGNED
     Bug Status : ASSIGNED
     Bug Whiteboard : Review team approval needed
     Bug Whiteboard : Review Team approval needed
     Set remo-approval flag to ?
     Set remo-approval flag to ?


Line 73: Line 72:
For budgets over $500 USD, there should still be a single Review Team member assigned.
For budgets over $500 USD, there should still be a single Review Team member assigned.


The flag called "needs-info" should be set against it the Mozilla Review Team alias on bugs that need council's attention. The process must be as follows:  
The flag called "needs-info" should be set against it the Mozilla Review Team alias on bugs that need Review Team's attention. The process must be as follows:  


* A SINGLE Review Team member is assigned to the bug
* A SINGLE Review Team member is assigned to the bug
Line 105: Line 104:


<pre>
<pre>
Hi [first name], thanks for submitting this request. Your request has been approved. Please follow these next steps before we can process your payment:  
Hi [first name], thanks for submitting this request. Your request has been approved.
* indicate the twitter hashtags, Flickr photos and blog posts related to your event on this bug and on your event wiki page
Please follow these next steps before we can process your payment:  
* indicate the twitter hashtags, Flickr photos and blog posts related to your eventon this bug
and on your event wiki page
* provide a PayPal account  
* provide a PayPal account  
* scan and attach all relevant receipts to this bug
* scan and attach all relevant receipts to this bug
Line 141: Line 142:


*;[receipts received]: receipts have been received from the bug wrangler
*;[receipts received]: receipts have been received from the bug wrangler
*;[WU needed]: funds need to be processed via Western Union


*;[XXX USD processed]: XXX amount of money has been processed
*;[XXX USD processed]: XXX amount of money has been processed
Line 148: Line 147:
*;[special]: In some cases, Reps will be owning an event that is already sponsored by Mozilla and as such, DO NOT require Review Team budget approval. For these special cases, the Reps needs to '''[[ReMo/SOPs/Budget/Special_Cases|follow this procedure]]'''.
*;[special]: In some cases, Reps will be owning an event that is already sponsored by Mozilla and as such, DO NOT require Review Team budget approval. For these special cases, the Reps needs to '''[[ReMo/SOPs/Budget/Special_Cases|follow this procedure]]'''.


*;[special deveng]: In some cases, Reps will be owning an event that is already sponsored by Mozilla's Developer Engagement Team and as such, DO NOT require Council budget approval. These events are overseen by Robyn Chau.  
*;[special deveng]: In some cases, Reps will be owning an event that is already sponsored by Mozilla's Developer Engagement Team and as such, DO NOT require Review Team budget approval. These events are overseen by Robyn Chau.  


*;[full processed]: bug wrangler has made a full payment
*;[full processed]: bug wrangler has made a full payment


*;[FR=AMOUNT]: indicated final amount request (For example, if the final amount requested is $800 USD, then the whiteboard should indicate [FR800]
*;[FR=AMOUNT]: indicated final amount request (For example, if the final amount requested is $800 USD, then the whiteboard should indicate [FR800]
313

edits