Re: [Twisted-Python] Proposal -- Code of Conduct

What needs to happen to move this proposal forward? -David On Sun, Jul 19, 2015 at 10:28 PM, Kevin Turner wrote: > I was chatting with some people at the Community Leadership Summit today > about the Recurse Center's social rules > , which reminde

Re: [Twisted-Python] Proposal -- Code of Conduct

I was chatting with some people at the Community Leadership Summit today about the Recurse Center's social rules[1], which reminded me of this thread. What's the status of this proposal? Links: 1. https://www.recurse.com/manual#sec-environment ___ Tw

Re: [Twisted-Python] Proposal -- Code of Conduct

Hi everyone, I'm sorry I haven't responded to the e-mails -- I have had a busy weekend, and my stack was a bit deep for personal projects. I will try to get caught up and see what the right next step is on Monday. Thanks for your understanding, Moshe Z. On Wed, Jun 24, 2015 at 1:27 PM Kevin Turn

Re: [Twisted-Python] Proposal -- Code of Conduct

I'm generally +1 on the idea of having a CoC. I'm content to delegate the details to subcommittee, so maybe I should leave it at that, but I find there's one point I want to reinforce here: On Sun, Jun 21, 2015, at 08:46 AM, Moshe Zadka wrote: > 4. A CoC has several purposes, and "banning people

Re: [Twisted-Python] Proposal -- Code of Conduct

> On Jun 23, 2015, at 11:02 PM, Amber Hawkie Brown > wrote: > > Russ has informed me that it's accessible on > https://github.com/django/djangoproject.com/blob/master/djangoproject/templates/conduct/index.html > >

Re: [Twisted-Python] Proposal -- Code of Conduct

Russ has informed me that it's accessible on https://github.com/django/djangoproject.com/blob/master/djangoproject/templates/conduct/index.html -- so we could potentially fork the repo and make it just that file or so :) Amber "Hawkie" Brown GPG: https://keybase.io/hawkowl > On 24 Jun 2015, at

Re: [Twisted-Python] Proposal -- Code of Conduct

> On 24 Jun 2015, at 10:12, Glyph wrote: > >>> Why isn't this a fork of an existing CoC? > > I agree that this is a problem. Django does not appear to have their CoC in > an easily-forkable format. Perhaps we should contact the Django project and > ask them to rectify that so that we can ma

Re: [Twisted-Python] Proposal -- Code of Conduct

I definitely meant "I don't think that should block adoption". -David On Tue, Jun 23, 2015 at 7:12 PM, Glyph wrote: > > On Jun 23, 2015, at 1:49 PM, David Reid wrote: > > So while it'd be nice for the PSF CoC to be updated such that it was > enforceable I think that should block adoption of a

Re: [Twisted-Python] Proposal -- Code of Conduct

> On Jun 23, 2015, at 1:49 PM, David Reid wrote: > > So while it'd be nice for the PSF CoC to be updated such that it was > enforceable I think that should block adoption of a CoC by the Twisted > Project. I hope that you meant >> I don't think that should block adoption… unless you meant

Re: [Twisted-Python] Proposal -- Code of Conduct

I'm not picky which CoC we use, but the fact that upstream requires approval shouldn't disqualify PSF. Part of my argument is that our contributions benefit a larger community. If PSF needs an enforcement clause, they might be more than willing to adopt the change -- and a bigger community would ce

Re: [Twisted-Python] Proposal -- Code of Conduct

While it should not in theory be difficult to update the PSF CoC, in practice I expect it would be quite difficult for the simple reason that: "This document was approved by the membership of the Python Software Foundation during the vote which concluded on 19 April 2013." Implying that any updat

Re: [Twisted-Python] Proposal -- Code of Conduct

Apologies...editing while on a call. On Tue, Jun 23, 2015 at 12:51 PM, Steve Waterbury wrote: > On 06/23/2015 03:31 PM, Jason J. W. Williams wrote: >> >> On Tue, Jun 23, 2015 at 11:59 AM, David Reid wrote: >>> >>> I'm going to come out strongly against using the PSF CoC. It is woefully >>> inade

Re: [Twisted-Python] Proposal -- Code of Conduct

On 06/23/2015 03:31 PM, Jason J. W. Williams wrote: On Tue, Jun 23, 2015 at 11:59 AM, David Reid wrote: I'm going to come out strongly against using the PSF CoC. It is woefully inadequate, it includes no mechanisms for reporting, and as any PSF member who has been on certain mailing lists knows

Re: [Twisted-Python] Proposal -- Code of Conduct

On Tue, Jun 23, 2015 at 11:59 AM, David Reid wrote: > I'm going to come out strongly against using the PSF CoC. It is woefully > inadequate, it includes no mechanisms for reporting, and as any PSF member > who has been on certain mailing lists knows it is actually completely > unenforceable. Enfo

Re: [Twisted-Python] Proposal -- Code of Conduct

I'm going to come out strongly against using the PSF CoC. It is woefully inadequate, it includes no mechanisms for reporting, and as any PSF member who has been on certain mailing lists knows it is actually completely unenforceable. -David On Tue, Jun 23, 2015 at 11:47 AM, Stephen Thorne wrote:

Re: [Twisted-Python] Proposal -- Code of Conduct

On Tue, Jun 23, 2015 at 11:47 AM, Stephen Thorne wrote: > http://bit.ly/psf-coc I like the PSF code of conduct. It's readable, and covers the bases with an emphasis on civility and respect. -J ___ Twisted-Python mailing list Twisted-Python@twistedmatr

Re: [Twisted-Python] Proposal -- Code of Conduct

I agree with Clayton's points. Please pick a code of conduct that others have used. Avoid the desire to specialize. I like the PSF code of conduct, http://bit.ly/psf-coc but any well regarded CoC will do. Stephen. On Tue, 23 Jun 2015 at 19:23 Clayton Daley wrote: > Not that I'm a heavy contrib

Re: [Twisted-Python] Proposal -- Code of Conduct

Not that I'm a heavy contributor, but: - A CoC is like a ToS in many ways. They rarely get read until there's a problem. - A CoC is like a License in many ways. They should be pretty standard infrastructure. I think both of these facts argue for joining Twisted to an existing CoC. N

Re: [Twisted-Python] Proposal -- Code of Conduct

Hi everyone, I am sure everyone understands that the Twisted community would love more diversity. While it is hard to achieve, it should be easy to remove one of the obvious blockers -- making underrepresented groups feel more welcome. I think, and hope, that our IRC channel, our issue system an

Re: [Twisted-Python] Proposal -- Code of Conduct

Some repilies to all the issues mentioned here: 1. I think we should definitely maintain our own copy. Sorry for it not being a fork, the only non-formatting changes I made are things that referrred to the Django-run events (since we don't run events -- I did replace some of this language with men

Re: [Twisted-Python] Proposal -- Code of Conduct

On Sun, Jun 21, 2015 at 2:30 PM, Amber "Hawkie" Brown wrote: > >> On 21 Jun 2015, at 19:00, Hynek Schlawack wrote: >> I am sure everyone understands that the Twisted community would love more diversity. While it is hard to achieve, it should be easy to remove one of the obvious b

Re: [Twisted-Python] Proposal -- Code of Conduct

> On 21 Jun 2015, at 19:00, Hynek Schlawack wrote: > >>> I am sure everyone understands that the Twisted community would love more >>> diversity. While it is hard to achieve, it should be easy to remove one of >>> the obvious blockers -- making underrepresented groups feel more welcome. >> Tha

Re: [Twisted-Python] Proposal -- Code of Conduct

>> I am sure everyone understands that the Twisted community would love more >> diversity. While it is hard to achieve, it should be easy to remove one of >> the obvious blockers -- making underrepresented groups feel more welcome. > Thanks for taking this on, Moshe. +1 >> My current draft, in

Re: [Twisted-Python] Proposal -- Code of Conduct

> On Jun 20, 2015, at 11:06 AM, Moshe Zadka wrote: > > Hi everyone, > > I am sure everyone understands that the Twisted community would love more > diversity. While it is hard to achieve, it should be easy to remove one of > the obvious blockers -- making underrepresented groups feel more wel

[Twisted-Python] Proposal -- Code of Conduct

Hi everyone, I am sure everyone understands that the Twisted community would love more diversity. While it is hard to achieve, it should be easy to remove one of the obvious blockers -- making underrepresented groups feel more welcome. I think, and hope, that our IRC channel, our issue system and