Add a FAQ on why people not hosting on PyPI should still register to …

…PyPI
pypa · Aug 30, 2015 · 6d05d80 · 6d05d80
1 parent e959219
commit 6d05d80
Showing 1 changed file with 15 additions and 0 deletions.
diff --git a/pep-0470-removal-of-external-hosting.rst b/pep-0470-removal-of-external-hosting.rst
@@ -354,6 +354,21 @@ particular PEP is intended to focus on getting us to a point where the
 capabilities of PyPI are straightforward with an easily understood baseline
 that is similar to existing models such as Linux distribution repositories.
 
+Why should I register on PyPI if I'm running my own repository anyways?
+-----------------------------------------------------------------------
+
+PyPI serves two critical functions for the Python ecosystem. One of those is as
+a central repository for the actual files that get downloaded and installed by
+pip or another package manager and it is this function that this PEP is
+concerned with and that you'd be replacing if you're running your own
+repository. However, it also provides a central registry of who owns what name
+in order to prevent naming collisions, think of it sort of as DNS but for
+Python packages. In addition to making sure that names are handed out in a
+first come, first serve manner it also provides a single place for users to go
+to look search for and discover new projects. So the simple answer is, you
+should still register your project with PyPI to avoid naming collisions and to
+make it so people can still easily discover your project.
+
 
 Rejected Proposals
 ==================