iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update PEP 815 (#825) 

* Explain how a Python team is created
* Clarify the special case when a Steering Committee member
  proposes a PEP
This commit is contained in:
Victor Stinner 2018-11-01 18:07:06 +01:00 committed by GitHub
parent 878f0e9ce7
commit 0ef5cfdaf4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-8015.rst
View File

@ -108,8 +108,14 @@ Python became too big to work as an unique team anymore, people
naturally have grouped themselves as teams to work more closely on
specific topics, sometimes called "Special Interest Group" (SIG).
When enough developers are interested by a specific topic, they can
create a new team. Usually, the main action is to ask the Python
postmaster to create a new "SIG" mailing list, but the team can choose
to use a different communication channel.
Team members are Python contributors and Python core developers. The
team is responsible to select who can join the team and how.
team is self-organized and is responsible to select who can join the
team and how.
Team members can get the bug triage permission on the team bug tracker
component. Working in a team is a nice way to learn more to maybe later
@ -240,7 +246,8 @@ Special Case: Steering Committee Members And PEPs
A committee member cannot be a PEP delegate.
A committee member can offer a PEP, but cannot decide how their own PEP
is approved.
is approved. In this case, the two other board members are responsible
to decide how the PEP is approved.
When the committee decides that a PEP must be voted, committee members
can vote as they are also core developers, but they don't have more