Launchpad itself

Use-case: setting up teams on behalf of others

Bug #633074 reported by Paul Sladen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I've just found myself setting up a series of teams on behalf of others, eg:

  https://launchpad.net/~dalton-maag

which shows a use-case that Launchpad does not cope with. FOAF is very developer-centric, with an administrator of a team having to also be a member of that team.

Ideally there would way to create and manage teams on behalf of other groups without needing to be a Launchpad-wide instance administrator.

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

I do not understand this issue. I can see you are not a member of the team you setup. You could make someone else the owner. Are you saying you want to be the owner, but do not want to be listed?

affects: launchpad → launchpad-registry
Changed in launchpad-registry:
status: New → Incomplete
Revision history for this message
Paul Sladen (sladen) wrote :

It would be useful to be able to create, setup, initialise and put a populated team into Launchpad without ever having been a member of it (for the minimal necessary duration of that setup).

Being owner is fine, but ideally one should have have to be a /member/ of a newly-created team (however short the duration).

Revision history for this message
Paul Sladen (sladen) wrote :

s/have have to be a member/not have to be a member/

Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: Incomplete → Triaged
importance: Undecided → Low
tags: added: teams
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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