06:00:31 #startmeeting i18n 06:00:32 Meeting started Wed Nov 19 06:00:31 2014 UTC. The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:00:32 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:00:37 #meetingname i18n 06:00:37 The meeting name has been set to 'i18n' 06:00:42 #topic agenda and roll call 06:00:46 Hi All 06:00:57 Hi 06:01:00 Hi! 06:01:12 hi 06:01:20 hi anish_ mfabian fujiwarat :) 06:01:35 hi 06:01:49 hi 06:02:05 hi 06:02:09 hi 06:02:15 hi shilpa epico ueno paragan :) 06:02:29 hi 06:02:42 hi juhp 06:02:57 * pravins looking for tagoh_ ^^ :) 06:03:13 almost all here. lets start 06:03:17 hi 06:03:20 #link https://fedoraproject.org/wiki/I18N/Meetings/2014-11-19 06:03:26 hi tagoh_ :) 06:03:30 #topic Upcoming schedule 06:04:09 #info 2014-11-04 Beta Release 06:04:09 #info 2014-11-18 [https://fedorahosted.org/fesco/ticket/1364 Fesco] Final Freeze (Former Final Change Deadline) 06:04:10 #info 2014-12-09 Fedora 21 Final Release 06:05:11 Freeze happened yesterday. Still as you know, we can try to provide zero day updates if anything still remained 06:05:49 right 06:06:08 google-noto will be one i think :) 06:06:23 any interesting blockers left? 06:06:30 thought its not package installed by default. 06:07:34 https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist 06:08:28 as usual anaconda is there 06:09:42 No blocker from i18n perspective yet :) 06:09:46 lets move forward 06:10:08 do bring, if any interesting here 06:10:15 #topic Outstanding topics 06:10:22 This one is pending from long now 06:10:35 #info #34: need Fedora i18n Mission Statement (i18n@lists.fedoraproject.org) 06:10:35 #link https://fedorahosted.org/i18n/ticket/34 06:10:53 * epico just added a new one. :) 06:11:07 epico: thanks, i saw that :) 06:11:13 .bug 1147670 06:11:15 thanks anish_ as well for input 06:11:16 juhp: Bug 1147670 keyboard layout chooser switches letters while typing - https://bugzilla.redhat.com/1147670 06:11:22 Let native speaker of every language feel comfortable and enjoyable. 06:12:21 juhp: is it fine, if we discuss bug in bugs corner topic? 06:12:24 odd I thought I changed the ticket to say Vision 06:12:26 sure 06:12:30 thanks juhp :) 06:12:46 now, we have number of nice statement 06:13:06 how, if we take positive from each statement and make one nice statement 06:13:11 or maybe I forget to click send... hm 06:14:17 pravins +1 06:15:21 i have pasted all statements @ http://piratepad.net/zt6yXxFcOb 06:15:29 just one below each other 06:15:35 hopefully not missed anyone 06:17:42 lets try to find tokens 06:19:32 do we find some commons and important tokens? 06:21:08 I think we can find best vision statement from these tokens 06:21:45 +1 for constantly 06:23:02 * pravins never thought it will be so difficult ;) 06:23:06 :) 06:23:36 I think using token (phrases) is a good idea to capture essences 06:23:48 Shouldn’t experiences be used in the singular? (“Constantly improve i18n user experience”)? 06:24:00 mfabian: yes 06:24:32 "technology accessible to users" also feel very important token 06:26:09 how about that one? :) 06:26:20 please feel free to edit or suggest 06:26:45 Vision statement looks really nice 06:27:00 pravins, I don't feel we need the word Team explicitly in the vision 06:27:15 juhp: right 06:27:17 it is the vision of the Fedora i18n project 06:27:21 agree 06:28:00 maybe better to use less technical words like Fedora vision statement. 06:28:46 aha 06:28:50 epico: in that case, what can we right 06:29:00 Fedora i18n project wants ....? 06:29:00 just a thought. 06:29:17 but I might be wrong. 06:29:32 epico: nope, very valid point. 06:29:49 I feel comfortable is a bit vague, sorry 06:30:04 np 06:30:11 of course it is all a bit subjective 06:30:18 epico, I tend to agree 06:30:25 let me paste here 06:30:33 juhp :) 06:30:33 The Vision of Fedora i18n is making technology accessible to users by constantly improving the i18n user experience and to make native speakers of every language feel comfortable. 06:31:11 I might add the vision statement probably doesn't even need to start with "The Vision of Fedora i18n is" 06:31:16 The Vision of Fedora i18n team is making technology accessible to users by continuous improvement of the i18n user experience and to make native speakers of every language feel comfortable. 06:31:22 Making * 06:31:37 Yes, why to stamp statement as a vision. 06:32:07 Yes, it also makes it shorter and clearer to omit "The vision of the Fedora i18n team is ... 06:32:19 juhp +1 06:33:02 only words mfabian has different are "constantly improving" to "continuous improvement" 06:33:22 looks Anish added it :) 06:33:24 I probably prefer continuous 06:33:36 me too 06:33:38 SGTM 06:33:38 Yes. 06:33:39 * epico thinks both are okay. 06:33:55 okay to me. 06:33:59 or continously :) 06:34:16 but continuous improvement is good I think 06:34:28 yes "continuous improvement" 06:34:40 I also feel accessible is vague 06:35:00 juhp: two statement with just 2 words change, making me confuse :( 06:35:05 can we remove one from there. 06:35:23 available? 06:35:53 accessible -> available? 06:36:40 epico: i think accessible is good word. accessibility is bit related here 06:36:52 "Making technology accessible to users by continuous improvement of the i18n user experience and to make native speakers of every language feel comfortable." 06:37:06 I have an alternative now at the bottom of the page 06:37:35 dunno how about "providing i18n innovation to users" instead? 06:37:55 pravins, just a suggests, both okay to me. :) 06:38:09 I was thinking accessible -> comfortable 06:38:26 "Making technology comfortable for (native speakers of) every language by continuous improvement of the i18n user experience" 06:38:40 juhp: The part in the parentheses “(native speaker of)” could be taken out to make it more concise, right? 06:38:51 even could remove "by continuous improvement of the i18n user experience" 06:38:56 mfabian, right 06:39:16 "Making technology comfortable for every language" 06:39:39 too brief? 06:39:43 juhp: yes 06:39:47 heh 06:39:50 “Making technology attractive for users of every language ...”? 06:40:04 usable? 06:40:06 i feel 06:40:08 ""Making technology accessible to users by continuous improvement of the i18n user experience and to make native speakers of every language feel comfortable."" 06:40:18 too long ;-P 06:40:19 just i am not much happy with the end 06:40:36 feel comfortable 06:40:37 I don't like the partial duplication of the first and second parts 06:40:50 aha 06:41:04 * epico also prefer a shorter one. 06:41:14 it feels feel awkward overall to me TBH 06:41:35 yes, we can avoid "and" 06:41:39 and have single statemenet 06:41:42 statement 06:41:46 right that was my thinking 06:42:37 (also don't think we should restrict to native speakers) 06:42:44 we also need to think, is this statement attractive to our stakeholder? 06:42:48 developers and users 06:42:51 true 06:43:00 Yes, I want to use English and Japanese although I am not a native speaker. 06:43:42 in that sense "attractive" captures more 06:43:53 "“Making technology attractive for users of every language ..." 06:44:11 I grabbed comfortable above but still feels it sounds a bit lukewarm :) 06:44:34 (no dots ;o) 06:44:36 "Making technology accessible to users by continuous improvement of the i18n user experience to make native speakers of every language feel comfortable." 06:45:05 we need to cut short agree 06:45:50 continuous improvement sounds more like Mission statement 06:45:55 i think we can decide couple of statement 06:45:58 and send on mailing list 06:46:02 and final one 06:46:03 juhp, right 06:46:26 in the vision everything is already done/perfect :) 06:46:37 nirvana :) 06:46:39 juhp: excellent point :) 06:46:48 good word.. 06:47:09 "reach nirvana state for i18n activities" ;) 06:47:18 simply remove the words after "by..." then? 06:48:04 though taking that to an extreme one should remove "making" too then hmm 06:48:23 pravins, haha 06:48:24 :-) 06:48:25 do we need to include "how" in the vision? 06:48:33 I don't think so 06:49:16 then I think "by continuous improvement of the i18n user experience" could be dropped. 06:49:29 tagoh_, +1 06:50:14 looks nice 06:50:17 "Fedora i18n makes technology accessible and attractive for users of every language." 06:50:29 excellent 06:50:48 +1 06:50:52 +1 06:50:55 can there be any alternative word for attractive? 06:51:09 otherwise looks good 06:51:11 +1. Yes, maybe we can decide on that? 06:51:11 * juhp still misses effortless 06:51:49 attractive -> make sense 06:52:04 "Fedora i18n makes technology accessible and make sense for users of every language." 06:52:11 hmm 06:52:23 attractive is better, I think. 06:52:32 mfabian, +1 06:52:37 * juhp is not married to attractive or comfortable 06:52:38 And doesn’t attractive already imply some level of effortlessness? 06:52:45 true 06:52:48 juhp: lol :) 06:52:56 If it takes too much effort, it is not very attractive. 06:53:03 mfabian, though it also sounds "pretty" 06:53:14 true 06:53:17 i think we can freeze ""Fedora i18n makes technology accessible and attractive for users of every language."" 06:53:24 attractive may also means easy of use. 06:53:43 perhaps we can sleep on it for some days? 06:53:47 Yes, ease of use, beauty, ... 06:53:48 epico: yes, we can use word attractive as per our interest :) 06:53:50 true 06:54:07 pravins :) 06:54:30 I guess I quite like it 06:54:32 excellent discussion we had overall :) 06:54:38 "Fedora i18n makes technology accessible and attractive for users of every language." 06:55:15 lets finalize this? 06:55:21 it seems to capture qualities of i18n quite well at a high level 06:55:37 Yes! 06:55:49 shall we post it to i18n and see if there is any more discussion? 06:55:58 i18n list 06:56:05 pravins, yeah 06:56:18 yes, we can say this if draft 06:56:24 sounds good 06:56:43 good work :) 06:57:17 yes, this is called collaborative vision statement :) 06:57:24 +1 06:57:30 * pravins forgot his laptop charger and about to die battery 06:57:36 oops 06:57:49 can't borrow one? 06:57:55 nope 06:58:01 i am logging from test machine 06:58:09 Maybe not just draft but final? I think it is really good. 06:58:14 #chair tagoh_ 06:58:14 Current chairs: pravins tagoh_ 06:58:35 ok, lets move on 06:58:47 mfabian, I suggest we give a few days or a week - no rush but yeah I think it is pretty good :-) 06:58:58 #action pravins will send an email to i18n list regarding statement 06:59:31 #info #36: gnome redesign plans for control-center Region and Languages (i18n@lists.fedoraproject.org) 06:59:35 #link https://fedorahosted.org/i18n/ticket/36 07:00:09 nothing new from me - maybe we should reach out to aday 07:00:28 but maybe better after f21 07:00:33 juhp: sure, as we decided last time, for this we need to be proactive 07:00:38 yes 07:00:40 juhp: sure. 07:00:42 thanks 07:00:48 lets move to next topic 07:00:57 #topic Outstanding task 07:01:01 #info #35: http://fedoraproject.org/wiki/I18N cleanup (i18n@lists.fedoraproject.org) 07:01:04 #link https://fedorahosted.org/i18n/ticket/35 07:01:12 mfabian, perhaps you could take to rtcm on it - I have mailed him 07:01:15 talk 07:01:44 #chair pravins_ 07:01:44 Current chairs: pravins pravins_ tagoh_ 07:01:44 do we want to have some irc discussion with rtcm? 07:02:07 juhp: does he there in WG meeting? 07:02:23 mfabian, about control-center design 07:02:33 juhp: yes. 07:02:38 pravins: not usually I think 07:03:13 juhp: hmm, then might be need to invite him sometime, specifically for this discussion 07:03:16 mfabian, since you have more tz overlap with them 07:03:25 we can 07:03:27 mfabian: can you ping him for same? 07:03:36 pravins, juhp: yes. 07:03:39 mfabian: thanks 07:03:45 I suggested to Rui that we could be involved int he discussion too 07:04:13 but like I say we are end of f21 cycle so may not be the best time dunno 07:04:13 #action mfabian to ping Rui for some dedicated discussion time on control-center redesign plans. 07:04:20 cool 07:04:50 we have one meeting plan after this for wiki cleanup 07:04:57 so lets try to discuss it there. 07:05:04 ok 07:05:29 hoping we can divide and conquer it quickly with all of your support :) 07:05:40 #topic New topics 07:05:43 #info #38: Adding metainfo for font packages (pravins) 07:05:48 #link https://fedorahosted.org/i18n/ticket/38 07:06:22 Glad to say we done with this 07:06:29 only couple might be remaiing 07:06:31 remaining 07:06:38 kudos to paragan for this :) 07:06:40 awesome! 07:06:48 +1 07:07:02 #action pravins to close ticket 38 07:07:14 #info #39: Bugs corner (pravins) 07:07:58 #link https://fedorahosted.org/i18n/ticket/39 07:08:15 As per we discussed in last meeting, i have created ticket for this 07:08:32 thanks! 07:08:55 I mentioned a bug earlier which seems not triaged completely yet 07:09:04 .bug 1147670 07:09:07 pravins_: Bug 1147670 keyboard layout chooser switches letters while typing - https://bugzilla.redhat.com/1147670 07:09:10 ah yes 07:12:35 tricky bug. 07:12:41 anyone able to reproduce same? 07:12:46 does anaconda use ibus now? 07:13:35 not that I know - does gnome run ibus by default these days? 07:13:59 on the installer? 07:14:05 guess not 07:14:16 No, anaconda does not use ibus. 07:14:33 ah 07:14:43 I have seen input misordering occasionally in general 07:14:49 tagoh_, well it is on Live 07:15:04 https://bugzilla.redhat.com/show_bug.cgi?id=1147670#c11 07:15:10 ah, okay. well, that depends on current locale I think 07:16:05 or it does perhaps - just remember ibus keeps running even after removing ibus-related input sources. 07:16:41 Live used ibus? 07:17:03 anaconda on Live. 07:17:42 dunno ... 07:17:47 epico, it is just running on desktop 07:18:18 anyway not sure anything we can do right now - just noticed it on the final FE list 07:18:25 juhp, exactly 07:18:32 we need more better, steps to reproduce 07:18:45 yeah - it seems not so easy to 07:19:38 if no more bugs lets move 07:20:32 we do have some more discussion after 40 minutes on #fedora-i18n for wiki cleanup. 07:20:33 #topic Open Floor 07:21:10 if we missed anything please bring up. 07:22:11 lets wait for two minutes and close the meeting 07:24:28 thanks you all for wonderful meeting. 07:24:36 #endmeeting