Migrate fedora-workstation repo to forge.fedoraproject.org #490

Closed
opened 2025-10-14 14:03:54 +00:00 by catanzaro · 24 comments
Owner

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.

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](https://docs.fedoraproject.org/en-US/workstation-docs/) * workstation/wg-docs - for the wg-docs directory in this git repo, source for [workstation-working-group docs](https://docs.fedoraproject.org/en-US/workstation-working-group/) * workstation/mclazy - for [mclazy](https://github.com/mcatanzaro/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.
Author
Owner

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

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

Metadata Update from @catanzaro:

  • Issue untagged with: meeting-request
  • Issue tagged with: meeting
**Metadata Update from @catanzaro**: - Issue **un**tagged with: meeting-request - Issue tagged with: meeting
Owner

+1

+1
Owner

+1 from me

+1 from me
Owner

+1

+1
Author
Owner

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.

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.
Author
Owner

Metadata Update from @catanzaro:

  • Issue untagged with: meeting
  • Issue tagged with: pending-action
**Metadata Update from @catanzaro**: - Issue **un**tagged with: meeting - Issue tagged with: pending-action
Author
Owner

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.

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

Might as well use gnome-sig.

Might as well use gnome-sig.
Author
Owner

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.

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

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

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

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.

Ah yeah, I see Pagure groups are different from FAS groups. According to [this documentation](https://docs.fedoraproject.org/en-US/forge-documentation/requesting_new_org_or_team/) 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.
Author
Owner

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

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....
Author
Owner

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

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

Metadata Update from @catanzaro:

  • Issue assigned to tpopela
**Metadata Update from @catanzaro**: - Issue assigned to tpopela
Author
Owner
We reopened https://pagure.io/fedora-infrastructure/issue/12755
Owner

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.

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.
Author
Owner

I agree.

I agree.
Owner

This issue tracker was migrated to https://forge.fedoraproject.org/workstation/tickets and I've closed all the opened issues, added comment to all the issues pointing at the relevant issue here in this issue tracker and also set the issue tracker at https://pagure.io/fedora-workstation as read-only.

This issue tracker was migrated to https://forge.fedoraproject.org/workstation/tickets and I've closed all the opened issues, added comment to all the issues pointing at the relevant issue here in this issue tracker and also set the issue tracker at https://pagure.io/fedora-workstation as read-only.
Author
Owner

So now we're halfway done:

  • workstation/tickets - for this issue tracker done
  • workstation/user-docs - for the user-docs directory in this git repo, source for workstation-docs -- to-do
  • workstation/wg-docs - for the wg-docs directory in this git repo, source for workstation-working-group docs -- to-do
  • workstation/mclazy - for mclazy done
So now we're halfway done: * ~~workstation/tickets - for this issue tracker~~ done * workstation/user-docs - for the user-docs directory in this git repo, source for workstation-docs -- to-do * workstation/wg-docs - for the wg-docs directory in this git repo, source for workstation-working-group docs -- to-do * ~~workstation/mclazy - for mclazy~~ done
Owner

Yes, I plan to work on those in the following days.

Yes, I plan to work on those in the following days.
Owner

The background logo extension has been migrated into here.

The background logo extension has been migrated into here.
Owner

@catanzaro wrote in #490 (comment):

  • workstation/user-docs - for the user-docs directory in this git repo, source for workstation-docs -- to-do

  • workstation/wg-docs - for the wg-docs directory in this git repo, source for workstation-working-group docs -- to-do

These were migrated to https://forge.fedoraproject.org/workstation/wg-docs and https://forge.fedoraproject.org/workstation/user-docs and there are opened MRs to clean up the content. I haven't looked into switching the sites over, that's for the next week.

@catanzaro wrote in https://forge.fedoraproject.org/workstation/tickets/issues/490#issuecomment-371531: > * workstation/user-docs - for the user-docs directory in this git repo, source for workstation-docs -- to-do > > * workstation/wg-docs - for the wg-docs directory in this git repo, source for workstation-working-group docs -- to-do These were migrated to https://forge.fedoraproject.org/workstation/wg-docs and https://forge.fedoraproject.org/workstation/user-docs and there are opened MRs to clean up the content. I haven't looked into switching the sites over, that's for the next week.
Owner

I've done workstation/wg-docs#507 and workstation/user-docs#507 to simplify things a little (avoid one extra directory level) and then I've done docs/docs-fp-o#41 to switch to the new locations. This works now (I've tested it with the change, where I was removing myself as the FWWG member). This is finished now.

I've done https://forge.fedoraproject.org/workstation/wg-docs/pulls/507 and https://forge.fedoraproject.org/workstation/user-docs/pulls/507 to simplify things a little (avoid one extra directory level) and then I've done https://forge.fedoraproject.org/docs/docs-fp-o/pulls/41 to switch to the new locations. This works now (I've tested it with the change, where I was removing myself as the FWWG member). This is finished now.
Sign in to join this conversation.
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
workstation/tickets#490
No description provided.