<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Daniel, <br>
<br>
On 02/09/2019 14:03, Daniel Karrenberg wrote:<br>
</div>
<blockquote type="cite"
cite="mid:586B9BC4-D383-4F12-9C74-CF1358538D30@ripe.net">
<meta http-equiv="Content-Type" content="text/html; 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; }
a { color: #3983C4; }
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>
<div class="markdown">
<p dir="auto">I consider this absolutely not ready for a
consensus call. It introduces a new process with grave
sanctions including</p>
<ul>
<li>
<p dir="auto">“Removing a presentation and video archive
from the meeting website”</p>
</li>
</ul>
</div>
</blockquote>
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. <br>
<blockquote type="cite"
cite="mid:586B9BC4-D383-4F12-9C74-CF1358538D30@ripe.net">
<div class="markdown">
<ul>
<li>
<p dir="auto">“Requiring that the violator leave the
meeting/social immediately without a refund (as per the
RIPE Meeting Terms and Conditions)” </p>
</li>
</ul>
</div>
</blockquote>
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. <br>
<blockquote type="cite"
cite="mid:586B9BC4-D383-4F12-9C74-CF1358538D30@ripe.net">
<div class="markdown">
<ul>
<li>
<p dir="auto">“Banning attendance for future meetings (in
the case of repeated violations, violence and extreme
violations)”</p>
</li>
</ul>
<p dir="auto">Yet there is no mention at all of appeal, review
or redress. This is not the way the RIPE community should
operate.</p>
</div>
</blockquote>
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.<br>
<blockquote type="cite"
cite="mid:586B9BC4-D383-4F12-9C74-CF1358538D30@ripe.net">
<div class="markdown">
<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.</p>
</div>
</blockquote>
Yes, have already discussed this and that is the plan. <br>
<blockquote type="cite"
cite="mid:586B9BC4-D383-4F12-9C74-CF1358538D30@ripe.net">
<div class="markdown">
<p dir="auto">Daniel</p>
</div>
</blockquote>
Thanks,<br>
<br>
Amanda <br>
<blockquote type="cite"
cite="mid:586B9BC4-D383-4F12-9C74-CF1358538D30@ripe.net">
<div class="markdown">
<p dir="auto">On 30 Aug 2019, at 13:13, Amanda Gowland wrote:</p>
</div>
<div class="plaintext">
<blockquote>
<p dir="auto">Thanks Hans Petter,<br>
<br>
Let me work the final few comments into the draft, and then
I'll poke some of the others to make sure they're happy for
us to do that.<br>
<br>
Amanda<br>
<br>
On 30/08/2019 11:07, Hans Petter Holen wrote:</p>
<blockquote>
<p dir="auto"> b) We can ask HPH to declare consensus + open
the call for volunteers<br>
<br>
<br>
Let me know when you are ready for me to do the last call
for consensus on the RIPE list.<br>
<br>
Maybe you also want a time-slot in the Community Plenary
on Thursday.<br>
<br>
Hans Petter</p>
</blockquote>
<p dir="auto">_______________________________________________<br>
diversity mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
<a href="https://mailman.ripe.net/"
moz-do-not-send="true">https://mailman.ripe.net/</a></p>
</blockquote>
</div>
<div class="markdown">
</div>
</blockquote>
<p><br>
</p>
</body>
</html>