Activity log for bug #253341

Date Who What changed Old value New value Message
2008-07-30 16:02:01 Joey Stanford bug added bug
2008-07-30 18:55:20 Matthew Paul Thomas description 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. 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.
2008-07-30 18:55:20 Matthew Paul Thomas title Registry improvements Active vs. placeholder projects are unhelpfully indistinct
2008-07-30 18:55:36 Matthew Paul Thomas launchpad: status New Confirmed
2009-01-01 16:36:36 Curtis Hovey launchpad-registry: status Confirmed Triaged
2009-01-01 16:36:36 Curtis Hovey launchpad-registry: importance Undecided Wishlist
2010-01-25 16:38:57 Curtis Hovey launchpad-registry: milestone series-10.05
2010-03-11 16:50:21 Curtis Hovey summary Active vs. placeholder projects are unhelpfully indistinct Hosted vs. placeholder projects are unhelpfully indistinct