fedora-infrastructure

#13044 [FAS] New Group Request: badges-team
Closed: Migrated to Fedora Forge by ryanlerch. Opened by jflory7.

Closed: Migrated to Fedora Forge
Reopen Issue

Describe what you would like us to do:

Create a new Fedora Account System (FAS) group badges-team with the following attributes:

  • Name: Fedora Badges Team
  • URL: https://docs.fedoraproject.org/en-US/badges/
  • Email: sysadmin-badges-members [at] fedoraproject [dot] org
  • Chat: #badges:fedoraproject.org (if this schema is supported, otherwise matrix.to/#/#badges:fedoraproject.org)

The badges-team group should have the following accounts as sponsors:

  • @abompard
  • @chris
  • @ekidney
  • @jflory7
  • @rolandixor
  • @t0xic0der

The badges-team group should have the following accounts as members:

  • @abompard
  • @chris
  • @ekidney
  • @jflory7
  • @nekonya3
  • @rolandixor
  • @smeragoel
  • @t0xic0der

When do you need this to be done by? (2026-01-21)

It will unblock us from creating a new Forgejo organization.

Metadata Update from @t0xic0der:
- Issue assigned to t0xic0der

Metadata Update from @t0xic0der:
- Issue tagged with: forgejo_migration, low-gain, low-trouble

Metadata Update from @t0xic0der:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

The group is now created https://accounts.fedoraproject.org/group/badges-team/.

What is missing:

  • matrix channel, I don't have permission to create it
  • Should the e-mail you mentioned be mailing list or just alias?

Metadata Update from @zlopez:
- Issue untagged with: forgejo_migration

if we are using this as a forge group -- it really needs to follow the naming scheme -- forge-badges-members

we are able to do the inheritied thing, but this is really just a waste to create a new group just to have to do that workaround anyway.

I didn't knew this will be a forgejo managed group, otherwise I wouldn't create it at all.

@zlopez wrote…
The group is now created https://accounts.fedoraproject.org/group/badges-team/.

Thanks @zlopez! This will make it easier to start grouping Fedora Badges people and things together.

@ryanlerch wrote…
if we are using this as a forge group -- it really needs to follow the naming scheme -- forge-badges-members

This is something unclear for me, as of yet. If I want to request a FAS group for a new team, SIG, or Working Group in Fedora, should all FAS group names from this point forward use the forge group naming scheme? What if a group name will be used across multiple git forges, e.g. GitLab?

@ryanlerch wrote…
we are able to do the inheritied thing, but this is really just a waste to create a new group just to have to do that workaround anyway.

@zlopez wrote…
I didn't knew this will be a forgejo managed group, otherwise I wouldn't create it at all.

What is the right approach for a FAS group that could exist between multiple git forges? In the case of Fedora Badges, we are spread across Pagure, GitLab, GitHub, and soon Forgejo. I am wondering what is the right pathway here.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/infra/tickets/issues/13044

Please continue any further discussion there.

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

low-gain low-trouble

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.