Migrate to Forgejo #104
Labels
No labels
category
budget
category
docs
category
limesurvey
category
meta
category
physical events
category
swag
category
virtual events
charter
ambassadorship
charter
events
charter
recognition
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mindshare/tickets#104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
homerepository from GitLab to theticketsrepository on Forgejo.docsrepository from GitLab to thedocsrepository on Forgejo.Outcome
The Mindshare Committee successfully conducts its March 5, 2026 meeting directly from the new Forgejo platform.
set status to To do
changed start date to February 19, 2026 and changed due date to February 27, 2026
changed the description
changed the description
assigned to @gwmngilfen
Updates:
Outstanding:
@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:
This would make the process of collaborating and working on Fedora Docs significantly easier for vast parts of the Fedora community.
CC: @p.boy
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!