06:00:09 <paragan> #startmeeting i18n
06:00:09 <zodbot> Meeting started Wed Dec 14 06:00:09 2016 UTC.  The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot.
06:00:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
06:00:09 <zodbot> The meeting name has been set to 'i18n'
06:00:10 <paragan> #meetingname i18n
06:00:10 <zodbot> The meeting name has been set to 'i18n'
06:00:10 <paragan> #topic agenda and roll call
06:00:10 <paragan> #link https://fedoraproject.org/wiki/I18N/Meetings/2016-12-14
06:00:13 <suanand> hi..
06:00:15 <mfabian_> Hi!
06:00:18 <epico> hi
06:00:25 <pravins> hi paragan :)
06:00:43 <paragan> Hi all
06:00:55 <paragan> #chair
06:00:55 <zodbot> Current chairs: paragan
06:01:10 <paragan> #chair suanand mfabian_ epico pravins
06:01:10 <zodbot> Current chairs: epico mfabian_ paragan pravins suanand
06:01:55 <paragan> let's start
06:02:01 <paragan> #topic Upcoming schedule
06:02:22 <paragan> so we have following upcoming milestone for Fedora 26
06:02:30 <paragan> #info 2017-01-10 	Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)
06:03:09 <paragan> Do think on any ideas if you have and submit Change for Fedora 26
06:03:45 <pravins> juhp: was suggesting last week, regarding idea of enabling emoji without adding any IME for it.
06:03:54 <juhp> hi!
06:04:04 <paragan> #chair juhp
06:04:05 <zodbot> Current chairs: epico juhp mfabian_ paragan pravins suanand
06:04:33 <paragan> aha
06:05:09 <paragan> lets discuss this on next topic
06:05:19 <paragan> #topic Outstanding issue
06:05:19 <mfabian_> pravins: By starting ibus by default?
06:05:31 <paragan> #info #69: Fedora 26 planning
06:05:31 <paragan> #link https://pagure.io/i18n/issue/69
06:05:41 <pravins> really not sure, may be if there is some option in GCC?
06:05:56 <juhp> g-c-c
06:06:18 <pravins> thanks juhp :)
06:06:52 <juhp> but i think fujiwarat is thinking about revising ibus emoji UI but I dunno if his plans include address the IME requirement...
06:07:59 <juhp> I also don't have a good idea for how to make the emoji feature easily accessible to non-ibus users
06:08:34 <juhp> but toggle in control-center for example would be seem nice
06:08:36 <paragan> I think pravins has done some work on collecting ideas for F26 in some ticket, let me find it
06:08:44 <juhp> aha +1
06:08:49 <paragan> #info https://pagure.io/i18n/issue/64#comment-4870
06:09:06 <paragan> all please check this link
06:09:10 <pravins> paragan: yeah, we had nice brainstorming in G11N FAD :)
06:10:03 <fujiwarat> My plan is to move emoji function from ibus engine to ibus panel.
06:10:16 <juhp> aha
06:10:47 <mfabian_> better dictionaries for ibus-typing-booster would be good. The hunspell dictionaries are good for spellchecking suggestions, but really bad for completion because they have no information about word frequency.
06:12:18 <mfabian_> I think I could generate better dictionaries by parsing Wikipedia dumps and taking only the 10000 most common words for each language
06:12:58 <paragan> maybe we can go once again to check on those idea suggested
06:13:12 <paragan> String Breakage monitoring
06:13:25 <pravins> mfabian_: definitely dictionary is crucial component for language related stuff and hunspell project is very silent from long time.
06:13:49 <paragan> I think this is currently being worked by suanand
06:14:36 <juhp> mfabian_: sounds useful
06:14:49 <mfabian_> Most hunspell dictionaries are OK for spellchecking, they go for completeness, they need to know every possible word which could exist to check whether a spelling is OK or not. That is quite different in purpose from completing something with the most likely completion. Very rare words are OK in a spell checking dictionary, but not in a dictionary for completion.
06:15:10 <juhp> mfabian_: right
06:15:12 <mfabian_> And the hunspell dictionaries have no information at all which words are common and which are rare.
06:16:05 <mfabian_> Dictionaries with word frequency information would improve completion a lot if one starts using ibus-typing-booster and not much user input has been learned yet.
06:16:11 <juhp> yep
06:16:37 <pravins> do agree but using same hunspell for both purpose does not make difference.
06:16:58 <pravins> s/difference/sense here.
06:17:08 <pravins> We might need some new package.
06:17:16 <juhp> sure
06:17:24 <juhp> I think that is what Mike is saying
06:17:43 <juhp> I think it makes sense
06:17:50 <mfabian_> I think I would package special dictionaries for completion in ibus-typing-booster, as not many words per language are needed, probably less then 10000 per language, it will not be very big.
06:17:57 <pravins> I have some script ready to run on Wikimedia dumps :)
06:18:12 <pravins> i remember for initial period we actually did it for Indian languages.
06:18:15 <mfabian_> pravins: Nice, I’ll have a look!
06:18:23 <pravins> let me upload those now.
06:18:30 <juhp> mfabian_: okay but having it as a separate project would allow others to make use of the data too though
06:18:38 <juhp> cool
06:19:07 <epico> mfabian_: I have one for Chinese, too.
06:19:33 <paragan> cool
06:19:38 <mfabian_> juhp: Maybe, I am not yet sure which format I would want for such dictionaries. A simple format with two columns "word frequency" might be useful for others. A more complicated format with triples of words for context maybe not.
06:20:14 <juhp> mfabian_: okay maybe it makes sense to first prove it in ibus-typing booster before factoring out...
06:20:26 <pravins> mfabian_: i doubt there might be something existing for this.
06:20:48 <mfabian_> pravins: I also think there is nothing for this yet.
06:20:49 <juhp> having it separate does also allow updating the data without having to push out a new typing-booster... :)
06:21:10 <paragan> right
06:21:32 <juhp> mfabian_: ah if you want context too that is even cooler I guess
06:21:47 <mfabian_> juhp: Yes, if I should go for a simple 2 column format, I think I’ll factor it out, but maybe I can do better than that.
06:21:56 <juhp> nice
06:22:10 <juhp> not much time for f26 though...
06:22:22 <juhp> just thinking aloud in terms of Changes :)
06:22:37 <juhp> though might be possible to do something perhaps?
06:23:09 <epico> mfabian_: https://www.mediawiki.org/wiki/Alternative_parsers
06:23:17 <paragan> yeah so if it looks doable then mfabian_ can submit a new Change for this
06:23:26 <epico> I used WikiExtractor.py
06:23:42 <juhp> paragan: btw the schedule does not seem to mention when system wide changes that need to be completed before mass-rebuild should be finished?
06:23:54 <mfabian_> Maybe too late for f26 though, I should probably do the change to the setup UI for multilingual setup and merge all egines into one first.
06:24:09 <juhp> mfabian_: aha - yes please
06:24:21 <juhp> that could also be a Change perhaps
06:24:50 <paragan> 2017-01-10 	Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)
06:24:51 <paragan> 2017-01-31 	Change Checkpoint: Proposal submission deadline (System Wide Changes)
06:24:51 <paragan> 2017-02-01 	Mass Rebuild
06:24:53 <paragan> I see this
06:25:11 <mfabian_> epico: Thank you, that looks useful!
06:25:33 <epico> Welcome :)
06:25:43 <paragan> epico++
06:25:43 <zodbot> paragan: Karma for pwu changed to 1 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:26:21 <pravins> epico++ for Wikiextractor script.
06:26:23 <zodbot> pravins: Karma for pwu changed to 2 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:26:36 <paragan> anyone got any suggestion for any change related to glibc?
06:26:59 <pravins> I am not following Glibc much from past sometime.
06:27:13 <pravins> Did we had any improvement on CLDR and glibc locale sync?
06:27:36 <mfabian_> pravins: No, not yet. I am still struggling with the UNDEFINED collation problem ...
06:28:53 <juhp> paragan: right but that is submission deadline, right?
06:29:06 <paragan> yes
06:29:55 <pravins> mfabian_: i remember, someone started working on Unicode CLDR and Glibc locale sync project.
06:30:18 <mfabian_> pravins: Mike Frysinger, but not really much so far.
06:30:48 <pravins> thanks mfabian_ , i will check :)
06:30:58 <pravins> mfabian++
06:30:59 <zodbot> pravins: Karma for mfabian changed to 1 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:35:24 <paragan> okay anything else need to be discussed more from https://pagure.io/i18n/issue/64#comment-4870 ?
06:37:45 <paragan> #topic No assignee issues
06:37:46 <paragan> #info #72: Proposal - I18n FAD in 2017
06:37:46 <paragan> #link https://pagure.io/i18n/issue/72
06:38:23 <pravins> Our last FAD was very useful, in fact from ideas. We are still using some ideas proposed in FAD :)
06:38:31 <pravins> its make it worth to have FAD soon.
06:38:40 <pravins> But 2 important issues.. Dates and Budget.
06:39:05 <pravins> I strongly feel aligning it with some conference can reduce budget and also increase participation.
06:39:12 <pravins> how others feel?
06:41:51 <paragan> #chair
06:41:51 <zodbot> Current chairs: epico juhp mfabian_ paragan pravins suanand
06:42:15 <paragan> pravins, maybe you can prepare initial draft and present it here for people to discuss
06:42:28 <paragan> that way we will get more to discuss
06:43:26 <paragan> Is there any conference coming say after 3 months from now? I don't think we will get approval for having FAD in next 3 months
06:43:37 <pravins> sure, make sense. I will prepare draft for it.
06:44:17 <pravins> Even i am doubtful for conference within 3 months.
06:44:22 <pravins> s/conference/FAD
06:44:59 <pravins> Here is list of some events in APAC https://fedoraproject.org/wiki/Ambassadors/APAC/Budget:2016
06:45:48 <paragan> thanks pravin
06:46:00 <paragan> let's move to next issue
06:46:11 <paragan> #info #71: Fedora 23 EOL bugs management
06:46:11 <paragan> #link https://pagure.io/i18n/issue/71
06:46:42 <juhp> pravins: +1 for combining with conference
06:47:26 <pravins> http://events.linuxfoundation.org/events/linuxcon-japan
06:47:38 <pravins> " June 2nd-5th 2015 "
06:47:45 <pravins> looks much more realistic
06:48:16 <paragan> #chair
06:48:16 <zodbot> Current chairs: epico juhp mfabian_ paragan pravins suanand
06:48:35 <paragan> can all please check if they have any Fedora 23 bugs reported/assigned?
06:48:55 <paragan> triage them and if needed move to f25/rawhide
06:48:59 <mfabian_> paragan: OK!
06:49:24 <pravins> paragan: sure.
06:49:44 <paragan> #info #63: Bug triaging activity post F24 Beta release
06:49:44 <paragan> #link https://pagure.io/i18n/issue/63
06:49:52 <juhp> yes
06:50:08 <pravins> this is i am planning to discuss with Bhushan today
06:50:10 <pravins> Satya is away
06:50:28 <pravins> May be we should change name of ticket for "post F25 Beta" :)
06:50:32 * pravins doing it now
06:50:53 <juhp> why Beta??
06:51:01 <juhp> I am not following the meaning well
06:51:07 <pravins> yeah, even not Beta
06:51:21 <juhp> post F25 release?
06:51:24 <pravins> plan was to do bug triaging early before EOL starts
06:51:37 <juhp> so please make that the title :)
06:51:46 <pravins> sure :)
06:51:49 <juhp> F24 bug triaging?
06:51:59 <juhp> or ?
06:51:59 <pravins> yeah, make sense
06:52:04 <juhp> F23?
06:52:11 <juhp> ah we have ticket for that
06:52:19 <pravins> F23 will anyhow not get autoclose by 20th Dec :(
06:52:27 <pravins> s/not/now
06:52:50 <juhp> this is why we have the previous ticket
06:53:51 <pravins> yeah.
06:54:22 <pravins> If we do bug triaging early, i.e. just after release of particular Fedora. We will be in much better state
06:54:59 <juhp> yeah regular triaging is best I think
06:55:24 <pravins> Just after GA release is good, like regular todo after release.
06:55:29 <paragan> so it looks to me like traiging of F23 bugs for previous issue and for this issue traiging of F25 issues?
06:55:39 <juhp> F24 I suppose
06:55:42 <pravins> yes
06:55:52 <pravins> moving F24 issue to F25 by triaging :)
06:56:13 <paragan> okay
06:56:16 <juhp> pravins: you will update the ticket title?
06:56:40 <pravins> yes.
06:57:18 <paragan> thanks pravins
06:57:35 <juhp> only reporter can change?
06:58:12 <paragan> at least all the members should get chance to change but I have seen some pagure ticket as well
06:58:48 <pravins> nope, it should be collaborative. Anyone can participate
06:59:52 <pravins> aha, about title change. Even i am struggling to change :)
07:00:24 <paragan> will check on it later on
07:00:32 <juhp> was afraid of that
07:00:36 <juhp> thanks
07:00:44 <paragan> #topic Open Floor
07:00:49 <paragan> anything here to discuss?
07:01:04 <paragan> if nothing then will close meeting in 2 minutes
07:01:26 <pravins> done.
07:01:33 <pravins> title changed.
07:02:56 <paragan> Thanks all for coming to this meeting
07:03:01 <paragan> #endmeeting