On 24 February 2010 03:10, Curtis Hovey <[email protected]> wrote:
> The challenge when designing for Launchpad is to understand the many > communities that use it. Your designs favour the connection between the > person/project and the end-user, but that is not a goal of Launchpad > [2]. The most important communities are Ubuntu contributors, project > developers, opportunistic developers, translators, and bug triagers. > Your designs drop information that the most important communities need. > The primary problem with the person and team pages is that they must act > as both information to other users and as a tool for the person/member. > There are many bugs reported by users regarding the team and person > pages: https://bugs.edge.launchpad.net/launchpad-registry > > For example, your design favours showing who is in the team, but this > information is rarely needed by the communities that use the team. That's a really interesting point: quite true as a criticism of Martin's design, but also perhaps an unrealized potential in Launchpad. There are many things where we'd like different facets of an object (person, product, team, ...) for people inside looking out or outside looking in. As a product maintainer I want a dashboard view of bugs, reviews, deadlines; as a potential user I want to know about the latest release, how to install it, announcements, etc. I don't think you should force people to different pages depending on membership, but perhaps different pages should be somehow available. It might be interesting to get a design language for this. -- Martin <http://launchpad.net/~mbp/> _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
