Thanks, Simon! Neither the link [1] in the mail list header or the wiki actually work. > > [1] http://2013.pycon-au.org/register/code_of_conduct >
Yes, I just copypasted the link from the wiki into the mailing list header, without checking that it actually works. It did at the time I put it into the wiki. That said I notice that PyCon has a new subdomain for this year's > conference and the following URL resolves [3] > > [3] http://2015.pycon-au.org/register/code_of_conduct > Thanks, changed it in both places. I'm also writing to the Pycon AU people to ask them for a non-expiring link to the Code of Conduct. > > As a interested observer, I am surprised that after what seems like months > of debate someone Yeah, it's been under a month (barely), and mostly because I'm moving between two continents, and taking forever to answer emails. > has not forked one of the PyCon Templates on GitHub and modified it to the > Melbourne PUG needs. > If you want to commit to marshall that discussion, brook an agreement and maintain the final text, be my guest. MPUG needs organisers, and not just to find talks, move chairs and order pizza. As for myself, these are the reasons I've steered this discussion towards the Pycon AU CoC and no other: - All of the MPUG organisers already attend or even help organise Pycon AU, so I knew that I would not be committing them to something they don't agree to when I suggested we use the Pycon AU Code of Conduct. - It's short. I participate in other projects, some of which have put in a lot of attention and care into their Codes of Conduct. These are also longer documents, and I wanted something that can be easily read. The truth is that a Code of Conduct is more a public statement of intentinos than a legal document. CoCs are always going to leave some leeway for interpretation, but 99% of their effect is in saying publically "we care about this things", and in the good response in case of complaints. The other 1% is in the details of the CoC, and I don't want that 1% to take 90% of the available efffort, as often happens. - I don't want to propose, get agreement to and maintain a Code of Conduct text. It's something I, personally, don't have the time or inclination to do. It's also something of a distraction in a resource-limited project like MPUG. If I had more time to give, I'd organise workshops. And I say this as the person who proposed we should have a CoC, edited the wiki to add it, and asked to be added as a mailing list admin in order to also add it to the mailing list header. Having said that, MPUG could use organisers. Nobody hired me besides asking me to organise pizza one day the person who did it could not attend. The next week, I was mailing people for talks so the programme could be ready a week before the meetup date, and now it looks like I have a position, when I just have a set of tasks I do, when I can do them. Same for the rest of organisers. If anyone in the mailing list wants to appoint themselves as a MPUG organiser, there is an infinite number of positions available, and you mostly choose what you want to work on. We're a friendly bunch! Regards, Javier
_______________________________________________ melbourne-pug mailing list [email protected] https://mail.python.org/mailman/listinfo/melbourne-pug
