[Cryptography-dev] Upcoming pyOpenSSL release

Paul Kehrer paul.l.kehrer at gmail.com
Wed Mar 16 20:22:24 EDT 2016


On March 16, 2016 at 11:34:32 AM, Cory Benfield (cory at lukasa.co.uk) wrote:
Speaking with my committer hat on… 


> On 16 Mar 2016, at 12:04, Hynek Schlawack <hs at ox.cx> wrote: 
> 
> # The communities need to coalesce. 
> 
> This is both an announcement and a question. I refuse to take care of the #pyopenssl channel and the pyopenssl-users mailing list. They have to be merged into PyCa. 
> 
> Now the question is: should I just send everyone to cryptography-dev and #cryptography-dev or are we going forth and finally do a #pyca/#pyca-dev channels and/or mailing lists? 
I don't really have an objection to #pyca/#pyca-dev. Assuming Alex is also okay with it would you be willing to do the freenode juju for setting up a channel redirect from #cryptography-dev and getting things like botbot.me configured? Is it possible to rename this mailing list?



I literally didn’t know that the list/channel existed. I’ve used #cryptography-dev for both purposes. I’d be ok with bringing it into /#?cryptography-dev/. 

> # Domain? 
> 
> We spoke a few times about it without a real conclusion. I find having a pyca.io like pypa.io would be neat. 

Sure. 
What do you envision as a landing page? We don't really have any content to live on a site like that right now right?



> # CoC 
> 
> The PSF CoC is crap. Anyone opposed adopting http://contributor-covenant.org which seems to be the general consensus outside “my constitutional rights are violated if I can’t go full Torvalds in code review” circles? 

I’m strongly +1 on adopting the contributor covenant, which I already use everywhere else I can. 
We've talked a bit in the past about a CoC for cryptography since there's a general consensus that the PSF CoC isn't particularly useful. This issue (https://github.com/pyca/cryptography/issues/2161) discussed Open Code of Conduct, but hynek mentioned contributor convenant at the time and it seems like it has gained some mindshare. I have no objection to it being adopted for pyopenssl and potentially cryptography as well.



Cory 
_______________________________________________ 
Cryptography-dev mailing list 
Cryptography-dev at python.org 
https://mail.python.org/mailman/listinfo/cryptography-dev 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20160316/e8870250/attachment.html>


More information about the Cryptography-dev mailing list