06:00:23 #startmeeting i18n 06:00:23 Meeting started Wed Feb 15 06:00:23 2017 UTC. The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:00:23 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:00:23 The meeting name has been set to 'i18n' 06:00:33 hi 06:00:37 #meetingname i18n 06:00:37 The meeting name has been set to 'i18n' 06:00:42 hi 06:00:47 #topic agenda and roll call 06:00:54 Hi! 06:00:55 #link https://fedoraproject.org/wiki/I18N/Meetings/2017-02-15 06:02:04 #chair fujiwarat tagoh_ mfabian 06:02:04 Current chairs: fujiwarat mfabian paragan tagoh_ 06:02:06 hi paragan 😃 06:02:14 hi 06:02:27 #chair pravins juhp 06:02:27 Current chairs: fujiwarat juhp mfabian paragan pravins tagoh_ 06:02:30 Hi all 06:02:44 hi 06:03:04 Hi suanand 06:03:10 #chair suanand 06:03:10 Current chairs: fujiwarat juhp mfabian paragan pravins suanand tagoh_ 06:04:09 * juhp wonders how the nextmeetings command works - seems this meeting does not appear? 06:04:35 ah nevermind maybe it does 06:04:36 #topic Upcoming schedule 06:04:36 #info 2017-02-07 Mass Rebuild 06:04:36 #info 2017-02-21 Change Checkpoint: Proposal submission deadline (Self Contained Changes) 06:04:36 #info 2017-02-28 Change Checkpoint: Completion deadline (testable) 06:04:36 #info 2017-03-07 Alpha Freeze 06:04:48 hi 06:05:02 juhp: we need to add appointment in calendar for it, i think we do have one. 06:05:31 yeah 06:05:47 but may be not in sync. 06:06:31 #chair epico 06:06:31 Current chairs: epico fujiwarat juhp mfabian paragan pravins suanand tagoh_ 06:06:39 (well I was offline last night unusually - so log didn't reflect today) 06:06:54 So last weekend Fedora mass rebuild has been completed 06:07:09 yes 06:07:33 we have ticket for that. we will discuss later on 06:07:56 Anyone still got any change to be submitted? 06:08:30 also whoever got Change accepted need to check on its completion before 2017-02-28 06:08:36 libpinyin 2.0 changes 06:09:00 epico, if you want you can submit self-contained change before 2017-02-21 06:09:53 sure, will do 06:10:03 thanks 06:10:23 lets move to our tickets/issues 06:11:02 #topic Outstanding issue 06:11:09 #info #69: Fedora 26 planning 06:11:10 #link https://pagure.io/i18n/issue/69 06:12:20 epico, after you submit change please add link to the submitted change to https://pagure.io/i18n/issue/69 06:13:04 okay 06:14:17 any more on the fontconfig Change? 06:14:44 nope 06:15:45 having a look at FTBFS issues on other packages first... will do work on fontconfig in this week. 06:17:34 #topic No assignee issues 06:17:35 #info #72: Proposal - I18n FAD in 2017 06:17:35 #link https://pagure.io/i18n/issue/72 06:18:19 I am still not clear on Dates and Venue 06:18:44 Actually depending upon date or month we have to decide tasks. 06:19:35 2017-05-30 F26 final release. So we are definitely doing it in F27 schedule timeline. 06:21:19 I think should decide theme/goal for the FAD first 06:21:59 Even this can work. My only concern was: Last time planning for F24 was one of imp. task at our hand. 06:22:02 so something like it. 06:22:23 I think Theme can be... Keeping Fedora contemporary from i18n side. 06:22:32 Latest fonts, latest input methods 06:22:44 and update locales.. such that Unicode CLDR 06:22:49 s/updated 06:23:24 saying that, we also have i18n tasks for Cloud and containers tech. i.e. flatpack 06:23:41 does above typed theme looks good? 06:24:06 so a F27 (or F28) planning meeting? 06:24:14 probably makes good sense 06:24:35 FAD is probably too short to achieve a lot of code etc 06:24:41 and history says. This FAD planning serve us for 2/3 years releases :) 06:24:46 yeah 06:25:34 great. I will add this information in FAD page. 06:25:43 november again looks good to me. 06:25:47 is there still time to arrange as a F27 planning FAD or should we target F28? (of course we don't know the length of those cycles yet either....) 06:26:08 FESCo is thinking to remove alpha freeze/compose/release but looks not yet for f27 maybe from f28+ 06:26:18 oh 06:26:39 paragan: what does that mean? 06:26:51 ah no alpha... I see 06:26:56 hmmmm 06:27:05 * juhp wonders 06:27:17 every day compose is like alpha 06:27:23 okay 06:27:39 make sense 06:27:46 but then no alpha blockers... 06:28:09 well it could save a week or two perhaps 06:28:28 yeah that needs some discussion which will occur when a new Change is submitted "Alpha Removal" Change 06:28:36 aha 06:29:06 more on it https://pagure.io/fesco/issue/1681#comment-75539 06:30:33 pravins, please update ticket when you have some more information 06:30:54 paragan: updated this discussion on ticket, will update page soon. 06:31:07 thanks 06:31:10 #info #63: Fedora 24 Bug triaging 06:31:10 #link https://pagure.io/i18n/issue/63 06:32:56 all please keep traiging their bugs 06:33:09 and see if they can be fixed/closed 06:33:28 sure. 06:34:29 #info #73: F26 mass rebuild fixes 06:34:29 #link https://pagure.io/i18n/issue/73 06:34:58 Please check the ticket description for the links and see if you got any package which is FTBFS 06:35:07 fix it as soon as possible :) 06:35:48 thanks for opening that 06:36:01 I had been waiting for the mail 06:40:37 lets move 06:40:55 #topic Open Floor 06:41:01 anyone got anything to discuss here? 06:41:10 https://bugzilla.redhat.com/show_bug.cgi?id=1413840 06:41:27 .bug 1413840 06:41:27 fujiwarat: Bug 1413840 – The various ibus-* modules tail to refresh gtk's immodule cache in every instance - https://bugzilla.redhat.com/1413840 06:41:36 http://pkgs.fedoraproject.org/cgit/rpms/ibus.git/tree/ibus.spec 06:41:49 Do you have any ideas to fix it? 06:43:11 checking 06:45:11 will check on it later on 06:46:44 "Note that because of the logic this only applies on the initial install, but the problem will cure itself on upgrades." 06:47:02 hmm 06:49:03 fujiwarat: might be missing ambiguous Requires(post) as the reporter suggested? 06:49:10 s/missing// 06:49:44 you could append %{_isa} I think 06:50:25 to enforce the correct arch 06:51:50 I don't know the recommended pre/post about 'if [ "$1" -eq 0 ]'. 06:53:57 any comments are welcome after this meeting. 06:56:10 #endmeeting