Replace pagure links with forge links #285

Closed
opened 2026-04-01 10:29:19 +00:00 by pbokoc · 1 comment
Owner

Some pages contain links to pagure repositories that have been migrated to Forge, e.g. here in the first sentence. The migrated repos have readmes that point to the new ones, but it would still be better if the links went directly to the new location.

There are currently 15 hits on the keyword pagure.io in the repo.

We might want to wait for everything to be migrated and then do this all at once.

Some pages contain links to pagure repositories that have been migrated to Forge, e.g. [here](https://docs.fedoraproject.org/en-US/council/procedures/tickets/) in the first sentence. The migrated repos have readmes that point to the new ones, but it would still be better if the links went directly to the new location. There are currently 15 hits on the keyword `pagure.io` in the repo. We might want to wait for everything to be migrated and then do this all at once.
jflory7 self-assigned this 2026-07-02 05:09:54 +00:00
Owner

I did an audit of the remaining pagure.io references in the repo. PR #287 (by @mwinters) already updated most links — thank you Michael! The commit message noted two exceptions: CoC (no public Forge repos) and fedora-badges (didn't exist on Forge at the time). Here is the current state of the 8 remaining references.

Ready to fix now (3 links):

Since PR #287 was merged, fedora-badges has been migrated to Forge as apps/badges-assets. Issue numbers track 1:1 between Pagure and Forge.

  • council/.../survey/how-to.adocpagure.io/fedora-badges/issue/800forge.fedoraproject.org/apps/badges-assets/issues/800
  • council/.../partials/attributes.adocpagure.io/fedora-badges/issuesforge.fedoraproject.org/apps/badges-assets/issues

The minimization repo has been archived on Forge as docs-archive/minimization. Issue numbers track 1:1.

  • project/.../objectives/minimization-phase-2.adocpagure.io/minimization/issue/13forge.fedoraproject.org/docs-archive/minimization/issues/13

Needs investigation before changing (1 link):

The fedora-diversity org is now dei on Forge. However, pagure.io/fedora-diversity/issue/98 is a closed historical issue ("Diversity decision making process") that predates the migration — dei/tickets issue numbers start at #17, so #98 doesn't exist there. This page (event-location-policy.adoc) already links to dei/tickets/issues/34 on the next line, so the context is established. I will check whether a redirect or annotation makes sense here, or if the Pagure link should be preserved as an archived reference.

  • council/.../policy/event-location-policy.adocpagure.io/fedora-diversity/issue/98

CoC — will address later (3 links):

The Code of Conduct issue tracker is still hosted on Pagure (pagure.io/CoC). These links are the active reporting path for CoC violations, so they need to be changed carefully once a better workflow is determined for the CoC Committee.

  • project/.../code-of-conduct/pages/index.adoc (2 references to pagure.io/CoC/new_issue)
  • council/.../procedures/tickets.adoc (1 reference to pagure.io/CoC/issues)

No change needed (1 reference):

  • project/.../initiatives.adoc — mentions "sun-setting Pagure" as descriptive context for the Forge initiative. This is accurate text, not a broken link.

Assisted-by: Claude Opus 4.6 (1M context)

I did an audit of the remaining `pagure.io` references in the repo. PR #287 (by @mwinters) already updated most links — thank you Michael! The commit message noted two exceptions: CoC (no public Forge repos) and fedora-badges (didn't exist on Forge at the time). Here is the current state of the 8 remaining references. **Ready to fix now (3 links):** Since PR #287 was merged, `fedora-badges` has been migrated to Forge as [`apps/badges-assets`](https://forge.fedoraproject.org/apps/badges-assets). Issue numbers track 1:1 between Pagure and Forge. - `council/.../survey/how-to.adoc` — `pagure.io/fedora-badges/issue/800` → `forge.fedoraproject.org/apps/badges-assets/issues/800` - `council/.../partials/attributes.adoc` — `pagure.io/fedora-badges/issues` → `forge.fedoraproject.org/apps/badges-assets/issues` The `minimization` repo has been archived on Forge as [`docs-archive/minimization`](https://forge.fedoraproject.org/docs-archive/minimization). Issue numbers track 1:1. - `project/.../objectives/minimization-phase-2.adoc` — `pagure.io/minimization/issue/13` → `forge.fedoraproject.org/docs-archive/minimization/issues/13` **Needs investigation before changing (1 link):** The `fedora-diversity` org is now [`dei`](https://forge.fedoraproject.org/dei) on Forge. However, `pagure.io/fedora-diversity/issue/98` is a closed historical issue ("Diversity decision making process") that predates the migration — `dei/tickets` issue numbers start at #17, so #98 doesn't exist there. This page (`event-location-policy.adoc`) already links to `dei/tickets/issues/34` on the next line, so the context is established. I will check whether a redirect or annotation makes sense here, or if the Pagure link should be preserved as an archived reference. - `council/.../policy/event-location-policy.adoc` — `pagure.io/fedora-diversity/issue/98` **CoC — will address later (3 links):** The Code of Conduct issue tracker is still hosted on Pagure (`pagure.io/CoC`). These links are the **active reporting path** for CoC violations, so they need to be changed carefully once a better workflow is determined for the CoC Committee. - `project/.../code-of-conduct/pages/index.adoc` (2 references to `pagure.io/CoC/new_issue`) - `council/.../procedures/tickets.adoc` (1 reference to `pagure.io/CoC/issues`) **No change needed (1 reference):** - `project/.../initiatives.adoc` — mentions "sun-setting Pagure" as descriptive context for the Forge initiative. This is accurate text, not a broken link. <sub>_Assisted-by: Claude Opus 4.6 (1M context)_</sub>
jflory7 added the due date 2026-07-06 2026-07-02 05:44:29 +00:00
Sign in to join this conversation.
No milestone
No project
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-07-06

Reference
council/docs#285
No description provided.