This page describes the current % allocations of our budget. See Funding priorities for more information about the goals and outcomes this budget is meant to support.
Budget allocations are distributed in 2 phases:
- Half 1 (H1, January - June)
- Half 2 (H2, July - December)
Any unspent funds remaining at the end of the half will be returned to the general pool for mid-year reallocation.
Amendments to budget allocations may be approved with a vote from the board, with input from the Treasurer and Board Chair, and financial validation from the LF Program Manager and Accountant.
Table 1:Budget Allocation by Category
| Category | % of budget | Purpose | Goal | Relevant Voting Body / Stakeholder |
|---|---|---|---|---|
| Community | 25% | Support initiatives that build and sustain the contributor community, including DEI, mentorship, documentation, onboarding, and contributor recognition. | Grow the contributor capacity of Jupyter | Community Subcommittee |
| Technical | 25% | Fund core project maintenance, modernization, and technical innovation, including architectural work, accessibility, security improvements and AI-related initiatives. | Improve the reliability, security, and consistency of Jupyter’s software | Technical Subcommittee |
| Events | 25% | Support global community engagement through events like JupyterCon, regional meetups, and workshops. | Foster global collaboration, knowledge-sharing, and visibility of Jupyter tools. | Linux Foundation (non-voting) |
| Operations and admin | 10% | Cover operational expenses such as legal fees, trademark protection, security coordination, board meetings, and infrastructure. | Ensure smooth governance and legal continuity of the Foundation’s operations. | Linux Foundation (non-voting) |