Mockups

Priorities for the Registry Team

The Registry priorities are defined in the catelog of user stories.

Feature	SP	Released
Notify experts about pending mailing lists	0.5	obsolete
Delete a poll	3	obsolete?
Complete initial Registry API	13	2.1.9
Rename a team w/mailing list	5	2.1.9
Team page should show who is subscribed	3	2.1.10
Making releases from milestones	3	2.1.10
Deleting releases	2	2.1.10
Contact any Launchpad user	2	2.1.11
Moving releases from one series to another	1	2.1.12
Project aliases	5	2.1.12
ShipIt person/account separation	8	2.2.3
Private teams	5	2.2.6
File releases download counters	5	2.2.5
Guided product registration		2.2.9
Branch series	3
Display project teams and people	3
Link PPAs to projects	5
Default mailing list subscription behaviour
Mute subscriptions
Wiki project description
Packaging link population	20
SFTP uploads for releases	20

Community organisations and hierarchy
Let people lurk on mailing lists	2
Personal Subscription Page	20
Private projects	20
Project creation and disclosure	8
Launchpad Vacation Mode	8
Remotely hosted/branded lists	13
Visibility of mailing list traffic to Lp
Nosy mailing list threads
Merging projects
Persistent mailing list archive urls	0.5
Mailing List Feeds	8
IMAP Archive	5
Branded Launchpad	100
Echelon across the Message table
Manage project announcements though the webservice API

Mark

Support: Marc Tardif (testing), Torsten Spindler (Ubuntu Solutions Group)

Community 3 Martin A.

Launchpad: Kiko

OEM: Joey

While the USG didn't provide scores, they did highlight that privacy items were at the top of their lists:
- "Better stealth for projects, people, and teams. I'd like the capability to make projects + teams completely hidden from the general public:
1. Project page is not visible
2. Bugs, branches, PPA, etc not visible
3. If I'm on a 'private' team, my public profile should not say so"
The USG representatives also mentioned that the creation of milestones was very undiscoverable.