PEP 8015: ban a core dev and update the PEP by vstinner · Pull Request #810 · python/peps
Expand Up
@@ -284,6 +284,9 @@ That's fine. Sometimes, doing nothing is the wisest choice.
PSF Code of Conduct Workgroup
=============================
Charter -------
The workgroup's purpose is to foster a diverse and inclusive Python community by enforcing the PSF code of conduct, along with providing guidance and recommendations to the Python community on codes of Expand All @@ -306,6 +309,41 @@ We work toward this common goal in three ways: The organization of this workgroup is defined by the `ConductWG Charter <https://wiki.python.org/psf/ConductWG/Charter>`_.
Special Case: Ban a core developer ----------------------------------
As any other member of the Python community, the PSF Code of Conduct Workgroup can ban a core developer for a limited amount of time. In this case, the core developer immediately looses their core developer status.
In general, a ban is only the last resort action when all other options have been exausted.
At the end of the ban, the developer is allowed to contribute again as a regular contributor.
If the developer changes their behaviour, another core developer can open a new vote to propose the developer for promotion to core developer. The vote follows the same process than for any other Python contributor.
How to update this PEP ======================
The first version of this PEP has been written after Guido van Rossum decided to resign from his role of BDFL in July 2018. Before this PEP, the roles of Python community members have never been formalized. It is difficult to design a perfect organization at the first attempt. This PEP can be updated in the future to adjust the organization.
The process to update this PEP is that someone proposes a change and the change must be validated by a vote. The vote is reserved to core developers, happens in public on the python-committers mailing list, and will be open for 1 month. The change is only approved if the number of "+1" exceed the number of "-1". Other votes (null, "+0" and "-0") are ignored.
Annex: Examples of Python Teams =============================== Expand Down
Charter -------
The workgroup's purpose is to foster a diverse and inclusive Python community by enforcing the PSF code of conduct, along with providing guidance and recommendations to the Python community on codes of Expand All @@ -306,6 +309,41 @@ We work toward this common goal in three ways: The organization of this workgroup is defined by the `ConductWG Charter <https://wiki.python.org/psf/ConductWG/Charter>`_.
Special Case: Ban a core developer ----------------------------------
As any other member of the Python community, the PSF Code of Conduct Workgroup can ban a core developer for a limited amount of time. In this case, the core developer immediately looses their core developer status.
In general, a ban is only the last resort action when all other options have been exausted.
At the end of the ban, the developer is allowed to contribute again as a regular contributor.
If the developer changes their behaviour, another core developer can open a new vote to propose the developer for promotion to core developer. The vote follows the same process than for any other Python contributor.
How to update this PEP ======================
The first version of this PEP has been written after Guido van Rossum decided to resign from his role of BDFL in July 2018. Before this PEP, the roles of Python community members have never been formalized. It is difficult to design a perfect organization at the first attempt. This PEP can be updated in the future to adjust the organization.
The process to update this PEP is that someone proposes a change and the change must be validated by a vote. The vote is reserved to core developers, happens in public on the python-committers mailing list, and will be open for 1 month. The change is only approved if the number of "+1" exceed the number of "-1". Other votes (null, "+0" and "-0") are ignored.
Annex: Examples of Python Teams =============================== Expand Down