* It is not obvious that "Jonnty" is a team.
- The red icon caused confusion with the "required person" icon in blueprints.
- Most people didn't even notice the different colour.
- The word "Team" next to the name/ID would be easier for people to spot and understand.
! We will use the default team icon of course, but we may want to try to append "team" to the team name?
* The affiliation info is really useful.
* There was confusion over whether the logo indicated a team or a project affiliation.
! This has always been true since teams often reuse project icons :( I think the listing of the project role answers user questions.
The UI implies we know more than the maintain role.
We have a UI ready to implement: http:// people. canonical. com/~curtis/ person- picker/ person- picker- 0.html
This presentation overlaps with bug 798764 and bug 798759.
* It is not obvious that "Jonnty" is a team.
- The red icon caused confusion with the "required person" icon in blueprints.
- Most people didn't even notice the different colour.
- The word "Team" next to the name/ID would be easier for people to spot and understand.
! We will use the default team icon of course, but we may want to try to append "team" to the team name?
* The affiliation info is really useful.
* There was confusion over whether the logo indicated a team or a project affiliation.
! This has always been true since teams often reuse project icons :( I think the listing of the project role answers user questions.
The UI implies we know more than the maintain role.