fedora-workstation

#490 Migrate fedora-workstation repo to forge.fedoraproject.org
Closed by tpopela. Opened by catanzaro.

Closed
Reopen Issue

We should migrate this repo to https://forge.fedoraproject.org/workstation. I propose the following four repos:

  • workstation/tickets - for this issue tracker
  • workstation/user-docs - for the user-docs directory in this git repo, source for workstation-docs
  • workstation/wg-docs - for the wg-docs directory in this git repo, source for workstation-working-group docs
  • workstation/mclazy - for mclazy

Migrating the docs might be tricky because they are sources for a live website, so we need to make sure to update the configuration of the website accordingly.

(I have edited my proposal in the first comment.)

Metadata Update from @catanzaro:
- Issue untagged with: meeting-request
- Issue tagged with: meeting

+1

+1 from me

+1

Agreed: Michael will request a migration tomorrow if nobody objects before then.

We can migrate the issue tracker and mclazy immediately. We can migrate user-docs and wg-docs only if we are confident the migration will not break the live websites.

Metadata Update from @catanzaro:
- Issue untagged with: meeting
- Issue tagged with: pending-action

We need to do one of the following before I can request a migration:

  • Create a new FAS group, e.g. fedora-workstation-wg
  • Just use gnome-sig, and make sure all Working Group members are added to gnome-sig

I don't have a strong preference here.

Might as well use gnome-sig.

Just kidding. We already have a FAS group https://pagure.io/group/fedora-workstation which I somehow missed. I'm not sure how, because I am myself a member.

That is not a FAS group. We only have https://accounts.fedoraproject.org/group/gnome-sig/

Ah yeah, I see Pagure groups are different from FAS groups.

According to this documentation it looks like we actually need two different groups: one for owners, and one for members. It seems the owners group is "immutable" which seems outrageous; there's really no way to change who owns the group? I think it'd be much simpler to have only one group, but we do need a way to change members frequently, so the main group definitely cannot be immutable. I guess we really do need two groups.

If we follow the template's suggested naming scheme, we would have: forge-workstation-owners and forge-workstation-members. I'm not sure whether this is actually the best naming, though.

So looks like we have a three-step process here: first we need an infrastructure ticket to request the FAS groups, and then another ticket to request the Forgejo organization, and then we'll have an empty organization so need to figure out how to actually move content into it....

Discovered and closed my previous infrastructure request, https://pagure.io/fedora-infrastructure/issue/12755

Metadata Update from @catanzaro:
- Issue assigned to tpopela

We reopened https://pagure.io/fedora-infrastructure/issue/12755

https://forge.fedoraproject.org/workstation has been created and if you agree I can start with migration of this issue tracker to https://forge.fedoraproject.org/workstation/tickets (which doesn't exist yet) next week.

I agree.

This issue tracker was migrated to https://forge.fedoraproject.org/workstation/tickets and I will shortly close all the opened issues here.

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

Please continue any further discussion there.

Metadata Update from @tpopela:
- Issue status updated to: Closed (was: Open)
Metadata

pending-action

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