<div dir="ltr"><div class="gmail_extra">On Wed, Mar 20, 2013 at 11:01 AM, Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, Mar 20, 2013 at 10:39 AM, Marcus Smith <<a href="mailto:qwcode@gmail.com">qwcode@gmail.com</a>> wrote:<br>
> Nick:<br>
><br>
> I'm not sure who owns it yet.<br>
<br>
</div>I ran into Jannis before he left this morning, and he was fairly sure<br>
someone decided it would also be a good idea to register it on<br>
BitBucket after the GitHub group was set up.</blockquote><div><br></div><div style>Yep, and my memory was correct this time, I did indeed register it at the time. I've given the current PyPA team access. Let me know who else needs access. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> If it is one of us, then it would need to be a group vote to use the pypa<br>
> "brand name" like this.<br>
> I'll try to get all the pypa people to come here and register their opinion.<br>
><br>
> here's my personal thoughts:<br>
><br>
> I understand the motivation to reuse our name, but probably less political<br>
> to start a new nifty short name.<br>
<br>
</div>A big part of my role at this point is to take the heat for any<br>
potentially political or otherwise controversial issues (similar to<br>
the way Guido takes the heat for deciding what colour various<br>
bikesheds are going to be painted in the core language design - the<br>
"BDFL-Delegate" title was chosen advisedly).<br>
<br>
While we certainly won't do it if you're not amenable as a group, I'll<br>
be trying my best to persuade you that it's a good idea to turn your<br>
self-chosen name into official reality :)<br>
<div class="im"><br>
> "pypack" or something. "pack" as in a group of people, but also short for<br>
> "packaging"<br>
<br>
</div>The reason I'd like permission to re-use the name is because I want to<br>
be crystal clear that pip *is* the official installer, and virtualenv<br>
is the official way to get venv support in versions prior to 3.3, and<br>
similar for distlib and pylauncher (of course, I also need to make<br>
sure Vinay is OK with that, since those projects currently live under<br>
his personal repo).<br>
<br>
I don't want to ask the pypa to change its name, and I absolutely *do<br>
not* want to have people asking whether or not pypa and some other<br>
group are the ones to listen to in terms of how to do software<br>
distribution "the Python way". I want to have one group that the core<br>
Python docs can reference and say "if you need to distribute Python<br>
software with and for older Python versions, here's where to go for<br>
the latest and greatest tools and advice". If we have two distinct<br>
names on GitHub and PyPI, it becomes that little bit harder to convey<br>
that pylauncher, pip, virtualenv, distlib are backwards compatible<br>
versions of features of Python 3.4+ and officially endorsed by the<br>
core development team.<br>
<div class="im"><br>
> In the spirit of the blog post, here's the 2 doc projects I'd like to see<br>
> exist under this new ~"pypack" group account, and be linked to from the main<br>
> python docs.<br>
><br>
> 1) "Python Packaging User Guide": to replace the unmaintained Hitchhiker's<br>
> guide, or just get permission to copy that in here and get it up to date<br>
> and more complete.<br>
> 2) "Python Packaging Dev Hub": a simpler name to replace<br>
> "python-meta-packaging"<br>
><br>
> give the ~10-15 people that are actively involved in the various packaging<br>
> projects and PEPs admin/merge access to help maintain these docs.<br>
<br>
</div>Yes, that sounds like a good structure.<br>
<div class="im"><br>
> and then announce this on python-announce as real and supported indirectly<br>
> by the PSF.<br>
<br>
</div>It's not PSF backing that matters, it's the python-dev backing to add<br>
links from the 2.7 and 3.3 versions of the docs on <a href="http://python.org" target="_blank">python.org</a> to the<br>
user guide on the new site (and probably from the CPython dev guide to<br>
the packaging developer hub). That's a fair bit easier for me to sell<br>
if it's one group rather than two.<br>
<div class="im"><br>
> people will flock IMO to follow it and contribute with pulls and issues<br>
<br>
</div>Yes, a large part of my goal here is similar to that of the PSF board<br>
when Brett Cannon was funded for a couple of months to write the<br>
initial version of the CPython developer guide.<br>
<br>
Cheers,<br>
<div class="HOEnZb"><div class="h5">Nick.<br>
<br>
--<br>
Nick Coghlan | <a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a> | Brisbane, Australia<br>
_______________________________________________<br>
Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org">Distutils-SIG@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/distutils-sig" target="_blank">http://mail.python.org/mailman/listinfo/distutils-sig</a><br>
</div></div></blockquote></div><br></div></div>