06:00:53 #startmeeting i18n 06:00:54 Meeting started Wed Mar 15 06:00:53 2017 UTC. The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:00:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:00:54 The meeting name has been set to 'i18n' 06:00:54 #meetingname i18n 06:00:54 The meeting name has been set to 'i18n' 06:00:54 #topic agenda and roll call 06:00:54 #link https://fedoraproject.org/wiki/I18N/Meetings/2017-03-15 06:01:03 hi 06:01:08 hi 06:01:11 ☺ 06:01:36 hi 😁 06:02:00 Hi all 06:02:07 hi 06:02:17 #chair tagoh suanand mfabian pravins epico 06:02:17 Current chairs: epico mfabian paragan pravins suanand tagoh 06:02:33 Hi 06:03:03 epico, anish_ hi 06:03:16 #chair anish_ 06:03:16 Current chairs: anish_ epico mfabian paragan pravins suanand tagoh 06:03:27 hi 06:03:37 juhp, hi 06:03:40 #chair juhp 06:03:40 Current chairs: anish_ epico juhp mfabian paragan pravins suanand tagoh 06:03:45 Let's start our meeting now 06:04:14 we will first look into next upcoming schedule milestones 06:04:17 #topic Upcoming schedule 06:04:17 #info 2017-02-28 Change Checkpoint: Completion deadline (testable) 06:04:17 #info 2017-03-07 Alpha Freeze 06:04:17 #info 2017-03-07 Software String Freeze 06:04:17 #info 2017-03-07 Bodhi activation point 06:04:18 #info 2017-03-21 Alpha release 06:04:34 so we are in F26 Alpha Freeze 06:05:20 Has anyone got any issues to fix for Alpha release? 06:05:55 https://qa.fedoraproject.org/blockerbugs/milestone/26/alpha/buglist 06:06:58 Last week I saw we were asked to provide some comment on bug https://bugzilla.redhat.com/show_bug.cgi?id=1405539 06:07:22 Thanks juhp for looking into this bug 06:07:34 welcome 06:07:46 it was discussed a bit in the WS WG meeting too 06:07:50 which I saw now removed from blocker list 06:08:15 and further discussion is going on that bug 06:08:16 Alpha blocket list? 06:08:31 yes 06:08:36 ok 06:09:27 I think its Rejected totally and will not be considered as blocker for any upcoming Fedora 26 releases (Beta and Final) 06:09:38 hmm ok 06:09:58 Hope we will see some better solution for that bug 06:10:06 I was hoping it might still be considered for final.... anyway hope something can be done to improve it 06:10:11 nod 06:10:18 yeah, we do have some more time for it. 06:11:59 next topic 06:12:25 #topic No assignee issues 06:12:26 #info #73: F26 mass rebuild fixes 06:12:26 #link https://pagure.io/i18n/issue/73 06:12:40 anyone still got any FTBFS bug to fix? 06:13:02 I think I am having only one now which I will fix this week 06:13:37 Few font packages failed to build due to bug in fontforge python module 06:13:39 thanks i will fix mine 06:13:55 anish_, :) 06:14:31 That has been reported upstream, patch has been provided which is merged in upstream and I have built that patch in Fedora 06:14:45 that's good 06:15:03 which helped to build these font packages now without any issue. 06:15:06 thanks paragan for fixes in fontforge. 06:15:18 you welcome :) 06:15:19 i did build for Lohit fonts yesterday with upstream new release. 06:16:14 pravins, thanks for fixing them now 06:17:00 :) 06:17:48 Let's revisit this ticket next meeting and close accordingly. 06:18:44 #info #72: Proposal - I18n FAD in 2017 06:18:45 #link https://pagure.io/i18n/issue/72 06:20:04 pravins, you want to update here? 06:20:05 aha, FAD 06:20:15 Thanks for all who added name in FAD proposal page. 06:20:47 I think, we must freeze date and locations prior moving ahead. 06:21:12 Considering success of our Last FAD at Japan i think we should do it again at Japan 06:21:31 what other members think? 06:22:30 yeah last time's FAD was good 06:23:04 last time, due to participation of Zanata and Translation team it was actually like mini conference. 06:23:18 yeah 06:23:19 but this time we are planning to make it short and more dedicated FAD for some tasks 06:23:31 yeah 06:23:39 may want to see how the community in other countries is :) 06:24:36 After Japan, i think second option we have is India. Brisbane is very costly. 06:24:51 Sydney would be another option 06:24:52 * pravins would love to be host :) 06:25:15 anish_: but at Sydney stay and conference room will cost us huge. 06:25:46 hmm if we can have budget then I would like to host it over here 06:26:48 Agree, but i think we will have max $5000 06:27:16 We can fly maximum 3-4 people and rest will need for accommodation and other items. 06:27:33 At present we have. 06:27:55 1. 3 people at India, 3 Japan, 1 at China, 1 Germany and 1 at Sydney. 06:28:30 so, from cost perspective either India or Japan. 06:28:33 makes more sense. 06:29:52 3rd option, as we thought do it aligning some conference. 06:29:59 I see GUADEC is happening in UK 06:30:14 But it will be short duration 06:30:16 https://2017.guadec.org 06:30:23 its in Jan 06:30:27 ohh 06:30:34 sorry its in June 06:30:36 i guess 06:30:49 28 jul-2ndaug 06:30:56 yeah 06:31:10 It make sense to host, i18n FAd with GUADEC 06:31:21 juhp: how do you think? 06:31:48 interesting idea 06:32:08 lets work out on this idea and see if we can actually make it. 06:32:25 I hope, we can get some concession from GUADEC for accommodation. 06:32:58 and, i am sure we will have more members to join from GUACED as well for FAD. 06:33:07 there is also Flock but again means a lot of travellers 06:33:27 flock is in US, very unrealistic from budget perspective. 06:33:39 UK seems to be more expensive than JP and cost of travel would be more than SYD 06:33:50 Personally I think a small separate focused FAD in APAC would be better probably 06:34:47 having together with some conference will help us to have more talks in conference..more i18n presence followed by FAD. 06:34:48 combining with another event could be a distraction too 06:34:58 that is true of course 06:35:03 GUADEC people give 80% accommodation for speakers 06:35:19 yeah, distraction point is valid. We will need more time that FAD. 06:35:29 say, if we decide 2 days FAD + 2 days conference. 06:35:53 anish_: is more familiar with GUADEC :) 06:36:39 present open options are: 1. APAC (India or Japan) 2. GUADEC (28 Jul - 2Aug) 06:37:35 I guess Tokyo has the advantage it is easier to get to than Pune - though it also seems good to do a different location this time perhaps though it is not necessity 06:38:15 third option would be Kula Lumpur 06:38:49 its middle and I can help with arrangement over there 06:39:00 But not sure about cost 06:39:15 Taiwan? 06:39:25 Malaysia 06:39:42 We do have Red Hat office in Kuala Lumpur but not sure how big. 06:39:49 Singpore might also be a possibility 06:39:50 Taiwan is cheap? 06:40:09 singapore is very costly :( 06:40:12 cheaper than Tokyo probably 06:40:18 pravins: true ;) 06:40:22 definitely :) 06:40:35 let me list out option again. 06:40:52 getting VISA is also imp part. 06:41:04 still Pune or Tokyo seems to make most sense from PoV of cost minimization 06:41:04 nod 06:41:23 and more participation from regional people. 06:42:07 there is also Beijing... 06:42:21 but there are less people 06:42:21 nod 06:42:23 so more travel. 06:42:58 yeah 06:43:11 Beijing is also a middle place... 06:43:17 Cost is important factor. It involves Travel + Accommodation. 06:43:35 if 3 people at host, it save T+A cost for them 06:43:53 yeah 06:43:54 So deciding other location than India is physical only when we have less T+A cost overall. 06:44:10 s/physical/feasible 06:44:18 right - we could all stay in Hotel Cocoon ;) 06:44:31 yeah. 06:45:27 1. India 2. Japan or 3. Location - Cost will be less than 1/2. 06:46:43 before next meeting i will add some cost estimations. 06:46:52 and lets propose tentative plan to council. 06:47:29 sounds good 06:48:34 yeah looks good 06:50:16 i am done. 06:51:44 #info #63: Fedora 24 Bug triaging 06:51:44 #link https://pagure.io/i18n/issue/63 06:51:54 keep triaging bugs again :) 06:52:29 there are still 51 NEW state bugs 06:54:57 #topic Open Floor 06:55:04 anything to discuss here? 06:57:28 Thanks all for coming to this meeting :) 06:57:32 #endmeeting