Fedora ARM

Fedora Budget

This page will serve as a public clearing house for all information regarding money allocated and spent by the Fedora Project. Budget numbers will be updated quarterly, and any changes to the process will be reflected here in this page.

Budget Numbers

Component Total Q1 Q2 Q3 Q4
TOTAL BUDGET $195,000 Q1 Q2 Q3 Q4
FEDORA EVENTS $115,000 Q1 Q2 Q3 Q4
COUNCIL $6,500 Q1 Q2 Q3 Q4
APAC $11,500 Q1 Q2 Q3 Q4
EMEA $21,650 Q1 Q2 Q3 Q4
LATAM $11,950 Q1 Q2 Q3 Q4
NA $29,400 Q1 Q2 Q3 Q4

The Fedora Budget Process

CalendarFiscal YearTopicResponsible
Feb '16FY16...Final Quarter Budget ReportRegional Treasurers → FCL
Mar '16FY17Budget Adjustment/AllocationCouncil → Regions/Subprojects
May '16FY17First Quarter Budget ReportRegional Treasurers → FCL
Jul '16FY18Budget Proposal for Next YearRegions and Subprojects, FCL
Aug '16FY17Second Quarter Budget Report Regional Treasurers → FCL
Aug '16FY18Budget Session at FlockFCL, Council
Sep '16FY18Ratification by CouncilCouncil (full consensus)
Oct '16FY18Budget SubmissionFCL → Red Hat
Nov '16FY17Third Quarter Budget ReportRegional Treasurers → FCL
Feb '17FY17Final Quarter Budget ReportRegional Treasurers → FCL
Mar '17FY18Budget Adjustment/AllocationCouncil → Regions/Subprojects
May '17FY18First Quarter Budget ReportRegional Treasurers → FCL
Jul '17...FY19Budget Proposal for Next YearRegions and Subprojects, FCL
............

FCL = Fedora Community Action and Impact Lead

  • Fedora 22-23: Remy DeCausemaker
  • Fedora 24+: TBD

Note that "→" in the chart above indicates that responsibility for that item feeds into a next step in responsibility; for example, regional treasurers are responsible for providing the FCL with the relevant information for their region, and the FCL is responsible for the general report to the community. Likewise, the Council is responsible for any top-level budget adjustment when the final budget comes in from our sponsor, and regions responsible to update accordingly if needed.

Regional Ambassadors will manage their own budgets, and report back quarterly on action and impact.

If a region does not submit a budget proposal within the timeline above, their budget will be allocated as general discretionary funds. Budgeted money not spent as planned may also be reallocated on a quarterly basis; if a region or budgeted subproject does not provide a quarterly update, budget for that region or subproject for future quarters may also be reallocated.

Regional Delegates

Each region will select three delegated roles:

  • Treasurer
  • The Regional Treasurer will be responsible for recording costs and disbursing funds. Cardholders don't necessarily have to serve this role, but it would reduce the number of hops between expense and report

  • Logistician
  • The Logistician Delegate will be accountable for shipping swag, banners, and other physical items that need to be shared regionally, as well as any other coordinating for event staffing and organization. This includes convening weekly ambassador IRC meetings.

  • Storyteller
  • The Storytelling Delegate will be accountable for Regional Reports. They don't necessarily have to write all the original content, they just need to be accountable for ensuring content makes it out onto our channels.

One person may hold no more than (2) of these roles at the same time.

Reimbursement

Holding with our current policies, reimbursement will depend on submission of an Event Report to the appropriate channels (mail lists, communityblog, and the planet/magazine when applicable)

Event reports going forward should also include a very short list of bullet points. These bullet points are the necessary ammunition we need to reinforce our proposals to increase funding for regional programs going forward.

Action is any typical or special activity that ambassadors lead regionally such as:

  • Tabling at Conferences, Conventions, or other large events
  • Presenting/Representing Fedora at Local Meetups
  • Organizing FADS, Workshops, or other Fedora-specific Events

Impact includes the outcomes from the activities as above. This includes things like:

  • Attendees contacted or reached
  • Fedora Badges issued at or as a result of the event
  • Pull requests and patches submitted as a result of event
  • Bugs reported/Tickets Filed
  • Candidates sourced (i.e. Outreachy, GSoC, and/or other FOSS programs)
  • Articles/Videos/Photos/Content published by or about regional team
  • Social media mentions and interactions generated by event
  • Other supporting evidence data that shows the results of your effort
  • Links to and reach of posts on Fedora social media and publishing channels