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.

Sign up for GitHub

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

Jump to bottom

PEP 13 Change Proposal - Remove CoC responsibility (WIP) #4134

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

PEP 13 Change Proposal - Remove CoC responsibility (WIP) #4134

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7a944f7
PEP 13 Change Proposal - Remove CoC responsibility (WIP)
malemburg Nov 21, 2024
ec2ea75
Remove additional reference to conduct issues.
malemburg Nov 22, 2024
d9c8a86
Add a missing line break
malemburg Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions peps/pep-0013.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,6 @@ The council has broad authority to make decisions about the project.
For example, they can:

* Accept or reject PEPs
* Enforce or update the project's code of conduct
* Work with the PSF to manage any project assets
* Delegate parts of their authority to other subcommittees or
processes
Expand All @@ -84,8 +83,7 @@ The council should look for ways to use these powers as little as
possible. Instead of voting, it's better to seek consensus. Instead of
ruling on individual PEPs, it's better to define a standard process
for PEP decision making (for example, by accepting one of the other
801x series of PEPs). It's better to establish a Code of Conduct
committee than to rule on individual cases. And so on.
801x series of PEPs). And so on.

To use its powers, the council votes. Every council member must either
vote or explicitly abstain. Members with conflicts of interest on a
Expand Down Expand Up @@ -169,8 +167,7 @@ Ejecting core team members
~~~~~~~~~~~~~~~~~~~~~~~~~~

In exceptional circumstances, it may be necessary to remove someone
from the core team against their will. (For example: egregious and
ongoing code of conduct violations.) This can be accomplished by a
from the core team against their will. This can be accomplished by a
steering council vote, but unlike other steering council votes, this
requires at least a two-thirds majority. With 5 members voting, this
means that a 3:2 vote is insufficient; 4:1 in favor is the minimum
Expand Down Expand Up @@ -344,6 +341,7 @@ History of amendments

2019-04-17: Added the vote length for core devs and changes to this document.

2024-12-01: Removed the responsibility to deal with code of conduct issues.


Acknowledgements
Expand Down