DNF and Anaconda ask to delay Zanata migration in March

Dear translators,

Anaconda[1] and DNF[2] gave the same answer today:
"Please can you delay migration and start after February 18? We are in 
the middle of RHEL 8.2 localization cycle, our team is working in Zanata 
and I want to minimize potential risk. Thanks."

It kinda bothers me a little bit. Please share your thoughts.

First assumption: the answer only concerns Anaconda and DNF projects.

1. Aren't we suppose to be upstream translation community for DNF and 
Anaconda? What does the RHEL localization cycle have to do here? Why 
March?
2. Fedora 32 schedule says string freeze is supposed to be reached at 
end of January [3]
3. Whatever external translators are helping RHEL:
    why wouldn't they be able to upload translations using Weblate? Same 
if centralized by a Red Hat employee.
    why wouldn't dev team use po merge features?
4. Migrating to Weblate for a translation team means to have a git 
repository to host translation, which only implies development teams

Anyone with insights or advice on how to handle this?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1785028#c9
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1787204#c4
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]