> On Jun 20, 2015, at 11:06 AM, Moshe Zadka <zadka.mo...@gmail.com> 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 welcome. 

Thanks for taking this on, Moshe.

> I think, and hope, that our IRC channel, our issue system and mailing list 
> have been a friendly, pleasant place. This is an attempt to clarify what we 
> mean by a "friendly, pleasant place". 
> 
> After some discussion on IRC, I volunteered to write up a Code of Conduct for 
> Twisted. It is mostly an adaptation of Django's CoC -- I think Django has a 
> nice track record of commitment to diversity, and, of course, we expect our 
> communities to overlap.

The one thing I'm wondering here is why we have our own CoC.  Particularly...

> My current draft, including instructions on how to build it, is in 
> https://github.com/moshez/twisted-coc <https://github.com/moshez/twisted-coc> 
> . I have intentionally not made the built documents available, in an attempt 
> to avoid someone picking them up before they're approved by us. 

Why isn't this repository either (A) just a simple text file saying "we have 
adopted the Django CoC" or (B) a very small fork of something else?  One of the 
concerns is licensing; if the text comes via Django, Django credits the "Speak 
Up!" project, which is CC-BY, apparently from this repository: 
<https://github.com/jnoller/talk-mentorship>.  Another is... is Twisted really 
distinct enough to need its own CoC?  Just s/Django/Twisted might be good 
enough?  (Since this is not a fork, figuring out if anything else has changed 
is rather tedious, even after having read both ;)).

Thanks again,

-glyph

_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Reply via email to