Dear translation teams,
I just finished a draft of the migration plan. This mostly is about schedule, and a little bit about the steps to get it done. Please ask any question you feel like (in public here or #fedora-i18n or in private).
https://fedoraproject.org/wiki/L10N_Move_to_Weblate
As Fedora 32 schedule isn't really decided yet, this may move a one or two weeks.
What worries me is to make sure we have all upstream project to understand the behavior of the new translation platform (direct connection to git instead of manual push/pull), and to find the best way to handle new processes with them (git branches will be used by Weblate).
So far, no alternative proposed to Weblate. If you have a tool and can demonstrate it answer our community needs, remember it really is open for discussion.
Have a nice day,
Jean-Baptiste
On Wed, Jul 31, 2019 at 7:20 PM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
https://fedoraproject.org/wiki/L10N_Move_to_Weblate
As Fedora 32 schedule isn't really decided yet, this may move a one or two weeks.
As Jean-Baptiste said, the Fedora 32 schedule isn't finalized yet, but the dates should not vary by more than one or two weeks. (The schedule should be approved by the end of August). I agree with the milestones outlined in the wiki page. From a Change proposal standpoint, it would be best to do this as a System-Wide Change proposal (due 2019-01-07), but I could also make a case for calling it a self-contained change. But the deadline shouldn't be an issue, as you'll want to get this started as soon as possible.
What worries me is to make sure we have all upstream project to understand the behavior of the new translation platform (direct connection to git instead of manual push/pull), and to find the best way to handle new processes with them (git branches will be used by Weblate).
If it would be helpful, I'd be happy to help you come up with a project plan and timeline so we can see how the migration will work. I can see the migration of the website, for example, being a long item, simply because of the workload on the CPE team.
So far, no alternative proposed to Weblate. If you have a tool and can demonstrate it answer our community needs, remember it really is open for discussion.
Speaking strictly from a project success perspective (as I have no experience with any translation tooling), we should make a final decision on the platform very soon or else target Fedora 33.
I'm afraid there is no alternative than being successful in this migration. Nobody assume our platform maintenance and more we wait the more risky our situation is. Brian and others already ask if we could go faster, without waiting much.
As the infrastructure team want to focus on key applications, I doubt they will assume the maintenance of a translation platform and a translation memory server.
So, the real question is, for what doesn't depend on contributor work, how much does the council is willing to invest in hosting services, and funding features. Because I doubt our l10n community member will be developing in weblate and related tools any soon.
I hope you, and others will be at the workshop to discuss it!
-------- Courriel d’origine -------- De : Ben Cotton bcotton@redhat.com Envoyé : 1 août 2019 15:34:41 GMT+02:00 Speaking strictly from a project success perspective (as I have no experience with any translation tooling), we should make a final decision on the platform very soon or else target Fedora 33.
-
Ben Cotton -
Jean-Baptiste