Special Cases
There are instances when a Rep is the owner of an event/initiative that is masterminded by Mozilla staff and has already been approved for sponsorship by Mozilla. These events DO NOT require Council budget approval.
Whiteboard
For these special cases, although budget is already approved, the Rep owning the event STILL NEEDS TO FILE A BUDGET REQUEST BUG (ie. creating an event page, identifying metrics of success, getting feedback from their mentor and from the council, reporting after the event).
The only difference is that the Reps needs to clearly indicate that their event/initiative has already been approved for budget. Moreover, the Reps needs to copy a Mozilla paid staff member on the bug and this staff member must confirm in a comment that this event is being sponsored by Mozilla.
To indicate that their event/initiative has already been approved for budget, the Rep needs to update the whiteboard accordingly:
Bug Status : ASSIGNED Bug Whiteboard : SPECIAL CASE - Mentor and Council Feedback Requested Set remo-approval flag to + or -
Council Voting
The Council still needs to vote in the voting pad to express support or push back. 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. However, the Council cannot block budget approval for the event/initiative.
Benefits
Filing a budget request bug even if the Rep-owned event/initiative is already approved for funding still has the benefit of ensuring that the Rep documents the event through ReMo channels, that the Rep gets constructive feedback from the Council on his event/campaign (particularly with regards to success metrics), and that we stay transparent in terms of what we spend. Essentially, the only difference is that for these types of budget requests, Council does NOT need to approve them as they are already approved.