Comment 298 for bug 59695

Matthieu:

I agree that this is an issue that has probably shed more negative light
on Ubuntu specificly than on any other distribution. The best way that
we can avoid a fiasco such as this is to fix the problems that come up
as soon as possible. The evidence of the length of time it took to
address this bug in a way that makes things safer for the users (even
though it's not a complete solution, yet) indicate there are problems
with communication in the Ubuntu community, but there are people pushing
to fix that in one way or another -- through launchpad changes, etc..
Hopefully communication will improve, and this sort of thing won't be
prone to happening again.

Andrea Corbellini explained to me the particular way this bug went awry
-- it was misassigned, then its priority was changed, so it slipped off
into bug-purgatory for quite a while. However, that shouldn't really be
possible, when there are so many trying to get action on it.

There are quite a few people trying to get Launchpad open-sourced, so
that work on it moves faster -- but Canonical needs to implement its
business plan, else there are a great many other things that will go
awry with Ubuntu -- and keeping Launchpad closed for now is a part of
that plan. But, it is also a part of the plan to open-source it. In
the meantime, we can file bugs (general or specific) on launchpad itself
that try to address communications issues in Launchpad, finding examples
of bugs that have run into particular issues, and filing reports on
those issues.