python · CasP0 · Feb 5, 2025
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -7,3 +7,8 @@ This repo uses the GitHub workflow that is used by other Python projects.
 - Copy and bump the date
 - Add any new items above the existing items
 - Remove any items marked closed or resolved on last update
+
+## Reviewing PEP's `Post-History` Header
+
+- Ensure that the PEP's `Post-History` header is reviewed for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
diff --git a/process/best-practices.md b/process/best-practices.md
@@ -33,6 +33,11 @@ Yet, one can only wear one at a time. It's important to reflect on one's role an
 
 > There's no single blueprint for success. ...consider their own organizations' history and values.
 
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
 ---
 
 [Bibliography - The Nonprofit Board Answer Book, Third Edition](https://www.amazon.com/Nonprofit-Board-Answer-Book-Executives-ebook-dp-B007T02Q7Y/dp/B007T02Q7Y/ref=mt_kindle)
diff --git a/process/onboarding.md b/process/onboarding.md
@@ -10,6 +10,8 @@
   - [ ] steering-council@ mailing list (which has private archives)
   - [ ] Discourse
 - [ ] Review [best practices](best-practices.md) for effective governance
+- [ ] Review the PEP's `Post-History` header for discussion threads
+- [ ] Discuss PEPs in the appropriate threads to gather community feedback and insights
 
 ## New Council Tasks
 

diff --git a/process/standing-delegations.md b/process/standing-delegations.md
@@ -56,3 +56,8 @@ efforts. As with the C API WG there is no standing PEP delegation as there are
 few PEPs specific to the documentation efforts, but the Editorial Board has
 specific autonomy and authority as described in PEP 732.
 
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2019-02-15_steering-council-update.md b/updates/2019-02-15_steering-council-update.md
@@ -102,3 +102,9 @@ For example, they can:
 - Work with the PSF to manage any project assets
 - Delegate parts of their authority to other subcommittees or
   processes
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2019-02-26_steering-council-update.md b/updates/2019-02-26_steering-council-update.md
@@ -92,3 +92,9 @@ For example, they can:
 - Work with the PSF to manage any project assets
 - Delegate parts of their authority to other subcommittees or
   processes
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2019-04-26_steering-council-update.md b/updates/2019-04-26_steering-council-update.md
@@ -176,3 +176,9 @@ For example, they can:
 - Work with the PSF to manage any project assets
 - Delegate parts of their authority to other subcommittees or
   processes
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2019-07-08_steering-council-update.md b/updates/2019-07-08_steering-council-update.md
@@ -80,6 +80,11 @@ PEP highlights include:
 - PEP 578, "Python Runtime Audit Hooks", Steve Dower.
   *Appointed Christian Heimes as BD.* "Landed, about to be marked Final."
 
+- Discussing PEPs in Threads Listed in the `Post-History` Header
+  - Review the PEP's `Post-History` header for discussion threads.
+  - Discuss PEPs in the appropriate threads to gather community feedback and insights.
+  - Emphasize the importance of community feedback and discussion.
+
 
 ### Interaction with PSF
 

diff --git a/updates/2019-11-09-steering-council-update.md b/updates/2019-11-09-steering-council-update.md
@@ -34,3 +34,9 @@ July 2019 through October 2019
 - [PEP 484](https://www.python.org/dev/peps/pep-0484/) policy for inclusion of stubs in typeshed was discussed and the [PR](https://github.com/python/peps/pull/1218/) around it. It was decided that a sentence would be changed to make type stubs an opt-out situation and not opt-in. 
 - [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion](https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539) were reviewed by the Steering Council. It was decided that the PEP as is would be rejected, but that the buildbot CI option will work. Nick has responded to the [discussion on Discourse](https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539/22) with the decision and suggestion.
 - It was decided that Ewa will help put together the Community Updates so they happen monthly. 
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2020-01-06-steering-council-update.md b/updates/2020-01-06-steering-council-update.md
@@ -17,3 +17,9 @@
 - Steering Council discussed PyPI’s typosquatting issues.
 - Group discussed the status of the GitHub migration plan. Ewa drafted a job description for the Project Manager role to help with the GitHub migration for the Dec 17th SC meeting. The Steering Council reviewed it and Ewa scheduled a call with the GitHub team for late January for next steps.
 - Steering Council decided to keep Zulip since the Packaging-wg plans on using it. We will re-evaluate usage next year. Guido informed the [Discourse thread](https://discuss.python.org/t/should-we-continue-using-zulip/2816/7). Brett [posted an announcement](https://python.zulipchat.com/#narrow/stream/116742-core.2Fhelp/topic/Engagement.20here.20might.20be.20winding.20down) in Zulip.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2020-11-02-steering-council-update.md b/updates/2020-11-02-steering-council-update.md
@@ -324,3 +324,8 @@
 - CZI grant request (https://github.com/python/steering-council/issues/26)
   was declined.
 
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-01-steering-council-update.md b/updates/2021-01-steering-council-update.md
@@ -106,3 +106,9 @@
   start a draft to the gist to explain the SC point of view.
 - All other items up for discussion got pushed to next week because we went
   30 minutes over.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-02-steering-council-update.md b/updates/2021-02-steering-council-update.md
@@ -63,3 +63,9 @@ impossibility to find a common replacement date in the week ]
   can benefit the Python community at large. It was decided that the steering
   council will email the Debian maintainers to try to reach some common ground
   and discuss how to proceed.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-03-steering-council-update.md b/updates/2021-03-steering-council-update.md
@@ -90,3 +90,9 @@
   discussion.
 - SC met with Ezio, PM for the GitHub Issues migration, to talk about
   status, progress and next steps, including keeping python-dev up to date.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-04-steering-council-update.md b/updates/2021-04-steering-council-update.md
@@ -76,3 +76,9 @@
   reviewers and PR authors could be beneficial and could help to avoid
   misunderstandings. It was decided that some devguide changes could be
   proposed.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-05-steering-council-update.md b/updates/2021-05-steering-council-update.md
@@ -28,3 +28,9 @@
   position and Carol placed it on the agenda for June 7th.
 - The Steering Council will not be meeting next week due to Memorial Day in
   the US.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-06-steering-council-update.md b/updates/2021-06-steering-council-update.md
@@ -37,3 +37,9 @@
 - Group discussed enum.Enum `repr` and `str` changes in 3.10 & 3.11. It was
   decided that Barry will email python-dev@ and strongly suggest that we
   rollback to 3.9 behavior for 3.10 and write a new PEP for 3.11.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-07-steering-council-update.md b/updates/2021-07-steering-council-update.md
@@ -44,3 +44,9 @@
   review the revised PEP if the author wants to revisit it.
 - Thomas created the private Python committers Discord and Pablo suggested
   we use it for the next virtual Sprint, which the group agrees with.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-08-steering-council-update.md b/updates/2021-08-steering-council-update.md
@@ -11,6 +11,12 @@
   reach out the [PEP 505](https://www.python.org/dev/peps/pep-0505/)(None-aware operators)
   authors to get a status update.
 
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
+
 # August 9
 - The Steering Council had a meeting with the GitHub issues PM (Ezio Melotti)
   to learn why there has been a long period of no progress and advise what
@@ -54,3 +60,9 @@
   communicate with Yury as they were building something similar for EdgeDB.
 - The Steering Council met with Ezio to discuss his progress with the GitHub
   migration project. The SC advised Ezio as to what the priority projects are.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-09-steering-council-update.md b/updates/2021-09-steering-council-update.md
@@ -37,3 +37,8 @@
   accept 649 but there is no clear path on how to handle the transition so community
   discussion is needed.
 
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-10-steering-council-update.md b/updates/2021-10-steering-council-update.md
@@ -46,3 +46,9 @@
   (Standardizing Enum str(), repr(), and format() behaviors) declined. The
   Steering Council will think of who else it can be delegated to, or take it
   on themselves.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.
diff --git a/updates/2021-11-steering-council-update.md b/updates/2021-11-steering-council-update.md
@@ -98,3 +98,9 @@
   time being there will be no communications about this to the PEP authors or
   the community as the SC wants to discuss this further. This discussion will
   continue with the new SC as well.
+
+## Discussing PEPs in Threads Listed in the `Post-History` Header
+
+- Review the PEP's `Post-History` header for discussion threads.
+- Discuss PEPs in the appropriate threads to gather community feedback and insights.
+- Emphasize the importance of community feedback and discussion.