PSF Strategy | Python Software Foundation

Notice: This page displays a fallback because interactive scripts did not run. Possible causes include disabled JavaScript or failure to load scripts or stylesheets.
Our direction for 2026–2031, how the board sets priorities, and how the community can follow and shape our progress.
The board will assess progress with staff and community input and publish its findings and any changes.
Read how the review works
The PSF Strategic Plan 2026 sets the foundation’s direction for 2026–2031. It connects our mission with choices about funding, staff capacity, programs, and partnerships.
The board adopted the plan and established an annual review at its July 8, 2026 meeting. Each resolution passed with 10 votes in favor, none against, and no abstentions. Read the adoption and annual review resolutions.
Open the PDF Read the adopted text
If the preview does not display, open the PDF in Google Drive.
The plan has four program goals and six organizational goals. This overview summarizes them. The adopted plan contains the full objectives and the board’s suggested tactical ideas.
Strengthen security across PyPI, CPython, distribution channels, and all PSF projects and services, from source to installation.
Support reliable infrastructure, CPython development, vulnerability management, packaging tools, python.org, and Python’s intellectual property, with sustainable funding and staffing.
Sustain PyCon US, improve grant-making and workgroups, support international collaboration, and welcome more Python users into the community.
Make it easier to discover and learn Python through advocacy, accessible resources, translation and localization, clearer beginner pathways, and community storytelling.
These goals apply across every PSF program and activity:
The PSF Board of Directors sets the foundation’s strategic direction. The plan guides decisions about where to focus the PSF’s budget and staff time. PSF staff shape how to carry out that direction through their work on programs and operations.
The board’s tactical ideas are suggestions and starting points for staff to develop. Expanding work depends on available staff time and sustainable funding. During planning, the board identified staffing capacity, the financial sustainability of PyCon US, and opportunities to deepen sponsor support as central considerations.
The board’s meeting minutes record its decisions. Annual reviews connect those decisions back to the plan’s goals and provide an opportunity to reconsider priorities with staff and community input.
Planning began at the 2024 board retreat, continued with community interviews in 2025, and developed through board planning sessions in early 2026. Staff reviewed the draft from April to June. The initial goals were shared in May, followed by a public draft and feedback period from June 4 to June 25, 2026. Input also came through PyCon US conversations, office hours, email, and the PSF discussion forum.
Feedback shaped the plan throughout its development. Staff input introduced security and vulnerability-management objectives before the June public draft. Following community consultation, the final plan added translation and localization, clearer pathways for directed funding, and PSF membership growth. It also makes staffing, sustainable support for CPython, and the scope of grant-making more explicit.
The board established an annual review alongside adoption. Each review must take place no later than the anniversary of adoption, with the first due by July 8, 2027.
The Executive Director and Board Chair are responsible for preparing the review materials. At each annual review, the board will:
The board may amend the plan at an annual review by vote, following the voting rules in the PSF Bylaws.
The PSF strategy repository on GitHub is the home for the plan’s Markdown text, changelog, and revision history.
The board adopted PSF Strategic Plan 2026 for 2026–2031 and established the annual review process. This is the initial adopted version.
The first annual review is due by July 8, 2027.
Tell us what is working, where the plan falls short, and what the board should consider at its next review. Feedback from staff and the community informs the board’s annual reviews.
Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice