#249 Migrate translations-scripts repo to GitLab
Opened 2 years ago by bcotton. Modified 6 months ago

This issue is for tracking the migration of the translations-scripts repo to the fedora/docs space on GitLab.

Coordinate this work with @jibecfed as it will require changes to the translations tooling.


Metadata Update from @bcotton:
- Issue tagged with: gitlab

2 years ago

hi, what's the added value to migrate to gitlab?

After some long thinking, the two other l10n repositories in the fedora-docs namespace (translated-source and localization) contain only generated content and no user interaction are really needed on those. Therefore, moving them to gitlab, which requires some work, yield no rewards.
This repository (translations-scripts) however is really tied to the build pipeline and I really think it would be a good idea to move it next to the docs-fp-o repository.
Additionally, it would give it a bit more exposure with the help of the group-wide dashboards and may even help bringing in new contributors (it's a long shot, I know, but still ;) ).
We can even think about adding some CI / automated testing with gitlab-ci at some point.

@jibecfed what do you think?

while I did not care about the gitlab migration since I'm fine with wherever the fedora-docs decides to store is code, the migration broke workflow

the document source code where moved to gitlab
the fedora-docs translation scripts see no content and erase everything in fedora-docs-l10n repository
weblate see the file on which the main component is base is missing, and raise an error

issue were discovered on fedora-install-guide, and impacts other components (system-administrators-guide)
our system is resilient enough not to fall apart, but still, it is broken ;)

Login to comment on this ticket.

Metadata
Boards 1
GitLab migration Status: Todo