Add a FAQ entry to PEP 470 on why people should register with PyPI

pep-0470.txt

@@ -355,6 +355,22 @@ 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
 ==================