05:30:10 #startmeeting i18n 05:30:10 Meeting started Mon Jun 28 05:30:10 2021 UTC. 05:30:10 This meeting is logged and archived in a public location. 05:30:10 The chair is vishalvvr. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:30:10 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:30:10 The meeting name has been set to 'i18n' 05:30:17 #meetingname i18n 05:30:17 The meeting name has been set to 'i18n' 05:30:22 hi 05:30:25 #topic agenda and roll call 05:30:30 Hi 05:30:35 hi 05:30:36 #link https://fedoraproject.org/wiki/I18N/Meetings/2021-06-28 05:31:01 #chair tagoh paragan suanand 05:31:01 Current chairs: paragan suanand tagoh vishalvvr 05:31:31 hi 05:32:17 hello 05:32:30 #chair pwu juhp 05:32:30 Current chairs: juhp paragan pwu suanand tagoh vishalvvr 05:33:10 Today priyam could not join the meeting, so i am chairing today's meeting :) 05:33:20 lets start with today's meeting. 05:34:01 #topic Upcoming schedule 05:34:10 #info 2021-06-29 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild) 05:34:17 #info 2021-06-29 Change Checkpoint: Proposal submission deadline (System Wide Changes) 05:34:23 #info 2021-07-20 Change Checkpoint: Proposal submission deadline (Self Contained Changes) 05:34:30 #link https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html 05:34:54 anyone has any upcoming schedule to be mentioned here? 05:35:48 nothing just keep noted Change deadlines 05:35:59 we will discuss about Change submission in its own ticket 05:36:23 okay, then lets move onto next topic then 05:36:35 #topic issues 05:36:42 #info #133: Transtats in fedora planning 05:36:46 #link https://pagure.io/i18n/issue/133 05:37:12 suanand, any update or progress on this ticket ? 05:37:31 #info latest release 0.8.4 has been deployed: https://transtats.fedoraproject.org/ 05:37:31 moreover, Transtats is ready for f35 https://transtats.fedoraproject.org/releases/view/fedora-35 05:37:55 Planning to start work on mentioned ticket, this qtr . 05:38:09 suanand ++ 05:38:18 suanand++ 05:38:18 vishalvvr: Karma for suanand changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 05:38:50 suanand++ 05:40:39 Thanks for the update suanand, do we have anything more to discuss in this ticket ? 05:40:41 Cool 05:41:45 okay then moving onto next ticket 05:41:57 #info #132: refresh I18N/Fonts 05:42:03 #link https://pagure.io/i18n/issue/132 05:42:16 No updates on it this time. 05:42:52 will take a look more next month. 05:43:30 okay, lets keep working on the wiki update and we will visit this ticket next time :) 05:43:42 Yep 05:44:44 moving onto next ticket 05:44:54 #info #139: brainstorming for i18n-Podcast 05:45:00 #link https://pagure.io/i18n/issue/139 05:45:20 I posted a comment on the podcast pagure ticket 05:45:31 #link https://pagure.io/fedora-podcast/issue/43 05:45:42 I thought it would be good to talk to them first... has anyone listed to any of the podcasts so far? 05:45:59 I heard Chris Murphy did one recently which is rolling out 05:46:07 listened to * 05:46:26 I didn't find time yet to listen 05:46:38 i always want to but forget about it :P 05:46:43 Nod 05:47:17 The AM radio of the internet :-) 05:47:26 will definitely listen to it this week :) 05:47:32 I will try too 05:48:22 Not sure but the podcast might be more in the Americas but I could be wrong? 05:48:30 podcast team 05:48:46 But it should be possible 05:49:04 Any other thoughts or suggestions? 05:50:16 juhp do you have any notes, slides or any pointer already prepared for the session? 05:50:17 I didn't have a time to flesh out the questions more either - but listening to one or two podcasts at least should give an idea of the style 05:50:26 Not particularly 05:50:42 maybe we all can review or a demo talk would help 05:52:02 This seems to be so easy but it is not :P 05:52:49 Ya I don't have much experience but it sounds fun at least - I think it is pretty informal will not be very technical, so ya 05:53:03 Maybe we can discuss more off-line 05:53:17 juhp +1 05:53:57 okay so moving onto next ticket 05:54:06 #info #135: Fedora 33 Bug triaging 05:54:12 #link https://pagure.io/i18n/issue/135 05:54:56 i can see 49 open ticket toady 05:55:51 okay lets keep working on it guys and get the count low. 05:56:15 any specific bug to be discussed here ? 05:57:34 s/toady/today 05:58:00 There is a kde bug about installing ibus-table 05:58:14 or rather rfe 05:58:51 Ah I see mfabian was already over it :-) 06:00:22 Ok nvm 06:01:08 lets move onto next ticket if nothing more to discuss 06:01:32 Yes I think many of us have a few bugs to triage there 06:03:01 #info #134: Tracker for Fedora 35 Changes 06:03:07 #link https://pagure.io/i18n/issue/134 06:04:29 anything to update here ? 06:05:53 I think paragan posted a change 06:06:04 for final Inscript2 06:06:05 yes I added link there 06:06:16 let me add here also 06:06:18 what are your thoughts removing myspell dir and use hunspell 06:06:25 #info https://fedoraproject.org/wiki/Changes/Enhanced_Inscript_as_default_Indic_IM 06:06:28 and create sym link to myspell 06:06:32 I also heard fujiwara is planning Change related to ibus 06:07:06 vishalvvr: I think it is a good idea and we could combine with the encoding change too 06:07:39 okay 06:07:54 Though that might need cooperation from package owners and/or ProvenPackager to achieve 06:08:45 mfabian and paragan any interest? 06:09:11 Then maybe we could revisit nuspell for F36 or later? 06:09:51 It would be good to draft a Change proposal seen if we want to do that 06:09:54 soon 06:10:50 true 06:11:08 any more thoughts/suggestion on the same? 06:11:44 Alternatively we could target F36 but as such the changes are quite small and probably combining them would reduce the overall amount of work 06:12:01 I mean directory change and encoding 06:12:32 How about drafting a Change and gathering forces? :) 06:12:48 juhp +1 06:13:19 Dunno if this would be SystemWide Change though? 06:13:24 Perhaps? 06:13:53 Cos then the submission deadline is tomorrow 06:13:59 how many packages is depending on it? 06:14:03 I can help being proven packager 06:14:55 Hmm 06:15:07 $ pagure list hunspell-* | wc -l 06:15:09 121 06:16:15 But basically all the applications is accessing dictionaries through API right? 06:16:22 Actually I dunno how the directory change affect dictionary packages 06:16:42 I think so 06:16:56 it should not I feel 06:18:00 then self-contained may be sufficient I suppose. 06:19:30 I have no /usr/share/hunspell on my system 06:19:39 So I can of wonder... 06:19:52 * I kind of 06:20:10 its myspell no? 06:20:19 Indeed that is my point 06:21:17 Well someone needs check/scope this 06:21:21 on a few packages 06:21:42 I forget how rpm handles renaming dirs to symlink for example 06:21:46 that is what I suggested last time, we need minimal changed packages in Copr to test 06:21:57 Yes that would be good 06:22:12 Today really :-| 06:22:27 Well maybe F36 is more realistic at this point 06:22:39 if someone could guide me on that then i can do it 06:23:05 vishalvvr: well you just need to update some hunspell packages to use the new dir 06:23:10 yeah it looks now F36 Change 06:23:19 juhp, okay 06:23:30 Well ideally hunspell too to use it 06:23:53 I think you are a bit familiar with that side from nuspell 06:25:06 juhp, yes 06:25:11 hunspell-filesystem owns /usr/share/myspell 06:26:17 Dunno if we could still target the encoding side of it - that could probably be SelfContained I feel 06:26:46 and can be done progressively unlike the directory change perhaps 06:27:01 Filing bugs might be a good start 06:27:29 Anyone any idea how many dictionaries are not using UTF-8? 06:28:00 Anyway we are running out of time... 06:28:49 okay sure let me file a bug for the same, and discuss in the next 06:28:57 Thanks 06:29:26 moving onto next ticket 06:29:29 #info #131: review/update @fonts group default packages: non-language specific extra fonts etc 06:29:33 #link https://pagure.io/i18n/issue/131 06:30:04 Okay I posted earlier asking about pt-sans-fonts 06:30:19 Let's see if any response 06:30:40 okay 06:31:13 It is probably too late for Source Pro for F35 but maybe later we can bring it to the desktop/workstation for discussion 06:32:36 thanks for the update juhp, anything more to discuss in this ticket 06:33:56 okay then moving into next topic 06:33:59 #topic Open Floor 06:36:11 Let's close the meeting if nothing more to discuss 06:37:16 Thank you all for joining this meeting :) 06:37:24 #endmeeting