fedora-infrastructure

#12409 Create a forge.fedoraproject.org org for the RISC-V SIG
Closed: Fixed by ryanlerch. Opened by abologna.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

Similarly to what was done somewhat recently for the Go SIG in #11795, I would like to ask for

https://gitlab.com/groups/fedora/sigs/risc-v/

to be created for the RISC-V SIG to host SIG-specific repositories.

Our primary use case is relocating the dist-git overlay that currently lives at on a third-party server: now that we have our own Koji instance on Fedora infrastructure, it makes sense to move the dist-git overlay "closer" too. More importantly, this would enable better collaboration via merge requests, which is something that we can't easily do currently.

Note that, while the current dist-git overlay appears very large at 1994 repositories, in reality most of those are obsolete and will simply be left behind. Our tracker indicates that we're going to need just shy of 160 repositories, and with the ongoing upstreaming effort that number is bound to only get smaller over time. The goal is, of course, to eventually merge all RISC-V specific changes back into Fedora and remove the need to have an overlay at all.

In terms of membership I think at least me, @rjones and @davidlt would have to be granted Owner role, with everyone else in the SIG getting Developer role.

Lets confirm that we can allow builds pulling from gitlab.com before we make this group. ;) Otherwise great!

@kevin I think it might be useful to have this area anyway, for non dist-git contents that still need riscv64 patches such as fedora-kiwi-descriptions but yes, it would be significantly less interesting if we can't use it for the dist-git overlay.

How can we validate that the approach could work? Do you want me to mirror some random dist-git repo to my own GitLab account? We still don't have builders attached to the RISC-V Koji instance...

I think, the problem here is firewall configuration, which is IP based. Most likely GitLab has multiple frontends for load balancing, or something like that.

Here are some details: https://docs.gitlab.com/user/gitlab_com/#ip-range

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

So, we didn't really go anywhere here. Should we assume we just want to wait and go with a forgejo space at this point? it should be pretty soon...

We would like to go with a forge.fedoraproject.org org now. ;)

riscv would be good, unless we are requiring -sig for sigs.

CC: @ryanlerch

happy to create the org for you in forge.fp.o!

you will be our first SIG

I am leaning towards starting not using the -sig suffix for the short names, (i.e. riscv)

we can always change the org names in forgejo a lot easier than the FAS group names anyway, and if we start with putting the -sig- in the fas group name, we are pretty much stuck with that, so im thinking

forge-riscv-owners and forge-riscv-members for the FAS groups that will map to the forge teams.

all i really need is a list of sponsors for those groups (the sponsors can then add the members whenever)

happy to create the org for you in forge.fp.o!

you will be our first SIG

I am leaning towards starting not using the -sig suffix for the short names, (i.e. riscv)

Sounds good to me, as a member of the SIG! Thank you :)

we can always change the org names in forgejo a lot easier than the FAS group names anyway, and if we start with putting the -sig- in the fas group name, we are pretty much stuck with that, so im thinking

forge-riscv-owners and forge-riscv-members for the FAS groups that will map to the forge teams.

all i really need is a list of sponsors for those groups (the sponsors can then add the members whenever)

I think as a first cut can you use the members and managers from the existing sysadmin-riscv group?
That may not stay 1:1 over time, but I think it's a good seed for the forgejo groups.

@kevin and @ryanlerch: Any update here? :)

Apoligies for the delay!

I have:

  • Created the forge-riscv-owners Fedora Accounts group with the following:

    • Fedora Accounts Owners: @davidlt & @kevin & @neil
    • Fedora Accounts Members: @davidlt & @kevin & @neil

  • Created the forge-riscv-members group with the following:

    • Fedora Accounts Owners: @davidlt & @kevin & @neil
    • Fedora Accounts Members: @davidlt & @kevin & @neil & @jmontleon

  • Created the new riscv organization on Fedora Forge -- https://forge.fedoraproject.org/riscv/

  • Added 2 teams to the new cloud org:

    • Owners -- https://forge.fedoraproject.org/org/cloud/teams/owners
    • Members -- https://forge.fedoraproject.org/org/cloud/teams/members

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

  • Changed the avatar to the fedora logo.

Next Steps

  1. Update the settings for your org, including the details like description etc -- https://forge.fedoraproject.org/org/cloud/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! Please also add @abologna and @kashyapc myself to the 'members' too.
Metadata
None

low-gain low-trouble ops

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.