Commit Graph

11 Commits

Author SHA1 Message Date
Hugo van Kemenade 5bdec964da
Meta: Add a governance topic (#2993)
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: Gregory P. Smith <greg@krypto.org>
Fixes https://github.com/python/peps/issues/2987
2023-02-02 12:50:01 +02:00
Adam Turner 113e490701
Several PEPs: Use explicit `:pep:` and `:rfc:` roles (#2209) 2022-01-21 11:03:51 +00:00
Hugo van Kemenade e5c7822dcd
PEPs 1, 426, 512, 545, 8001, 8002, 8016: rename master to main (#2179) 2021-12-03 12:29:10 +01:00
Brett Cannon bb4751379a
Many PEPs: Normalize the 'Created' field (#1805) 2021-02-09 08:54:26 -08:00
Marti Raudsepp 9b64c6ea75
Various typo/grammar/style fixes (#1789)
Changes detected by Topy (https://github.com/intgr/topy), all changes
verified by hand, false positives have been omitted.

These range from straight-out misspellings to debatable hyphen placement.
The hyphen changes are supported by grammar manuals of style.
2021-02-03 06:06:23 -08:00
Nathaniel J. Smith d4a5364baf
PEP 13: make it real (#857) 2018-12-26 22:40:25 -08:00
Łukasz Langa 5bd92c746b
Accept PEP 8016 and reject other governance proposals 2018-12-17 17:09:10 +01:00
Nathaniel J. Smith ad3b078c20
PEP 8016: remove confusing term "strict majority" (#846)
This doesn't change the meaning at all; just removes a confusing term.

Thanks to Xiang Zhang for pointing this out here:
https://discuss.python.org/t/pep-8016-the-steering-council-model/394/36
2018-11-30 17:49:58 -08:00
Nathaniel J. Smith 8fd0cdeb66 PEP 8016: more tweaks based on discussion (#838)
* PEP 8016: more tweaks based on discussion

* Removed the requirement that council members have to be core team
  members; added the requirement that non-core-team council candidates
  need to be nominated by a core team member. Rationale: Steve Dower
  is worried that we may have a shortage of core team members who are
  willing to serve on the council. I'm not worried myself, but I like
  Steve and don't want him to worry; this is an easy way to help with
  that. Requiring a core team member nomination should be harmless,
  since any candidate that can't get a nomination is certainly not
  going to win a vote, and it lets us filter out random jokers early.

* Added some language to emphasize that emeritus core team members
  will still be listed on the website and their past contributions
  will continue to be recorded.

* Changed the vote tie-breaker from "seniority as a core team member"
  to "mutual agreement or random chance". Victor pointed out that
  seniority is not always known or unique, and anyway this doesn't
  make much sense if we're allowing non-core-team member candidates.
  The goal was always just to have some unambiguous resolution that
  doesn't require voting again, and this seems like a simpler and more
  reliable option.

* Clarified that in the never-going-to-happen edge case where a core
  team member misbehaves so badly that the project has to kick them
  out AND that core team member is on the council, then they're also
  removed from the council.

* Added link to the second discussion thread.

* Made a few small wording tweaks and fixed some ReST formatting.

* PEP 8016: fix the definition of "Python committer" to match reality

* Rephrase the emeritus text again, to hopefully be even more clear

* One more wording tweak

* s/emeritus/inactive/, and remove the [TBD]
2018-11-15 21:29:16 -05:00
Nathaniel J. Smith 572be20994 PEP 8016: add more details about how emeritus members work (#834) 2018-11-05 22:46:39 -05:00
Nathaniel J. Smith 5175b24a04 PEP 8016 - initial draft (#827) 2018-11-05 13:00:49 -05:00