forge/forge
9
6
Fork 3
Code Issues 77 Pull requests 1 Projects 2 Wiki Activity Actions

rename "translations" into "localization-docs" #400

New issue
Closed
opened 2026-02-10 22:50:13 +00:00 by jibecfed · 5 comments
jibecfed commented 2026-02-10 22:50:13 +00:00
Copy link

As part of L10N group migration to Forgejo, we requested two groups, one for localization project, one for the Antora Documentation system: https://fedoraproject.org/wiki/L10N/Forgejo

First request were fulfilled as #110
The second request, the Antora documentation system were handled in #354

The issues:

  • the name we requested were changed without discussion with the L10n community
  • Chosen name sounds "logical" since it will contain translations, but people not experienced in Fedora localization internals (population of the world minus... 3 ?), there is no way to understand "translations" is not related to everything related to "translations in Fedora Linux" but a technical space dedicated to the really specific internationalization of the Fedora documentation system...
  • I can't reopen ticket on forge repository, any reason for that?

This is even more confusing since "localization" is already referring to "everything related to translation".

Please change the name to something that is related to fedora docs translations and that can't be confused with localization group.
I am sorry this goes in conflict with the perfect naming we all want on new tooling.

The automation defined for fedora docs internationalization is there: https://pagure.io/fedora-docs/translations-scripts/
The fact all the internationalization is defined outside of Antora and push all the translations in the same place is more of a technical constraints than a strong design choice.

Note: Antora have no internationalization support: https://gitlab.com/antora/antora/-/issues/208

As part of L10N group migration to Forgejo, we requested two groups, one for localization project, one for the Antora Documentation system: https://fedoraproject.org/wiki/L10N/Forgejo First request were fulfilled as https://forge.fedoraproject.org/forge/forge/issues/110 The second request, the Antora documentation system were handled in https://forge.fedoraproject.org/forge/forge/issues/354 The issues: * the name we requested were changed without discussion with the L10n community * Chosen name sounds "logical" since it will contain translations, but people not experienced in Fedora localization internals (population of the world minus... 3 ?), there is no way to understand "translations" is not related to everything related to "translations in Fedora Linux" but a technical space dedicated to the really specific internationalization of the Fedora documentation system... * I can't reopen ticket on forge repository, any reason for that? This is even more confusing since "localization" is already referring to "everything related to translation". Please change the name to something that is related to fedora docs translations and that can't be confused with localization group. I am sorry this goes in conflict with the perfect naming we all want on new tooling. The automation defined for fedora docs internationalization is there: https://pagure.io/fedora-docs/translations-scripts/ The fact all the internationalization is defined outside of Antora and push all the translations in the same place is more of a technical constraints than a strong design choice. Note: Antora have no internationalization support: https://gitlab.com/antora/antora/-/issues/208
t0xic0der added this to the Sprint 14 project 2026-02-11 03:02:46 +00:00
ryanlerch commented 2026-02-11 09:29:23 +00:00
Owner
Copy link

The current use case for organizations is to align them with the organizations that use them. For example, when "Apps" is fully migrated, it will contain a range of different applications. This will include:

  • Multiple repositories related to Fedora Messaging
  • Multiple repositories for each application (where applicable)
  • Documentation repositories for each application

The 'teams' feature in Forgejo can be used to manage access to these repositories within the organization.

By this definition, localizations for documentation as a whole would belong in the l10n organization, correct?

My concern with localization-docs is that the name suggests it's an organization for documentation about localization, rather than an organization for localized documentation content. This naming could be misleading.

The current use case for organizations is to align them with the organizations that use them. For example, when "Apps" is fully migrated, it will contain a range of different applications. This will include: * Multiple repositories related to Fedora Messaging * Multiple repositories for each application (where applicable) * Documentation repositories for each application The 'teams' feature in Forgejo can be used to manage access to these repositories within the organization. By this definition, localizations for documentation as a whole would belong in the `l10n` organization, correct? My concern with `localization-docs` is that the name suggests it's an organization for documentation *about* localization, rather than an organization for localized documentation content. This naming could be misleading.
jibecfed commented 2026-02-11 10:41:36 +00:00
Author
Copy link

Indeed, this is the localization of Fedora docs, and not documentation related to localization.
About ownership, in a perfect world, the fedora docs group should own this, but I am fine it is owned by localization team since I know how it works and am willing to maintain it.
About organization in Forgejo, could we have sub groups of project the same way gitlab does it? It would prevent the confusion between "and organization" and the "group of projects" we need here for technical reasons.

Indeed, this is the localization of Fedora docs, and not documentation related to localization. About ownership, in a perfect world, the fedora docs group should own this, but I am fine it is owned by localization team since I know how it works and am willing to maintain it. About organization in Forgejo, could we have sub groups of project the same way gitlab does it? It would prevent the confusion between "and organization" and the "group of projects" we need here for technical reasons.
ryanlerch commented 2026-02-12 01:03:05 +00:00
Owner
Copy link

@jibecfed wrote in #400 (comment):

About organization in Forgejo, could we have sub groups of project the same way gitlab does it? It would prevent the confusion between "and organization" and the "group of projects" we need here for technical reasons.

We are tracking an upstream proposal for adding this feature -- but its not expected anytime soon:

#224

@jibecfed wrote in https://forge.fedoraproject.org/forge/forge/issues/400#issuecomment-386833: > About organization in Forgejo, could we have sub groups of project the same way gitlab does it? It would prevent the confusion between "and organization" and the "group of projects" we need here for technical reasons. We are tracking an upstream proposal for adding this feature -- but its not expected anytime soon: https://forge.fedoraproject.org/forge/forge/issues/224
jibecfed commented 2026-02-17 09:18:20 +00:00
Author
Copy link

Ok, what do we do in the meanwhile?

Ok, what do we do in the meanwhile?
t0xic0der commented 2026-02-17 11:26:36 +00:00
Member
Copy link

@jibecfed, since the subnamespaces would take a while to be implemented, I have gone ahead with the renaming. Please find the namespace here and update your bookmarks accordingly. The FAS group mappings have remained unchanged, though. Closing as fixed.

@jibecfed, since the subnamespaces would take a while to be implemented, I have gone ahead with the renaming. Please find the namespace [here](https://forge.fedoraproject.org/localization-docs) and update your bookmarks accordingly. The FAS group mappings have remained unchanged, though. Closing as fixed.
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 14
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#400
No description provided.