Re: Permissions vs. Impact mismatch: Orphaning and Retiring

2021-03-18 Thread Fabio Valentini
On Wed, Mar 17, 2021 at 5:33 PM Mattia Verga via devel wrote: > > Il 17/03/21 11:41, Vít Ondruch ha scritto: > > > > I think the problem is that the groups can be removed from package only > > by the main admin. If the main admin is non-responsive, then the whole > > group is kind of hostage.

Re: Permissions vs. Impact mismatch: Orphaning and Retiring

2021-03-17 Thread Mattia Verga via devel
Il 17/03/21 11:41, Vít Ondruch ha scritto: > > I think the problem is that the groups can be removed from package only > by the main admin. If the main admin is non-responsive, then the whole > group is kind of hostage. Every group member should be able to remove > the group from the package IMHO.

Re: Permissions vs. Impact mismatch: Orphaning and Retiring

2021-03-17 Thread Vít Ondruch
Dne 16. 03. 21 v 18:22 Mattia Verga via devel napsal(a): Il 16/03/21 17:50, Fabio Valentini ha scritto: Hi everybody, I've realized that there's a big mismatch between the permissions that are necessary and the immediate impact for orphaning and retiring a package: orphan: - is reversible by

Re: Permissions vs. Impact mismatch: Orphaning and Retiring

2021-03-16 Thread Mattia Verga via devel
Il 16/03/21 17:50, Fabio Valentini ha scritto: > Hi everybody, > > I've realized that there's a big mismatch between the permissions that > are necessary and the immediate impact for orphaning and retiring a > package: > > orphan: > - is reversible by single button press by anybody in "packager"

Permissions vs. Impact mismatch: Orphaning and Retiring

2021-03-16 Thread Fabio Valentini
Hi everybody, I've realized that there's a big mismatch between the permissions that are necessary and the immediate impact for orphaning and retiring a package: orphan: - is reversible by single button press by anybody in "packager" group - has no immediate effect / effect only after 6 weeks of