Confirmed users
887
edits
Reps/SOPs/Budget/Special Cases: Difference between revisions
no edit summary
No edit summary |
|||
| Line 8: | Line 8: | ||
* Large scale inter-community meetups | * Large scale inter-community meetups | ||
These events '''DO NOT''' require Council budget approval but Council should be able to provide feedback on the budget. | === Budget Request === | ||
Your budget needs to be requested AND approved at least 2 months prior to the event. If it is not, there is a high chance it will be rejected. | |||
=== Pre-Approval === | |||
These events '''DO NOT''' require Council budget approval but Council should be able to provide feedback on the budget. | |||
However, these events do require the approval of staff members. The approval chain is: | |||
* One person on the team that is funding the event | |||
* One Reps staff member (currently Rosana or Brian) | |||
The goal is not to try and deny budget, but to do a sanity check that the budget has been optimized before the event organization kicks off in earnest. | |||
=== Whiteboard === | === Whiteboard === | ||
| Line 24: | Line 37: | ||
=== Council Voting === | === Council Voting === | ||
The Council still needs to vote in the voting pad to express support or reservations about the event/initiative. Although not mandatory, it is highly recommended that special | The Council still needs to vote in the voting pad to express support or reservations about the event/initiative. Although not mandatory, it is highly recommended that special case still get majority approval from Council. If the majority vote is negative, this indicates that the Council does not approve of this event and the Rep is strongly encouraged to work with Mozilla paid-staff to address the concerns raised. That said, the Council '''CANNOT''' block budget approval for special cases. | ||
=== Payment === | === Payment === | ||