15:29:19 #startmeeting L10N Localization group 15:29:19 Meeting started Mon Sep 23 15:29:19 2019 UTC. 15:29:19 This meeting is logged and archived in a public location. 15:29:19 The chair is jibec[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:29:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:29:19 The meeting name has been set to 'l10n_localization_group' 15:29:26 #meetingname L10N 15:29:26 The meeting name has been set to 'l10n' 15:29:49 #chair asamalik jibec 15:29:49 Current chairs: asamalik jibec jibec[m] 15:29:53 .hello2 15:29:54 asamalik: asamalik 'Adam Samalik' 15:30:14 * asamalik waves 15:30:36 #topic documentation system internationalization 15:30:48 as discussed on docs mailing list, I moved all previously existing action to https://teams.fedoraproject.org/project/translation-platform-migration/epic/11 15:30:52 .hello 15:30:52 bexelbie: (hello ) -- Alias for "hellomynameis $1". 15:30:55 * bexelbie is lurking 15:31:02 .hello2 jibec 15:31:03 jibec[m]: Sorry, but you don't exist 15:31:12 * .hello2 jibecfed 15:31:20 :D 15:32:08 asamalik: what are the requirement on your side to allow localization in production? 15:32:33 jibec[m]: from what I remember (and it's been some time) I feel like it should work 15:32:39 although when I last checked it's not building 15:32:46 so I'll have a look at that 15:32:51 .hello bex 15:32:52 bexelbie: bex 'Brian (bex) Exelbierd' 15:32:56 wrong command earlier 15:33:02 but I think we got that into a working state, right? 15:33:15 back then in Strasbourg 15:33:37 yes, but I did had to do a lot of changes 15:33:50 and there is an open PR for you to review https://teams.fedoraproject.org/project/translation-platform-migration/us/12 15:34:09 excellent! 15:34:35 oh, how did I miss that? :) 15:35:12 I think I remember this, yes 15:35:18 I think this provides the required steps for the global site.yml file to be generated in all languages 15:35:38 how many? 15:35:42 you may have to adapat the language switcher button to have the correct list of languages 15:35:49 right 15:36:13 and all the site.yml files are the same for each language except the language code in the path 15:36:31 yep 15:36:33 * asamalik makes a note to review 15:37:12 and our localization system will generate what is required there, whatever we have translations or not, so the antora generator doesn't have to think 15:37:34 right 15:37:58 other point is: https://teams.fedoraproject.org/project/translation-platform-migration/us/13 15:38:04 I won't merge it now, but from reading it quickly it does what I'd expect it to do 15:38:13 do you have a way to send emails when something goes wrong? 15:38:29 #action asamalik review PR to enable automatic language detection on the docs build side https://pagure.io/fedora-docs/docs-fp-o/pull-request/117# 15:39:19 jibec[m]: I can't see how that would be a "no", even though I don't know how to do that at this very moment 15:40:48 that's about the po/pot file repos, right? 15:41:00 ok, basically, I would like to receive an email if errors, so I can fix it, most of the time, it crashed was because a l10n repository was missing, and on really rare occasion, because of a script mistake 15:41:28 when I add a new component (new content) to the docs, we need to create new repos for that in the l10n space in Pagure, right? 15:41:31 you will have to create a pagure bot, and ask me to give the required rights on the 37... l10n repositories :D 15:41:32 yes 15:41:38 * asamalik is remembering all the details now 15:42:11 hum, my wifi is bad, so my "yes" was about "that's about the po/pot file repos, right?" 15:42:24 what do you mean by a pagure bot? 15:43:47 a technical account 15:44:10 so it can create new repos? 15:44:17 because we don't have an automation for that, right? 15:44:34 repo creation is manual and I manage it 15:45:58 the technical account will commit new pot files and update po files in all l10n repos, and it will commit localized content 15:47:23 are these technical accounts a thing in Fedora? 15:47:23 you can see it here: https://pagure.io/fedora-l10n/fedora/commits/master some commits comes from master, others are automatic update of pot/po files 15:48:13 I have no idea, don't you use some already? 15:48:20 I don't 15:49:35 what worries you? 15:50:44 maybe bexelbie can help here? 15:51:54 sorry I was just thinking 15:52:41 just to remind myself, we have these l10n repos with po/pot files, and one giant repo wit all the translated Antora sources, right? 15:52:49 yes 15:53:24 and we have a script that I started and basically you wrote most of it in the end that does the conversion between those 15:53:29 https://pagure.io/fedora-docs/translated-sources/ 15:54:05 please let me know if I can help 15:54:07 * bexelbie reads back 15:54:39 what was my help needed with? 15:54:40 and that script runs somewhere, or do you run it? 15:54:49 I'll ask the fedora infra team to move the l10n repositories form fedora-l10n/* to fedora-docs-l10n/* so the URL are a little bit more explicit 15:55:15 asamalik: for now, I'm running it on my desktop 15:55:58 bexelbie: asamalik was having doubts about the creation of a technical account for Pagure 15:55:59 so we'd need a service to run this... that could definitely run in the fedora openshift 15:56:31 that may be legit - we need to talk to infra about that 15:56:35 it should be possible though 15:56:46 yeah 15:56:56 we'd basically need a service in Fedora openshift that can push to Pagure 15:57:14 and that can ideally create repos 15:57:25 that is definitely possible when there is a human account "owning" this action 15:58:01 yes, that would be probably just configuring the keys... although having it more "group owned" would be the best, we have a lot of buses in Prague :P 15:58:23 repository creation is not that important for this script 15:58:43 it's only once in a while, and only after you add a new antora component in our mail site.yml 15:58:59 so I can do it manually 15:59:29 jibec[m]: well I could just write something real quick that would check what soruces we consume with Antora, make sure we have po/pot repos for that and possibly create those missing, and then generate the configs for Antora to be able to build the site 15:59:42 right 16:00:04 if it's quick and if it works, it's no reason to say no :p 16:00:13 but it needs to be done super quick, otherwise builds start to fail :P 16:00:49 jibec[m]: do you have a link for the conversion script? 16:00:54 I have to go, thank you for coming, I'll be available on IRC when required, on office hours 16:01:07 yeah I have to run as well 16:04:36 Internet lost 16:06:59 #endmeeting