06:30:28 #startmeeting i18n 06:30:28 Meeting started Wed Mar 14 06:30:28 2018 UTC. The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:30:28 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:30:28 The meeting name has been set to 'i18n' 06:30:28 #meetingname i18n 06:30:28 The meeting name has been set to 'i18n' 06:30:28 #topic agenda and roll call 06:30:28 #link https://fedoraproject.org/wiki/I18N/Meetings/2018-03-14 06:30:33 hi .. 06:30:39 hi 06:30:53 hi 06:30:59 hi 06:31:13 hi 06:31:36 hi 06:32:21 #chair suanand_ tagoh epico bhavin192 pyadav vishalvvr 06:32:21 Current chairs: bhavin192 epico paragan pyadav suanand_ tagoh vishalvvr 06:32:24 Hi all 06:32:35 welcome to bi-weekly Fedora i18n meeting 06:33:09 Yesterday only we had our Fedora i18n test day https://fedoraproject.org/wiki/Test_Day:2018-03-13_I18N_Test_Day 06:33:30 Hopefully everyone has completed testing Fedora 28 and submitted results to results page 06:33:31 hello 06:33:39 #chair juhp 06:33:39 Current chairs: bhavin192 epico juhp paragan pyadav suanand_ tagoh vishalvvr 06:34:00 I am glad that we got good number of testers this time 06:34:27 I will generate the Summary of this test day soon and will share the results on the test day page 06:34:35 Hi☺ 06:34:37 also we can discuss on that in next meeting 06:34:41 #chair mfabian 06:34:41 Current chairs: bhavin192 epico juhp mfabian paragan pyadav suanand_ tagoh vishalvvr 06:35:44 thank you all who participated in i18n test day 06:35:44 paragan: thanks 06:35:50 Yes good to see 06:37:14 okay let's have a look at current Fedora 28 schedule 06:37:25 #topic Upcoming schedule 06:37:25 #info 2018-03-06 Beta Freeze (*) 06:37:25 #info 2018-03-27 Beta Release (Preferred Target) 06:37:25 #info 2018-04-03 Beta Release (Target #1) 06:37:25 #info 2018-04-17 Final Freeze (*) 06:37:37 so we are in beta freeze 06:38:30 your package updates will only be in updates-testing repository 06:38:38 even if it reached to stable karma 06:39:00 there is yet no confirmation on when to release Fedora 28 06:39:10 as there are some issues going on 06:39:51 if anyone want to know more about them then they are listed here -> https://pagure.io/fesco/issue/1862 06:41:13 Keep testing Fedora 28 as we saw some changes in anaconda spokes and also gnome-initial-setup 06:42:16 I saw yesterday Gnome 3.28.0 megaupdate has been submitted https://bodhi.fedoraproject.org/updates/FEDORA-2018-5ebe0eb1f2 06:42:25 not yet in testing repo 06:42:34 maybe by tomorrow it will be available 06:44:17 yes 06:44:30 thanks for the fesco issue link 06:45:04 if nothing more to discuss here then let's move to tickets 06:45:20 I am not picking all the Change tickets today but only tracker 06:45:25 hi 06:45:41 going by serial numbers 06:45:50 #topic No assignee issues 06:45:50 #info #78: package Liberation Classic Font in Fedora (pnemade) 06:45:50 #link https://pagure.io/i18n/issue/78 06:45:59 #chair pravins 06:45:59 Current chairs: bhavin192 epico juhp mfabian paragan pravins pyadav suanand_ tagoh vishalvvr 06:46:13 hmm, this is still pending on me. :( 06:46:23 any eta? 06:46:25 i did not find time in last 2 weeks. 06:46:37 Just an update 06:46:39 hi 06:47:16 pravins: how long is the process to make an upstream release? :) 06:47:26 I am going to bump the version of existing liberation-fonts package from 1.07.4 to 2.00.1 06:47:34 i agree, i have been very late into this. 06:47:38 for rawhide? 06:47:42 in fact want to do it as soon as possible, 06:47:44 for rawhide 06:47:48 pravins: no, just asking, curious 06:48:04 hopefully there should not be anything to check 06:48:18 just the version bump should work 06:48:21 if, i am not doing before next meeting. Will ask someone else to take over it and i will just provide guidance 06:48:43 personally I feel we don't really need LiberationOne though 06:49:00 paragan: that is fine. But there is one issue. Liberation-fonts 1.07 has narrow and liberation 2.00 does not have narrow. 06:49:02 but no doubt someone will disagree 06:49:11 pravins: you saw tagoh's screenshots? 06:49:21 i think, we already have different package for liberation-narrow. 06:49:23 pravins: ah 06:49:49 pravins: ah yes we do 06:50:04 or did ;-) 06:50:09 lol 06:50:12 no, i did not saw tagoh's screenshot. 06:50:14 f19 06:50:23 yeah, it might be "did" ;) 06:50:45 .bug 1375061 06:50:47 juhp: Bug 1375061 – RFE: try switching to Liberation Fonts 2 again - https://bugzilla.redhat.com/1375061 06:50:50 pravins: very much so 06:51:41 pravins: it is a subpackage of liberation-fonts 06:51:45 most of the time, even my spectacle does not help to find hinting difference ;) 06:52:01 well there are certainly differences 06:52:13 for some glyphs at least 06:52:18 9 06:52:24 and some sizes 06:52:29 pravins, thanks then that is easy update for liberation-fonts :) 06:52:38 for larger sizes not very much 06:53:00 yeah, for larger size not much. In fact, if one explore outline inside fontforge, those are ditto same. 06:53:19 Anyone have concerns on using liberation 2.00 ? 06:53:36 pravins: okay 06:53:47 the approach we missed last time was providing backup for old version. I regret, we did not tried to provide liberation 1.07.4 with different name in F21 06:53:51 s/using/moving to/ 06:54:02 okay 06:54:17 No concern, since we are more determined to provide backward compatibility to end-users this time. 06:54:28 pravins: how long is the maintainer process to roll a new release? 06:54:48 need to build binary tarballs etc, right hmm 06:54:52 nice comments by Thorsten Leemhuis 06:55:14 Anyway I think more people are in favour of moving to 2 than not 06:55:34 so I suggest we go ahead for Rawhide first? 06:56:07 juhp: sounds good to me 06:56:14 yes, rawhide. 06:56:36 paragan: can go ahead with bumping existing version and As soon as i do new release, can build new version. 06:56:54 not many fixing 06:57:00 but yeah for liberation1 wait for me :) 06:57:14 I am building it now in rawhide 06:57:19 pravins: you are planning 2.00.2 release? 06:57:26 paragan: great! 06:57:37 pravins, how can we get liberation-narrow then? 06:57:46 its dropped from liberation-fonts spec 06:57:55 it is packaged separately 06:57:57 * pravins checking 06:58:10 pravins: also is Liberation1 a better name? 06:58:59 https://admin.fedoraproject.org/pkgdb/package/rpms/liberation-narrow-fonts/ 06:59:38 pravins: that's a dead package, right? 06:59:40 juhp: yeah, because of naming issue liberation classic work pending. We have limitation on adding more characters to existing name. 06:59:43 this does not look good 06:59:44 https://koji.fedoraproject.org/koji/packageinfo?packageID=14374 06:59:46 juggler[m]: yes 07:00:05 pravins: no, I mean Liberation1 rather than LiberationOne 07:00:10 hi 07:00:17 I hope narrow users will loose then this font in rawhide 07:00:23 this is dead, since we re-packaged liberation 1.07 in Fedora. 07:00:36 s/hope/think/ 07:00:44 yeah shrug 07:00:50 paragan: we can use same spec and enable it for Fedora rawhide. 07:00:56 dunno how important narrow is? 07:01:04 oh 07:01:07 pravins, how? 07:01:10 it is important, it is also replacement of some Windows font. 07:01:12 adding new source for narrow? 07:01:14 I see 07:01:25 * juhp is also confused 07:01:28 where is narrow 2.00.1 07:01:41 what i think. 07:01:47 1. Package liberation 2.00.1 07:01:54 if upstream tarball is separate we should package it separately 07:02:04 Maybe pravins means for Liberation 1 07:02:12 2. Pacakge liberation-narrow - User liberation 1.07.4 and delete all fonts except narrow. (I used same approach earlier) 07:02:34 3. Package Liberation 1.07.4 with new name, will remove Liberation narrow in new package. 07:03:25 hmm 07:03:43 lets use step by step approach? 07:03:52 paragan ^^ 07:03:57 its actually confusing :( 07:04:29 1 understood 07:04:32 why is the step 2 and 3 needed? 07:04:34 2 what is this? 07:05:03 Step 2: only to get LiberationNarrow pacakge from liberation 1.07.3 in Fedora. 07:05:14 3 if we need to provide narrow then we need to package it separately or we can even include in main liberation-fonts spec 07:05:17 tagoh: 2 to get narrow 07:05:24 3 to get LiberationOne 07:06:17 so no 2 upstream releases of narrow font? 07:06:23 pravins: was there an upstream plan for Narrow? 07:06:55 Good question 07:07:05 missing changelog etc sounds not a good idea to me. and we already have 1.07.4 in fedora so should we simply package narrow as new ? 07:07:22 +1 07:07:50 Could narrow become a separate source package again? 07:08:08 juhp: yeah, that is good suggestion. Lets split Narrow and a new package. 07:08:10 well maybe using the current tarball would be okay... mmm 07:08:13 okay 07:08:16 upstream repository itself. 07:08:24 or add narrow back to 1.07.5 or so and update the package? 07:08:32 please decide for once and forever 07:08:39 for narrow 07:09:00 yeah, making it different Repo will resolve all issues in future. 07:09:10 s/Repo/gitrepo 07:09:23 tagoh: erm it's already in .4 07:09:45 juhp: aha 07:09:57 tagoh: Narrow is only Liberation 1 07:10:10 oh ok 07:10:14 ah, okay. seems confused 07:10:17 that's the problem 07:10:18 What happens: for switching to Liberation 2, i created new package of Narrow. Then we again rolled back, so again back to earlier stuff :) 07:10:30 pravins: ah 07:10:45 so we will have liberation2 and liberationNarrow1 in rawhide if both packaged and updated? 07:10:54 so we can just revamp liberation-narrow-fonts again, no problem 07:11:17 no need to rename Narrow, since no conflict with Liberation2. 07:11:22 right 07:11:30 so just restore dead package right? 07:11:30 we just bring it back 07:11:33 nod 07:11:34 yes 07:11:42 pravins: but where is the source? 07:11:49 ok 07:11:54 paragan: yeah and once i will release new liberation-narrow update source and s-url 07:12:16 okay 07:12:23 so next rawhide will contain only liberation2 fonts without narrow 07:12:30 once we restore narrow font 07:12:37 perfect !! 07:12:46 the next to next rawhide will have all liberation mix fonts 07:13:11 next to next rawhide means? 07:13:26 I mean whenever package gets restored 07:13:31 yes 07:13:34 after that rawhide compose 07:13:39 okay 07:14:39 lets now execute it !! 07:14:49 it is perfectly fine, if there is still confusion ;) 07:15:43 okay 07:16:22 good discussion 07:16:28 lets move to other tickets 07:17:39 #info #82: Fedora 28 i18n test day (pnemade) 07:17:39 #link https://pagure.io/i18n/issue/82 07:18:01 I think I have given the update so nothing more to add here 07:18:44 #info if anyone still missing then complete your i18n test day testing and submit the results 07:19:06 #info test day results will be shared next meeting 07:19:26 * epico will fill it. 07:19:45 * pravins login after 15min. 07:20:18 #info #83: Tracker for Fedora 28 Changes (pnemade) 07:20:18 #link https://pagure.io/i18n/issue/83 07:20:40 I think our all changes are completed and tested in testday event 07:20:54 thank you all Change owners for completing them on time :) 07:22:57 next ticket 07:23:05 #info #84: Fedora 26 Bug triaging (pnemade) 07:23:06 #link https://pagure.io/i18n/issue/84 07:23:35 this has been worked by QA people and only few bugs are pending in F26 queue 07:23:53 not much to update on this ticket 07:24:41 great 07:24:47 #info today remaining bugs count against F26 is 10 07:25:42 mostly ibus abrt bugs which can be closed with note that please test against F28 or add needinfo and if no update close after one month with INSUFFICIENT_DATA 07:26:04 last ticket 07:26:38 #info #85: Docs Beats for Fedora 28 (pnemade) 07:26:39 #link https://pagure.io/i18n/issue/85 07:28:03 I think all the Change submitted already got their docs ticket https://pagure.io/fedora-docs/release-notes/issues 07:28:40 fujiwarat, tagoh epico mfabian I request all the Change owners to add if needed more information in their own ticket 07:30:23 should we track the individual relnotes? 07:30:24 #topic Open Floor 07:30:32 not sure 07:30:41 or just pray for the best? ;) 07:30:44 there are tickets per Change t 07:30:58 Could we at least add them to the ticket? 07:31:07 sure that can be done 07:31:13 or ticket(s) :) 07:31:16 okay 07:31:29 I would just like more eyes on the relnotes for the changes 07:31:42 I would like to review them anyway 07:31:59 thanks 07:33:29 okay 07:33:50 Anything to discuss in this Open Floor? 07:34:13 Do we need to change the time for this meeting? 07:34:18 ah 07:34:29 good question 07:35:26 I was wanting to suggest that due to a kind of conflict - if we can find another suitable day? 07:36:06 maybe Tue or Thu? 07:36:24 or any other day actually 07:37:34 anyone have any days where they are not available? 07:37:46 hmm we already lost pravins 07:38:03 perhaps we could also discuss on list? 07:39:23 many any day could work... 07:39:27 maybe * 07:40:11 well it's not super urgent, I could also open a ticket 07:40:40 paragan: any thoughts? 07:40:51 okay good to open a ticket if needed to change the time 07:40:52 we are over time I think 07:40:56 okay will do 07:40:57 yes 07:41:06 closing the meeting in 2 min 07:42:30 #endmeeting