Notice: This page displays a fallback because interactive scripts did not run. Possible causes include disabled JavaScript or failure to load scripts or stylesheets.

≡ Menu

PSF Meeting Minutes for Jan. 14, 2026

Subscribe via RSS

Title: 2026-01-14 PSF Board Meeting Minutes Encoding: utf-8 Author: psf at python.org Content-Type: text/x-rst

The Python Software Foundation
Minutes of a Regular Meeting of the Board of Directors

January 14, 2026

A regular meeting of the Python Software Foundation ("PSF") Board of Directors was held over Group Conference Call via phone and Internet Relay Chat/Slack beginning at 13:00 UTC, on January 14, 2026. Olivia Sauls took notes/minutes.

All votes are reported in the form "Y-N-A" (in favor-Y‚opposed-N‚abstentions-A; e.g. "5-1-2" means "5 in favor, 1 opposed, and 2 abstentions").

1   Attendance

The following members of the Board of Directors (11 of 12) were present at the meeting: Christopher Neugebauer, KwonHan Bae, Cristián Maureira-Fredes, Deb Nicholson, Georgi Ker, Jannis Leidel, Denny Perez, Abigail Mesrenyame Dogbe, Sheena O'Connell, Cheuk Ting Ho, Simon Willison.

Olivia Sauls (Program Director), Ee Durbin (Director of Infrastructure), Marie Nordin (Community Communications Manager), Loren Crary (Deputy Executive Director), Seth Larson (Python Security Developer in Residence), Kelly Ragland (Finance Manager), Jacob Coffee (Infrastructure Engineer) and Mike Fiedler (PyPI Safety & Security Engineer) were also in attendance.

2   Minutes of Past Meetings

Minutes from prior meeting December 10, 2025:

RESOLVED, that the Python Software Foundation approve the minutes at https://mail.python.org/archives/list/psf-important@python.org/thread/IET46RGH4QLXBHZQLEMLSAJFCY5GUUSS/ as representing a true and accurate record of the December 12, 2025 meeting.

Approved, 10-0-1

3   Board and Staff Monthly Reports for January 2026

3.1   Deb Nicholson

  • Support fundraising work, comms etc.
  • Support PyCon US planning
  • Meet with potential institutional funders
  • Work on internal staffing capacity
  • Review organizational goals for the coming year

3.2   Oliva Sauls

  • PyCon US 2026
    • Budget work
    • CFP review rounds 1 and 2
    • Outreach and promotion
    • Startup Row application promotion
    • Keynote selection
    • Vendor management; AV team, F&B team, captioning team
    • Hotel block management
    • Travel grants
    • Room planning
  • Managing Community Communications Manager
  • Offboarding with Director of Infrastructure and working on the transition with the Infrastructure Engineer
  • PTO

3.3   Laura Graves

January report not provided.

3.4   Ee Durbin

January report not provided.

3.5   Loren Crary

  • Correspondence with current and prospective sponsors
  • Contract negotiation with current and prospective sponsors
  • Assessing and pursuing grant opportunities
  • Drafting and revising strategic public communications
  • Board relations
  • 2025 end of year fundraiser support
  • Strategic team management and support
  • Targeted outreach to promote PyCon US Call for Proposal and PyCon US/PSF sponsorship program
  • Managing Programs Director & Community Communications Manager

3.6   Marie Nordin

  • Fundraiser
    • Retrospective with team, produce readout for Board
    • Wrap up: finalize numbers with accounting, results blog post
  • PyCon US
    • Community Booths
    • PSF Booth
    • Comms support
  • 2025 Annual Impact Report
    • Finalize designer
    • Content coordination
  • Python Developers Survey
    • Coordination with JetBrains
    • Produce promotions: blog post, social media, community promotion kit
  • Fellows WG
    • Q4 vote processing
    • Refresh support for WG
  • Grants
    • Meetup pro
    • Transparency report
    • Future of program
  • Sponsors benefit communications

3.7   Seth Larson

  • Authored and shared “End of Year Report” with Alpha-Omega. Working on transforming this content into our own PSF Annual Report for security.
  • PyCon US “Trailblazing Python Security” track
    • Receiving training on how to review talks, timelines, with reviewer team.
    • Talk reviewers are completing phase 1 reviews, phase 2 next.
  • [Published an update on PEP 770](https://sethmlarson.dev/pep-770-sbom-data-from-pypi-fedora-and-redhat) (“SBOMs for Python packages”) showing what’s happened since:
    • Published a white paper with Alpha Omega
    • Fedora, CentOS, and Red Hat have adopted PEP 770 in their Python packages and are soliciting feedback from SBOM and vulnerability scanners.
  • Sovereign Tech Agency
    • We accepted $87K from STA to work on ZIP/tar fuzzing improvements and PyPI account links. Seth worked on the ZIP/tar fuzzing improvements.
    • Migrated the “python3-libraries” fuzzing definition to the Python GitHub organization for more controlled ownership over the fuzzing definitions by core team. This is following a public discussion on owning these definitions on DPO.
    • Added Hypothesis-based property testing for generating ZIP/tar targets for fuzzing.
    • Added triggers for CI of CPython when relevant standard libraries are modified to run fuzz targets within the PR, similar to CPython language.
  • PEP 811 “Python Security Response Team (PSRT) membership and operations” has been accepted!
    • Jacob implemented more for the PSRT bot which will help enforce deadlines for reports and remind coordinators when they need to make progress or set metadata.
    • New policy for membership, operations.
    • Adopts GHSA as the primary reporting method, email list will become secondary and we’ll begin redirecting reporters to GHSA for per-project reports. Email list is maintained for requests that don’t fall into one project (such as standards, PEPs, etc).
    • Implementing PEP in the PSRT Devguide documentation in January after STA work has concluded. Adopting the PSRT bot in January.

3.8   Mike Fiedler

  • Mike returned from two weeks of travel, including AWS re:Invent and DevOpsDays Tel Aviv.
  • Malware Response
    • December saw a high malware report volume, with over 300 inbound reports. The automated quarantine system proved highly effective, catching over 50 malicious projects with zero false positives. This demonstrated the system's reliability and reduced manual intervention requirements during periods of reduced availability, and accounted for over 100 of the inbound reports (since multiple reports triggered quarantines).
    • Mike continued responding to security inbox items throughout the month despite holiday scheduling, maintaining PyPI's security posture through the year-end period.
    • The high volume of inbound reports has created a backlog for triage, and Mike is balancing that backlog with forward-looking work, expecting to complete the backlog by the end of January.
  • Trusted Account Associations
    • Mike made significant progress on the Trusted Account Associations project This work enables users to associate external accounts with their PyPI identity, improving account recovery options and laying groundwork for enhanced verification features.
    • Key deliverables included:
      • Merged the [account associations data model](https://github.com/pypi/warehouse/pull/19053), establishing the foundation for account linking
      • Split and refined commits for [draft review of the implementation](https://github.com/pypi/warehouse/pull/19197)
      • Updated the implementation to use a GitHub App instead of OAuth App, future-proofing the integration
      • Added email notification support for account association eventsSecurity Infrastructure Improvements
  • Security Infrastructure Improvements
  • Community Engagement
    • Presented at DevOpsDays Tel Aviv
    • Attended AWS re:Invent
    • Submitted two talks to the [PyCon US 2026 security track](https://pretalx.com/pycon-us-2026/)
    • Discussed potential 2026 security audit funded by Sovereign Tech Agency
    • Contributed to Alpha-Omega year-end summary
  • Other Items

3.9   Jaime Barrera

  • Correspondence with attendees in helpscout
  • Sponsorship Benefit Tracking
  • Worked on the floorplan w/loren and olivia
  • Photographer Research for US PyCon 2026
  • My first time leading a Brass meeting
  • Communication templates for Sponsor
  • Registration tracking and report(comparing 2025 to 2026)

3.10   Jacob Coffee

  • Working on transition items, PyCon, preparing for FOSDEM and SCALE conference talks

3.11   Maria Ashna

  • PEP 541 Backlog current
  • PyPI Account Recovery Issues current
  • Over ~2000 PyPI account recovery issues have been resolved in 2025
  • Over ~500 PEP 541 issues have been resolved in 2025
  • Ongoing review process of PyPI Org applications
  • Preparing blog post on the first year impact as the inaugural PyPI Support Specialist

3.12   Abigail Mesrenyame Dogbe

  • PyCon US Poster Reviews
  • Meeting with the Python Cameroon and Python Togo organizers (as part of my continued efforts to support community organizers)
  • Supporting the outreach of our fundraising efforts
  • Progress with the Community and Conference Organizers Kit

3.13   Sheena O'Connell

  • PSF: board meeting and comms, community office hours
  • COMMUNITY: Some PyCon Namibia fund-hunting
  • COMMUNITY: Chats with leaders from a few Southern African Python communities to better understand their needs and plans, and to build connections so we can get a few people to cross borders later in the year
  • COMMUNITY: PyCon Africa: Weighing in on discussions about levelling up CoC function

3.14   Denny Perez

January report not provided.

3.15   Cristián Maureira-Fredes

January report not provided.

3.16   Simon Willison

January report not provided.

3.17   Jannis Leidel

January report not provided.

3.18   Georgi Ker

January report not provided.

3.19   KwonHan Bae

  • PSF - participated in board discussions via Slack and email
  • PSF - attended board meeting
  • COMMUNITY : Python Asia Organize
  • COMMUNITY : PyCon KR Organize

3.20   Tania Allard

January report not provided.

3.21   Cheuk Ting Ho

  • PyCon US CfP mentoring
  • PyCon US CfP review
  • PyLadies Tokyo workshop

3.22   Chris Neugebauer

January report not provided.

4   Work Group Reports

4.1   Code of Conduct

  • Nothing to report at this time.

4.2   Grants

  • Nothing to report at this time.

4.3   Sponsors

  • Nothing to report at this time.

4.4   Marketing

  • Nothing to report at this time.

4.5   Jobs

  • Of the 459 Job submissions created in January 2026:
    • 132 have status approved
    • 9 have status archived
    • 12 have status draft
    • 148 have status expired
    • 73 have status rejected
    • 75 have status removed
    • 10 have status review

4.6   Trademarks

  • Nothing to report

4.7   Fellows

  • Nothing to report

4.8   Packaging

  • Nothing to report

4.9   Infrastructure

  • Nothing to report

4.10   Scientific Python

  • Nothing to report

8   New Business

  • The PSF discussed amending the PSF Trademark Policy and and voted on the following resolution:

    RESOLVED, that the official Trademark Policy be amended to include the Python Package Index (PyPI) marks, permitting community use only where the project clearly disclaims Foundation affiliation, avoids using "pypi" or “PyPI” as a standalone domain name, and does not compromise Foundation infrastructure.

    Approved; 11-0-0, 2026-01-14

  • The PSF discussed the PSF Trademark Policy and voted on the following resolution:

    RESOLVED, that the Board intends to adopt amendments to the trademark policy, to the effect that individuals named by a resolution by the board or code of conduct work group, or individuals whose Membership has been revoked by the Board due to violation of a written policy, be ineligible to use PSF trademarks. This resolution does not enact such a policy.

    Approved; 11-0-0, 2026-01-14

  • The PSF discussed the Community Partner Program and voted on the following resolution:

    RESOLVED, that the Python Software Foundation Board of Directors approve updates to the Grants Working Group charter, as written at https://docs.google.com/document/d/1AzKskuoL3OphYmh9P5QrCUKoflsO84wwav6yhLTzdJ8/edit?usp=sharing.

    Approved; 11-0-0, 2026-01-14

  • The PSF discussed reinstating Meetup Pro Network grants and voted on the following resolution:

    RESOLVED, that the Python Software Foundation Board of Directors approve reopening Meetup Pro Network grants, administered by PSF Staff.

    Approved; 11-0-0, 2026-01-14

9   Discussions

  • The board discussed the 2026 Fundraiser results.
  • The board discussed an update on the PyCon US 2026 CFP and current registrations.
  • The board discussed criteria and cost for the Meetup Pro program.
  • The board discussed the Anthropic donation and communications.
  • The board discussed transition plans for the PSF staff.
  • The board discussed strategic planning meeting prep.

Meeting adjourned at 15:01 UTC