PEP 13 Change Proposal - Remove CoC responsibility (WIP)

Will add URL to the Discourse topic later.

Author: malemburg

peps/pep-0013.rst

@@ -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
@@ -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
@@ -343,7 +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