spelling conventions and errors (#812)
This commit is contained in:
parent
9459fd81ba
commit
a187ebc254
16
pep-8015.rst
16
pep-8015.rst
|
@ -94,9 +94,9 @@ This is the largest group: anyone who uses Python.
|
||||||
Python Contributors
|
Python Contributors
|
||||||
===================
|
===================
|
||||||
|
|
||||||
Once a Python user sends an email to a Python mailing list, comments the
|
Once a Python user sends an email to a Python mailing list, comments on
|
||||||
Python bug tracker, proposes or reviews a Python change, they become a
|
the Python bug tracker, proposes or reviews a Python change, they become
|
||||||
Python contributor.
|
a Python contributor.
|
||||||
|
|
||||||
|
|
||||||
Python Teams
|
Python Teams
|
||||||
|
@ -115,7 +115,7 @@ become a core developer.
|
||||||
|
|
||||||
A team might become allowed to decide on their own PEPs, but only the Core
|
A team might become allowed to decide on their own PEPs, but only the Core
|
||||||
board can allow that (and the board has the power to revoke it as well).
|
board can allow that (and the board has the power to revoke it as well).
|
||||||
Such case is exceptional, currently a single team has such permission:
|
Such a case is exceptional, currently a single team has such permission:
|
||||||
the Packaging team.
|
the Packaging team.
|
||||||
|
|
||||||
See `Annex: Examples of Python Teams`_.
|
See `Annex: Examples of Python Teams`_.
|
||||||
|
@ -180,7 +180,7 @@ Election of Python Core Board members
|
||||||
|
|
||||||
The Python Core Board is composed of 3 people. They are elected for three
|
The Python Core Board is composed of 3 people. They are elected for three
|
||||||
year terms, and each year a member is replaced. A board member can be
|
year terms, and each year a member is replaced. A board member can be
|
||||||
candidate for the seat they are leaving. Candidates have 2 weeks to
|
a candidate for the seat they are leaving. Candidates have 2 weeks to
|
||||||
apply, and a vote is open for 1 month. The vote uses the `Condorcet
|
apply, and a vote is open for 1 month. The vote uses the `Condorcet
|
||||||
method <https://en.wikipedia.org/wiki/Condorcet_method>`_. Votes are
|
method <https://en.wikipedia.org/wiki/Condorcet_method>`_. Votes are
|
||||||
private during the vote, but become public when the vote completes.
|
private during the vote, but become public when the vote completes.
|
||||||
|
@ -314,15 +314,15 @@ Special Case: Ban a core developer
|
||||||
|
|
||||||
As any other member of the Python community, the PSF Code of Conduct
|
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
|
Workgroup can ban a core developer for a limited amount of time. In this
|
||||||
case, the core developer immediately looses their core developer status.
|
case, the core developer immediately loses their core developer status.
|
||||||
|
|
||||||
In general, a ban is only the last resort action when all other options
|
In general, a ban is only the last resort action when all other options
|
||||||
have been exausted.
|
have been exhausted.
|
||||||
|
|
||||||
At the end of the ban, the developer is allowed to contribute again as a
|
At the end of the ban, the developer is allowed to contribute again as a
|
||||||
regular contributor.
|
regular contributor.
|
||||||
|
|
||||||
If the developer changes their behaviour, another core developer can
|
If the developer changes their behavior, another core developer can
|
||||||
open a new vote to propose the developer for promotion to core
|
open a new vote to propose the developer for promotion to core
|
||||||
developer. The vote follows the same process than for any other Python
|
developer. The vote follows the same process than for any other Python
|
||||||
contributor.
|
contributor.
|
||||||
|
|
Loading…
Reference in New Issue