CAUTION[External]: This email originated from outside of the organisation. Do not click on links or open the attachments unless you recognise the sender and know the content is safe.
Hi,
On Fri, Nov 6, 2020 at 8:22 AM Brian Nisbet <brian.nisbet@heanet.ie> wrote:
>
>
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.python.org%2Fpsf%2Fconduct%2F&data=04%7C01%7C%7Ccc2c863f0ff24669545008d8841b8fa0%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637404601201294919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=STgrDjNTpNj2w0uT15tOBaIybbn3stfsh7KUl3S8Ky0%3D&reserved=0
I found this an impressive collection of documents. There's clearly
been a lot of careful thought put into this code.
I particularly like the "Our Community" section at the start,
especially the first bullet about being open.
The summary of process in the Python code goes from #4 (Evaluate the
reported incident) to #5 (Propose a behavioral modification plan) and
#6 (Propose consequences for the reported behavior). It is only at
this point that there's an acknowledgement that a report could be in
error. I think that for clarity of communication, we should make sure
the process itself does not appear to pre-judge the outcome.
The section on decision making is useful input to us in a couple of
contexts. Firstly, they require a 2/3 majority in a vote of the Code
of Conduct WG when deciding on behavioral modification plans and
consequences for violation of the code. If we chose to adopt this
model it would mean a significantly larger team than the current
Trusted Contacts team, which was previously three members and is now
two. This is because the vote needs to be possible if a member has a
conflict of interest or is unavailable. Presumably, this means at
least four people in the Code of Conduct team.
Many thanks,
Leo