PEP 1: Remove mentions of peps@python.org, update the process #1541
Conversation
- peps@python.org is replaced by mentioning @python/pep-editors; python-checkins by the repository - Devs with write access are encouraged to submit PRs rather than push commits directly. - Developers with write access are expected to handle their PRs themselves, and may mention @python/pep-editors if needed. This corresponds to the current situation (and means less work/responsibility for PEP editors, without a real downside). - Taking ownership of a PEP is done through GitHub rather than e-mail - A note about core devs managing their own PRs is repeated in "PEP Editor Responsibilities & Workflow": people might look there instead of reading all of "Submitting a PEP".
|
+1 LGTM. I don't suppose it's possible to mention @pep-editors without the python/ in front of it? |
|
Welp, it didn't turn into a link, so I'm presuming that, no, it's not possible. :) |
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
|
Thank you for this update to PEP 1! |
|
Fine with me. (When was I dropped from the list of PEP editors? I don't recall withdrawing, though I may simply have forgotten that I requested to be dropped in the aftermath of my BDFL retirement. In any case I've requested to be added to the team.) |
AA-Turner
added a commit
to AA-Turner/peps
that referenced
this pull request
Aug 15, 2020
…#1541) Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
mnm678
added a commit
to mnm678/peps
that referenced
this pull request
Oct 22, 2020
…#1541) Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
gaborbernat
added a commit
to gaborbernat/peps
that referenced
this pull request
Dec 13, 2020
…#1541) Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
See discussion on Discourse.
This PR does a bit more than just replace the mailing list with the GitHub group: I meant to be closer to the current practice. Please amend and update this however you see fit.
peps@python.orgis replaced by mentioning @python/pep-editorsthemselves, and may mention @python/pep-editors if needed.
This corresponds to the current situation (and means less
work/responsibility for PEP editors, without a real downside).
"PEP Editor Responsibilities & Workflow": people might look there
instead of reading all of "Submitting a PEP".