Hosted vs. placeholder projects are unhelpfully indistinct

Bug #253341 reported by Joey Stanford on 2008-07-30
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug 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.

description: updated
Changed in launchpad:
status: New → Confirmed

Random implementation ideas:

The Overview page for a placeholder project could include "(placeholder)" in both its <title> (important for search engine results) and main heading, like the 43 People site's pages for celebrities who don't use 43 People. <http://www.43people.com/profile/view/99326>

Where active projects have a description, placeholder projects could instead have a brief paragraph explaining why the project being in Launchpad at all. (I don't mean "This project was registered on <date> by <person>", but "Launchpad)

Similarly, the Bugs and Code pages for a project that doesn't use Bugs or Code could begin with a one- or two-sentence blurb explaining exactly why Launchpad is tracking bugs separately from the project's bug tracker (bug 35646) or branches separately from the project's VCS. This blurb would likely be a little different for projects that used Launchpad at all, vs. projects that were complete placeholders.

From discussion in bug 253360: Perhaps the project registration form should start out with radio buttons for "(*) a project I maintain" or "( ) a placeholder project that exists elsewhere". If you choose the former, you're shown as maintainer on the resulting project page; if you choose the latter, the maintainer isn't shown at all (bug 251834).

Matthew Paul Thomas (mpt) wrote :

Whoops, incomplete paragraph there. Complete version:

Where active projects have a description, placeholder projects could instead have a brief paragraph explaining why the project is in Launchpad at all. Something like: "<project> is registered in Launchpad to help <distributions that use Launchpad for bug-tracking> track bugs in their <project> packages. It also lets people host branches of the <project> code using Bazaar." Perhaps followed by an invitation for curious upstream contributors to see the list of bugs that are recorded as existing upstream but that are already fixed in a distribution, if there are any; and the list of hosted branches for the project, if there are any.

Curtis Hovey (sinzui) on 2009-01-01
Changed in launchpad-registry:
importance: Undecided → Wishlist
status: Confirmed → Triaged
Curtis Hovey (sinzui) on 2010-01-25
Changed in launchpad-registry:
milestone: none → series-10.05
Curtis Hovey (sinzui) on 2010-03-11
summary: - Active vs. placeholder projects are unhelpfully indistinct
+ Hosted vs. placeholder projects are unhelpfully indistinct
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers