Adding some explanatory text there would be a good thing. But I think it would probably not have helped the specific case of the "prelink" product.
My guess is that the user thought that "launchpad == ubuntu bug tracker" (not "ubuntu uses launchpad to track bugs", but "launchpad is only the bug tracker for ubuntu").
So he did a search for "prelink" in the front page, had no hit and was suggested to do something (actually, create a product, but I do not think the user read it), and obedently filed a bug in the form.
This sort of confusion is going to happen again. I think preventing such oddities in the future involves:
* Making the front page search a global search, or maybe just a bug search. Submitting ubuntu bugs is probably the dominant use case for new users by far.
* Not suggesting creating a product if the front page search gives no hit. That should only be suggested by the product search on <https://launchpad.net/products>.
Adding some explanatory text there would be a good thing. But I think it would probably not have helped the specific case of the "prelink" product.
My guess is that the user thought that "launchpad == ubuntu bug tracker" (not "ubuntu uses launchpad to track bugs", but "launchpad is only the bug tracker for ubuntu").
So he did a search for "prelink" in the front page, had no hit and was suggested to do something (actually, create a product, but I do not think the user read it), and obedently filed a bug in the form.
This sort of confusion is going to happen again. I think preventing such oddities in the future involves:
* Making the front page search a global search, or maybe just a bug search. Submitting ubuntu bugs is probably the dominant use case for new users by far. /launchpad. net/products>.
* Not suggesting creating a product if the front page search gives no hit. That should only be suggested by the product search on <https:/
Remember, users do not read _anything_: www.joelonsoftw are.com/ uibook/ chapters/ fog0000000062. html
http://