[Cryptography-dev] Upcoming pyOpenSSL release

2016-03-19 Thread Hynek Schlawack
Hi, after a (too) long time, we’re zeroing in to a new pyOpenSSL release. Currently we’re mostly waiting for cryptography 1.3 to drop and to understand this very scary test failure: https://github.com/pyca/pyopenssl/issues/447 *** At that occasion, I would like to raise a few questions and ex

Re: [Cryptography-dev] Upcoming pyOpenSSL release

2016-03-19 Thread Ian Cordasco
On Mar 16, 2016 7:04 AM, "Hynek Schlawack" wrote: > > Hi, > > after a (too) long time, we’re zeroing in to a new pyOpenSSL release. Currently we’re mostly waiting for cryptography 1.3 to drop and to understand this very scary test failure: https://github.com/pyca/pyopenssl/issues/447 > > *** > > A

Re: [Cryptography-dev] Upcoming pyOpenSSL release

2016-03-19 Thread Paul Kehrer
On March 16, 2016 at 11:34:32 AM, Cory Benfield (c...@lukasa.co.uk) wrote: Speaking with my committer hat on…  > On 16 Mar 2016, at 12:04, Hynek Schlawack wrote:  >  > # The communities need to coalesce.  >  > This is both an announcement and a question. I refuse to take care of the > #pyopenss

Re: [Cryptography-dev] Upcoming pyOpenSSL release

2016-03-19 Thread Donald Stufft
> On Mar 16, 2016, at 8:22 PM, Paul Kehrer wrote: > > 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? For pypa.io we just have some high level “here’s what the PyPA is, here’s our communication stuff, here’s some goals an

Re: [Cryptography-dev] Upcoming pyOpenSSL release

2016-03-19 Thread Hynek Schlawack
> 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 ma

Re: [Cryptography-dev] Upcoming pyOpenSSL release

2016-03-19 Thread Cory Benfield
Speaking with my committer hat on… > On 16 Mar 2016, at 12:04, Hynek Schlawack 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 in