too hard to register a project and its team
Bug #435767 reported by
Martin Pool
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
lp:~sinzui/launchpad/register-project-maintainer
- Ian Booth (community): Approve
-
Diff: 262 lines (+141/-7)4 files modifiedlib/canonical/launchpad/icing/css/forms.css (+3/-0)
lib/lp/registry/browser/product.py (+22/-3)
lib/lp/registry/browser/tests/project-add-views.txt (+2/-0)
lib/lp/registry/browser/tests/test_product.py (+114/-4)
tags: | added: projects teams |
tags: | added: disclosure sharing |
description: | updated |
description: | updated |
Changed in launchpad: | |
assignee: | nobody → Curtis Hovey (sinzui) |
status: | Triaged → In Progress |
tags: |
added: privacy-transitions removed: sharing |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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