Hi, On Fri, Nov 6, 2020 at 8:22 AM Brian Nisbet <brian.nisbet@heanet.ie> wrote:
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