Thanks a lot, Josh. Two notes on why your answer doesn't work for my question:
- I'm trying to avoid forking and maintaining the code myself, as well as gathering the necessary consensus on every word of the language. If someone in the MPUG community cares enough to do it, well, they can, but I won't. My proposal was that we adopt the Pycon AU code of Conduct. The LCA code is a different text. - Why the Pycon AU's CoC and no other? Because 100% of our organisers and most of our presenters already attend Pycon AU, so they already subscribe it. It's also shorter than other options, so less to read and discuss. MPUG is resource-starved, I wanted to avoid spending cycles on the CoC, and just adopt one, announce it, move on. Longer version of this rationale on the linked mailing list thread. I hadn't thought of it until this very moment, but if the pycon-au site is in source control anywhere, and you can give me access, I can just offer a patch via Pull Request where the Pycon AU CoC is served from a stable URL, something like http://pycon-au.org/code_of_conduct/ , and then link there. Would that be acceptable? It's always nice to interact with you, even if it's business talk! Regards, J On Thu, Apr 9, 2015 at 12:27 PM, Joshua Hesketh <[email protected]> wrote: > Hello Javier, > > You can find a copy of Linux Australia's Code of Conduct under a creative > commons license here: > > https://github.com/linuxaustralia/constitution_and_policies/blob/master/code_of_conduct.md > > You're also welcome to fork it for your own use and suggest improvements > via pull requests. > > Cheers, > Josh > > > On 09/04/15 17:22, Javier Candeira wrote: > > Hi, Pycon-AU, > > At MPUG we are using a link to Pycon AU's Code of Conduct as an example > of our own procedure in case of complaints. If needed, here's our mailing > list thread for background: > > First email in thread: > https://mail.python.org/pipermail/melbourne-pug/2015-March/002255.html > Message about link expiry: > https://mail.python.org/pipermail/melbourne-pug/2015-April/002320.html > Last (so far) email in thread: > https://mail.python.org/pipermail/melbourne-pug/2015-April/002321.html > > However, the yearly links (in the 2014 registration, etc) expire. > > Could you please provide a non-dated, non-expiring link we could use > permanently? > > Thanks, > > Javier Candeira, MPUG person. > > > > _______________________________________________ > pyconau-orgs mailing > [email protected]http://lists.linux.org.au/mailman/listinfo/pyconau-orgs > > >
_______________________________________________ melbourne-pug mailing list [email protected] https://mail.python.org/mailman/listinfo/melbourne-pug
