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?

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.