Based on https://docs.fedoraproject.org/en-US/forge-documentation/requesting_new_org_or_team/
We intend to migrate the Fedora Rust SIG related repositories from https://pagure.io/projects/fedora-rust/%2A to forge.fp.o -- that is, some of the projects under the pagure.io/fedora-rust namespace, but not all of them: Some projects for tools and libraries that are not specific to Fedora were already migrated to codeberg.org instead, in accordance with the more limited scope of forge.fp.o compared to pagure.io.
Please let me know if any further information is needed.
Desired Organization Name (Short Name):
rust
Full Name of Oranization:
Fedora Rust SIG
Description of Organization's Purpose:
This organization will host repositories and manage collaboration for the Fedora Rust SIG.
Website URL (Optional):
N/A
Avatar/Logo (Optional):
https://decathorpe.fedorapeople.org/rust-sig/fedora-rust.png
Fedora Accounts Group for Organizing Owners:
forge-rust-owners
This group does not exist yet. I think initializing it with the "active" subset of the sponsors of the rust-sig FAS group makes sense (decathorpe, jistone, ngompa, zbyszek).
rust-sig
decathorpe
jistone
ngompa
zbyszek
Two sponsors (eclipseo and ignatenkobrain) both had all their packages orphaned due to non-responsive maintainer processes years ago and are no longer active SIG members. It doesn't make sense to add them as "Owners" of the new forgejo org. I would remove them as "Sponsors" and members of the existing rust-sig FAS+dist-git group too, but I can't >:-)
eclipseo
ignatenkobrain
Target Organization Name:
Team Name:
members
Description of Team's Purpose (Optional):
Desired Permission Level in Forgejo:
Write
Fedora Accounts Group to Map to Team:
forge-rust-members
This group does not exist yet. I think initializing it with the active members of the rust-sig FAS group makes sense (alebastr, blinxen, dcavalca, decathorpe, jistone, mulhern, music, ngompa, salimma, zbyszek) - that is, all current members of the rust-sig FAS+dist-git group, except for the two inactive SIG members noted above.
alebastr
blinxen
dcavalca
mulhern
music
salimma
Include all repositories:
Yes
Metadata Update from @james: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: forgejo_migration, low-gain, low-trouble, ops
Metadata Update from @james: - Issue assigned to ryanlerch
Fedora Accounts Group for Organizing Owners: forge-rust-owners This group does not exist yet.
This group does not exist yet.
Forgejo - FAS wise, is the structure in such a way that you cannot pick up the sponsor + rust-sig membership as a group that could be used in forgejo? It would seem that this would lead to needing some synchronization of membership between the groups at some level and I am wondering at which level it would be more sustainable to do.
sponsor
I would remove them as "Sponsors" and members of the existing rust-sig FAS+dist-git group too, but I can't >:-)
Is there no fesco or otherwise procedure to do so? It seems pretty straightforward to get consensus from the other sponsors on this.
I agree, it would be easier (and avoid duplication / needing to keep multiple groups in sync) if we could just map the existing rust-sig FAS+dist-git group sponsors to the "owners" team and its members to the "members" team in the new "rust" org. I was under the impression that this was not possible, which is why I followed the template in the documentation for forge org+team requests.
ok
we have recently confimed that we can add a group as the members of a group in Fedora Accounts. However, there is no way to use the sponsors as the owners.
We can set it up this way for you:
forge-rust-owners group -> maps to Owners team on Forge () forge-rust-members group, we add rust-sig group as a member to that Fedora Accounts group. We wont add sponsors to the forge-rust-members group.
Owners
essentially this just means you add members to the rust-sig group, the membership will appear in forge-rust-members, and they will get permissions to the Members team on forge.
Members
Thanks for using Fedora Forge!
I have:
Created the forge-rust-members Fedora Accounts group with the following:
Created the new rust organization on Fedora Forge -- https://forge.fedoraproject.org/rust/
Added 2 teams to the new rust org:
Updated the teams mapping so the Fedora Accounts teams map, and on next login any users in the Fedora Accounts groups will be granted access to the mapped teams in Fedora Forge.
Next Steps 1. Update the settings for your org, including the details like description etc -https://forge.fedoraproject.org/org/rust/settings 2. File a request for an icon with the design team to use as your avatar here on forge: https://gitlab.com/fedora/design/team/requests/-/issues 3. Add a profile page for your organization: https://docs.fedoraproject.org/en-US/forge-documentation/create_org_profile_page/ 4. Migrate from Pagure: https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure_repository/
Metadata Update from @ryanlerch: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks! Looks good to me.
Did you intentionally leave yourself as member of the "owner" group or was that only until I logged in the first time so that the group isn't empty? https://forge.fedoraproject.org/org/rust/teams/owners
yeah -- i was in there (because i created the org) until one of the other owners logged in.
now i have logged in again this morning i have been removed as an owner.