What should we do with the issue tracker of localization-docs repositories? #68

Open
opened 2026-06-09 16:10:07 +00:00 by rffontenelle · 2 comments
Member

Currently, localization-docs repositories have their own issue tracker enabled, however I believe localization issues should be centralized in here instead of each repository.

Ideas:

  1. Set external issue tracker with URL https://forge.fedoraproject.org/localization/tickets/issues/ (causing its built-in issue tracker to be disabled)
  2. Disable the issue tracker

I prefer the first option because the second may leave the user in doubt on how to report issues from one of the localization-docs repository.

All this can be done via API, so not too difficult.

Currently, localization-docs repositories have their own issue tracker enabled, however I believe localization issues should be centralized in here instead of each repository. Ideas: 1. Set external issue tracker with URL https://forge.fedoraproject.org/localization/tickets/issues/ (causing its built-in issue tracker to be disabled) 2. Disable the issue tracker I prefer the first option because the second may leave the user in doubt on how to report issues from one of the localization-docs repository. All this can be done via API, so not too difficult.
Owner

I also vote for option 1.

I also vote for option 1.
Owner

Thanks for taking care of this, option 1 is great, I didn't know it was possible! Forgejo rocks :)

Thanks for taking care of this, option 1 is great, I didn't know it was possible! Forgejo rocks :)
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
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
localization/tickets#68
No description provided.