06:01:13 <paragan> #startmeeting i18n
06:01:13 <zodbot> Meeting started Wed Jan 18 06:01:13 2017 UTC.  The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot.
06:01:13 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
06:01:13 <zodbot> The meeting name has been set to 'i18n'
06:01:18 <mfabian> ☺
06:01:25 <paragan> #meetingname i18n
06:01:25 <zodbot> The meeting name has been set to 'i18n'
06:01:35 <paragan> #topic agenda and roll call
06:01:48 <paragan> #link https://fedoraproject.org/wiki/I18N/Meetings/2017-01-18
06:01:56 <fujiwarat> hi
06:02:38 <pravins> hi
06:03:44 <paragan> mfabian, fujiwarat, pravins hi
06:03:53 <paragan> #chair mfabian, fujiwarat, pravins
06:03:53 <zodbot> Current chairs: fujiwarat mfabian paragan pravins
06:04:15 <pravins> sundeep is away today.
06:05:16 <paragan> #topic Upcoming schedule
06:05:16 <paragan> #info 2017-01-31  Change Checkpoint: Proposal submission deadline (System Wide Changes)
06:05:17 <paragan> #info 2017-02-01  Mass Rebuild
06:05:17 <paragan> #info 2017-02-14  Change Checkpoint: Proposal submission deadline (Self Contained Changes)
06:06:39 <paragan> The last milestone for F26 schedule was "Proposal submission deadline (Changes requiring mass rebuild) "
06:07:16 <paragan> now next is for System Wide Changes but not requiring any mass rebuild
06:07:41 <paragan> also we can see mass rebuild is scheduled on 2017-02-01
06:08:32 <juhp> hi, sorry for late
06:08:42 <pravins> last time we did good with Build failure issue but it took much more time, lets see if we can resolve issues quickly.
06:08:48 <paragan> juhp, hi
06:08:55 <paragan> #chair juhp
06:08:55 <zodbot> Current chairs: fujiwarat juhp mfabian paragan pravins
06:09:26 <paragan> yeah we will monitor our packages for any FTBFS bugs and will try to fix them soon
06:09:46 <paragan> lets move to next topic
06:09:50 <paragan> #topic Outstanding issue
06:09:57 <paragan> #info #69: Fedora 26 planning
06:09:57 <paragan> #link https://pagure.io/i18n/issue/69
06:11:08 <paragan> I see that transdiff got few questions asked on devel mailing list to which Sundeep and pravins has replied
06:12:23 <pravins> paragan: yeah, looks confusion with need of transdiff for Fedora but it more towards translation side.
06:13:02 <pravins> it is at very basic stage presently and in long term with more collaboration, we can understand how effectively can we use it. like Bodhi etc.
06:14:25 <juhp> I am not sure if suanand has time for Transdiff for f26, I feel better to focus on Transtats itself for now
06:14:57 <juhp> Transdiff could be a useful devel tool perhaps
06:17:15 <paragan> yes it can be useful tool for package maintainers or to us to find out 100% translation status for packages
06:17:54 <paragan> more on this will come from Sundeep next week :)
06:18:11 <juhp> okay
06:18:48 <paragan> another change we got submitted https://fedoraproject.org/wiki/Changes/FontconfigCacheDirChange
06:19:15 <pravins> juhp: yeah both can be good.
06:19:39 <pravins> Though i was in impression that, transdiff is one of the important component of transtat, so it will be useful in both places.
06:19:45 <paragan> but it needs some discussions with ostree developers
06:19:58 <pravins> but yeah, ultimate goal is transtat, so good to go for it.
06:19:59 <paragan> so its not yet approved by FESCo
06:20:16 <pravins> ohh, what is reasoning?
06:20:19 <juhp> that one seems more controversial... but suggestion/question is if cache files can be generated at buildtime even, though install time also seems valid really
06:21:07 <paragan> ^^ right
06:21:26 <juhp> neither
06:22:05 <juhp> tagoh_ is away now
06:23:08 <paragan> okay no problem
06:23:15 <paragan> let's move to next topic
06:23:44 <paragan> #topic No assignee issues
06:23:44 <paragan> #info #72: Proposal - I18n FAD in 2017
06:23:44 <paragan> #link https://pagure.io/i18n/issue/72
06:24:08 <pravins> I created page for it just
06:24:09 <pravins> https://fedoraproject.org/wiki/FAD_I18N_2017
06:24:15 <pravins> but still not sure, when to do it.
06:24:21 <pravins> So we need some more clarity on place and timeline.
06:24:27 <pravins> Thinking Nov might be good again.
06:25:58 <paragan> pravins, thanks
06:26:57 <paragan> #info #63: Fedora 24 Bug triaging
06:26:57 <paragan> #link https://pagure.io/i18n/issue/63
06:27:15 <paragan> I think this is ongoing
06:27:36 <pravins> again i think need to decide date and plan for it.
06:28:36 <paragan> yeah we can decide any day to triage the i18n bugs for past releases as well
06:31:06 <paragan> let's move to next topic
06:31:17 <paragan> #topic Open Floor
06:31:24 <paragan> anyone got anything to discuss here?
06:31:30 <juhp> or we could decide now :)
06:31:30 <pravins> Elections results :)
06:32:35 <paragan> https://fedoraproject.org/wiki/Releases/26/Schedule
06:33:16 <paragan> after what milestone we can have bug triage day?
06:33:42 <paragan> mass rebuild?
06:34:36 <juhp> good question
06:35:35 <pravins> for Bug triaging, i think we should start preparing before 1 week
06:35:44 <juhp> not sure when/how is optimal - it could also be more than once
06:35:58 <pravins> so, lets see if its 9th Feb, we should have things ready by 2-3 Feb
06:36:23 <pravins> so, lets plan separate preparation meeting on 2nd Feb?
06:37:00 <juhp> prepare bug lists?
06:37:15 <pravins> yeah, basically plan was
06:37:23 <pravins> 1. To identify all bugs need traige.
06:37:27 <pravins> 2. Create slot of 5 bugs.
06:37:53 <pravins> 3. Send it to mailing list/community blog regarding triaging day and interested participants can pick respective slot for triage
06:38:04 <pravins> dunno, if we can have any badge or not.
06:38:12 <pravins> but, basically plan to involve more people
06:39:06 <juhp> slots means per person??
06:39:21 <pravins> yes.
06:39:27 <juhp> I see okay
06:39:49 <juhp> maybe first step should be triaging our own f24 bugs?
06:39:49 <pravins> so rather than doing only by our team, other members can also help and understand issues :)
06:40:06 <juhp> sure
06:44:25 <paragan> okay lets discuss on this more in next i18n meeting
06:44:39 <paragan> if any plan comes before that we will announce on the list
06:45:07 <paragan> next meeting is on 1st Feb
06:46:23 <juhp> ah I see buglist is in the ticket...
06:47:40 <paragan> yes
06:49:39 <paragan> if nothing is there to discuss I will close the meeting in 2 minutes
06:53:56 <paragan> #endmeeting