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 618: Self-Nomination for BDFL-Delegate #28

Closed
brandtbucher opened this issue Jun 14, 2020 · 7 comments
Closed

PEP 618: Self-Nomination for BDFL-Delegate #28

brandtbucher opened this issue Jun 14, 2020 · 7 comments

Comments

@brandtbucher
Copy link
Member

@gvanrossum has agreed to act as BDFL(-Delegate?) for PEP 618.

While PEP 1 states that such self-nominations are accepted by default and can be vetoed by the SC, it's otherwise quite vague. Beyond the PEP header, is there any requirement to communicate the decision to the SC or others? If so, how?

@gvanrossum
Copy link
Member

I expect to have time to review PEP 618 later this week.

@warsaw
Copy link
Member

warsaw commented Jun 15, 2020

I have no objection's to Guido serving as BDFL-Delegate for PEP 618. I've added this agenda item to the Steering Council meeting for 2020-06-15.

@vstinner
Copy link
Member

BDFL-Delegate: Guido van Rossum <[email protected]> header was added to the PEP in python/peps#1429 which was merged by Guido.

@warsaw
Copy link
Member

warsaw commented Jun 15, 2020

True, but let's make it official, as pointed out by @brandtbucher

@gvanrossum
Copy link
Member

At the very least please clarify the process. PEP 1 was not enough for Brandt and me to know how to proceed.

@brandtbucher
Copy link
Member Author

Particularly confusing is this bit:

However, content review and final acceptance of the PEP must be requested of the core developers, usually via an email to the python-dev mailing list.

The part about "final acceptance" just seems incorrect.

@warsaw
Copy link
Member

warsaw commented Jun 15, 2020

The SC approves of @gvanrossum as PEP-Delegate for PEP 618. We will also be updating the PEP 1 language to clarify the process. Thank you!

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

5 participants
@vstinner @warsaw @gvanrossum @brandtbucher and others