Skip to content

Comments

PEP 811: Defining Python Security Response Team membership and responsibilities#4669

Merged
hugovk merged 10 commits intopython:mainfrom
sethmlarson:psrt-membership
Oct 27, 2025
Merged

PEP 811: Defining Python Security Response Team membership and responsibilities#4669
hugovk merged 10 commits intopython:mainfrom
sethmlarson:psrt-membership

Conversation

@sethmlarson
Copy link
Contributor

@sethmlarson sethmlarson commented Oct 22, 2025 •
edited
Loading

Basic requirements (all PEP Types)

  • Read and followed PEP 1 & PEP 12
  • File created from the latest PEP template
  • PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Title clearly, accurately and concisely describes the content in 79 characters or less
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • Author, Status (Draft), Type and Created headers filled out correctly
  • PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
  • Required sections included
    • Abstract (first section)
    • Copyright (last section; exact wording from template required)
  • Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
  • PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
  • Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

  • PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
  • Suggested sections included (unless not applicable)
    • Motivation
    • Rationale
    • Specification
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
  • Python-Version set to valid (pre-beta) future Python version, if relevant
  • Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
  • Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

📚 Documentation preview 📚: https://pep-previews--4669.org.readthedocs.build/pep-0811/

@hugovk hugovk changed the title Defining Python Security Response Team membership and responsibilities PEP 811: Defining Python Security Response Team membership and responsibilities Oct 22, 2025
@hugovk
Copy link
Member

hugovk commented Oct 22, 2025

I resolved the merge conflict, which merged in main and fixed the build error.

@sethmlarson
Copy link
Contributor Author

sethmlarson commented Oct 22, 2025

Thanks @hugovk!

hugovk
hugovk reviewed Oct 22, 2025
View reviewed changes
Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Mostly nits.

@sethmlarson @hugovk
Apply suggestions from code review
d244891 
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
hugovk
hugovk approved these changes Oct 23, 2025
View reviewed changes
@hugovk hugovk added the new-pep A new draft PEP submitted for initial review label Oct 23, 2025
hugovk
hugovk reviewed Oct 23, 2025
View reviewed changes
@sethmlarson @hugovk
Apply suggestions from code review
b59e69f 
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
hugovk
hugovk reviewed Oct 23, 2025
View reviewed changes
@sethmlarson sethmlarson marked this pull request as ready for review October 23, 2025 13:46
@sethmlarson sethmlarson requested a review from a team as a code owner October 23, 2025 13:46
willingc
willingc reviewed Oct 23, 2025
View reviewed changes
Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work @sethmlarson. A few minor suggestions.

sethmlarson and others added 2 commits October 24, 2025 17:44
@sethmlarson @willingc
Apply suggestions from code review
7b92d49 
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
@sethmlarson
Also mention PSF staff as a potential PSRT pre-req
34abffb
@sethmlarson
Copy link
Contributor Author

sethmlarson commented Oct 24, 2025

Thanks for the review @willingc! I've addressed your comments and accepted your changes.

@sethmlarson sethmlarson requested a review from gpshead October 24, 2025 19:54
willingc
willingc approved these changes Oct 25, 2025
View reviewed changes
Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @sethmlarson. Looks good.

@hugovk hugovk merged commit 2325e57 into python:main Oct 27, 2025
5 checks passed
zklaus pushed a commit to zklaus/peps that referenced this pull request Nov 3, 2025
@sethmlarson @hugovk
@willingc @zklaus
PEP 811: Defining Python Security Response Team membership and respon…
c417265 
…sibilities (python#4669)

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hugovk hugovk hugovk approved these changes

@gpshead gpshead gpshead approved these changes

@willingc willingc willingc approved these changes

Assignees

No one assigned

Labels

governance new-pep A new draft PEP submitted for initial review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@sethmlarson @hugovk @gpshead @willingc