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

Meta: Classify Accepted Process PEPs as non-historical & mark PEP 8001 Final #2385

Merged

Conversation

CAM-Gerlach
Copy link
Member

Currently, Accepted but not yet implemented (Active) PEPs of the Process types are getting dumped into the "Historical" category, which isn't accurate and makes them much less visible, despite being in the process of implementation. Both PEP 581 (PEP-0581), the GitHub issue migration, and PEP 676 (PEP-0676), outlining the new PEP build system, fall into this category, despite both being actively in the process of being implemented and certainly not "historical".

Also, I noted PEP 8001 (PEP-8001) on the governance model vote is still listed as "Accepted", despite said vote having concluded (and the resulting decided-upon SC governance model fully implemented) years ago, so it does belong in the "historical" category.

As such, I've tweaked the classification logic to sort Accepted Process PEPs in to non-Historical category, along with Active ones, and updated PEP 8001 to Final since the process it describes is long concluded and now of only historical interest.

@CAM-Gerlach CAM-Gerlach self-assigned this Mar 7, 2022
@CAM-Gerlach CAM-Gerlach added the meta Related to the repo itself and its processes label Mar 7, 2022
@CAM-Gerlach CAM-Gerlach changed the title Meta: Classify accepted Process PEPs as non-historical and mark PEP 8001 Final Meta: Classify Accepted Process PEPs as non-historical & mark PEP 8001 Final Mar 7, 2022
@CAM-Gerlach CAM-Gerlach force-pushed the meta-classify-accepted-non-historical branch from d09a0ca to 1309e29 Compare March 11, 2022 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA signed meta Related to the repo itself and its processes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants