08:30:10 #startmeeting g11n (l10n focused) 08:30:11 Meeting started Wed Apr 6 08:30:10 2016 UTC. The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:30:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 08:30:11 The meeting name has been set to 'g11n_(l10n_focused)' 08:30:15 #meetingname g11n (l10n focused) 08:30:15 The meeting name has been set to 'g11n_(l10n_focused)' 08:30:20 #topic agenda and roll call 08:30:21 #link https://fedoraproject.org/wiki/G11N/Meetings/2016-04-06 08:30:34 hi.. 08:30:35 hi pravins 08:30:35 who available for meeting today? :) 08:30:40 hi suanand aeng :) 08:30:43 #chair suanand aeng 08:30:43 Current chairs: aeng pravins suanand 08:31:03 while other joins lets see upcoming schedule. 08:31:12 #topic Upcoming schedule 08:31:12 #link https://fedoraproject.org/wiki/Releases/24/Schedule 08:31:19 #info 2016-04-19 Beta Freeze (*) 08:31:20 #info 2016-04-19 Change Checkpoint: 100% Code Complete Deadline 08:31:20 #info 2016-05-03 Beta Release 08:31:20 #info 2016-05-24 Final Freeze (*) 08:31:20 #info 2016-06-07 Fedora 24 Final Release (GA) 08:31:21 hi 08:31:27 hi jibecfed_ :) 08:31:30 #chair jibecfed_ 08:31:30 Current chairs: aeng jibecfed_ pravins suanand 08:32:05 Beta release happening in couple of weeks. Hoping our translations will get pulled by developers. 08:32:26 whats the usual process to notiffy the package maintainer? 08:32:40 aeng: good question, even i dont know. 08:32:55 but may be send email them on devel@list? 08:32:59 paragan: ^^ 08:33:05 hi 08:33:07 hmm... perhaps emailing for now? we've got all their email address in Zanata 08:33:19 or yeah.. devel@list 08:33:29 yes fedora devel list 08:33:32 aeng: +1 its important to start pinging them from now. 08:33:53 #info Its time to ping devels for pulling translations from Zanata. 08:34:06 #topic New members joined in trans 08:34:11 #info Eduardo Silva - joined for portuguese 08:34:12 Fas name: hoboprimate 08:34:12 #info Eduardo Silva - joined for portuguese 08:34:12 Fas name: hoboprimate 08:34:28 Translation sprint helped to bring couple and actually more members in translation projects. 08:34:48 hi 08:34:54 agree. The sudden burst of activity in translation brings interest 08:34:54 They already did translation for F24 and i have also awarded badges to them :) 08:34:55 +1, can see it in french team too 08:34:58 hi juhp :) 08:35:00 #chair juhp 08:35:00 Current chairs: aeng jibecfed_ juhp pravins suanand 08:35:30 #chair epico paragan 08:35:30 Current chairs: aeng epico jibecfed_ juhp paragan pravins suanand 08:35:45 but also, credit to people who organise it and coordinating with them 08:36:17 true without local ambassadors, coordinators its difficult to make this happen. 08:36:41 thats the point ;) 08:36:50 we should organize a feedback in Flock 08:36:54 gnokii: good catch :) 08:37:01 +1 jibecfed_ 08:37:21 #idea jibecfed_ suggested to organize feedback session in flock. 08:37:45 lets discuss this further in vFAD topic. 08:37:47 moving to next topic. 08:37:48 #topic Fedor 24 I18N test day planning 08:37:49 #link https://fedorahosted.org/i18n/ticket/60 08:38:07 Bit worried for this presently, we have i18n test day on 12th April (coming Tue) 08:38:22 and still not much work on Test case cleanup and adding new test cases. 08:38:39 who update those test cases 08:38:40 ? 08:38:50 no dedicated person for it :( 08:38:57 QA team? 08:39:00 but i requested Satya last week 08:39:11 yeah, requested help from FLTG. 08:39:45 I can help review to see if I understand it, but can't write them 08:39:51 Fedora QA helps in organizing test day, example for created testday app, test day wiki page. 08:40:25 how about gathering tomorrow and work on cleanup of test cases? 08:41:06 it can be whole day, so one can do it as per his time availability. 08:41:36 so all available qa? 08:41:37 yeah we really need to have the test-cases updated and ready ASAP 08:41:52 perhaps devel should help too 08:41:59 at least update existing test cases 08:42:09 right, so all i18n devel can help to review and update there test cases. 08:42:17 yes 08:42:26 We have few regular test cases and we add few as per new features. 08:42:28 yeah we all can update/clean test cases 08:42:48 I think good to send a reminder to i18n list 08:43:00 or direct emails too 08:43:12 #link Fedora 23 test day https://fedoraproject.org/wiki/Test_Day:2015-09-01_i18n 08:43:18 deve@list agian? 08:43:31 juhp: good idea. 08:43:51 devel list will be too broader though. 08:44:28 #action pravins to send email on i18n and g11n list to cleanup test cases. 08:44:51 moving to next topic 08:44:51 #topic ZNTA-1009 Redhad translation content is imported into Zanata (wrong display and questionable usage as there is no access to context) 08:44:52 #link https://zanata.atlassian.net/browse/ZNTA-1009 08:45:24 jibecfed_: added this topic earlier. 08:45:32 jibecfed_: would you like to update on issue? 08:45:39 I created this bug to understand, but finally I'm opposed to that change 08:45:52 aha, aeng already replied on ticket. 08:46:02 yup 08:46:05 to be usefull, translation memory should link to source and context 08:46:26 agree 08:46:34 thats something that can be helpful 08:46:41 if we can't have this, I don't see the point, it's like a glossary, it's a hint but not a memory 08:47:10 so if redhat what to do that, we should be able to go see the context and access to source 08:47:35 jibecfed_, its not redhat wants to do that 08:47:53 the decision to have redhat tm available is to help out translators with more reference 08:48:13 most of the japanese translators find it really useful 08:49:07 if translator doesn't agree, they can always ignore the TM, like I mentioned,, perhaps filtering of TM would be useful for those who doesnt want to see that 08:49:20 i think this is solvable, so need to check who has uploaded Translation memory, we can ask/request him to open. 08:49:30 aeng: right, i remember we discussed on this feature in Tokyo. 08:50:35 yeah... we in the process of developing new editor, that is why less effort is putting in into this editor 08:51:04 (sorry, disconnection) 08:51:38 last sentence I saw was : jibecfed_: if it is more consistent with Zanata interface and if we can access to source, it's good, if not ... 08:51:38 #info Zanata is in the process of developing new editor. Filtering TM would be available after some time. 08:52:16 disconnected again 08:52:54 jibecfed: given in PM 08:52:56 next subject 08:52:56 lets work further on ticket you raised. :) 08:53:11 #topic Fedor 24 L10N test day planning 08:53:11 #link https://fedorahosted.org/G11N/ticket/18 08:53:12 #link https://fedorahosted.org/fedora-qa/ticket/480 08:54:17 #link http://testdays.fedorainfracloud.org/events/3 08:54:35 i hope someone from FLTG will provide report soon. 08:55:36 noriko: just in time :) 08:55:47 woohoo 08:55:48 hi, sorry coming in late. I was caught by traffic jam :`-( 08:55:52 Wanted to say, L10N test day went very well. !! 08:56:00 with so many participants. 08:56:08 yay :-D 08:56:14 What should be next steps? 08:56:21 i think we need to prepare report soon. 08:57:12 we should have separate reports, i18n, l10n, fltg and zanata? 08:57:34 umm, last time i wrote article on commblog common for i18n and l10n test day. 08:57:58 i'll do stats, i'll send it to list this weekend, and with graphics (not only raw data) 08:58:02 noriko: what kind reports for zanata and fltg?? 08:58:02 i18n test and l10n test are definitely and totally different things :-) 08:58:20 ask them ? 08:58:51 jibecfed, have you got the list of contributors? 08:58:58 I can take care of l10n, you pravins should be able to take care i18n, right? 08:59:14 yes, definitely. 08:59:39 #link Fedora 23 G11N test day article. https://fedoramagazine.org/globalization-test-days-report-fedora-23/ 08:59:54 we can either have single or different, both are fine with me :) 09:00:18 getting report is important, for such a nice event :) 09:00:25 yup 09:00:41 aeng: no, I tried yesterday to find it with Zanata's API, but I didn't find anything to extraction to track changes 09:01:01 and we actually jumped to next topic. 09:01:02 #topic vFAD for Translations 09:01:02 #link https://fedorahosted.org/G11N/ticket/5 09:01:03 jibecfed, there's a contributors api for project/version 09:01:27 aeng: ah ? please share link 09:01:28 500+ heats for our article in commblog 09:01:47 #link https://communityblog.fedoraproject.org/translate-fedora-24-in-your-language/ 09:02:04 Its ranking 4th in overall article in last months. !! 09:02:32 #link https://fedoraproject.org/wiki/G11N/vFAD_Translation 09:02:37 Operation part went well. 09:02:44 now its time for effective closing 09:03:06 and that is what aeng and jibecfed discussing now :) 09:04:06 yep, i wait for aeng's link for API 09:04:14 It will be nice if we have list of participants, language and number of words/link they translated. 09:04:23 s/link/line 09:05:17 * aeng trying to get the information 09:05:37 aeng: I use this page to get information : https://zanata.ci.cloudbees.com/job/zanata-api-site/site/zanata-common-api/rest-api-docs/index.html 09:06:02 #action aeng and jibecfed will provide stats for Virtual translation sprint window. 09:06:02 but there is only basics, there is nothing to track changes per contributor 09:06:21 ah... its in 3.90 09:06:31 https://zanata.atlassian.net/browse/ZNTA-742 09:06:46 alright... what I can do... get information from database 09:07:01 and query on list of contributors 09:07:14 then from there... we can use rest api to get the contribution stats 09:07:33 i will get the list of contributors by friday 09:08:02 aeng: nice, it will help :) 09:08:18 * aeng noting down to do list 09:08:36 pravins, whats the date range? 09:08:43 1-5th april 09:08:51 done 09:08:56 overall commenting on translation sprint. 09:09:04 aeng: i'll be pleased to help, please share raw stats with me 09:09:18 jibecfed, will do 09:09:28 It definitely created awareness in community regarding, there used to Window in Fedora release schedule, where one can contribute for translation 09:09:42 i am sure, more contributors will be waiting for next one. 09:10:22 We have badge for participants. https://badges.fedoraproject.org/badge/fedora-24-translation-sprint 09:10:25 :), good effort guys 09:10:33 so if you participated during this time, please ping me for this badge. 09:10:55 anyhow i am going to award badge, based on stats provided by aeng and jibecfed :) 09:10:57 Thanks aeng 09:11:06 :) 09:11:06 pravins: if aeng extract contributors, would they still have to ping you ? 09:11:18 ok 09:11:18 no. 09:11:31 next topic 09:11:32 #topic Live media with langpacks included 09:11:32 https://fedorahosted.org/G11N/ticket/17 09:11:45 i will get all of contributors during this time, and also the total words they contributed 09:12:32 excellent !! 09:12:43 paragan: thanks for comment in ticket 09:12:59 about langpacks, there is a major issue 09:13:18 it works when explicitly installing it with dnf, but not from the livecd 09:13:42 i think pnemad works on this, but i don't have details 09:14:22 right, i also talked with paragan earlier. 09:14:28 as commented it will take some time 09:14:36 its important issue. 09:14:53 paragan: lets add this in i18n test cases, so more people will understand issue. 09:15:15 aha, it means we will all face this issue in LiveCD testing :) 09:15:18 better not add it otherwise I need to explain everyone 09:15:26 same thing again and again 09:15:48 should we expect it for F24 ? Docs team are making release notes, we should advise them 09:16:15 true. 09:16:16 I will try my best but the decision is in Server and Workstation WG people 09:16:30 whether to add langpacks-\* packages or not 09:16:42 Do we have any other ticket which reference this in WG/Server group trac? 09:16:54 Server WG don't user trac 09:17:00 aha 09:17:01 Workstation uses I think 09:17:16 just thought good to refer it in our trac ticket. 09:17:27 will add it 09:17:33 but will other people comment there? 09:18:04 anyways will add reference in our ticket 09:18:15 i think only if required. 09:18:26 thanks paragan for an update, hoping we will get solution during F24 :) 09:18:38 moving to next topic 09:18:40 #topic [Queries in this week] 09:18:47 #info highlighted letters in menus / shortcuts 09:19:37 Richard has already provided answer to it. 09:20:08 #info Choosing branches 09:20:23 and noriko has already provided answer for this. 09:20:29 aeng: one more query to you. 09:20:56 yup 09:21:00 If i do translation in f24 branch and try to translate same line in master.... Will i get suggestion/reference from f24 branch? 09:21:26 since, i did few translation for f24 branch and wanted to replicate it in master. 09:21:30 depends on how the master brnach will be created 09:21:48 if i get it in suggestion with 100% match, just need to copy it ;) 09:21:59 sure, will try for it. 09:22:10 if master is created based on f24 branch (create version feature), then it will have all the history and reference 09:22:54 umm, normally we convert master to F24. 09:22:56 if master is already there and you wish to merge in translation from f24 branch, then use "merge translations" feature, that will bring all matching and approved/translated across 09:23:16 this is what i was looking for :) 09:23:44 but yeah.. there are few ways to bring across translations 09:23:48 #info One can "merge translations" feature to bring all matching and approved string from master to f24. 09:24:05 thanks aeng, may be you can see this thread on trans list. :) 09:24:16 "Choosing branches" 09:24:27 last topic 09:24:30 #topic Next Meeting Date and Time 09:24:30 ok 09:24:39 can we have someone to chair next meeting? 09:24:51 it should happen on 20th April 09:25:18 time i am still not sure but may be regular one 04:30 UTC> 09:25:52 let me ask on mailing list again. 09:26:09 #action pravins to ask on mailing list for next meeting time and chair. 09:26:20 jibecfed: i think 04:30UTC works well for you. 09:27:09 moving to next one. 09:27:09 #topic Open Floor 09:27:18 if nothing else lets close meeting in 2 minutes.. 09:27:29 pravins: sorry disconnected again :( 09:27:39 i'll read the log 09:27:43 no problem, thought so :) 09:27:44 :) 09:27:52 time to get cable 09:28:06 yeah 09:28:12 thanks all for nice meeting. 09:28:18 thanks all 09:28:20 thanks pravins 09:28:20 #endmeeting