[Cryptography-dev] PyCA domain

[Paul Kehrer]

I agree that we should probably pick up a domain. Like JP, I’m not a huge fan of the .io TLD, although looking around I’m not sure there’s a better option (pyca.ninja, pyca.dating!). py.ca is, of course, squatted already.

A wildcard is no problem though, so we can manage subdomains by not managing them at all.

On June 10, 2014 at 6:36:53 AM, Jean-Paul Calderone (jean-paul at hybridcluster.com) wrote:

On 06/10/2014 05:38 AM, Hynek Schlawack wrote:  
> Hi,  
>  
> since I’m considering to move service_identity into PyCA (comments  
> welcome), I would like to suggest to grab pyca.io (which is currently  
> free) and use it as our own namespace for our RTFD sites. In this  
> case service-identity.pyca.io. I’m pretty sure that’s good for our  
> braaaand (we wanted to push PyCA anyway in the “cryptography” thread)  
> and it would give us some uniformity (same for pyopenssl.pyca.io,  
> bcrypt.pyca.io, potentially cryptography.pyca.io… etc, pp).  
>  

I'm actively disinterested in a .io domain for pyopenssl.  

Jean-Paul  

> Opinions?  
> —h  
> _______________________________________________  
> Cryptography-dev mailing list  
> Cryptography-dev at python.org  
> https://mail.python.org/mailman/listinfo/cryptography-dev  


_______________________________________________  
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/20140610/fa056fa2/attachment-0001.html>