i18n
LOGS
06:00:12 <pravins> #startmeeting i18n
06:00:12 <zodbot> Meeting started Wed Mar 18 06:00:12 2015 UTC.  The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot.
06:00:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
06:00:16 <pravins> #meetingname i18n
06:00:16 <zodbot> The meeting name has been set to 'i18n'
06:00:22 <pravins> #topic agenda and roll call
06:00:24 <pravins> hi all
06:00:30 <pravins> #link https://fedoraproject.org/wiki/I18N/Meetings/2015-03-18
06:00:47 <lijli> hi
06:01:31 <paragan> hi
06:01:34 <pravins> hi lijli paragan :)
06:02:01 <pravins> ok, we can go through schedule while other joins
06:02:06 <pravins> #topic Upcoming schedule
06:02:06 <pravins> #info 2015-03-10 	Alpha Release
06:02:07 <pravins> #info 2015-03-24 	Software Translation Deadline
06:02:07 <pravins> #info 2015-03-31 	Beta Freeze
06:02:07 <pravins> #info  2015-03-31 Change Checkpoint: 100% Code Complete Deadline
06:02:29 <fujiwarat> hi
06:02:47 <pravins> fujiwarat: hi
06:03:09 <tagoh_> hi
06:03:13 <pravins> hi tagoh_ :)
06:03:14 <pravins> #info #36: gnome redesign plans for control-center Region and Languages (anishpatil)
06:03:14 <pravins> #link https://fedorahosted.org/i18n/ticket/36
06:03:21 <pravins> anish is away today, so we will skip this ticket.
06:03:52 <pravins> lets move to most important ticket for the day :)
06:03:54 <pravins> #info #42: Fedora 22 i18n test day (tagoh)
06:03:58 <pravins> #link https://fedorahosted.org/i18n/ticket/42
06:04:17 <epico> hi
06:04:26 <pravins> hi epico :)
06:04:27 <pravins> I wrote an article yesteday http://fedoramagazine.org/your-chance-to-contribute-in-fedora-22-development-cycle-through-test-days/
06:04:32 <pravins> I think we can share it around, it mentions i18n changes in good details.
06:05:04 <tagoh_> we'll  have an event tomorrow right. is there any concerns to do the test day with alpha image? does anyone have any important fixes after that?
06:05:44 <juhp> hi
06:05:49 <pravins> hi juhp :)
06:06:05 <pravins> as far as i know, no any changes from i18n perspective.
06:06:24 <juhp> pravins, thanks
06:06:43 <pravins> good to go with Alpha.
06:07:15 <juhp> probably either is okay but alpha more widely available
06:07:44 <juhp> anyone tested TC1?
06:08:26 <pravins> no
06:08:38 <tagoh_> me neither
06:09:05 <pravins> tagoh_: i think, we will ask to test with Alpha and lets user decide if he wants to go with any latest image.
06:09:43 <tagoh_> sure
06:11:16 <pravins> As a organizers, i think it will be good to try it early and fix instructions. If anything missing.
06:11:29 <tagoh_> definitely
06:11:37 <tagoh_> will try after the meeting
06:11:41 <pravins> me too :)
06:11:54 <pravins> I wanted to design flyer for same. But not much time remaining now.
06:12:16 <pravins> Will be working tomorrow with smaitra__ paragan and Bhushan here.
06:12:29 <pravins> lijli: do you have any concerns for tomorrow i18n test day?
06:13:17 <pravins> Not a single reply on badge ticket i proposed ;)  https://fedorahosted.org/fedora-badges/ticket/360
06:13:58 <pravins> lets move forward to next tickets.
06:14:01 <pravins> #topic New topics
06:14:05 <pravins> #info #40: Fedora 22 planning (pravins)
06:14:08 <pravins> #link https://fedorahosted.org/i18n/ticket/40
06:14:22 <pravins> Nothing to discuss on this. Might be while testing tomorrow we can find some issue.
06:14:37 <pravins> I have mentioned all our changes in Article.
06:15:07 <pravins> #info #43: I18n FAD in 2015 (pravins)
06:15:10 <pravins> #link https://fedorahosted.org/i18n/ticket/43
06:15:28 <pravins> juhp: As per suggestion in last meeting, removed "team" word from page ​https://fedoraproject.org/wiki/FAD_I18n_2015
06:15:38 <pravins> Next task is decide date and venue
06:15:50 <juhp> okay
06:16:25 <pravins> things to consider are
06:16:32 <pravins> 1. It should be near to RH facility, so we can get meeting room without extra overhead.
06:16:45 <pravins> 2. Maximum attendees should be available locally. It will reduce travel cost.
06:17:03 <pravins> 3. Date: 3 month after date of approval. So one can easily get VISA and cheap flight tickets.
06:17:22 <juhp> better to avoid overlap with fudcon?
06:17:53 <pravins> yes
06:18:23 <pravins> also fudcon is just 3 month away, i dont think we will get approval so quick.
06:18:33 <pravins> I see we have 4 people in Japan.
06:19:04 <pravins> juhp: tagoh_ dueno fujiwarat
06:19:08 <pravins> and 3 in Pune, India
06:19:13 <pravins> anish, parag and me
06:19:40 <pravins> we have choice in between both
06:21:11 <juhp> between means more travel though :)
06:21:26 <juhp> ah you mean either perhaps
06:21:33 <pravins> yeah, either actually :)
06:22:03 <pravins> dunno, if anyone wants join in from community later.
06:22:12 <pravins> may be smaitra__ lijli would also love to join.
06:22:20 <pravins> s/love/like
06:22:43 <juhp> yeah
06:23:23 <pravins> i will recommend for Japan.
06:24:09 <pravins> we have Red Hat facility there, more members locally.
06:25:23 <pravins> can we freeze on location today? :)
06:25:37 <juhp> pravins, but you seem to be keen to organize :)
06:25:46 <juhp> I don't either or both myself
06:26:31 <pravins> even me too ready for both locations. Pune or Japan
06:26:33 <juhp> could we colocate it?  sounds a bit complicated perhaps - perhaps we could connect by video conference....
06:27:05 <juhp> tagoh_, how do you think?
06:27:40 <tagoh_> I don't mind either honestly. more interested in  how many people will join other than us
06:27:51 <juhp> good point
06:28:22 <juhp> it may also depend on travel budget...
06:28:40 * smaitra__ will joini18n test day tomorrow.
06:28:43 <pravins> As you know FAD is basically gathering of Fedora contributors to complete specific tasks.
06:28:57 <pravins> So if any other Fedora contributor willing to join its fine for us.
06:29:03 <juhp> sure
06:29:05 <pravins> smaitra__: nice.
06:29:50 <pravins> juhp: yes, that is why i want to soon prepare budget and see if we can get approval for same.
06:30:02 <pravins> cant go for budget without location and date :(
06:30:47 <juhp> right
06:32:02 <juhp> so for f23?
06:32:05 <pravins> yeah
06:32:34 <pravins> at present  November looks more reasonable date to me. plenty of time for preparation.
06:32:59 <juhp> okay then might be more f24 :)
06:33:29 <pravins> year, will start development for f24 :)
06:33:51 <pravins> lets comment on ticket for suggestions.
06:34:06 <pravins> hopefully we will decide in next meeting :)
06:34:30 <pravins> may be i should drop an email to osas, regarding we planning for it. how to proceed ahead.
06:34:39 <juhp> good ideas
06:34:49 <pravins> lets move forward.
06:34:53 <pravins> #info #47: Workflow improvement (tagoh)
06:34:57 <pravins> #link https://fedorahosted.org/i18n/ticket/47
06:35:37 <pravins> tagoh_: would you like to elaborate here?
06:35:38 <juhp> pravins, maybe update purpose too :)
06:36:18 <pravins> that is why, we cant go ahead with exact date and location. All depends on it :(
06:36:26 <tagoh_> sure
06:36:42 <juhp> pravins, yep
06:37:38 <tagoh_> just proposed it to make the meeting more efficiency, to add more obvious category into the trac ticket system.
06:38:16 <pravins> right.
06:38:39 <juhp> +1
06:38:40 <pravins> so basically tickets which requires discussion in meeting and need some conclusion should get added to agenda.
06:38:41 <tagoh_> because we sometimes see no updates but in the agenda. after that we can simply drop it from the agenda. to do this, we all need to aware of this change and apply the workflow on trac.
06:39:14 <pravins> +!
06:39:20 <pravins> +1 :)
06:39:26 <tagoh_> I could just make the change but it won't work without notice. this agenda is including that too :)
06:40:48 <pravins> tagoh_: so tickets with type=meeting will only get added into agenda?
06:41:42 <tagoh_> not really. status may be more important so that there may be some tasks needing some discussions.
06:41:52 <pravins> aha
06:42:14 <pravins> agree.
06:43:01 <pravins> in ambassadors meeting they discuss only those tickets which is in "meeting" type but agree there is different work.
06:44:42 <tagoh_> we could more simplify the workflow perhaps though. e.g. change the category from "meeting" to "task" once some tasks for that happened. and back to the "meeting" if we need to discuss like that. that said dunno what if no "tasks" for the topic?
06:46:02 <pravins> we have only two category task or meeting.
06:46:29 <pravins> if no task, then after meeting may be we can close same.
06:46:36 <tagoh_> or we can just try that way without any changes on trac, but the workflow. i.g. chaning the category
06:47:22 <pravins> tagoh_: its very nice suggestion. Lets go ahead and see how its goes from next meeting.
06:47:35 <pravins> are you planning to draft if on wiki?
06:47:41 <pravins> s/if/it
06:48:02 <tagoh_> to add new status or change the category? :)
06:48:17 <tagoh_> pravins: I can
06:49:16 <pravins> i think change the category :)
06:49:40 <tagoh_> okay
06:50:03 <pravins> thanks you tagoh_ initiating this.
06:50:04 <pravins> #topic New task
06:50:07 <pravins> #info #45: Docs beat for Fedora 22 (pravins)
06:50:10 <pravins> #link https://fedorahosted.org/i18n/ticket/45
06:50:29 <pravins> page is available now https://fedoraproject.org/wiki/Documentation_I18n_Beat
06:51:08 <pravins> feel free to add points now.
06:51:26 * pravins will do some initial updates to it soon.
06:52:03 <pravins> is there anything for docs_beat? if not lets move ahead to our last topic :)
06:53:03 <tagoh_> changes holders should add something at least :)
06:53:53 <pravins> agree :)
06:54:18 <pravins> may be we can plan some activity day for it?
06:54:56 <tagoh_> basically that wouldn't take a time so much though...
06:55:10 <pravins> yes, its just 10 minutes work.
06:55:20 <pravins> sure, will notify change owners.
06:55:31 <pravins> and we are on next topic
06:55:36 <pravins> #topic Open Floor
06:56:34 <pravins> if nothing there, will close meeting in two minutes.
06:56:54 <pravins> Looking forward to see you all tomorrow on #fedora-test-day
06:58:01 <lijli> pravins, tagoh_ could you update the test build location to test day's page?
06:58:20 <lijli> alt.fedoraproject.org/pub ?
06:58:44 <lijli> alpha tc or latest beta tc
06:59:22 <pravins> lijli: both will work
06:59:23 <tagoh_> lijli: I did already
06:59:39 <pravins> we have not any changes after alpha freeze.
06:59:50 <pravins> if one wants he still can go with latest beta TC
07:00:02 <lijli> tagoh_, thanks
07:00:40 <lijli> pravins, ok, I will try latest beta tc build tomorrow
07:00:40 <pravins> lets close the meeting.
07:00:48 <pravins> lijli: nice :)
07:00:56 <pravins> thank you for nice meeting.
07:01:02 <pravins> #endmeeting