Docs localization migration from pagure.io to forge.fedoraproject.org #52
peartown
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?
A tracking issue for the migration of Docs localization repositories from pagure.io to the new Fedora Forge.
Progress of the migration is mostly recorded in the comments. If there was a need, another issue can be filed (and linked as dependency).
The plan is:
List of (scheduled?) tasks:
Migrated repositories:
The plan is, of course, a subject of a discussion and/or modification.
there is a ticket to open for infrastructure team to stop the current automation system. I will open it and link it to this ticket.
I will have to migrate the script by opening a pull request on https://pagure.io/fedora-docs/translations-scripts/ (should we migrate this repository first?)
I suggest to lock all docs repositories in Weblate until our migration is done, and publish a message on top of each components linking to #52 (without sending email to users, we don't want to spam them ;))
after each repository migration, we can remove the message and unlock the repository
Is it meant that we want have translation-scripts under
localization-docs(notdocs) in the forge?I thought if the repositories would be mirroring the ones in pagure, we could wait with the locking repos in Weblate and the locks could not last long. The translation will be present in both forgejo and pagure. But I have no strong opinion here. It would resemble a 'big bang' approach. On the other hand, when we make locks in Weblate, we can 'a pilot' or 'POC' any one selected repository and see if everything in the chain (source -script - pot/po - script - translated sources) works. And if it works we can remove the lock for the repository.
I have to warn that I might not be very quick with preparing the repositories in either forge and Weblate. ;)
I am also not sure if I will be able to create the mirrors without authentization (permissions) to the pagure's fedora-docs-l10n repositories.
It is possible to pull from Pagure to Forgejo without permissions, but to push back indeed requires privileges. See Pulling from a remote repository, and the following section, from Forgejo docs.
I hope we do not need to push, at least for now.
@jibecfed wrote in #52 (comment):
Sorry, I have read this again now. I misunderstood before, I guess. You speak about migration by a pull request. So now I assume the repository will finally stay under the
docsorg (namespace) - under the Docs team responsibility. And you will use PR to adapt the scripts as they will work withourmigrated repositories under thelocalization-docs...?Originally, my idea was that we will create (migrate) all the pagure.io/projects/fedora-docs-l10n repositories to the forge.fp.o/localization-docs and make them mirroring the ones (old) in pagure. And we could work in the 'background' on the changes, while the translation automation would not have to be stopped for the Docs website. But today I have doubts that we can migrate the repositories to the forge and make them mirrors of the pagure ones. So, maybe, we will have to stop the translation automation and change the translations-scripts first, as you suggested. Then migrate repositories 'normally' and work further on the changes in the repositories and weblate. After we will have everything ready, then restart the translation automation.
This is a draft of the announcement which could be published in the Fedora Discussion announcements category. It could also serve as a base for information on the Weblate. Comments, suggestions.... are welcome.
Fedora Documentation translations are not available
Fedora Documentation translations are put on hold as the Fedora Localization Team has started the process of migration from pagure.io to the Fedora Forge. Translation projects of the documentation are locked on the Fedora translation platform. No translation updates can be found in languages on the Fedora Documentation.
The migration involves all repositories which support and ensure the availability of translations of the Fedora Documentation. There is no possibility the migration can be performed 'on the fly' as changes in the repositories, related scripts and continuous integration with the translation platform cannot be dealt with independently. Therefore the translation process of the Fedora Documentation is kept on hold.
We regrettably ask the Fedora contributors, our translation community, to pull back from translating of the Fedora Documentation and wait till the translation automation of the documentation is resumed again.
The progress of migration can be followed in the localization tracker as issue #52.
To migrate a repository from pagure to the forge so as the (new) migrated repository in the forge is a (pull] mirror of the (old) one repository in the pagure:
All repositories from pagure created in the forge - as mirrors; the aim was to preserve the history of changes which can occur before we finally are ready to run translation automation using the (new) repos, thus to make the necessary locking translations in weblate as short as possible.
I migrated a few docs repositories to forgejo (only those related to translations)
https://pagure.io/fedora-docs/localization
migrated as https://forge.fedoraproject.org/docs/localization-stats
https://pagure.io/fedora-docs/translations-scripts
migrated as https://forge.fedoraproject.org/docs/translations-scripts
https://pagure.io/fedora-docs/translated-sources/
migrated as https://forge.fedoraproject.org/docs/translated-sources
I created a request to infrastructure team to change the current automation to use these new repositories: infra/tickets#13171
Before the automation is changed to Fedora Forge repositories, i think we should 1) lock doc projects, 2) make sure forge repositories are updated by git-pulling changes from respective Pagure repository, 3) leave the projects locked (?)
We could also make some repos cleaning - removing unused, renaming...
I will write (hopefully today) my idea into an separate issue so you can voice your opinion if yes or no, and if as a part of the migration or leave it rather after.
@jibecfed I'm working on updating translation-scripts README, and one step is to add a fedmsg hook. This is straightforward in Pagure, but how does this apply in Forgejo?
I don't see anything related to fedmesg hook on https://docs.fedoraproject.org/en-US/forge-documentation/
I suggest to open an issue to get the info https://forge.fedoraproject.org/forge/forge/ (and maybe help them by updating the doc)
Wild guess: this is by default and there is nothing to do.
@peartown wrote in #52 (comment):
I suggest you keep track of weird things in https://fedoraproject.org/wiki/L10N/Forgejo or in the first message of this ticket
We'll handle it after we are done with the technical migration
Tomorrow the post in Community Blog will be published.
I intend to start locking the projects/components in Weblate on Wednesday and place a short notice for the translators with link to the post. After I lock a project I would like to work on its configuration changes (in Weblate and forge). And go project by project.
I would be grateful if you (Rafael?) could supervise my work/changes. ;)
Sure.
The steps are, basically:
How about add an announce about this? It could be to the whole Fedora Weblate instance like "Fedora docs translation projects are locked due to on-going migration to Fedora Forge. See <link to blog post>"
Exactly, something like this I had in my mind. 👍
We might need to set push from mirror to Pagure, or remove mirror setting.
See error from https://translate.fedoraproject.org/projects/fedora-docs-l10n-project/nav/:
See issue comment in https://github.com/go-gitea/gitea/issues/7609:
I assume setting push would solve the read-only status.
Yes, it was expected. I have chosen between having to remove the mirror setting in the forge, or to pull from pagure to forge in the moment of migration. Purpose of the mirroring was to retain the history and a sync'd state.
I would not keep pagure in sync after, ie. mirroring from forge to pagure. Am I not seeing anything...? :)
All translation projects locked in Weblate, except fedora-docs-l10n/release-notes. I tried (twice) to push over 1300 outgoing commits, but it failed. So I am not sure what to do with the project/repositories.
localization-docs/project repository is transferred to a normal repository (mirroring setting removed) in the forge. I also added the gitea webhook for it. But we are probably not able to push changes from Weblate into it, unless jibec logs in to the forge as weblatebot, then weblatebot should be synced/added as a member to localization-docs.
weblatebot is not listed as a member in https://forge.fedoraproject.org/org/localization-docs/teams/members, which might explain why we're getting access denied:
To confirm my previous message, I manually added weblatebot as member of https://forge.fedoraproject.org/localization-docs/project (Settings > Collaborators > Add collaborator weblatebot) and the translation push worked just fine. I removed it as this was a simple test.
for reference: forge/forge#448
for reference:
Gitea credentials in Fedora Weblate - https://care.weblate.org/#ticket/zoom/12178
Issue for Forgejo hook, pull requests and documentation - https://github.com/WeblateOrg/weblate/issues/18453