Create a new Fedora Account System (FAS) group flock-team with the following attributes:
flock-team
#flock:fedoraproject.org
The flock-team group should have the following accounts as sponsors:
The flock-team group should have the following accounts as members:
The Flock Organizing Team meets today at 14:00 UTC, so it would be convenient if this group were created in advance of that. However, it is a short notice, so it is understandable if not.
A less urgent timeline would be by the end of this week (2026-01-16). I want to explore getting a Forgejo organization created for Flock on the git forge, but I think there should be a proper FAS group for people whom have key roles to play in the planning, organization, and execution of Flock to Fedora each year.
Metadata Update from @zlopez: - Issue assigned to zlopez - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
The group is now created https://accounts.fedoraproject.org/group/flock-team/.
What is missing:
I assume this is the same situation as https://pagure.io/fedora-infrastructure/issue/13044
@zlopez wrote… The group is now created https://accounts.fedoraproject.org/group/flock-team/.
Thanks @zlopez. This FAS group will allow me to set up more dynamic permissioning for various Flock administrative purposes as well as integration with some apps and services, like Pretalx and Pretix. My motivation for requesting this FAS group is because I see this as a larger collaboration/effort than a single project.
@zlopez wrote… matrix channel, I don't have permission to create it
What kind of permission issue do you mean? Is this something with the IdM system or an issue with the Matrix room? I am curious how this part works in the backend.
@zlopez wrote… Should the e-mail you mentioned be mailing list or just alias?
The email listed here should be flock-team [at] fedoraproject [dot] org. It is a single contact address alias, not a mailing list. Is this OK?
@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 assume this is the same situation as https://pagure.io/fedora-infrastructure/issue/13044
@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 assume this is the same situation as https://pagure.io/fedora-infrastructure/issue/13044
What is the right approach for a FAS group that could exist between multiple git forges? Also, for example here, I intended to use the FAS group membership email alias as the new email for the flock-team-{members,sponsors} email addresses. This is an improvement from hard-coding FAS usernames into an infrastructure file (fasjson aliases) that only a few know how to maintain. It makes FAS the tool we use as a gateway for access to various Flock web properties.
flock-team-{members,sponsors}
fasjson
@zlopez wrote… matrix channel, I don't have permission to create it What kind of permission issue do you mean? Is this something with the IdM system or an issue with the Matrix room? I am curious how this part works in the backend.
I don't have access to management part of matrix, so I need somebody who do to create the room.
@zlopez wrote… Should the e-mail you mentioned be mailing list or just alias? The email listed here should be flock-team [at] fedoraproject [dot] org. It is a single contact address alias, not a mailing list. Is this OK?
Never tried to create an alias. I assume it should be alias for all members of the group. Need to check how that could be created.
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/infra/tickets/issues/13036
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)