#10911 Allow adding fedora-llvm-team to repos
Closed: Fixed 11 months ago by ryanlerch. Opened 2 years ago by nikic.

There is currently a fedora-llvm-team group (https://accounts.fedoraproject.org/group/fedora-llvm-team/), but it is not possible to add this group as a committer to rpm/test repos.

Even ignoring compat rpm repos, the LLVM group maintains 20 rpm and test repos, so permission management has become something of a mess.

I'm not really sure what makes it possible to add a FAS group to a repo -- is is possible to change fedora-llvm-team that "kind" of group?


The group needs to be created in pagure manually otherwise it doesn't work.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

Yeah, so we need to:

  • Add a mailing list that will get all the mails to the group. I guess fedora-llvm-team@lists.fedoraproject.org ? (fedora infra)
    (This must be a private list as it will be CC'ed on security bugs).
  • create a bugzilla.redhat.com account for that group (you)
  • Add the group to pagure (fedora infra)
  • users in group will need to logout and back on to src.fedoraproject.org to get the new group membership. (you, them)
  • group will need to be added to all the packages (you? or fedora infra).

If that all sounds ok, Shall I setup the list and add the group?

If we switch from individual commit access to using the group, how will that impact notifications of activity in the repo?

Oh sorry that I didn't reply for so long here. ;(

Basically it shouldn't affect that at all. Any users who are also admins/commit will get notifications and anyone who is 'watching' the repo will also get them.

The private list is just for bugs from bugzilla.

Does that make sense?

Do you still want to move forward here?

Metadata Update from @ryanlerch:
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

a year ago

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

a year ago
  1. i have created a new private mailing list https://lists.fedoraproject.org/admin/lists/fedora-llvm-team.lists.fedoraproject.org/ with tstellar@fedoraproject.org as the owner. Private here means each member has to be moderated by an owner of the list before getting access, and the list archives are private.

  2. there is now the new group in dist-git owned by tstellar: https://src.fedoraproject.org/group/fedora-llvm-team

  3. the fedora-llvm-team group on FAS now has the new mailing list above listed as the mailing list.

Finally, here is what you have to do @tstellar:

  1. make a bugzilla account for fedora-llvm-team@lists.fedoraproject.org -- this is what pagure expects for the group

  2. get the users in the FAS group to log out and log back in to dist-git pagure to gain access to the new pagure group.

  3. add the group (whatever pagure acl you want it to have) to the packages in distgit pagure.

I have created the bugzilla account just to make sure things work as expected. If you need the password for that account, it can be reset using the BZ reset mechanism and the mailing list.

Going to close this one off as fixed now.

Metadata Update from @ryanlerch:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

11 months ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog