Infrastructure/fedora-infrastructure

Forgejo: Owner access to @jflory7 for @CommOps #12558

New issue

Open

opened 2025-05-13 20:48:13 +00:00 by jflory7 · 4 comments

jflory7 commented

2025-05-13 20:48:13 +00:00

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:

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.

# 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.

ryanlerch commented

2025-05-14 06:10:43 +00:00

Owner

Metadata Update from @ryanlerch:

Issue assigned to ryanlerch

**Metadata Update from @ryanlerch**: - Issue assigned to ryanlerch

ryanlerch commented

2025-05-14 06:13:51 +00:00

Owner

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.

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.

zlopez commented

2025-05-14 09:34:25 +00:00

Contributor

Metadata Update from @zlopez:

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

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

kevin commented

2025-05-15 21:52:48 +00:00

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?

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?

Sign in to join this conversation.

No labels

Fixed with Explanation

Initiative Worthy

Insufficient data

Will Not or Can Not fix

mini-initiative

Needs investigation

packager_workflow_blocker

🔥 URGENT 🔥

Waiting on Assignee

Waiting on External

Waiting on Reporter

release-monitoring

request-for-resources

websites-general

No milestone

No project

No assignees

4 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#12558

No description provided.