Migrate to Forgejo #104

Closed
opened 2026-02-19 11:20:24 +00:00 by justwheel · 8 comments
justwheel commented 2026-02-19 11:20:24 +00:00 (Migrated from gitlab.com)

Summary

Migrate the Mindshare Committee's issue tracking and documentation repositories from GitLab to the new Fedora Forgejo instance.

Background

As part of the broader Fedora Infrastructure migration, the project is moving away from GitLab to Forgejo. A Forgejo organization already exists for the Mindshare Committee. The Mindshare Committee needs to lead by example, migrate its workflows to the new platform, and provide updates on this progress back to the Council.

Details

  • Migrate the home repository from GitLab to the tickets repository on Forgejo.
  • Migrate the docs repository from GitLab to the docs repository on Forgejo.
  • Update event request issue templates for events to link out to past event reports, if available.
  • @gwmngilfen has volunteered to handle the migration via the web UI.
  • The agreed-upon target deadline for this migration is February 27, 2026.

Outcome

The Mindshare Committee successfully conducts its March 5, 2026 meeting directly from the new Forgejo platform.

# Summary Migrate the Mindshare Committee's issue tracking and documentation repositories from GitLab to the new [Fedora Forgejo](https://forge.fedoraproject.org/mindshare) instance. # Background As part of the broader Fedora Infrastructure migration, the project is moving away from GitLab to Forgejo. A Forgejo organization [already exists](https://forge.fedoraproject.org/mindshare) for the Mindshare Committee. The Mindshare Committee needs to lead by example, migrate its workflows to the new platform, and provide updates on this progress back to the Council. # Details * Migrate the `home` repository from GitLab to the `tickets` repository on Forgejo. * Migrate the `docs` repository from GitLab to the `docs` repository on Forgejo. * Update event request issue templates for events to link out to past event reports, if available. * @gwmngilfen has volunteered to handle the migration via the web UI. * The agreed-upon target deadline for this migration is February 27, 2026. # Outcome The Mindshare Committee successfully conducts its March 5, 2026 meeting directly from the new Forgejo platform.
justwheel commented 2026-02-19 11:20:24 +00:00 (Migrated from gitlab.com)

set status to To do

set status to **To do**
justwheel commented 2026-02-19 11:20:24 +00:00 (Migrated from gitlab.com)

changed start date to February 19, 2026 and changed due date to February 27, 2026

changed start date to February 19, 2026 and changed due date to February 27, 2026
justwheel commented 2026-02-19 12:00:49 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
justwheel commented 2026-02-19 14:48:26 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
justwheel commented 2026-02-19 14:48:32 +00:00 (Migrated from gitlab.com)

assigned to @gwmngilfen

assigned to @gwmngilfen
gwmngilfen commented 2026-02-26 14:54:25 +00:00 (Migrated from gitlab.com)

Updates:

Outstanding:

  • Home migration, as above
  • Docs CI workflow, once we have the runner. @jwwheeler can you confirm the CI in the old docs repo was just a sanity check that Antora can build the site? It doesn't appear to publish to a branch....
Updates: - Home is blocked due to an error with the migration tool. This is tracked at https://forge.fedoraproject.org/forge/forge/issues/374#issuecomment-561052 - Docs is migrated - [core docs site.yml has been updated](https://gitlab.com/fedora/docs/docs-website/docs-fp-o/-/merge_requests/50). - Readme on GitLab has been updated to make the migration clear - GitLab repo has been made read-only - CI runner has been [requested](https://forge.fedoraproject.org/forge/forge/issues/424) Outstanding: - Home migration, as above - Docs CI workflow, once we have the runner. @jwwheeler can you confirm the CI in the old docs repo was just a sanity check that Antora can build the site? It doesn't appear to publish to a branch....
justwheel commented 2026-03-26 01:47:21 +00:00 (Migrated from gitlab.com)

@gwmngilfen Thanks for looking into the docs CI for Mindshare Committee. The CI publishing workflow is not consistently adopted, but there are a few examples of GitLab docs repos that do this… somewhere. :slight_smile:

If this repo is not one of them, you likely need to chat with @darknao and @pbokoc. @LecrisUT might also have some leads on this. It would be a major win to figure out how to get a CI pipeline that can do the following:

  1. Run Antora to build and generate the docs
  2. Use Vale?
  3. Publish the build artifacts as HTML content on a short-term host (e.g., 14 or 21 days)

This would make the process of collaborating and working on Fedora Docs significantly easier for vast parts of the Fedora community.

CC: @p.boy

@gwmngilfen Thanks for looking into the docs CI for Mindshare Committee. The CI publishing workflow is not consistently adopted, but there are a few examples of GitLab docs repos that do this… somewhere. :slight_smile: If this repo is not one of them, you likely need to chat with @darknao and @pbokoc. @LecrisUT might also have some leads on this. It would be a major win to figure out how to get a CI pipeline that can do the following: 1. Run Antora to build and generate the docs 2. [Use Vale?](https://forge.fedoraproject.org/docs/tickets/issues/9) 3. Publish the build artifacts as HTML content on a short-term host (e.g., 14 or 21 days) This would make the process of collaborating and working on Fedora Docs significantly easier for vast parts of the Fedora community. CC: @p.boy
Owner

Discussed in 2026-04-02 Mindshare Committee meeting.


The Mindshare Committee conducted a final review of our migration tasks and verified that all GitLab repositories have been successfully archived and redirected to the new Fedora Forge. As this transition to Forgejo is now fully complete and the old GitLab workflow is deprecated, this ticket is resolved and shall be closed! 🌊🎬

We may need to work with some individual folks with past tickets opened, in case they are unaware about our migration from GitLab to Forgejo (e.g., Ticket #105). We can all do our part to make sure that we help bring the community along with us in this change in process!

_Discussed in [2026-04-02 Mindshare Committee meeting](https://discussion.fedoraproject.org/t/mindshare-committee-meeting-2026-04-02-forgejo-migration-success-event-support-requests/185321)_. --- The Mindshare Committee conducted a final review of our migration tasks and verified that all GitLab repositories have been successfully archived and redirected to the new Fedora Forge. As this transition to Forgejo is now fully complete and the old GitLab workflow is deprecated, this ticket is resolved and shall be closed! 🌊🎬 We may need to work with some individual folks with past tickets opened, in case they are unaware about our migration from GitLab to Forgejo (e.g., Ticket #105). We can all do our part to make sure that we help bring the community along with us in this change in process!
Sign in to join this conversation.
No milestone
No project
No assignees
2 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
mindshare/tickets#104
No description provided.