Repository navigation
Improve Release Process / Weblate integration #3137
Description
Activity
@ignotus666 knows more about the Weblate process. I think the mess was created by the website having conflicts.
we would require that a translator had a visible Github identity associated with the Weblate (or git) contributions.
Unfortunately this isn't possible. Everyone with a weblate account can make changes to that. Therefore the Weblate PRs should be checked by the translators.
Therefore the Weblate PRs should be checked by the translators.
...who would be required to have visible Github identities, so they could sign off their check by closing the raised issue.
Kind of. Yes. But there are no guarantees that that's the case.
What I'm saying is that there's no point us raising the current issues unless that is guaranteed to be the case. So either we change policy to require it or we drop creating the issues at all and just rely on Weblate. There's no point trying to maintain something inherently broken.
The issues are for notifying translators to start translating. Maybe we can condense it to one issue which pings all translators. That reduces complexity
If the translation is being managed through Weblate, we should have a way on Weblate of notifying the translators. The Github management shouldn't be related.
Weblate does have a notification system and I did use it to notify the translators.
However, there might be translators who are on GitHub and Weblate.
Discussing the translation process is inconvenient on Weblate in my opinion.
I think @jamulussoftware/translators should judge how we handle translation in future.
Reacted by Peter L Jones- locked and limited conversation to collaborators
on Aug 3, 2023
What is the current behaviour and why should it be changed?
The current release process documentation makes little reference to how either app or website documentation is managed through Weblate, or how a someone handling the release process can check who has been making changes to a translation on Weblate (or, indeed, directly via git).
Describe possible approaches
Ideally, the tooling would be able to maintain the current Weblate translators without intervention and we would require that a translator had a visible Github identity associated with the Weblate (or git) contributions.
In any case, improved documentation on how translations work is needed or needs to be referened with clear guidance in the release process documentation.
Has this feature been discussed and generally agreed?
Raised concerns over in #3126. Closing that issue based on raising this.