<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.markdown { white-space: normal; }
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
h1 { font-size: 1.4em; }
h2 { font-size: 1.2em; }
h3 { font-size: 1.1em; }
blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
blockquote a { color: #777777; }
blockquote blockquote a { color: #999999; }
blockquote blockquote blockquote a { color: #BBBBBB; }
math[display="inline"] > mrow { padding:5px; }
div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="markdown">
<p dir="auto">We are not commiunicating: My point is that <em>any</em> action taken on behalf of the community needs a process for appeal and review. This is especially true if the action can be perceived as corrective or punitive and/or if it involves some form of judgement about behavior. In these cases we better have a well defined process for appeal and review in place before someone disagrees with what we are doing. I included the examples to make the point that the new process proposes <em>grave</em> sanctions. I was not addressing the sanctions themselves.</p>
<p dir="auto">But since we are here:</p>
<p dir="auto">On 2 Sep 2019, at 14:09, Amanda Gowland wrote:</p>
</div>
<div class="plaintext"><blockquote><p dir="auto">Hi Daniel,<br>
<br>
On 02/09/2019 14:03, Daniel Karrenberg wrote:</p>
<blockquote><p dir="auto">I consider this absolutely not ready for a consensus call. It introduces a new process with grave sanctions including<br>
<br>
*<br>
<br>
“Removing a presentation and video archive from the meeting website”<br>
</p>
</blockquote><p dir="auto">Disagree. If someone violates the CoC in their presentation, they should be given an opportunity to remove the offending material and re-upload. Likewise, if there's a video recording of someone being racist/sexist/homophobic/harrasing (for example), the video should either be removed or have the offending content edited out.</p>
</blockquote></div>
<div class="markdown">
<p dir="auto">Removing someone’s contribution from a community forum is <em>serious</em> business in a community that is about exchanging information and opinions! </p>
<p dir="auto">Maybe we should incorporate some of the words you just wrote in the draft itself. At the moment it reads like removal is the only option. Again: how are disputes with the author solved? Will the CoC team dictate the edits? What happens in case of a dispute?</p>
</div>
<div class="plaintext"><blockquote><blockquote><p dir="auto"> *<br>
<br>
“Requiring that the violator leave the meeting/social immediately<br>
without a refund (as per the RIPE Meeting Terms and Conditions)”<br>
</p>
</blockquote><p dir="auto">This is nothing new. We already state this in the T&Cs for the RIPE Meeting that all attendees agree to in the registration process.</p>
</blockquote></div>
<div class="markdown">
<p dir="auto">The process proposed <em>is</em> new.</p>
</div>
<div class="plaintext"><blockquote><blockquote><p dir="auto"> *<br>
<br>
“Banning attendance for future meetings (in the case of repeated<br>
violations, violence and extreme violations)”<br>
<br>
Yet there is no mention at all of appeal, review or redress. This is not the way the RIPE community should operate.<br>
</p>
</blockquote><p dir="auto">This was discussed on Friday with HPH - I'll be adding some text in here re: Appeal...as well as incorporating the rest of his feedback.</p>
</blockquote></div>
<div class="markdown">
<p dir="auto">Lets hear it!</p>
</div>
<div class="plaintext"><blockquote><blockquote><p dir="auto">I also suggest to have the language reviewed by the NCC legal team for legality and precision<br>
before considering a consensus call.<br>
</p>
</blockquote><p dir="auto">Yes, have already discussed this and that is the plan.</p>
</blockquote></div>
<div class="markdown">
<p dir="auto">Good to hear.</p>
<p dir="auto">Thanks. </p>
<p dir="auto">Daniel</p>
</div>
</body>
</html>