<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Camille,<br>
Probably first step would be listing CoC Committee members, probably
here: <a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/CodeOfConduct_Committee">http://wiki.osgeo.org/wiki/CodeOfConduct_Committee</a><br>
<br>
One thing I've been pondering since seeing the first few questions
about CoC being discussed is how to "classify" what is considered a
CoC breach. I'm yet to see any hard guidelines as to what is/is not
acceptable. (And this sucks up large amounts of bandwidth on email
lists).<br>
<br>
Looking around for what we can borrow as a standard reference, I
wonder whether we can borrow from film classifications:<br>
<br>
I'm familiar with the Australian classifications (being an
Australian myself), which are well defined:<br>
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Australian_Classification_Board#Film_and_video_game_classifications">https://en.wikipedia.org/wiki/Australian_Classification_Board#Film_and_video_game_classifications</a><br>
<br>
For a conference, we could suggest a classification at a level or G
or PG:<br>
<br>
<i>Parental Guidance (PG) – Not recommended for viewing or playing
by people under 15 without guidance from parents or guardians.
Contains material that young viewers may find confusing or
upsetting. The content is mild in impact.</i><i><br>
</i><i>Violence should be mild and infrequent, and should be
presented in "a stylised or theatrical fashion, or in an
historical context".</i><i><br>
</i><i>Themes should have a "mild sense of menace or threat" and be
"discreet"</i><i><br>
</i><i>Frightening or Intense Scenes should be "mildly frightening"
and have "low intensity"</i><i><br>
</i><i>Crude Humor should be "mild" or "low level"</i><i><br>
</i><i>Sex, nudity and drug use should be mild, infrequent,
"discreetly implied" and "justified by context".</i><i><br>
</i><i>Coarse language should be mild and infrequent, and be
justified by context.</i><br>
<br>
<br>
<div class="moz-cite-prefix">On 26/09/2015 12:26 am, Camille Acey
wrote:<br>
</div>
<blockquote
cite="mid:CAA94jw8E8ruTf2J6V3cqa134uscuzfY0t0rXEwhWZuPGHWfJcA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>So the committee has been established! From where
I stand, here is what is on our plates: <br>
<br>
</div>
- staffing up CoC Voting Committee (responsible for
working with moderators, LOCs, and the board to figure
out how to confidentially handle CoC reports and
violations)<br>
</div>
- draft suggested CoC workflow<br>
</div>
- communicate CoC and suggested workflow to LOCs, forum
moderators, board and membership<br>
</div>
<div><br>
</div>
Is there anything else we should be tackling? <br>
<br>
I also feel like there might be some information gathering
to be done now that FOSS4G has finished. I've already seen
some attendee information and it might be interesting to
find out from Sanghee & co what worked well/could have
been better in terms of creating an inclusive gathering. <br>
<br>
</div>
Thoughts?<br>
</div>
Camille<br>
<div>
<div>
<div><br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
COC-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:COC-discuss@lists.osgeo.org">COC-discuss@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/coc-discuss">http://lists.osgeo.org/cgi-bin/mailman/listinfo/coc-discuss</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P +61 2 9009 5000, W <a class="moz-txt-link-abbreviated" href="http://www.lisasoft.com">www.lisasoft.com</a>, F +61 2 9009 5099</pre>
</body>
</html>