"Latest memberships" is less interesting than "Most active teams"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Each person's Launchpad page has a "Latest memberships" section, listing the teams they joined most recently. But how recently they joined is a poor indicator of how interesting the team is.
One way of fixing this would be to measure team activity (perhaps by total karma of team members), and to list the most active instead of the most recent.
Another way of fixing it (which I would prefer) would be to list *all* teams someone is a member of on their person page, instead of on a separate "Show team participation" page.
These solutions may not be mutually exclusive: even if all team participations are listed on a person's page, it may still be useful to sort them by activity (at least by default).
[Originally discovered during user testing.]
description: | updated |
Changed in launchpad-registry: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
I was thinking about this today. Previously, a team to the user was simply a list than in many cases dictated the ACL to a product. We've added team mailing lists and team PPAs so we're at a point now where a team has begun to take on more meaningful role. So it makes sense that we should explore this topic further.
From the suggestions provided, I see inherent drawbacks:
1) total karma of team members doesn't reflect activity actually in that team unless we can tie the team to a product. e.g. Ubuntu LoCo teams are team-only entities not associated with a product or distro. However they do have a mailing list, perhaps a forum, and maybe a team ppa. Some may even have openid enabled websites which they use LP to login to.
2) List all teams on a person page would make for a very long page for some folks. I can't see how a user by default wants to see all the teams (we have those nifty little team icons there anyway) a person belongs to, but I can see they would want to know what teams and products/ projects/ distros they are most active in.
So in principle I agree to the idea. Developing a solution for this though will take a bit of thought.