parent
b0983b22b1
commit
5aed1fd130
|
@ -34,9 +34,9 @@ This PEP describes:
|
|||
* The decision delegation process;
|
||||
* Any changes to the PEP process to fit the new governance model;
|
||||
|
||||
This PEP does *not* name a new BDFL. Should this model be adopted, it will be
|
||||
codified in PEP 13 along with the names of all officeholders described in this
|
||||
PEP.
|
||||
This PEP does *not* name a new BDFL. Should this model be adopted, it
|
||||
will be codified in PEP 13 along with the names of all officeholders
|
||||
described in this PEP.
|
||||
|
||||
|
||||
Open discussion points
|
||||
|
@ -207,7 +207,7 @@ ask, and provide insight into the impact on other users of Python that
|
|||
the GUIDO may not be as familiar with. The CoP are the GUIDO's
|
||||
trusted advisers, and a close working relationship is expected.
|
||||
|
||||
The CoP shall consistent of 3 members, elected from among the core
|
||||
The CoP shall consist of 3 members, elected from among the core
|
||||
developers. Their term runs for 3 years and members may run for
|
||||
re-election as many times as they want. To ensure continuity, CoP
|
||||
members are elected on a rotating basis; every year, one CoP member is
|
||||
|
|
Loading…
Reference in New Issue