<div dir="ltr">Hey folks, <div><br></div><div>would it make sense to put this into a google doc and allow people to add comments and suggest language updates?</div><div><br></div><div>Based on the great feedback I am not sure what has been updated or not so far and would like to add some comments inline.</div><div><br></div><div>That said, if this is not a great workflow for others I will be happy to add into the conversation in email form.</div><div><br></div><div>-guido</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Aug 9, 2018 at 5:47 AM María Arias de Reyna <<a href="mailto:delawen@gmail.com">delawen@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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">shane@punderthings.com</a>> 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 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">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">Board@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/board</a><br>
_______________________________________________<br>
Board mailing list<br>
<a href="mailto:Board@lists.osgeo.org" target="_blank">Board@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/board</a></blockquote></div>