[FOSS4G-Oceania] [FOSS4G-OCEANIA] Code of Conduct Review

[John Bryant]

OK I've updated the permissions on the CoC docs and added Cameron as a
commenter. I will open up more docs in the next few days as I find time.

Cheers
John

On Sat, 30 Mar 2019 at 12:10, John Bryant <johnwbryant at gmail.com> wrote:

> Apologies, I have been remiss and haven't updated permissions since we
> moved to the Team Drive area. We should continue with the
> transparent-by-default policy, in my opinion.
>
> I'm traveling right now, but will aim to fix up the permissions in the
> next 2 days, once I get my feet back on the ground (unless someone else
> beats me to it).
>
> Cheers
> John
>
>
> On Sat., 30 Mar. 2019, 4:29 am Cameron Shorter, <cameron.shorter at gmail.com>
> wrote:
>
>> Seems I don't have access to view these documents. I suggest making the
>> document publicly viewable, and then provided comment access to people who
>> wish to contribute. (I've just requested access).
>>
>> Cheers, Cameron
>> On 29/3/19 8:07 pm, adam steer wrote:
>>
>> Hi Kim,
>>
>> Thanks for coordinating this - could we please extend the review date to
>> Tuesday Wednesday?
>>
>> …in an effort to help people feel like they don’t *need* to rush to do
>> stuff over the weekend.
>>
>> Regards, and thanks
>>
>> Adam
>>
>> On Fri, 29 Mar 2019 at 13:13, Kim Fitter <kimfitter at yahoo.com> wrote:
>>
>>> All,
>>>
>>> One of the actions from our last meeting was to review the code of
>>> conduct for the conference.
>>>
>>> A code of conduct is a public statement that sets the ground rules and
>>> tone for participating in the event.
>>>
>>>
>>> There are two documents in the 2019 Code of Conduct folder:
>>>
>>> *Code of Conduct
>>> <https://drive.google.com/open?id=1TBCnrkrl90EJGVzVUT-J-l2z_zrBKPCWaI_rFm4MCOA>*
>>> - This includes a short and long versions to be published publicly on
>>> the website and/or emails.
>>>
>>> Handling a Code of Conduct Incident - volunteers
>>> <https://drive.google.com/open?id=1SA2B7Tw4lf4Kk_p-JEGPf8uHL1qnkYv1OoqIoM5MYKw>
>>> - This includes a process for handling an incident by a volunteer or
>>> committee member as reported by an attendee.
>>>
>>>
>>>
>>> > Please review both documents and add any comments/ questions. Reviewing
>>> these documents also lets you know the process and the location of this
>>> document in the hopefully unlikely event you ever need this information.
>>>
>>>
>>> > For *committee members,* once you have completed your review, then
>>> please* add your name *in the second document under *Nominated
>>> Responsible Persons* by *Monday 1 April* .
>>>
>>>
>>> If you have any questions then please let me know.
>>>
>>> Have a great weekend!
>>>
>>> Cheers
>>> Kim
>>>
>>>
>>> _______________________________________________
>>> FOSS4G-Oceania mailing list
>>> FOSS4G-Oceania at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>
>>
>>
>> --
>> Dr. Adam Steer
>> http://spatialised.net
>> https://www.researchgate.net/profile/Adam_Steer
>> http://au.linkedin.com/in/adamsteer
>> http://orcid.org/0000-0003-0046-7236
>> +61 427 091 712
>> skype: adam.d.steer
>> tweet: @adamdsteer
>>
>> _______________________________________________
>> FOSS4G-Oceania mailing listFOSS4G-Oceania at lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>
>> --
>> Cameron Shorter
>> Technology Demystifier
>> Open Technologies and Geospatial Consultant
>>
>> M +61 (0) 419 142 254
>>
>> _______________________________________________
>> FOSS4G-Oceania mailing list
>> FOSS4G-Oceania at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/foss4g-oceania/attachments/20190331/80c276a2/attachment.html>