...
Expenses fell under three categories: technical resources (AWS, Packet, TestRail, GitHub, OCLC); FOLIO-funded developers; and membership expenses with OLF.
Figure 1
Income | Total | Expense | Total | |
|---|---|---|---|---|
Memberships | $295,000 | Amazon Web Services | $ 107,777 | |
EBSCO tech support | $84,500 | Packet | $ 4,668 | |
Suppl from members | $42,400 | TestRail | $ 29,700 | |
GitHub | $ 582 | |||
OCLC | $ 2,700 | |||
OLF | $ 9,850 | |||
Salaries and Benefits | $275,000 | |||
$421,900 | $330,277 |
There were two FOLIO-funded developers at the beginning of the year but one took another position. FOLIO would likely have had a shortfall if we had paid two full-time developers.
...
Additionally, FOLIO had some other other activity funded by other entities:
- FOLIO hired a documentation consultant and Leipzig University provided $134,000 for one year’s work, and EBSCO directly paid the consultant for a time to finish some parts of the work
- The German consortium hbz provided $100,000 for a developer working at Duke University
- Google “Season of Docs” provided $12,750 for interns to assist with the documentation
...
When FY22 began, nobody had a true picture of FOLIO’s basic costs or if the project could afford to cover them. For FY23 we are on sound footing. We have $370,000 in membership commitments, and ⅔ of those funds have already arrived. EBSCO is increasing its underwriting of the AWS costs. Budgeting for one full time developer and full AWS costs at their current level, we will have sufficient funds for the recurring basic costs, with the likelihood of some budget surplus again.
Figure 2
Figure 3
