Created 8 years ago
Maintained by mattdm
This repository is where budget data and information is shared publicly  |  http://pagure.io/fedora-budget
Members 3
Michael S committed 3 years ago

Fedora Budget

This repository is where budget data and information is shared publicly

The Fedora Fiscal Year is from March 1 to February 28. Fiscal years are numbered by the year in which they end. For example, the fiscal year from March 1, 2016 to February 28, 2017 is FY17.

Ledger data files are stored in FYXX/ledger/ for the current year and in fyXX/ledger for previous years.

FY16 and FY15 are historical data from before the adoption of ledger. FY17 contains an archive file from before the adoption of ledger.

The website for the budget is http://budget.fedoraproject.org There you will find the data reported and documentation. This repo contains the files used to build that website (using AsciiBinder) and the raw transaction data. This site is rebuilt via a webhook (in progress) on Fedora's Jenkins Server. The built site is pushed to the fedora-budget-site repository.

How is this site published

Note: More complete information needs to be written, this is the "expert" guide.


  1. A jenkins job, triggered manually by bexelbie today, creates the html and pushes it to the publishing repo on the stg branch.
  2. Once an hour infra has a script that gets any updated code from this repo and stages it.
  3. Once an hour the mirrors sync the code base built in step #2.
  4. When stage looks good, bexelbie merges stg to prod in the publishing repo and steps 2 and 3 repeat.

There is a conversation about more-frequent/on-depand publishing here: https://pagure.io/fedora-infrastructure/issue/5747

Testing Locally

The easiest way to test locally is:

  1. git checkout master
  2. git merge your_branch
  3. asciibinder package
  4. cd _package/main
  5. mv budget/* . ; accept all overwrites ignore the error about _images
  6. docker run -p 3000:80 -v /path/to/cwd:/var/www/html:Z fedora/apache
  7. firefox localhost:3000

Alternately, you can edit the _distro_map.yml to reference your topic branch and skip straight to step 3 above.


Creative Commons License"

This work is licensed under a Creative Commons Attribution 4.0 International License.

See LICENSE.txt.