#120 Allocate FY18Q2 budget across regions
Closed: approved 2 years ago Opened 2 years ago by mitzie.

Please allocate the budget for the 2nd quarter (June-August 2017) across regions. It's been already 2 weeks while we are in Q2, and we need the final numbers to do our planning.


I'm adding a comment to this on behalf FAmSCo.
Not only EMEA requested the final numbers, there are some other things to consider:

  • Some of the regions overspent Q1 and requested more money
  • FAmSCo did a call for Release Parties, but there are some problems with the swag production (Region who overspent, were allowed to fund only specific events, not swags)
  • LATAM run out of swags, and they have actually no budget to produce swags (even DVDs)

FAmSCo took care of these requests and brings them up additionally to the ticket EMEA filed. Ideally we should:

  • Allocate the budget for the other quarters (if not, at least for Q2)
  • Allow Regions to produce swags for the F26 release cycle if they need to do so. This should be treated as an extra-budget, as no region was/is aware of the budget change this year.

I need to check the status of that allocation as I suspect @mattdm will look to me first on this. I am on planes or in airports for the next 20 hours so it will be delayed, but is a priority.

@mattdm can you update me on the status of hte mission and the additional budget plan?

Metadata Update from @bex:
- Issue assigned to mattdm

2 years ago

@robyduck following up on the swag and event funding issues. This ticket is asking for a general allocation and we need to do that.

However, please ask FAmSCo to help reinforce the message that regions running out of money are STRONGLY encouraged to open council tickets asking for more funds to meet specific goals and objectives. I suspect if a region had opened a ticket and said we need $XX for release parties it would be viewed favorably by the council if the amount and locations made sense.

Metadata Update from @bex:
- Issue marked as blocking: #113

2 years ago

Proposed Resolution:

Each region to be allocated an additional $3000/quarter for quarters 2-4 of budget. Additional budget is available upon request from the council for items that are not able to met with this budget. The goal continues to be encourage good ideas and new thinking, not default approval of the same things from last year without evaluation.

Approval of this will also result in #125 #113 and #108 being closed as resolved by #120's allocations.

Questions about mission/mindshare/targets should be opened as non-budget tickets with the council or with the Mindshare initiative.

This ticket will use council lazy consensus rules as this action mirrors discussions from the Council FAD. The ticket is considered approved with 3 +1s and no -1s by Wednesday 2 August.

Metadata Update from @bex:
- Issue assigned to bex (was: mattdm)

2 years ago

Metadata Update from @jwboyer:
- Issue unmarked as blocking: #108
- Issue unmarked as blocking: #125

2 years ago

@jkurik @jwboyer I am invalidating your votes as there was an error.

@robyduck pointed out that my memory is error. Based on the Council FAD the correct resolution should be:

Proposed Resolution:

Each region to be allocated an additional budget amount for use in Quarters 2-4 per the table below. Additional budget is available upon request from the council for items that are not able to met with this budget. The goal continues to be encourage good ideas and new thinking, not default approval of the same things from last year without evaluation.

APAC $4000
EMEA $7000
LATAM $3000
NA $9000

Approval of this will also result in #125 #113 and #108 being closed as resolved by #120's allocations.

Questions about mission/mindshare/targets should be opened as non-budget tickets with the council or with the Mindshare initiative.

This ticket will use council lazy consensus rules as this action mirrors discussions from the Council FAD. The ticket is considered approved with 3 +1s and no -1s by Wednesday 2 August.

@jwboyer and @jkurik please revote.

After clarification with @bex , I am +1 to the corrected proposal.

Closing as approved. Budgets have been updated. budget.fp.o is being regenerated to reflect this change.

Metadata Update from @bex:
- Issue close_status updated to: approved
- Issue status updated to: Closed (was: Open)

2 years ago

+1. Sorry for the belated reply.

Login to comment on this ticket.

Metadata