<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">On March 16, 2016 at 11:34:32 AM, Cory Benfield (<a href="mailto:cory@lukasa.co.uk">cory@lukasa.co.uk</a>) wrote:</div> <div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div></div><div>Speaking with my committer hat on…<span class="Apple-converted-space"> </span><br><br><br>> On 16 Mar 2016, at 12:04, Hynek Schlawack <hs@ox.cx> wrote:<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> # The communities need to coalesce.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> 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.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> 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?<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>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 <a href="http://botbot.me">botbot.me</a> configured? Is it possible to rename this mailing list?</p><div><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div><br><br>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/.<span class="Apple-converted-space"> </span><br><br>> # Domain?<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> We spoke a few times about it without a real conclusion. I find having a pyca.io like pypa.io would be neat.<span class="Apple-converted-space"> </span><br><br>Sure.<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>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?</p><div><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div><br><br>> # CoC<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> 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?<span class="Apple-converted-space"> </span><br><br>I’m strongly +1 on adopting the contributor covenant, which I already use everywhere else I can.<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>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 (<a href="https://github.com/pyca/cryptography/issues/2161">https://github.com/pyca/cryptography/issues/2161</a>) 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.</p><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div><br><br>Cory<span class="Apple-converted-space"> </span><br>_______________________________________________<span class="Apple-converted-space"> </span><br>Cryptography-dev mailing list<span class="Apple-converted-space"> </span><br>Cryptography-dev@python.org<span class="Apple-converted-space"> </span><br>https://mail.python.org/mailman/listinfo/cryptography-dev<span class="Apple-converted-space"> </span><br></div></div></span></blockquote></div></div></div></body></html>