Re: [python-committers] discuss.python.org participation

On Fri, Oct 12, 2018, at 11:55, Brett Cannon wrote: > On Thu, 11 Oct 2018 at 01:30, Antoine Pitrou wrote: > > > > > What concerns me is that there are several long-time and/or prominent > > developers who are not even registered (*) on discuss.python.org. For > > example Benjamin Peterson, Lar

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

[python-committers] Note: I published the first draft of PEP 8001

See: https://discuss.python.org/t/pep-8001-python-governance-voting-process/233 Cheers, Ł signature.asc Description: Message signed with OpenPGP ___ python-committers mailing

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