<div><span style="color: rgb(160, 160, 168); ">On Wednesday, February 6, 2013 at 8:38 PM, Jesse Noller wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div><br></div><div><br></div><div>On Feb 6, 2013, at 8:04 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div>On Thu, Feb 7, 2013 at 10:43 AM, Jacob Kaplan-Moss <<a href="mailto:jacob@jacobian.org">jacob@jacobian.org</a>> wrote:</div><blockquote type="cite"><div><div>OK I just bought both. If the PSF wants them, I'll transfer them.</div><div>Otherwise I'll sit on 'em for a year and then let 'em expire.</div></div></blockquote><div><br></div><div>Heh, I just did the same thing for "<a href="http://pythonhosted.org">pythonhosted.org</a>". (borrowing the</div><div>name from Fedora, where the main site is all under <a href="http://fedoraproject.org">fedoraproject.org</a>,</div><div>while <a href="http://fedorahosted.org">fedorahosted.org</a> is their project hosting service. We're only</div><div>talking about docs hosting, rather than full project hosting, but it's</div><div>the same general idea).</div><div><br></div><div>Personally, what I would love to see happen is:</div><div><br></div><div>Near term: <a href="http://packages.python.org">packages.python.org</a> becomes a CNAME to another top-level</div><div>site (obviously, my suggestion is "<a href="http://pythonhosted.org">pythonhosted.org</a>", since I just</div><div>bought that for a year in order to be to mention it without worrying</div><div>about whether or not it would remain available)</div><div><br></div><div>Slightly longer term: the <a href="http://pythonhosted.org">pythonhosted.org</a> (or whatever) naming scheme</div><div>includes subdomains (e.g. <a href="http://six.pythonhosted.org">six.pythonhosted.org</a>, in addition to</div><div><a href="http://pythonhosted.org/six">pythonhosted.org/six</a>)</div><div><br></div><div>Even longer term: PyPI offers the option to set up a project's</div><div>pythonhosted subdomain as a ReadTheDocs reference (using the existing</div><div>subdomain delegation feature of RTFD)</div><div><br></div><div>Cheers,</div><div>Nick.</div></div></blockquote><div><br></div><div>Care not which name we choose I do!</div><div><br></div><div>All sound excellent, and nicks plan sounds great.</div><div><br></div><div><br></div><div><br></div><blockquote type="cite"><div><div><br></div><div><br></div><div>-- </div><div>Nick Coghlan | <a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a> | Brisbane, Australia</div></div></blockquote><div>_______________________________________________</div><div>Catalog-SIG mailing list</div><div><a href="mailto:Catalog-SIG@python.org">Catalog-SIG@python.org</a></div><div><a href="http://mail.python.org/mailman/listinfo/catalog-sig">http://mail.python.org/mailman/listinfo/catalog-sig</a></div></div></div></span></blockquote><div>+1 on Nick's plan as well. And echoing the sentiment I don't care what name we use. </div>
<div>
<br>
</div>