Translations are coming from everywhere, project by project on a "vertical" way. It comes from a project and through the packaging process it reach the user, project by project. When an Hungarian or French use Fedora in his language, use many software when using Fedora, and see translations (and localisation) on a horizontal way ( ie, per locale ). To improve the end-user experience, we need to think and act in a transversal way.
Proposal - try to change the way we provides translation to end-user
Provide translations to end user on a "horizontal" way. We want to push translation directly to the end user, without requiring efforts from upstream and packagers. This will bring more reactivity, reduce efforts all across the ecosystem.
Context : please note this is not Fedora software focused but Fedora product focused, it means it also includes upstream projects perimeter.
Current process :
We see errors > we do the work upstream > we find their translation platform (all different) and correct it > we ask for the publication of a new minor version > we request new Fedora packages ===> from 3 weeks to 3 years, with many unneeded actors solicitation, resource utilization. As Ralph Bean would say, this is not really Factory 2.0 compliant.
Idea of new process :
We see errors > we correct it > we submit the content to end user > and we submit modification upstream (at the same time) ===> translation process only involve the language team that has the responsibility for quality, distribution and upstream. There is also a faster feedback loop from locale community to translators
Use case example : I want to make easy to translate software in Gnome Software for a community, by using the current translation process, it will be a never-ending painful work. By having an middle platform to translate and push strings directly to end-user, it would make translation team way easier.