12:09:13 #startmeeting L10N Translation platform migration 12:09:14 Meeting started Mon Jan 6 12:09:13 2020 UTC. 12:09:14 This meeting is logged and archived in a public location. 12:09:14 The chair is jibec. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:09:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:09:14 The meeting name has been set to 'l10n_translation_platform_migration' 12:09:20 #meetingname L10N 12:09:20 The meeting name has been set to 'l10n' 12:09:28 #meetingtopic Translation platform migration 12:09:34 #chair suanand jibec 12:09:34 Current chairs: jibec suanand 12:09:45 .hello2 12:09:46 suanand: suanand 'Sundeep Anand' 12:09:51 .hello2 12:09:52 jibec: jibec 'Holcroft' 12:09:58 haha, not the good account 12:10:02 .hello2 jibecfed 12:10:04 jibec: jibec 'Holcroft' 12:10:12 .fas jibecfed 12:10:12 jibec: jibecfedora 'Jean-Baptiste' - jibecfed 'Jean-Baptiste Holcroft' - testjib 'test jibecfed' <2251146@holcroft.fr> 12:10:22 happy new year, sorry I was on long leaves .. 12:10:28 :) 12:10:36 happy new year to you too, glad to see you back :) 12:10:50 #topic Phase 1 - weblate beta period 12:11:04 beta works fine 12:11:11 nice 12:11:15 no major issues for the moment, projects comes slowly 12:11:34 (by when we're planning to go Prod??) 12:11:34 we now have gitlab support also (ability for weblate to open pull requests on gitlab) 12:11:45 oh, great 12:12:02 a lot of projects are on gitlab 12:12:35 I think I should open a discussion to have a formal GO/NO GO for production, so I can change the URL from https://translate.stg.fedoraproject.org to https://translate.fedoraproject.org 12:13:02 * suanand thinks to have stg and prod both 12:13:16 (not sure though) thoughts? 12:13:59 (stg for testing) 12:14:28 what would we do in stg that we won't do in prod? 12:15:16 may be test all new features first in stg.. and shall push tested and bug-fixed code to prod 12:16:12 we are not devlopping Weblate, so we won't have to push anything 12:16:18 well, I guess keeping one instance may be okay - as we have upstream support for all testing 12:16:28 but I can ask for a minimalist installation in staging for testing purposes 12:16:35 right - just realize that :) 12:16:49 ok 12:17:12 #action jibecfed: ask approval for production to translator mailing list 12:17:13 well, I was thinking about integration(s) like MT etc .. 12:18:00 #action jibecfed: ask weblate team how to handle tests and if a test instance makes sense to them 12:18:06 #topic Phase 2 - Weblate in production 12:18:15 (agree) 12:18:16 follow-up is there: https://fedoraproject.org/wiki/L10N_Move_to_Weblate 12:18:33 we had 115 projects in Zanata 12:18:39 94 are to migrate 12:18:48 7 are done, 5 are in progress 12:19:43 okay 12:19:45 this is really slow, many of our upstream projects don't store pot in repository, which makes Weblate usage more difficult 12:20:17 Yeah, need to handle that 12:20:28 I've ask for support upstream: https://github.com/WeblateOrg/weblate/issues/3349 12:20:48 few projects creates and push POT build time.. 12:20:50 either this issue or this one will solve the problem: https://github.com/WeblateOrg/weblate/issues/3263 12:21:14 yes, I don't like this way of doing it, but I understand the reasons 12:21:43 two ways to workaround this problem: add the pot upstream, but update it only once in a while with a bot 12:22:08 or create a dedicated repository for localization 12:22:29 For little projects, I suggest to keep the pot in repository and update it at each commit 12:22:59 (how weblate utilize POT files?) 12:23:26 pot files are used to add a new language and to update existing languages for new strings 12:23:50 hmm - okay - so no manual upload - nice! 12:24:15 any other subject here? 12:24:46 many projects maintain release specific branches 12:25:34 so, developer might have to hint that in weblate.. 12:25:53 you basically create one component per active branch 12:26:30 I would rather feel to create component per fedora release f31 f32 f33 12:26:31 Weblate will help translators to propagate translation between components and warn if inconsistencies 12:26:57 suanand: if this makes sense for upstream, it's what we should do yes 12:27:05 anaconda works like this 12:27:21 I think cockpit will also do the same 12:27:35 but other projects such as pulseaudio and ibus don't follow that scheme 12:27:41 * suanand suggests this! 12:27:50 I know.. 12:28:34 anyways - we may discuss more on this! 12:29:20 would you like to share some info about the ability to sign FPCA in weblate? 12:30:27 Apologies - I could not have done it yet.. 12:30:28 #info projects maintaining multiple release branches can create multiple components in W.eblate. Weblate will help translators to propagate translation between components and warn if inconsistencies 12:30:35 no worries 12:30:45 would you like to share about transtats? 12:30:59 #topic transtats 12:31:21 Transtats - we have few discussions on what's next 12:31:53 it growing and a lot of things to be done; still priority is to schedule string change job and some alerts 12:32:01 (for possibly f32) 12:32:56 written a post: https://fedoramagazine.org/tracking-translations-with-transtats/ 12:33:44 bravo for the blog post :) I hope you'll get feedbacks! 12:34:03 I guess migration to Weblate may span to f33 .. 12:34:35 Any bottlenecks? 12:34:54 If no, may be Yes - good to start Go/No Go discussions 12:35:31 the main issue for me is fedora websites 12:35:36 I need them to ask my questions 12:36:07 all other key projects will have migrated by january 28 12:36:29 F33 will be the removal of the zanata instance 12:36:37 okay - are you coming in devconf CZ ? 12:36:50 no, but I'll be at Fosdem 12:37:26 I would suggest to keep zanata for a complete f-release after migration if that helps .. because a lot of changes at upstream level would be needed 12:37:38 fosdem - gr8 12:39:54 I'll consider this info, but projects should expect the removal of Zanata by september 12:40:08 hm - okay 12:40:09 #info removal date of Zanata may be september 2020 12:41:44 any other subjects? 12:42:03 seems - I'm good (nope) 12:42:13 #endmeeting