FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

PEP 1: Further clarify PEP-Delegate notification & acceptance process by CAM-Gerlach · Pull Request #2273 · python/peps · GitHub

Repository navigation

PEP 1: Further clarify PEP-Delegate notification & acceptance process - #2273

Merged
JelleZijlstra merged 2 commits into
python:mainfrom
CAM-Gerlach:pep-1-clarify-delegate-process
Feb 1, 2022
Merged

JelleZijlstra merged 2 commits into
python:mainfrom
CAM-Gerlach:pep-1-clarify-delegate-process

Conversation

Copy link
Copy Markdown
Member

Followup to #1430 and PRs #2256 and #2257 , and discussed on python/steering-council#97 , to ensure the description of how PEP delegates should notify and request approval of the Steering Council is clear and consistent, and matches actual established practice, based on the descrepencies with the current merged language identified by @AA-Turner and discussed further with @willingc .

Comment thread pep-0001.txt
Comment thread pep-0001.txt Outdated

AA-Turner left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I think this is helpful in making the process more explicit, and being more instructive for authors and potential sponsors.

Some suggestions (and the one when I clicked the wrong button when trying to start the review)

A

Comment thread pep-0001.txt Outdated
Comment on lines +304 to +305
The Steering Council will generally accept such self-nominations by default,
but may choose to decline them.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality
Suggested change
The Steering Council will generally accept such self-nominations by default,
but may choose to decline them.
The Steering Council will ordinarily approve such self-nominations,
but may choose to decline them.

If "ordinarily" is too formal, "usually" also works.

"approve" makes more explicit that you must hear back in the affirmative from the Council.

A

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I see what you're trying to do here, but I'm concerned it is getting a bit far away from the original intended meaning—it now implies that the SC will typically approve nominations, but no longer directly mentions the decision-making rationale of approve-by-default, the original purpose of this sentence. It is now making a statement on approval probabilty (offers will be ordinarily approved) rather than approval strategy (offers will be approved by default unless there is a significant reason not to do so), as "ordinarily" (and "usually") refers to frequency while "generally" more generically is a general hedge, while "accept [...] by default" was what "generally" was referencing, not "accept" alone.

A more conservative suggestion that keeps the original meaning but applies your "approve" change would be the following:

Suggested change
The Steering Council will generally accept such self-nominations by default,
but may choose to decline them.
The Steering Council will generally approve such self-nominations by default,
but may choose to decline them.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Also, @brettcannon, thoughts?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Thanks for the added rationale -- the "generally" and "by default" felt odd in the same sentence, but I see they are serving different purposes.

Comment thread pep-0001.txt Outdated
Comment thread pep-0001.txt Outdated
CAM-Gerlach marked this pull request as draft January 25, 2022 23:00
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Brett Cannon <brett@python.org>
CAM-Gerlach force-pushed the pep-1-clarify-delegate-process branch from 359fca9 to 318a336 Compare January 25, 2022 23:06
CAM-Gerlach marked this pull request as ready for review January 25, 2022 23:08

AA-Turner left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Substantive changes look good

Comment thread pep-0001.txt

Copy link
Copy Markdown
Member Author

Hey @brettcannon , is there any objection to going ahead with this? Or should we ask for another formal round of SC review here?

Copy link
Copy Markdown
Member

Nope, go ahead and merge it!

JelleZijlstra merged commit 920f92f into python:main Feb 1, 2022

Copy link
Copy Markdown
Member Author

Thanks @brettcannon !

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants


Back | FazBrowse Home | New Git URL