#620 Notification e-mail/ticket should explain how a user can remove himself from the group
Opened by ppisar. Modified

Some people reply to their tickets that they are fine with the removal
https://pagure.io/find-inactive-packagers/issue/576#comment-811428.

Users can actually remove themselves by visiting https://accounts.fedoraproject.org/ and activating "Leave" button at the member list of the packager group.

I proposed enhancing the notifications with a self service howto. That could decrease amount of open tickets.


What happens to packages maintained by the user when they push the "leave" button from the packager group? Are they automatically orphaned? Is the user also removed from being co-maintainer / collaborator to packages?

And we need to find out what happens if a user belongs to a group that has commit access to some packages, but they are removed from the packagers group?...

Metadata Update from @bcotton:
- Issue assigned to bcotton
- Issue tagged with: feature

Those are good questions. I'll find out. Although I'm not sure it will make much of a practical difference, since people won't be able to close the tickets anyway (as they aren't the person who opened them).

I guess the user looses a write access to various places of Fedora project, e.g. pushes to dist-git. But the packages, Bodhi updates etc. will still be assigned to him. Ideally accounts system should emit a FMN message that the user left the group and Pagure should orphan / remove the user from the package. Though I doubt this business logic so implemented.

The tickets could be closed by the regular script which creates the tickets.

I guess the user looses a write access to various places of Fedora project, e.g. pushes to dist-git. But the packages, Bodhi updates etc. will still be assigned to him. Ideally accounts system should emit a FMN message that the user left the group and Pagure should orphan / remove the user from the package. Though I doubt this business logic so implemented.

The tickets could be closed by the regular script which creates the tickets.

About Bodhi permissions, I've just checked: the update creation is only possible to users within the packager group, so even if the user is assigned to a group which has commit privileges, they will not have permissions to push or edit updates.

Metadata