<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>+1</div><div><br></div><div>Nicely done Guido.</div><div><br></div><div>Bruce</div><div><br>On 12 Aug 2018, at 09:12, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>I love Guido's suggestions.</p>
<p>They are bringing Maria's CoC ideas into a well constructed
message which will be appealing to a wide audience.</p>
<p>I've added a few more comments into Guido's version of the email.
<br>
</p>
<br>
<div class="moz-cite-prefix">On 12/08/2018 3:54 AM, Guido Stein
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAGPdrTekwociE1Cpgi38csJDtNSoeH6G0sCrWK4poFWRsxp9WA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">Maria,
<div><br>
</div>
<div>thanks for putting this together.</div>
<div><br>
</div>
<div>I have add some of my comments and an alternate statement
to the document. I created an alternate statement to help
clarify the information being relayed in the document as I saw
it and I also removed the details about events and openness
work.</div>
<div><br>
</div>
<div>I think a clear statement about what is going on, what you
plan to do about it, and a call to action would get bogged
down by a rehash or description of how things work which could
probably go into an actual CoC. I am trying to set the tone
forward thinking and encourage behavior I think is best rather
then try to explain details of operations.</div>
<div><br>
</div>
<div>I think that building mechanisms for reporting CoC
violations and clarity about how things work will be key to
the CoC. At the risk of sharing something you already have a
handle on, I recommend reading this article about CoC: <a href="https://opensource.guide/code-of-conduct/" moz-do-not-send="true">https://opensource.guide/code-of-conduct/</a></div>
<div><br>
</div>
<div>I hope that this is helpful. If my alternative text is too
distracting, feel free to blow it away. I am here to help, not
tell anyone how to be. I would have left comments and edits in
the document without an alternative, but found it difficult to
do so because I had a difference approach.</div>
<div><br>
</div>
<div>I applaud everyone for participating in this conversation
and putting in their two cents.</div>
<div><br>
</div>
<div>-Guido</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sat, Aug 11, 2018 at 8:25 AM Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com" moz-do-not-send="true">jmckenna@gatewaygeomatics.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks
María, edited. -jeff<br>
<br>
<br>
On 2018-08-11 6:46 AM, María Arias de Reyna wrote:<br>
> Drive Document to comment and edit:<br>
> <a href="https://docs.google.com/document/d/1RiAwgA8YQTV6QcbufnP6Xdh7fur3H73cjPhwUQ5PU4o/edit?usp=sharing" rel="noreferrer" target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1RiAwgA8YQTV6QcbufnP6Xdh7fur3H73cjPhwUQ5PU4o/edit?usp=sharing</a><br>
> <br>
> Sorry for the delay, I am a bit offline these days.<br>
> <br>
> On Thu, Aug 9, 2018 at 4:29 PM, Guido Stein <<a href="mailto:guido@guidostein.com" target="_blank" moz-do-not-send="true">guido@guidostein.com</a>> wrote:<br>
>> Hey folks,<br>
>><br>
>> would it make sense to put this into a google doc and
allow people to add<br>
>> comments and suggest language updates?<br>
>><br>
>> Based on the great feedback I am not sure what has
been updated or not so<br>
>> far and would like to add some comments inline.<br>
>><br>
>> That said, if this is not a great workflow for others
I will be happy to add<br>
>> into the conversation in email form.<br>
>><br>
>> -guido<br>
>><br>
>> On Thu, Aug 9, 2018 at 5:47 AM María Arias de Reyna
<<a href="mailto:delawen@gmail.com" target="_blank" moz-do-not-send="true">delawen@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi Shane,<br>
>>><br>
>>> Comments inline;<br>
>>><br>
>>> On Tue, Aug 7, 2018 at 9:44 PM, Shane Curcuru
<<a href="mailto:shane@punderthings.com" target="_blank" moz-do-not-send="true">shane@punderthings.com</a>><br>
>>> wrote:<br>
>>>> A couple of brief suggestions from a
bystander (apologies in advance if<br>
>>>> this is improper as an outsider).<br>
>>>><br>
>>>> - The critical part to a code of conduct is
how specifically you solicit<br>
>>>> reports and show that you're dealing with
them. Ensuring that people<br>
>>>> wishing to make reports feel comfortable
about the process, and can be<br>
>>>> secure their issues will be treated
completely confidentially if they<br>
>>>> request so.<br>
>>>><br>
>>>> Thus, thinking through who the specific
individuals are who will get the<br>
>>>> incoming CoC issues is important, so that you
have a consistent and<br>
>>>> timely response.<br>
>>><br>
>>> I agree. That's one of the issues I faced when I
tried to contact the<br>
>>> CoC: I didn't have clear who was behind it. It
shouldn't be personal,<br>
>>> but, at the same time, you need to know who you
are sending your<br>
>>> problems to. If not, some people may not feel
safe to send anything.<br>
>>><br>
>>>><br>
>>>> - Personally, I would *not* include
statements about the local event<br>
>>>> funding issues (or whatever those are: I'm
not involved in active OSGeo<br>
>>>> work) in your announcement email. I would
guess your focus *with this<br>
>>>> announcement* is on having people be more
polite and focused on actual<br>
>>>> issues on the list, rather than dealing with
any reporting/finance<br>
>>>> issues.<br>
>>><br>
>>><br>
>>> My original idea was to have two separated
statements: one for that<br>
>>> issue and the other one more generic.<br>
>>><br>
>>>><br>
>>>> Keeping the message simple is important to
ensure that any questions<br>
>>>> that do come up in replies are just about
appropriate conduct. Keeping<br>
>>>> the conversation on this thread (in the
announcement) and from the<br>
>>>> individuals serving as CoC contact points
focused on just the CoC will<br>
>>>> help get the message across.<br>
>>>><br>
>>>> Does that make sense?<br>
>>>><br>
>>>> One minor comment: it seems that you've
copied the text for the OSGeo<br>
>>>> CoC from other sources. It would be polite
to reference the source you<br>
>>>> copied from at the end of the CoC.
Separately, showing where you copied<br>
>>>> parts from is a good indicator to community
participants that you're<br>
>>>> serious about the CoC, since you are re-using
widely used terms from<br>
>>>> other communities.<br>
>>>><br>
>>>> The ASF does this in our CoC:<br>
>>>><br>
>>>> <a href="https://www.apache.org/foundation/policies/conduct#endnotes" rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.apache.org/foundation/policies/conduct#endnotes</a><br>
>>><br>
>>><br>
>>> Makes sense. I wasn't there for the first
version, maybe someone who<br>
>>> was on the original group can fill the gaps?<br>
>>><br>
>>>><br>
>>>> Hope that helps!<br>
>>>><br>
>>>><br>
>>>> - Shane Curcuru<br>
>>>> Punderthings LLC<br>
>>>> Also volunteers as Director and community
member at the ASF<br>
_______________________________________________<br>
Board mailing list<br>
<a href="mailto:Board@lists.osgeo.org" target="_blank" moz-do-not-send="true">Board@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/board</a></blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/board">https://lists.osgeo.org/mailman/listinfo/board</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Board mailing list</span><br><span><a href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a></span><br><span><a href="https://lists.osgeo.org/mailman/listinfo/board">https://lists.osgeo.org/mailman/listinfo/board</a></span></div></blockquote></body></html>