Uh oh!
There was an error while loading. Please reload this page.
PEP 1: Relax CODEOWNERS rule to allow PEP editors to "own" PEPs - #2252
Conversation
CAM-Gerlach
commented
Jan 20, 2022
Yeah, it certainly seems like a simple oversight to me; PEP 1 may not have envisioned PEP editors who weren't core developers, like you, me and @JelleZijlstra are today. This affects you too on PEP 676, and @JelleZijlstra is already listed as CODEOWNER on PEP 673 and PEP 675, so it seems worth clarifying (even if, I think, we all understand the intent of it). |
AA-Turner
commented
Jan 20, 2022
Build failed due to reST typo, now fixed. |
JelleZijlstra
left a comment
There was a problem hiding this comment.
#2112 is where we generally approved PEP editors as sponsors. This is consistent with that change.
CAM-Gerlach
left a comment
There was a problem hiding this comment.
Two small textual suggestions; otherwise ✔️ from me
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We've three PEP editors approving, I'll wait until tomorrow afternoon (~4pm UTC, 20/01) and merge if there's no negative comments A |
Rosuav
commented
Jan 20, 2022
I wonder if the last sentence might be less awkward as "sponsor/co-author(s) are added"? The singular/plural discrepancy is hard to handle, but maybe combining them might feel better. |
CAM-Gerlach
commented
Jan 20, 2022
Great suggestion @Rosuav ; this also bypasses the "and"/"or" issue I was haggling over |
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Chris Angelico <rosuav@gmail.com>
AA-Turner
commented
Jan 20, 2022
Thanks all for the reviews, merged |
xref #2228 (comment)
A