forge/forge
9
0
Fork 1
Code Issues 59 Pull requests Projects 3 Wiki Activity Actions

Migrate Weblate translations/internationalization tooling from Pagure/GitLab/GitHub to Forgejo #110

New issue
Open
opened 2025-07-11 15:24:34 +00:00 by jwheel · 7 comments
jwheel commented 2025-07-11 15:24:34 +00:00 (Migrated from codeberg.org)
Copy link

Summary

Create an automated migration script to update Weblate configuration for repo-level localization and translations from existing git forges in use (e.g. Pagure, GitLab, GitHub) to Forgejo.

Background

Fedora uses Weblate as our tool to handle localization and translations. Weblate provides a user-friendly interface for translators to translate various strings across the project. These strings are used in software packages as well as Fedora public websites like Fedora Docs, fedoraproject.org, and more. Due to the Free Software approach taken by Weblate, we also have a special community relationship with the Weblate team, and they have accommodated us significantly to make Weblate a useful tool for the Fedora community.

I was speaking with Jean-Baptiste Holcroft, the main lead on the Fedora Weblate project, about what work would be required to move our repos from other git forges to Forgejo. It will require a large amount of menial work to modify each project configuration to get it working, give write access to the Forgejo repo/server, etc.

If this work cannot be automated somehow, it could threaten the health of our localization efforts, and our ability to deliver translated strings by our localization contributors for the next release of Fedora Linux in a Forgejo-first world.

Details

A research activity needs to be conducted to review the existing configuration, understand what APIs are available in Weblate, and what interfaces could be used to create automation that assists with the Weblate config migration. This is an area where we need help of someone experienced with Forgejo, our existing use of other git forges, and willing to learn more about how Weblate in Fedora works.

Once the research activity is completed, it will then be easier to make a proposal on how to simplify the migration of Weblate configuration data to avoid outages on our localization/internationalization tooling, and ensure the hard work of our global translator community is recognized and shipped in each release of Fedora, whether that is for software packaged in Fedora Linux or official Fedora documentation about the latest release.

Outcome

Proactive planning on how to handle Weblate migration ensures an easier migration of our localization tooling when we start to move the center of gravity for Fedora git forges from other forges to Forgejo.

# Summary Create an automated migration script to update Weblate configuration for repo-level localization and translations from existing git forges in use (e.g. Pagure, GitLab, GitHub) to Forgejo. # Background Fedora uses [Weblate](https://weblate.org/en/) as our tool to handle localization and translations. Weblate provides a user-friendly interface for translators to translate various strings across the project. These strings are used in software packages as well as Fedora public websites like Fedora Docs, fedoraproject.org, and more. Due to the Free Software approach taken by Weblate, we also have a special community relationship with the Weblate team, and they have accommodated us significantly to make Weblate a useful tool for the Fedora community. I was speaking with [Jean-Baptiste Holcroft](https://accounts.fedoraproject.org/user/jibecfed/), the main lead on the Fedora Weblate project, about what work would be required to move our repos from other git forges to Forgejo. It will require a large amount of menial work to modify each project configuration to get it working, give write access to the Forgejo repo/server, etc. If this work cannot be automated somehow, it could threaten the health of our localization efforts, and our ability to deliver translated strings by our localization contributors for the next release of Fedora Linux in a Forgejo-first world. # Details A research activity needs to be conducted to review the existing configuration, understand what APIs are available in Weblate, and what interfaces could be used to create automation that assists with the Weblate config migration. This is an area where we need help of someone experienced with Forgejo, our existing use of other git forges, and willing to learn more about how Weblate in Fedora works. Once the research activity is completed, it will then be easier to make a proposal on how to simplify the migration of Weblate configuration data to avoid outages on our localization/internationalization tooling, and ensure the hard work of our global translator community is recognized and shipped in each release of Fedora, whether that is for software packaged in Fedora Linux or official Fedora documentation about the latest release. # Outcome Proactive planning on how to handle Weblate migration ensures an easier migration of our localization tooling when we start to move the center of gravity for Fedora git forges from other forges to Forgejo.
ryanlerch added this to the Backlog project 2025-11-03 04:12:21 +00:00
ryanlerch modified the project from Backlog to Sprint 12 2025-11-04 01:08:13 +00:00
t0xic0der commented 2025-11-17 03:29:58 +00:00
Member
Copy link

I want to note that increase of assigned points under this ticket, given the "wide as an ocean but deep as a puddle" scope of the request here. I have connected with @jibecfd in the Fedora Localization chat and have begun planning on this work.

I want to note that increase of assigned points under this ticket, given the "wide as an ocean but deep as a puddle" scope of the request here. I have connected with @jibecfd in the Fedora Localization chat and have begun planning on this work.
t0xic0der commented 2025-12-15 04:04:29 +00:00
Member
Copy link

Here's some information from their Wiki page, courtesy of @jibecfd.

https://fedoraproject.org/wiki/L10N/Forgejo

Please note that this document is awaiting approvals from the likes of @peartown, @raphael, etc., and only then would the work be actionable here.

Here's some information from their Wiki page, courtesy of @jibecfd. https://fedoraproject.org/wiki/L10N/Forgejo Please note that this document is awaiting approvals from the likes of @peartown, @raphael, etc., and only then would the work be actionable here.
jibecfed commented 2026-01-08 17:06:23 +00:00
Copy link

content of https://fedoraproject.org/wiki/L10N/Forgejo looks good to me

content of https://fedoraproject.org/wiki/L10N/Forgejo looks good to me
t0xic0der commented 2026-01-12 07:01:32 +00:00
Member
Copy link

I have been added to the sysadmin-forge group by @ryanlerch. I will take the documentation https://docs.fedoraproject.org/en-US/forge-documentation/creating_a_new_org/ for a spin to see if this is exhaustive enough to satiate this usecase.

I have been added to the `sysadmin-forge` group by @ryanlerch. I will take the documentation https://docs.fedoraproject.org/en-US/forge-documentation/creating_a_new_org/ for a spin to see if this is exhaustive enough to satiate this usecase.
t0xic0der commented 2026-01-12 09:27:41 +00:00
Member
Copy link

We are settling for the names forge-localization-owners (instead of the proposed fedora-l10n-admin name) for the administrators and forge-localization-commit (instead of the proposed fedora-l10n-commit name) for the committers. The requested members will be added as well. We have not added members from the similarly functioning l10n-admin (has 0 sponsors and 0 members) and l10n-commits (has 0 sponsors and 46 members) groups, as we are making a minimal migration. The remaining folks can be added manually by the folks belonging to the forge-localization-owners group at a later point in time. For more information on why the naming scheme was changed, please see this documentation.

We are settling for the names `forge-localization-owners` (instead of the proposed `fedora-l10n-admin` name) for the administrators and `forge-localization-commit` (instead of the proposed `fedora-l10n-commit` name) for the committers. The requested members will be added as well. We have not added members from the similarly functioning [`l10n-admin`](https://accounts.fedoraproject.org/group/l10n-admin/) (has 0 sponsors and 0 members) and `l10n-commits` (has 0 sponsors and 46 members) groups, as we are making a minimal migration. The remaining folks can be added manually by the folks belonging to the `forge-localization-owners` group at a later point in time. For more information on why the naming scheme was changed, please see this [documentation](https://docs.fedoraproject.org/en-US/forge-documentation/fas_group_naming_standards/).
t0xic0der commented 2026-01-12 10:02:07 +00:00
Member
Copy link

For the secondary group requests, we are settling for the name forge-localization-docs (instead of the proposed fedora-docs-l10n name) with the proposed user added. As I do not have access to your Pagure namespace, I cannot stop the automations and/or make the required changes to be done before the migration goes through. I will have to defer to you folks to perform the migration from the source namespace to the destination one - please see this documentation.

For the secondary group requests, we are settling for the name `forge-localization-docs` (instead of the proposed `fedora-docs-l10n` name) with the proposed user added. As I do not have access to your Pagure namespace, I cannot stop the automations and/or make the required changes to be done before the migration goes through. I will have to defer to you folks to perform the migration from the source namespace to the destination one - please see this [documentation](https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure/).
t0xic0der commented 2026-01-12 10:32:04 +00:00
Member
Copy link

The namespace has been created here and three different teams requested can be found here, here and here respectively. They will be mapped against the Fedora Accounts group that can be found here, here and here, respectively, once this pull request gets merged and the playbook is executed. @ryanlerch, could you please review this pull request when you find some time? I will notify here again once the execution is through, and then the actual repository migrations can commence.

The namespace has been created [here](https://forge.fedoraproject.org/localization) and three different teams requested can be found [here](https://forge.fedoraproject.org/org/localization/teams/owners), [here](https://forge.fedoraproject.org/org/localization/teams/commit) and [here](https://forge.fedoraproject.org/org/localization/teams/docs) respectively. They will be mapped against the Fedora Accounts group that can be found [here](https://accounts.fedoraproject.org/group/forge-localization-owners/), [here](https://accounts.fedoraproject.org/group/forge-localization-commit/) and [here](https://accounts.fedoraproject.org/group/forge-localization-docs/), respectively, once this [pull request](https://pagure.io/fedora-infra/ansible/pull-request/3034) gets merged and the playbook is executed. @ryanlerch, could you please review this pull request when you find some time? I will notify here again once the execution is through, and then the actual repository migrations can commence.
t0xic0der modified the project from Sprint 12 to (deleted) 2026-01-12 10:57:23 +00:00
ryanlerch modified the project from (deleted) to Sprint 12 2026-01-12 11:05:04 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and could be worked on immediately when capacity is available.

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
Sprint Status
Review
This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic

  
Work Item
Spike

  
Work Item
Task

  
Work Item
User Story

  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Backlog Status
Needs Review
Backlog Status
Ready
Chore
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 12
Assignees
Clear assignees
No assignees
t0xic0der
3 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
forge/forge#110
No description provided.