05:36:00 #startmeeting i18n 05:36:00 Meeting started Tue Jul 24 05:36:00 2018 UTC. 05:36:00 This meeting is logged and archived in a public location. 05:36:00 The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:36:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:36:00 The meeting name has been set to 'i18n' 05:36:00 #meetingname i18n 05:36:00 The meeting name has been set to 'i18n' 05:36:00 #topic agenda and roll call 05:36:01 #link https://fedoraproject.org/wiki/I18N/Meetings/2018-07-24 05:36:09 ☺ 05:36:09 hi 05:37:12 hi 05:37:14 hi 05:37:26 hello 05:38:35 hi :) 05:39:16 #chair mfabian suanand pwu spathare__ juhp pravins 05:39:16 Current chairs: juhp mfabian paragan pravins pwu spathare__ suanand 05:39:22 lets start the meeting 05:39:27 we have less agenda today 05:39:30 hi 05:39:42 #chair pyadav 05:39:42 Current chairs: juhp mfabian paragan pravins pwu pyadav spathare__ suanand 05:39:54 #topic Upcoming schedule 05:39:54 #info 2018-07-03 Change Checkpoint: Proposal submission deadline (System Wide Changes) 05:39:54 #info 2018-07-11 Mass Rebuild 05:39:54 #info 2018-07-24 Change Checkpoint: Proposal submission deadline (Self Contained Changes) 05:39:54 #info 2018-07-31 Software String Freeze 05:39:55 hi 05:40:33 so today is Self Change proposal deadline 05:40:50 also Software String Freeze has been announced on devel list 05:41:54 that was reminder email 05:41:58 hi 05:42:06 #chair fujiwarat tagoh 05:42:06 Current chairs: fujiwarat juhp mfabian paragan pravins pwu pyadav spathare__ suanand tagoh 05:42:43 If you have got any mass rebuild bugs for rawhide or F28, try to fix it as soon as possible 05:43:05 anyone have the link? 05:43:35 yes for the mass rebuild failures 05:44:07 * pwu got several FTBFS bugs because of python 2.x. 05:44:13 well you should have got the bugs reported already 05:44:34 https://kojipkgs.fedoraproject.org/mass-rebuild/f29-failures.html 05:44:54 pwu: I fixed the google-noto-emoji-fonts one yesterday, I just saw the bugzilla mail and didn’t notice that it was assigned to you at first. 05:45:20 mfabian++ 05:45:26 mfabian: Thanks! 05:45:45 mfabian++ 05:46:20 I got 5 failed FTBFS bugs. 05:47:43 good to fix them as soon as possible 05:48:19 for python issues, python packaging team is very good in helping and fixing the issues in porting to python3 05:49:31 okay let's move 05:49:34 yes, I have seen some people helping to fix failures 05:51:07 #topic No assignee issues 05:51:07 #info #98: Hackathon during flock 2018 (pravins) 05:51:07 #link https://pagure.io/i18n/issue/98 05:51:25 anything to discuss here? 05:51:59 (or dependency breakage actually) 05:52:04 we already have few points in this ticket for agenda 05:52:39 We renamed the hackfest session to "i18n development and testing" I think 05:53:26 https://pagure.io/flock/issue/33 05:54:40 okay 05:54:58 yes 05:55:16 I don't think the schedule is out yet 05:55:46 yes 05:56:32 I think we will do a little more planning ahead of the event 05:57:46 sure 05:59:18 long pause :) 05:59:38 lets move to next ticket 05:59:47 #info #99: Tracker for Fedora 29 Changes (pnemade) 05:59:48 #link https://pagure.io/i18n/issue/99 06:00:16 I see pravins has worked on the Liberation fonts2 Change proposal 06:00:23 pravins, thanks for your help 06:00:45 Change has been announced yesterday on devel list 06:01:08 good 06:01:24 so I think we have got 3 Changes in total for Fedora 29 06:01:44 I will create separate tickets to track them 06:02:23 next ticket 06:02:36 #info #100: Fedora 27 Bug triaging (pnemade) 06:02:36 #link https://pagure.io/i18n/issue/100 06:02:49 This activity is going on by QE team 06:03:05 I see some of the bugs got traiged already 06:05:28 #topic Open Floor 06:05:32 anything to discuss here? 06:06:12 if not then will close the meeting in 2 minutes :) 06:06:28 I heard from tagoh that the final changes for the Noto CJK change have landed in Rawhide 06:06:48 Could we discuss https://pagure.io/i18n/issue/103 ? 06:07:03 I dunno if it came up while I was away last month 06:07:15 about #fedora-i18n channel 06:07:31 I did not pick it as you were away and I did not see any updates to this ticket 06:07:41 okay :) 06:07:46 updates? 06:07:53 bbarve, we may need arrange time for the QA for Noto CJK as juhp pingd in email and ticket? 06:07:53 yes, Noto is ready for testing on rawhide now 06:08:06 great tagoh++ 06:08:14 juhp, updates mean what you were expecting 06:08:18 lijli: yes please 06:08:49 paragan: well the motivation for the ticket was to start using #fedora-i18n again 06:08:49 lijli, juhp yep sure. Will plan for the tests 06:08:57 thanks!! 06:09:03 thanks bbarve 06:09:18 as per the title :) 06:09:48 we could have a meeting tag too :) 06:10:51 Both #fedora-g11n and #fedora-i18n are largely unused nowadays 06:11:38 The last sentence also asks if we are happy with our Fedora subproject name "I18n"? 06:12:02 I think we should promote the fedora i18n "brand" more 06:12:22 since fedora g11n seems no longer so active? 06:12:51 yeah, we are more using trans and i18n 06:12:56 not that much g11n. 06:13:03 right 06:13:46 yeah, and we don't have a group named g11n :) 06:13:51 I think the name question was brought up by tagoh 06:14:35 I think the keyword 'g11n' might work for the internal discussion in each company. 06:15:26 okay so is there any proposal for this ticket to resolve it? 06:15:36 yes I did. because people still sometimes confuse the name. it seems not that obvious for them 06:20:09 fujiwarat: g11n is common nowadays? 06:20:18 tagoh: right 06:20:42 Is something like "i18n software development" clearer? 06:21:14 I can't really think of a clearer short-name - something including the word language perhaps? 06:21:42 paragan: well simplest would be for everyone to join #fedora-i18n again 06:21:50 that was the original intention 06:22:42 juhp: Did you see any people to find g11n chat? 06:22:44 i think we need a separate ticket for any rename discussion 06:24:49 fujiwarat: are we seeing more people coming to #fedora-g11n?? Not that I am aware, but of course #fedora-g11n is bigger channel since both trans and i18n people there 06:26:37 juhp: I don't think many people to search g11n but i18n or l10n or translation. 06:26:52 How do people feel about #fedora-i18n vs #fedora-g11n? 06:26:55 fujiwarat: right 06:27:11 fujiwarat: I think I understood your comment now thanks 06:27:28 :) 06:28:29 So do you all want to rejoin to #fedora-i18n channel? 06:28:45 A few of us hardcores holdouts never left :) 06:28:49 okay I have joined there and added it to autojoin channel list :) 06:29:23 I left as we have topic for that channel as deprecated channel 06:29:53 :) 06:30:20 but still, good to have on g11n channel as well. 06:30:31 oaky 06:30:33 okay 06:30:40 paragan: good point 06:30:45 It magically changed 06:30:49 now 06:30:52 ;) 06:32:15 great 06:33:12 I think if everyone joins we could have more communication there 06:33:37 any objections? 06:33:57 no 06:34:14 * suanand no 06:35:11 tagoh, mfabian, suanand, vishal_vr? 06:35:16 nope 06:35:22 nope 06:35:23 No objections. 06:35:29 juhp, no 06:35:59 So please join.... 06:38:39 It might be good to create fedora-qe and fedora-l10n 06:39:31 we have general #fedora-qa and #fedora-l10n channel 06:39:54 indeed 06:39:54 ok, I see. 06:41:07 #fedora-l10n shows "moved to #fedora-g11n" :). 06:44:55 Yes #fedora-i18n did too 06:45:09 well that is up to Fedora L10n to decide 06:45:25 I think we are over time? 06:47:33 so should we close? 06:48:26 Thanks all who came to this meeting 06:48:31 #endmeeting