# Steering Council Updates for August 2024

**URL:** <https://discuss.python.org/t/steering-council-updates-for-august-2024/71845>\
**Category:** Core Development\
**Tags:** sc-update\
**Created:** [November 21, 2024, 6:24am UTC](https://discuss.python.org/t/steering-council-updates-for-august-2024/71845 "2024-11-21T06:24:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gpshead](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/gpshead/32/54_2.png) [@gpshead](https://discuss.python.org/u/gpshead)\
**Post date:** [November 21, 2024, 6:24am UTC](https://discuss.python.org/t/steering-council-updates-for-august-2024/71845/1 "2024-11-21T06:24:14Z")

</div>

# 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/)

* * *

Poster’s notes:

Per [this earlier poll](https://discuss.python.org/t/should-we-post-sc-updates-in-core-development-rather-than-committers/60998) we’re now posting our updates in the Core Development channel.

We received feedback that the updates so far have been rather terse (yep). We’re aiming for more text in the future updates. September and October updates are written (thanks Velda!) the rest of us got blocked on time availability to deal with review and any final edits. Expect PRs for those [in our steering-council github](https://github.com/python/steering-council) repo where soon.