[EdLUG] Proposed text for a "Code of Conduct" document

[Thomas Kluyver]

I disagree - if problems ever do come up, then having something a little bit more detailed written down about what's expected will be invaluable. People would disagree on what counts as "being an arse", and it's easy for it to mean "the decision makers' mates are OK". The 'judge, jury and executioner' problem makes it more important to have some written guidelines, not less.

Hopefully we'll never have an issue with anyone's conduct at EdLUG meetings. But it doesn't cost us anything to have a code of conduct there in case it does come up.

Thomas

On Sun, May 26, 2019, at 9:32 PM, Colin Hodge wrote:
> Why?
> 
> Can't we just stick to the "don't be an arse" rule? Codification of this kinda stuff just causes problems.
> 
> The ppl incharge still are judge jurorly and executioner in most small groups any how.
> 
> BB
> Hodge
> 
> On Fri, 24 May 2019, 12:28 Tai Kedzierski, <dch.tai at gmail.com> wrote:
>> Hello everybody,
>> 
>> I've put together a Code of Conduct text, to be added to the website
>> 
>> 
>> +++
>> TL;DR = 
>> 
>> * It is here https://gitlab.com/edlug/edlug.gitlab.io/blob/code-of-conduct/pages/code-of-conduct.md
>> * It should change nothing for us in day-to-day. It's more for future proofing.
>> * Anybody can comment, anybody can propose changes
>> * (technical) Pull Request thread here: https://gitlab.com/edlug/edlug.gitlab.io/merge_requests/1
>> * I'd like to merge this by Sunday evening if no impediments
>> 
>> 
>> +++
>> Details =
>> 
>> You may have been aware that conferences publish a code of conduct for their events, and that now various communities and meetup groups are following suit in turn. The rationale is
>> 
>> 1. It states matter-of-factly that there is indeed behaviour that is considered undesirable by the community organisers
>> 2. It states what specifically is undesirable, rather than leaving it be arbitrarily decided on-the-spot
>> 3. It states what can be expected in case of a breach, rather than arbitrarily enforced haphazardly
>> 4. And of course who to talk to when a problem arises
>> 
>> In our case, we have so far as I know not had any issues (which is great !), however there is always that one-time-in-the-future when it would be good to ensure we have something.
>> 
>> So in principle, nothing should change for us day-to-day, we will simply have a properly defined policy in place that boils down to the basic:
>> 
>> * "no harassment or bullying"
>> * "no sexual, sexist or racist content/behaviour, however light or casual you thought it was."
>> 
>> The text is available to read here: https://gitlab.com/edlug/edlug.gitlab.io/blob/code-of-conduct/pages/code-of-conduct.md
>> 
>> If you are a Git or Gitlab user, please feel free to send a diff or make a pull request against the 'code-of-conduct' branch if you would like to make any direct changes.
>> 
>> The merge request with full changes to the website is here: https://gitlab.com/edlug/edlug.gitlab.io/merge_requests/1
>> 
>> 
>> If you have any concerns with the text, please let me know.
>> 
>> 
>> My aim is to merge this change into the live website some time on Sunday evening, if nobody objects strongly.
>> 
>> 
>> Thanks
>> 
>> Tai
>> 
>> 
>> 
>> 
>> ===
>> Tai Kedzierski
>> Linux Operations and Deployments Engineer
>> 
>> 
>> I use LibreOffice <https://www.libreoffice.org/> , a free, Freedom-respecting replacement for MS Office
>> 
>> *Open Source Free Software is a matter of liberty, not price.*
>> https://www.fsf.org/about/what-is-free-software
>> --
>> EdLUG mailing list
>> EdLUG at lists.edlug.org.uk
>> https://lists.edlug.org.uk/mailman/listinfo/edlug
> -- 
> EdLUG mailing list
> EdLUG at lists.edlug.org.uk
> https://lists.edlug.org.uk/mailman/listinfo/edlug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.edlug.org.uk/pipermail/edlug/attachments/20190527/29b479fe/attachment.html>