Re: [python-committers] PEP 8015: Organization of the Python community

Hi, Since October 8, we had many productive discussions on governance PEPs and I made multiple changes to my PEP 8015. See the "Version History" at the end. The latest (I hope the *last*) change is that the Steering Committee is now made of 5 people instead of 3, there are no term limits (instead

Re: [python-committers] PEP 8015: Organization of the Python community

Brett: > Is this here to mean the expectation that the conduct WG will manage CoC > issues for the core development team? Core developers and Steering Committee members are at the same level than any other Python contributor when they misbehave. I expect the "autonomous" conduct workgroup to hand

Re: [python-committers] PEP 8015: Organization of the Python community

Hi Brett, I just updated my PEP to take in account your comments. Le ven. 12 oct. 2018 à 20:33, Brett Cannon a écrit : >> Team members are Python contributors and Python core developers. The >> team is responsible to select who can join the team and how. > > How is this bootstrapped? Do I get to

Re: [python-committers] PEP 8015: Organization of the Python community

Hi, To take in account all discussions around my PEP 8015, I updated it: it’s now the version 4. I added a Version History at the bottom of the PEP to help reviewers. In short: votes are now announced in advance (0, 1 or 3 weeks depending on the vote) and only open for 1 week instead of 1 month, t

Re: [python-committers] PEP 8015: Organization of the Python community

Le 15/10/2018 à 12:00, Victor Stinner a écrit : > Le lun. 15 oct. 2018 à 11:35, Antoine Pitrou a écrit : >>> I don't want to put this responsibility on the board. So yes, >>> conflicts between core developers will be handled by the conduct WG. >> >> How does that work? The conduct WG doesn't eve

Re: [python-committers] PEP 8015: Organization of the Python community

Le lun. 15 oct. 2018 à 11:35, Antoine Pitrou a écrit : > > I don't want to put this responsibility on the board. So yes, > > conflicts between core developers will be handled by the conduct WG. > > How does that work? The conduct WG doesn't even seem to have published > procedures. Also we canno

Re: [python-committers] PEP 8015: Organization of the Python community

Le 15/10/2018 à 10:30, Victor Stinner a écrit : > >>> The organization of this workgroup is defined by the >>> `ConductWG Charter `_. >> >> Is this here to mean the expectation that the conduct WG will manage CoC >> issues for the core development t

Re: [python-committers] PEP 8015: Organization of the Python community

Le ven. 12 oct. 2018 à 20:33, Brett Cannon a écrit : >> Python became too big to work as an unique team anymore, people >> naturally have grouped themself as teams to work more closely on >> specific topics, sometimes called "Special Interest Group" (SIG). >> >> Team members are Python contributor

Re: [python-committers] PEP 8015: Organization of the Python community

On Mon, 8 Oct 2018 at 13:08, Victor Stinner wrote: > Hi, > > I just finished to write the PEP 8015: "Organization of the Python > community". I had limited time to write it, so sorry if some parts > still look "raw". Full content below. HTML version: > >https://www.python.org/dev/peps/pep-801

[python-committers] PEP 8015: Organization of the Python community

Hi, I just finished to write the PEP 8015: "Organization of the Python community". I had limited time to write it, so sorry if some parts still look "raw". Full content below. HTML version: https://www.python.org/dev/peps/pep-8015/ Right now, the HTML page still returns me a 404 error. In the