Rosetta doesn't let Rosetta Experts promote team members to Admins

Bug #1776 reported by Jordi Mallach on 2005-08-15
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Medium
Unassigned

Bug Description

As a rosetta expert, I'm trying to promote a Czech team member to Admin, but with my current permissions I can't.

I think Experts should be able to change permissions for members of a team even if they don't belong to it.

Christian Reis (kiko) wrote :

That's interesting, because I don't know how we could do this sort of checking. The team itself has no marker indicating it's a language team, and it doesn't seem reasonable to let Rosetta Experts edit the membership of any team in Launchpad. We can structure the language teams hierarchically to fix this, but the creating of language teams will then need to be constrained somewhat. Carlos?

Matthew Paul Thomas (mpt) wrote :

1. Ondrej creates a new "Ubuntu New Czech Translators" team, which consists of Ondrej (admin), ubuntu-l10n-cs (member), and any other new members desired.
2. Jordi changes Ubuntu's Czech translation group from ubuntu-l10n-cs to Ubuntu New Czech Translators.

This is a hack, but it wouldn't be necessary if (as should usually happen) the current admin was available to make Ondrej an admin of the existing team.

Guilherme Salgado (salgado) wrote :

Why not just make the rosetta-admins team the owner of all translation teams? This way, all members of rosetta-admins would be able to do whatever they want with the translation teams and its members.

Matthew Paul Thomas (mpt) wrote :

Because then if you were the owner of a team and I wanted to mess with you, I would create a dummy product, then make your team one of the translation teams for my product's translation group. Suddenly you wouldn't be the owner of your own team any more.

Guilherme Salgado (salgado) wrote :

What I meant is that instead of having some of the translation teams (e.g. ubuntu-l10n-da, ubuntu-l10n-nl) owned by Daf, others (e.g. ubuntu-l10n-bg, ubuntu-l10n-gl) owned by Carlos, and maybe even others (that I'm not aware of) owned by someone else, we should make these teams owned by the rosetta-admins. I suggest this because I think the rosetta experts should be able to manage teams created to group translators.

BTW, I'm not suggesting that this should be done automatically.

Carlos Perelló Marín (carlos) wrote :

I think this suggestion of setting the rosetta-admins the owner of the teams is a good solution.

Changed in rosetta:
status: New → Accepted
Dafydd Harries (daf) wrote :

Perhaps we can get Stuart to do something like:

UPDATE Person SET teamadmin = (SELECT id FROM Team WHERE name = 'rosetta-admins') WHERE name ~ '^ubuntu-l10n-';

How are we going to avoid this problem with teams we create in future? Just change the ownership by hand?

Changed in rosetta:
assignee: nobody → stub
Stuart Bishop (stub) wrote :

I think a simple update like this will break things, as the existing team administrators may no longer be members of their team once I've changed ownership (team admins are implicitly members, not explicitly).

I can write a short script to change the team ownership, adding the old administrator as an administrative member of the team if this is the preferred solution.

Alternatively, I can add rosetta-experts as an admin member of all the translation teams leaving the ownership unchanged.

If adding rosetta-exports as a member will not cause any unwanted side effects, I think this is a better way to go as it allows translation team owners to remove them if they object to this behavior.

For the future, we could create a 'create translation team' link that creates a team with rosetta-admins being the owner or an admin member. However, I wouldn't bother if this is a one off situation for Ubuntu translation teams.

Stuart Bishop (stub) on 2006-04-17
Changed in rosetta:
assignee: stub → nobody
Jeroen T. Vermeulen (jtv) wrote :

Is this still a problem? It appears to be a workaround for a translation team admin being unavailable, which is not specific to translation teams and can be solved by regular admins.

I don't recall seeing many requests for such admin changes, and it's been almost 3 years since the last comment on this bug, so this doesn't look like a priority anymore.

Changed in rosetta:
status: Confirmed → Won't Fix
Jordi Mallach (jordi) wrote :

Well, if in the future Launchpad gets another person to do a "Rosetta Expert"-like role, it would possibly byte again. But for now, it's probably ok to close and ignore it as AFAIK I was the only one in the team.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers