too hard to register a project and its team

Bug #435767 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Curtis Hovey

Bug Description

The standard practice on Launchpad is (should be) to create a team per project, not to have it owned by a single person.

This cannot be done during project registration. It must be done after the project is registered. The sharing rules were setup for the registrant, not the intended maintainer.

Launchpad could make it clear that the registrant will be the the maintainer, and allow
the registrant to choose another user or team.

Maintainer
  [me ] (/)
    [ ] I do not want to maintain this Launchpad project

Related branches

Revision history for this message
Curtis Hovey (sinzui) wrote :

This described the last step of Guided-project registration. The feature will resume work in 3.1,10, but I do not think it will be finished until the follow release of 3.1.12

Changed in launchpad-registry:
milestone: none → 3.1.11
status: New → Triaged
importance: Undecided → High
Revision history for this message
Curtis Hovey (sinzui) wrote :

The 3.1 effort is focusing on just-in-time registration. This feature is still valuable and may be in scope, but it will not be worked in the near future.

Changed in launchpad-registry:
importance: High → Low
milestone: 3.1.11 → none
Curtis Hovey (sinzui)
tags: added: projects teams
Curtis Hovey (sinzui)
tags: added: disclosure sharing
Curtis Hovey (sinzui)
description: updated
Curtis Hovey (sinzui)
description: updated
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → Curtis Hovey (sinzui)
status: Triaged → In Progress
tags: added: privacy-transitions
removed: sharing
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
tags: added: qa-ok
removed: qa-needstesting
Ian Booth (wallyworld)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.