fedora-infrastructure

#12558 Forgejo: Owner access to @jflory7 for @CommOps
Closed: Fixed by ryanlerch. Opened by jflory7.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

In the Forgejo staging environment, I would like to receive the owner role for the CommOps team organization:

  • https://forgejo.apps.ocp.stg.fedoraproject.org/CommOps
  • https://forgejo.apps.ocp.stg.fedoraproject.org/jflory7

This will help me facilitate early testing of the Forgejo staging environment for the CommOps team.

When do you need this to be done by? (2025-05-16)

Not urgent, but as soon as possible.

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

This is done using FAS groups.

You are able to name groups whatever you want in forgejo (other than the owners group -- that cannot be changed.)

if you want a contributors group that has write access, all i need is what you want the group to be named, and what FAS group to map it to. Same with the owners group, but I just need to know what FAS group to map that to.

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

We should use the same convention (and document it!) that we decided on for gitlab...

forgejo-fedora-sig-commops-owners

Or, can forgejo auth set different levels of access based on group properties?
Or do we need seperate groups like gitlab?

Did this get sorted out? Do we have groups here and is @jflory7 in them?

EDIT: Whoops. This ticket is for staging, not prod.
Edited by mwinters

This is done. closing

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

low-gain low-trouble ops

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.