Comment 0 for bug 253341

Taken from a discussion with MPT:

The Launchpad collaboration model relies on the existence of placeholder
projects. But as far as we know, we have never designed how placeholder
projects should be presented or claimed, and we have not well considered
handling placeholder projects when new features (such as Answers) have
been added to Launchpad.

We will know this problem is fixed when:

* <https://launchpad.net/projects>, and its search results, clearly
   distinguish between projects that use Launchpad and projects that
   don't.

* A test shows that most people (aim for over 75%) can tell,
   within 5 seconds of arriving at any of a project's Overview pages
   (e.g. <https://edge.launchpad.net/amarok/stable/1.4.8>), whether
   that project uses Launchpad.
   <http://www.uie.com/articles/five_second_test/>

* A test shows that most people can tell, within 5 seconds of arriving
   at a project's Bugs page (e.g.
   <https://bugs.launchpad.net/gnome-applets>), whether the project
   uses Launchpad for bug tracking.

* A survey of maintainers of projects that don't use Launchpad shows
   that a large majority of them are happy with the way their project is represented in Launchpad.

* <https://launchpad.net/firefox> does not claim that Firefox uses
   Launchpad for either code hosting or translations.

* <https://blueprints.launchpad.net/debian/+addspec> does not let you
   register a blueprint.