[melbourne-pug] Code of Conduct for MPUG

[Javier Candeira]

Thanks, Tim.

Sufficient to me and to the other organisers. We're all volunteers here. I
suggested the Pycon CoC because we've all (individually, though not
collectively as MPUG) been involved with Pycon, so we've all accepted the
code at one point or another.

TO me the exact wording matters less than the public commitment to a) zero
tolerance for assholery and agression, and b) swift action, up to and
including calling police if the situation escalates, in case stern words do
not suffice.

If we don't use the Pycon CoC, we should take a vote on which CoC to adopt.
My vote is for "any". I really think the difference between those is
negligible for our purpose. I'd rather optimise for getting it done by the
end of the day, and moving on.

J

On Tue, Mar 10, 2015 at 1:02 PM, Tim Richardson <tim at growthpath.com.au>
wrote:

> FYI:
> Linus Torvalds just accepted a patch to the kernel, written apparently by
> around 60 kernel devs. It is extremely minimalist. That is something of a
> triumph.
>
> The people involved have called it Code of Conflict :)
>
> It represents a barely good enough code, but on the other hand it's easy
> to get really detailed. A code should be good enough to allow sufficient
> objectivity when enforcing which is actually cultural. "Sufficient" is up
> to you Javier, I think.
>
>
>
> http://www.linux.com/news/featured-blogs/158-jim-zemlin/815318-on-the-linux-kernels-code-of-conflict
>
> and here is doc patch:
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b0bc65729070b9cbdbb53ff042984a3c545a0e34
>
>
> On Mon, Mar 9, 2015 at 7:51 PM, Javier Candeira <javier at candeira.com>
> wrote:
>
>> Today, reading Kathy Levinson's powerful piece on sexism and
>> whistleblowing [1], I've realised that MPUG doesn't have a Code of
>> Conduct.
>>
>> [1]
>> https://medium.com/@katylevinson/sexism-in-tech-don-t-ask-me-unless-you-re-ready-to-call-somebody-a-whistleblower-e5d545e547b0
>>
>> Yeah, "we've never have had problems in the past" yada yada, but I've
>> never had to file a police report for assault either, that doesn't
>> mean laws on assault aren't needed. So I'd like to add a reference to
>> a Code of Conduct to our wiki page, and to mention that the organisers
>> will personally do our best to enforce it.
>>
>> I like Pycon's CoC [2], but it mentions Pycon and Linux Australia,
>> which have nothing to do with us, except we're a Python User Group and
>>  some of us also attend those... hardly a legal afiliation. I also
>> like the Apache Foundationś CoC [3], though it's a bit too long. What
>> the Pycon one loses in exhaustiveness, it gains in brevity.
>>
>> [2] http://2013.pycon-au.org/register/code_of_conduct
>> [3] https://www.apache.org/foundation/policies/conduct.html
>>
>> I'd definitely much rather not have to write and maintain a CoC
>> myself. Any idea of a clean "white-label" CoC that we can just link
>> to? I know, lazy, but I'd like to get this done tonight.
>>
>> If no suggestion comes for a better solution, I'll add a line to the
>> wiki stating that MPUG meetings are not ran by Pycon or Linux
>> Australia, but its organisers adhere to Pycon's Code of Conduct in
>> matters of civility and inclusivity.
>>
>> Cheers,
>>
>> Javier
>> _______________________________________________
>> melbourne-pug mailing list
>> melbourne-pug at python.org
>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>
>
>
>
> --
>
>
>
> *Tim Richardson, Director*
> GrowthPath, Data-driven profit growth
>
> Mobile: +61 423 091 732
> Office: +61 3 8678 1850
> I tweet useful business & IT tips at growthpath_au
>
> GrowthPath Pty Ltd
> ABN 76 133 733 963
>
>
>
>
> <http://www.growthpath.com.au/>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150310/e1e193e5/attachment-0001.html>