[Board] Improve Community Behaviour

Bruce Bannerman bruce.bannerman.osgeo at gmail.com
Sun Aug 12 14:47:33 PDT 2018


+1

Nicely done Guido.

Bruce

> On 12 Aug 2018, at 09:12, Cameron Shorter <cameron.shorter at gmail.com> wrote:
> 
> I love Guido's suggestions.
> 
> They are bringing Maria's CoC ideas into a well constructed message which will be appealing to a wide audience.
> 
> I've added a few more comments into Guido's version of the email. 
> 
>> On 12/08/2018 3:54 AM, Guido Stein wrote:
>> Maria,
>> 
>> thanks for putting this together.
>> 
>> 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.
>> 
>> 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.
>> 
>> 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: https://opensource.guide/code-of-conduct/
>> 
>> 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.
>> 
>> I applaud everyone for participating in this conversation and putting in their two cents.
>> 
>> -Guido
>> 
>> 
>>> On Sat, Aug 11, 2018 at 8:25 AM Jeff McKenna <jmckenna at gatewaygeomatics.com> wrote:
>>> Thanks María, edited.  -jeff
>>> 
>>> 
>>> On 2018-08-11 6:46 AM, María Arias de Reyna wrote:
>>> > Drive Document to comment and edit:
>>> > https://docs.google.com/document/d/1RiAwgA8YQTV6QcbufnP6Xdh7fur3H73cjPhwUQ5PU4o/edit?usp=sharing
>>> > 
>>> > Sorry for the delay, I am a bit offline these days.
>>> > 
>>> > On Thu, Aug 9, 2018 at 4:29 PM, Guido Stein <guido at guidostein.com> wrote:
>>> >> Hey folks,
>>> >>
>>> >> would it make sense to put this into a google doc and allow people to add
>>> >> comments and suggest language updates?
>>> >>
>>> >> 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.
>>> >>
>>> >> That said, if this is not a great workflow for others I will be happy to add
>>> >> into the conversation in email form.
>>> >>
>>> >> -guido
>>> >>
>>> >> On Thu, Aug 9, 2018 at 5:47 AM María Arias de Reyna <delawen at gmail.com>
>>> >> wrote:
>>> >>>
>>> >>> Hi Shane,
>>> >>>
>>> >>> Comments inline;
>>> >>>
>>> >>> On Tue, Aug 7, 2018 at 9:44 PM, Shane Curcuru <shane at punderthings.com>
>>> >>> wrote:
>>> >>>> A couple of brief suggestions from a bystander (apologies in advance if
>>> >>>> this is improper as an outsider).
>>> >>>>
>>> >>>> - The critical part to a code of conduct is how specifically you solicit
>>> >>>> reports and show that you're dealing with them.  Ensuring that people
>>> >>>> wishing to make reports feel comfortable about the process, and can be
>>> >>>> secure their issues will be treated completely confidentially if they
>>> >>>> request so.
>>> >>>>
>>> >>>> Thus, thinking through who the specific individuals are who will get the
>>> >>>> incoming CoC issues is important, so that you have a consistent and
>>> >>>> timely response.
>>> >>>
>>> >>> I agree. That's one of the issues I faced when I tried to contact the
>>> >>> CoC: I didn't have clear who was behind it. It shouldn't be personal,
>>> >>> but, at the same time, you need to know who you are sending your
>>> >>> problems to. If not, some people may not feel safe to send anything.
>>> >>>
>>> >>>>
>>> >>>> - Personally, I would *not* include statements about the local event
>>> >>>> funding issues (or whatever those are: I'm not involved in active OSGeo
>>> >>>> work) in your announcement email.  I would guess your focus *with this
>>> >>>> announcement* is on having people be more polite and focused on actual
>>> >>>> issues on the list, rather than dealing with any reporting/finance
>>> >>>> issues.
>>> >>>
>>> >>>
>>> >>> My original idea was to have two separated statements: one for that
>>> >>> issue and the other one more generic.
>>> >>>
>>> >>>>
>>> >>>> Keeping the message simple is important to ensure that any questions
>>> >>>> that do come up in replies are just about appropriate conduct.  Keeping
>>> >>>> the conversation on this thread (in the announcement) and from the
>>> >>>> individuals serving as CoC contact points focused on just the CoC will
>>> >>>> help get the message across.
>>> >>>>
>>> >>>> Does that make sense?
>>> >>>>
>>> >>>> One minor comment: it seems that you've copied the text for the OSGeo
>>> >>>> CoC from other sources.  It would be polite to reference the source you
>>> >>>> copied from at the end of the CoC.  Separately, showing where you copied
>>> >>>> parts from is a good indicator to community participants that you're
>>> >>>> serious about the CoC, since you are re-using widely used terms from
>>> >>>> other communities.
>>> >>>>
>>> >>>> The ASF does this in our CoC:
>>> >>>>
>>> >>>> https://www.apache.org/foundation/policies/conduct#endnotes
>>> >>>
>>> >>>
>>> >>> Makes sense. I wasn't there for the first version, maybe someone who
>>> >>> was on the original group can fill the gaps?
>>> >>>
>>> >>>>
>>> >>>> Hope that helps!
>>> >>>>
>>> >>>>
>>> >>>> - Shane Curcuru
>>> >>>>    Punderthings LLC
>>> >>>>    Also volunteers as Director and community member at the ASF
>>> _______________________________________________
>>> Board mailing list
>>> Board at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/board
>> 
>> 
>> _______________________________________________
>> Board mailing list
>> Board at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/board
> 
> -- 
> Cameron Shorter
> Technology Demystifier
> Open Technologies and Geospatial Consultant
> 
> M +61 (0) 419 142 254
> _______________________________________________
> Board mailing list
> Board at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/board
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20180813/13f03c67/attachment.html>


More information about the Board mailing list