05:31:26 #startmeeting i18n 05:31:26 Meeting started Mon Aug 22 05:31:26 2022 UTC. 05:31:26 This meeting is logged and archived in a public location. 05:31:26 The chair is paragan. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 05:31:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:31:26 The meeting name has been set to 'i18n' 05:31:26 #meetingname i18n 05:31:26 The meeting name has been set to 'i18n' 05:31:26 #topic agenda and roll call 05:31:37 #link https://fedoraproject.org/wiki/I18N/Meetings/2022-08-22 05:32:28 hi 05:32:37 Hi 05:32:47 hi 05:33:03 I am wearing my Dresden Flock t-shirt today 05:33:09 * suanand is around 05:33:19 hi 05:33:39 Hi all 05:33:54 #chair pwu tagoh[m] JensPetersen[m] suanand fujiwara 05:33:54 Current chairs: JensPetersen[m] fujiwara paragan pwu suanand tagoh[m] 05:34:04 Let's start this meeting 05:34:19 #topic Upcoming schedule 05:34:19 #info Tue 2022-08-23 Bodhi updates-testing activation point 05:34:19 #info Tue 2022-08-23 Change Checkpoint: 100% Code Complete Deadline 05:34:19 #info Tue 2022-08-23 Beta Freeze (starts at 1400 UTC) 05:34:36 So tomorrow will be Beta freeze 05:35:41 also keep watching https://qa.fedoraproject.org/blockerbugs/milestone/37/beta/buglist 05:36:16 We will check Change completion status in individual tickets 05:36:34 anything else to discuss here? 05:37:49 let's move to next topic then 05:38:08 #topic Issues 05:38:16 #info #161: add QA testcase for OS upgrade testing (pnemade) 05:38:16 #link https://pagure.io/i18n/issue/161 05:38:19 hi 05:38:25 there is no update here yet 05:38:35 but I think QE people will help us 05:39:56 yes 05:40:02 so let's see if we can get some testcase steps defined for our upcoming F37 testday 05:40:06 paragan i am woking on it 05:40:15 Thanks priyam 05:40:23 #chair priyam 05:40:23 Current chairs: JensPetersen[m] fujiwara paragan priyam pwu suanand tagoh[m] 05:40:58 anyone got anything to say here? 05:42:26 We need to review 05:42:47 and prepare 05:42:58 Dunno if we need a testday ticket? 05:43:20 where you want testday ticket? 05:43:49 Just a suggestion to track the preparations, anyway... 05:44:00 yes we will review this upgrade testcase before adding it to our testday 05:44:33 Sorry I noticed there is no Test Day topic - so it was a more general comment 05:44:44 yes..i will create ticket for it 05:44:53 Okay 05:45:09 let's move to next issue 05:45:18 #info #163: create a wiki page table of Emoji input support across desktop/toolkits (petersen) 05:45:19 #link https://pagure.io/i18n/issue/163 05:46:01 Sorry no update - also changes coming f37 05:46:41 Okay thanks 05:47:21 moving to next ticket 05:47:31 #info #166: Review new fonts table (tagoh) 05:47:31 #link https://pagure.io/i18n/issue/166 05:47:47 Yes, I added a comment there to update current status 05:48:48 We have a few languages apparently not expected results, even though we have intentionally minimal font package sets in comps. I'll start to file a bug for them. 05:50:14 tagoh[m], Thank you for this update. 05:51:34 let's move to next issue 05:51:45 I am still bit unsure about Nashk for Arabic Sans 05:52:04 Naskh 05:52:14 Sure 05:54:20 If we have enough space, we should have proper assigned font sets right. we may have similar discussions about Chinese before though. if we should keep consistensy regardless of what generic alias are more preferrable for particular language, we should ship sans in comps as default font right. 05:54:34 maybe good to keep discussions about it. 05:54:43 Ah so if we install langpacks-ar then Sans becomes Sans I see 05:54:59 Yes 05:55:10 I think we could consider to add it to @fonts 05:55:53 I should we had. but some fonts was dropped because it is serif and not used in installer etc? 05:56:15 * I think we should had. but some fonts was dropped because it is serif and not used in installer etc? 05:56:20 Right but probably this not so huge 05:57:00 Alright. that is sane. that's good to me. 05:58:44 paragan: Thanks. please go ahead. 05:58:50 Sure 05:58:56 thanks for having this discussion 05:59:14 #info #169: Fedora 37 i18n test day/week (pnemade) 05:59:15 #link https://pagure.io/i18n/issue/169 05:59:32 #info Test day page => https://fedoraproject.org/wiki/Test_Day:2022-09-06_I18N_Test_Day 05:59:51 I have setup the testday event now 06:00:14 we will be having testweek from 6th Sept to 12th Sept 06:00:23 Okay duh here is the ticket 06:00:29 Please do join all and provide your test results 06:01:34 * paragan thinks sometimes if we should just stop creating tickets and have open discussion meeting only :) 06:01:47 That is fine too 06:02:00 As long as it is on the agenda :-) 06:02:24 anything to discuss for this testday ticket? 06:02:48 We need to prepare I think 06:03:20 Where prepare means review/consider the test-cases 06:03:24 we need to check if any testcase need update 06:03:30 That is our task. good to keep it as a ticket IMHO. 06:04:01 okay 06:05:01 I am still wondering what is the best way - have a meeting(s), do a dry-run next week, some other approach, liking pairing or small focus group? 06:06:37 we can have meeting to discuss on this 06:06:42 yes i was planning to have review test meeting on thursday 06:07:43 paragan yes that will be good to have 06:08:46 thanks priyam 06:09:39 moving to next issue 06:09:40 #info #170: F37 Change: Gettext Runtime Subpackage (suanand) 06:09:41 #link https://pagure.io/i18n/issue/170 06:10:06 Is this Change implementation completed and its bug moved to ON_QA status? 06:10:21 Ya.. bugs have been submitted for dependents packages, latest had been built in rawhide and f37 06:11:00 we can probably move it to ON_QA 06:11:13 ? 06:11:25 Sounds good to me +1 06:11:34 okay cool, moving then 06:11:48 Also thinking about rebasing f36 06:12:05 suanand, thanks for this update 06:12:52 moving to next issue 06:13:11 #info #171: F37 Change: Firefox Langpacks Subpackage (petersen) 06:13:12 #link https://pagure.io/i18n/issue/171 06:13:37 I think this can be moved too 06:13:44 At least I am not aware of any issues 06:14:48 JensPetersen[m], Thanks for this update 06:14:59 moving to next issue 06:15:09 #info #172: F37 Change: IBus 1.5.27 (fujiwara) 06:15:09 #link https://pagure.io/i18n/issue/172 06:15:17 Is this Change implementation completed and its bug moved to ON_QA status? 06:16:15 I believe it is already ON_QA and the final release should be imminent 06:16:31 Ok good to know that 06:16:55 ibus-hangul is rebuilt for ibus. 06:17:36 Ok 06:18:11 moving to next issue 06:18:21 #info #173: F37 Change: ibus-libpinyin 1.13 (pwu) 06:18:21 #link https://pagure.io/i18n/issue/173 06:18:31 Is this Change implementation completed and its bug moved to ON_QA status? 06:18:44 ibus-libpinyin 1.13.0 is released. 06:18:53 I will move the bug to ON_QA soon. 06:19:11 pwu, Sure thank you for this update 06:19:36 thanks 06:19:59 moving to next issue 06:20:22 #info #174: Noto package splitting (tagoh) 06:20:23 #link https://pagure.io/i18n/issue/174 06:22:24 Yes, I created this ticket since Noto upstream has been created separate repo per scripts and had a release. according to our packaging guidelines, source packages would be supposed to be per released archives. hence we need to split current noto packaging. 06:23:26 Maybe we can advertise this by submitting F38 Change 06:24:04 as noted, we have a few issues. not checking exactly how many they have but I guess it may be >100 repos. it is too much to maintain them by one. should we have a sort of maint group to noto? 06:24:26 I can always help with any package reviews :) 06:24:34 It is a big undertaking 06:24:54 we need this first in some Copr repo to test this change work 06:25:43 another one is, the upgrading path should be no problem since the change should be only happened in source not binary. so we don't need to make any changes in current package. just need to retire it once all source packages are in. but yeah, we need a lot of package reviews for new source right. 06:25:54 definitely need some volunteers :) 06:26:08 Sure. 06:27:01 I hope scripting could help otherwise hard to scale I fear 06:28:23 Right. I'll try to fignre out how much we can reduce packaging costs. 06:28:24 Great, thanks 06:29:32 Thanks 06:29:39 moving ahead 06:29:50 #topic Open Floor 06:29:58 just wanted to hear any cases for the gorup of package maintenance. 06:30:00 anyone got any topic to discuss here? 06:30:08 if anyone knows 06:31:58 I think it is possible to make a noto-fonts package group 06:32:05 for example 06:32:43 Is there any document for process? 06:34:27 I am not aware of any document yet 06:34:53 Okay 06:37:23 It might be a pagure group? Not completely sure 06:37:46 Anyway good to experiment in copr I agree 06:38:59 Yep, I'll prepare copr repo once everything is ready to go. 06:39:26 #info https://fedoraproject.org/wiki/Packaging_Committee#Review_Process_Exemption_Procedure 06:40:26 Ah yes, could help 06:41:34 Yes, thanks for the pointer. that would be worth considering. 06:41:47 yes 06:43:14 Anything else to discuss here? 06:44:40 Thank you all for joining this meeting 06:44:43 #endmeeting