Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meeting notes for the Steering Council for August 2024 #257

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,7 @@ for filename in filenames:
- [2024-01,02,03](updates/2024-01,02,03-steering-council-update.md)
- [2024-04,05,06](updates/2024-04,05,06-steering-council-update.md)
- [2024-07](updates/2024-07-steering-council-update.md)
- [2024-08](updates/2024-08-steering-council-update.md)
<!-- [[[end]]] -->

## Process
Expand Down
35 changes: 35 additions & 0 deletions updates/2024-08-steering-council-update.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Steering Council Updates for August 2024

## 2024-08-07

- Conclusion of the Code of Conduct violation
- Discussion on [PEP 667 - Consistent views of namespaces](https://peps.python.org/pep-0667/) semantic changes

## 2024-08-14

- Deliberation of the decision regarding the Code of Conduct violation
- Discussion on how to make the Steering Council more effective by suggesting a different body parallel with the Steering Council to deal with social matters
- Highlight on the need to make clarification on the following different bodies: Code of Conduct Working Group, Steering Council and Python Software Foundation
- Discussion on the resignation of a Core Python Developer
- Mentoring survey: still to be released
- Discussion on [PEP 741 - Python Configuration C API](https://peps.python.org/pep-0741/)

## 2024-08-21

- Discussion on [PEP 741 - Python Configuration C API](https://peps.python.org/pep-0741/)
- Discussion on having overlapping Steering Council terms for continuity’s sake
- Discussion on mentorship, its role and how the Steering Council can improve mentorship for some at-risk packages/libraries

## 2024-08-28

- Cleared out pending tasks and re-evaluated the priority tasks
- Accepted [PEP 741 - Python Configuration C API](https://peps.python.org/pep-0741/)
- Tabled discussion of [PEP 12 – Sample reStructuredText PEP Template](https://peps.python.org/pep-0012/) changes (regrouping rejection rationale, and adding a discussion of publishing new modules to PyPI) for the Core Dev sprint
- Discussion on publishing to PyPI, specifically:
- Getting approval
- Process or flow of release
- Re-review of [PEP 667 - Consistent views of namespaces](https://peps.python.org/pep-0667/)
- Discussion on more explicit authority for the Release Manager’s role going forward
- Highlight on the ongoing [PEP 13 – Python Language Governance](https://peps.python.org/pep-0013/) discussion on potential changes
- Discussion on whether there should be a PEP for PyREPL
- Discussion on how to know when something needs a PEP or not and update [PEP 2 –Procedure for Adding New Modules](https://peps.python.org/pep-0002/)
Loading