Company account or team

Asked by Univention

I work for Univention GmbH and so far we have used a "shared" account "https://launchpad.net/~univention-dev".
According to our internal documentation is was first registered by my colleague "<email address hidden>", but now our shared mail address "<email address hidden>" is registered with it. I have the credentials for that account and login for that works fine.

But the last address was once used to also register a second account "univention" which seems to no longer exists. But if I try to create a team "univention" it fails with the error, that the name is already taken:
> univention is already in use by another person or team.

To improve our security I'm trying to setup something which would allow individual users to login with their private account and still be able to upload packages to the only PPA we care for: "https://launchpad.net/~univention-dev/+archive/ubuntu/ppa/+packages" if possible that name/URL should not change as our users have this configured for years.

From reading https://answers.launchpad.net/launchpad/+question/210711 I get that I probably need to convert `univention-dev` into a "Team". But before starting on that journey I'd like to verify that this is the correct thing to do.

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jürgen Gmach (jugmac00) said (last edit ):
#1

Thanks for your question.

Converting a person into a team is not a regular thing, but it has been done before:
https://answers.launchpad.net/launchpad/+question/695623

We will discuss this internally tomorrow and get back to you.

Revision history for this message
Jürgen Gmach (jugmac00) said :
#2

Regarding the first part of your inquiry.

The account `univention` was registered 2017 with the mentioned email address, but instead of validating it, it was invalidated, so the account never got active, and now lives in a placeholder state.

We could
- leave it as it is
- merge it into `univention-dev` so `univention` gets free again
- merge it the other way around, but that is something you do not want to do, as you want to keep the PPA URL
- create a complete new account with a different email address and merge it into `univention` so it is available as the latter

That is entirely on you.

Revision history for this message
Jürgen Gmach (jugmac00) said :
#3

Regarding the second part of your inquiry.

As my colleague outlined in https://answers.launchpad.net/launchpad/+question/695623 there are several options to go ahead, of which

- the first one can be done by yourself, ie grant other accounts permission to upload to your PPA
- the second one requires you to create a new team, of which the current `univention-dev` would become a member, and then we do some back and forth renaming at the database level, so at the end the team is named `univention-dev`
- the third way implements an inplace upgrade of a person into a team

As mentioned, the first one could be done right now by you (see the linked answer), the second one needs some careful planning and some test runs on our staging platform on our side, and the third one would be the long term solution, where we need to find time for the implementation, so you could not expect that in the next couple of weeks.

What do you think?

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
Philipp Hahn (pmhahn) said :
#5

Am 07.10.22 um 16:35 schrieb Jürgen Gmach:
> Your question #703398 on Launchpad itself changed:
> https://answers.launchpad.net/launchpad/+question/703398
>
> Status: Open => Needs information
>
> Jürgen Gmach requested more information:
> Regarding the second part of your inquiry.
>
> As my colleague outlined in
> https://answers.launchpad.net/launchpad/+question/695623 there are
> several options to go ahead, of which
>
> - the first one can be done by yourself, ie grant other accounts permission to upload to your PPA
> - the second one requires you to create a new team, of which the current `univention-dev` would become a member, and then we do some back and forth renaming at the database level, so at the end the team is named `univention-dev`
> - the third way implements an inplace upgrade of a person into a team
>
> As mentioned, the first one could be done right now by you (see the
> linked answer), the second one needs some careful planning and some test
> runs on our staging platform on our side, and the third one would be the
> long term solution, where we need to find time for the implementation,
> so you could not expect that in the next couple of weeks.
>
> What do you think?

Sorry for the late reply, but other tasks preempted me.

1. I have created a new account "univention-sec" associated with
"<email address hidden>".

Please merge that account into the never-activated "univention" so that
afterwards
- "univention" is active and associated with "<email address hidden>"
- "univention-sec" is gone

2. I have created a new team "https://launchpad.net/~univention-team"
which "univention-dev" and "univention-sec" (resp. "univention") and me
(hahn) should be members off.

Please rename that team to "univention-dev" as outlined in your 2. above.

At the end:
- "univention-dev" should be the team owning the already existing PPAs
- "univention" should be "taken" and either associated with "packages@"
(preferred) (or "security@").

Thanks.

Philipp Hahn

FYI: The linked answer contains this command:
 > bzr branch lp:ubuntu-archive-tools
The checked out repository contains a single file
THIS_REPOSITORY_HAS_BEEN_MOVED_TO_GIT with this content:
 > https://git.launchpad.net/ubuntu-archive-tools