Gitlab Access Rights for extension modules

Reason of this issue:

Some people (that shouldn't have them) have owner access rights in extension modules

I think I know what happened and will try to revert it. The goal of this issue is to have some place where it is documented. Then we can point people here in case something goes wrong ;). Thanks to @nils.dreier for pointing out the issue.

What happened:

Two weeks ago @andreas.dedner wrote a mail to the dune-devel mailinglist where he pointed out, that extension and staging modules should have more core developers as owner. I first tried to give access rights to all extension modules to all members of the group core. Unfortunately this lead to the situation that developer of core got owner rights in extension modules. I removed this group access and handed out individual access rights to the core developers.

Removing the group access unfortunately didn't remove the owner access for everyone. I thought it works since the access rights do not show up in the extension group or the individual module but apparently the user still has them. Since the access right doesn't show up correctly you can't simply remove them. Trying around showed that removing people from the core group and adding them again seems to do the trick. This whole issue sounds like a gitlab bug to me and I will report it there ;)

What will I do next

I will remove all non-core-developer from the core group and add them again with the same rights as before. I hope that everyone has the correct access rights afterwards. If not you can comment here or write me a mail.