<div dir="ltr">What is clear to me after reading the Python Code of Conduct sent by Brian, and FIRST code of conduct sent by Myriam that our coc is a lot less clear and more complicated. I know we will be discussing this tomorrow during our meeting but I was just wondering out loud how much of a revamp we are getting ourselves in.<div>-salam</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 9, 2020 at 11:19 AM Brian Nisbet <<a href="mailto:brian.nisbet@heanet.ie">brian.nisbet@heanet.ie</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir="ltr"> <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Leo,</div> <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> One point that I'm definitely sure on is that we will need a larger team than what we have at the moment, especially as we were discussing needs for people to still be able to attend and function at a meeting.</div> <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Brian</div> <div> <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div id="gmail-m_-7233463309548522438Signature"> <div> <div id="gmail-m_-7233463309548522438divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif"> <p style="margin-top:0px;margin-bottom:0px">Brian Nisbet </p> <p style="margin-top:0px;margin-bottom:0px">Service Operations Manager</p> <p style="margin-top:0px;margin-bottom:0px">HEAnet CLG, Ireland's National Education and Research Network</p> <p style="margin-top:0px;margin-bottom:0px">1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland</p> <p style="margin-top:0px;margin-bottom:0px">+35316609040 <a href="mailto:brian.nisbet@heanet.ie" target="_blank">brian.nisbet@heanet.ie</a> <a href="http://www.heanet.ie" target="_blank">www.heanet.ie</a></p> <p style="margin-top:0px;margin-bottom:0px">Registered in Ireland, No. 275301. CRA No. 20036270 </p> </div> </div> </div> </div> <div id="gmail-m_-7233463309548522438appendonsend"></div> <hr style="display:inline-block;width:98%"> <div id="gmail-m_-7233463309548522438divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Leo Vegoda <<a href="mailto:leo@vegoda.org" target="_blank">leo@vegoda.org</a>><br> <b>Sent:</b> Sunday 8 November 2020 19:21<br> <b>To:</b> Brian Nisbet <<a href="mailto:brian.nisbet@heanet.ie" target="_blank">brian.nisbet@heanet.ie</a>><br> <b>Cc:</b> <a href="mailto:coc-tf@ripe.net" target="_blank">coc-tf@ripe.net</a> <<a href="mailto:coc-tf@ripe.net" target="_blank">coc-tf@ripe.net</a>><br> <b>Subject:</b> Re: [coc-tf] Python Community CoC & Procedures</font> <div> </div> </div> <div><font size="2"><span style="font-size:11pt"> <div>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.<br> <br> <br> Hi,<br> <br> On Fri, Nov 6, 2020 at 8:22 AM Brian Nisbet <<a href="mailto:brian.nisbet@heanet.ie" target="_blank">brian.nisbet@heanet.ie</a>> wrote:<br> ><br> > <a href="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" target="_blank"> 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</a><br> <br> I found this an impressive collection of documents. There's clearly<br> been a lot of careful thought put into this code.<br> <br> I particularly like the "Our Community" section at the start,<br> especially the first bullet about being open.<br> <br> The summary of process in the Python code goes from #4 (Evaluate the<br> reported incident) to #5 (Propose a behavioral modification plan) and<br> #6 (Propose consequences for the reported behavior). It is only at<br> this point that there's an acknowledgement that a report could be in<br> error. I think that for clarity of communication, we should make sure<br> the process itself does not appear to pre-judge the outcome.<br> <br> The section on decision making is useful input to us in a couple of<br> contexts. Firstly, they require a 2/3 majority in a vote of the Code<br> of Conduct WG when deciding on behavioral modification plans and<br> consequences for violation of the code. If we chose to adopt this<br> model it would mean a significantly larger team than the current<br> Trusted Contacts team, which was previously three members and is now<br> two. This is because the vote needs to be possible if a member has a<br> conflict of interest or is unavailable. Presumably, this means at<br> least four people in the Code of Conduct team.<br> <br> Many thanks,<br> <br> Leo<br> </div> </span></font></div> </div> -- <br> coc-tf mailing list<br> <a href="mailto:coc-tf@ripe.net" target="_blank">coc-tf@ripe.net</a><br> <a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a><br> </blockquote></div>