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

PEP editor as a PEP sponsor #73

Closed
jorenham opened this issue Aug 9, 2021 · 11 comments
Closed

PEP editor as a PEP sponsor #73

jorenham opened this issue Aug 9, 2021 · 11 comments

Comments

@jorenham
Copy link

jorenham commented Aug 9, 2021

For my PEP, @gvanrossum proposed that @JelleZijlstra would make an appropriate sponsor (see python/peps#2045
), as he has been helping me with the PEP since I first suggested the feature in python/typing#813. However, @JelleZijlstra is not a core developer, and I came to understand that this is not allowed. Would it be possible to make an exception to this rule?

@hugovk
Copy link
Member

hugovk commented Aug 9, 2021

PEP 1 says it's allowed with approval from the Steering Council, so you're in the right place!

Ideally, a core developer sponsor is identified, but non-core sponsors may also be selected with the approval of the Steering Council.

https://www.python.org/dev/peps/pep-0001/#submitting-a-pep

@JelleZijlstra
Copy link
Member

As background, I have been a core developer on https://github.com/python/typeshed/ and https://github.com/python/mypy for a few years, and more recently I have become a PEP editor and a triager on the CPython repo.

@brettcannon
Copy link
Member

I thought we had a standing rule that PEP editors could sponsor PEPs since they obviously know how a PEP should be structured and handled?

@JelleZijlstra
Copy link
Member

Not in PEP 1 (Hugo linked the relevant text above), and if that rule is present somewhere else I'm not aware of it.

@brettcannon brettcannon changed the title Non-core dev PEP sponsor PEP editor as a PEP sponsor Aug 11, 2021
@gvanrossum
Copy link
Member

Bumping this in the hope that it'll make the next SC agenda. Maybe before ruling about the general case (which might require a long discussion) the SC could quickly decide that it's okay for Jelle to sponsor the specific PEP we're talking about here? (That PEP is about adding +T and -T to indicate co-/contra-variance for type variables.)

@warsaw
Copy link
Member

warsaw commented Sep 7, 2021

Thanks @gvanrossum - I've pinged the SC to see if we can provide an answer before our next meeting.

@warsaw
Copy link
Member

warsaw commented Sep 8, 2021

@gvanrossum The SC is fine with @JelleZijlstra being the PEP Sponsor for this PEP.

@warsaw
Copy link
Member

warsaw commented Oct 18, 2021

There's nothing more to do for this ticket, closing.

@warsaw warsaw closed this as completed Oct 18, 2021
@gvanrossum
Copy link
Member

So there's no ruling on the general case and no update to PEP 1 to bring it in line with Brett's recollection?

@warsaw
Copy link
Member

warsaw commented Oct 18, 2021

What exactly should PEP 1 be updated to say? Do you mind submitting a PR against PEP 1 to change the language?

@gvanrossum
Copy link
Member

Sure, see python/peps#2112

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants