Ludek, please use this UI to register to the mailing list:
You can also respond without registering using the same URL.
>> Because Cockpit and Composer already moved to weblate, we
>> definitely finish our translations there.
>> But in general I would really prefer to have RHEL 8.2 translation
>> cycle finished first (18 February) and migrate after that.
> Could we turn things around and see the situation as an opportunity?
> Since I joined Fedora in 2015, I never had an opportunity to
> contribute a RHEL release, and being able to see RHEL translators'
> work/feedback always were really limited.
Absolutely. We are pushing our translations to Zanata/ Weblate approx.
4 times a year during the RHEL 7 and RHEL 8 localization schedules.
Our scope is limited though, we focus on customer critical components
such as: installation (anaconda, dnf), administration (cockpit,
composer), storage, networking, selinux, comps.
Good, then, I should be able to create a component list for these
projects to make it easier to find.
This is something which needs to be coordinated with the respective
RHEL sub teams. If you need, I can provide you with contact
information but I am no the person who has access to their git
What you can do: go in this list of issues to tell the team they can
migrate if they make sure it won't impact RHEL 8 localization schedules:
I'm unsure of what you call "storage" and "networking":
I have blivet in storage category:
Could you provide a more precise list?
selinux looks like to have one fork per platform, I feel like we should
probably merge the effort upstream instead of translating multiple time
the same content:
Could you contribute or invite RH dev team to contribute the discussion?