04:30:47 <pravins> #startmeeting globalization
04:30:47 <zodbot> Meeting started Wed Jun  3 04:30:47 2015 UTC.  The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:30:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
04:30:55 <pravins> #meetingname globalization
04:30:55 <zodbot> The meeting name has been set to 'globalization'
04:31:01 <pravins> hi all
04:31:04 <apeter> hi
04:31:06 <Satya> hi
04:31:08 <pravins> who are available for meeting?
04:31:10 <aeng> hi
04:31:11 <juhp> hi
04:31:15 <pravins> #topic agenda and roll call
04:31:22 <paragan> hi
04:31:34 <apeter> :)
04:31:44 <camunoz> hi pravins
04:31:48 <pravins> hi apeter paragan aeng juhp  Satya :)
04:31:58 <pravins> hi camunoz :)
04:32:02 <pravins> #link https://fedoraproject.org/wiki/G11N/Meetings/2015-06-03
04:32:04 <Satya> hi
04:32:17 <fujiwarat> hi
04:32:22 <mkim> hi
04:32:27 <pravins> hi mkim fujiwarat :)
04:32:32 <noriko> hi
04:32:36 <pravins> hi noriko :)
04:32:36 <apeter> cool.. nice to see all :)
04:32:54 <pravins> first of all welcome all to our first ever Fedora Globalization meeting.
04:33:19 <Satya> Thanks for all of your efforts!
04:33:20 <pravins> we have big topic list in agenda, so lets start.
04:33:21 <juhp> thanks pravins for setting this up :)
04:33:27 <pravins> #topic Upcoming schedule
04:33:29 <Satya> +1
04:33:32 <apeter> +1
04:33:34 <pravins> #info 2015-06-23 	Change Checkpoint: Proposal submission deadline (System Wide Changes)
04:33:34 <pravins> #info not scheduled yet 	Side Tag Builds Deadline
04:33:34 <pravins> #info 2015-06-16 	Mass Rebuild
04:33:35 <pravins> #info 2015-07-14 	Branch Fedora 23 from Rawhide (Rawhide becomes future F24)
04:33:35 <pravins> #info 2015-07-28 	Alpha Freeze (*), Software String Freeze, Change Checkpoint: Completion deadline (testable), Bodhi activation point
04:34:58 <pravins> Point to note here: we have around 3 weeks to propose if we are planning to propose any specific change in Fedora 23.
04:35:37 <pravins> its good we started discussion in early development cycle of F23.
04:35:44 <juhp> https://fedoraproject.org/wiki/Releases/23/Schedule
04:35:44 <pravins> moving to next topic
04:35:59 <apeter> ok
04:36:06 <pravins> #topic Zanata feedback survey - Ani
04:36:22 <pravins> apeter: please give some brief about the idea
04:36:25 <apeter> thanks pravins
04:37:11 <apeter> what i was thinking is now that Zanata has entered into Fedora community since F22, and we have completed one release, its time we collect some feedback from the community
04:37:22 <apeter> this will help us to have more interaction with the community
04:37:52 <pravins> #idea collect feedaback from Fedora community about zanata
04:38:07 <apeter> Conduct a survey from the Fedora community translators
04:38:10 <mkim> apeter, good idea. do you have particular survey questions to use in survey and how would this survey be conducted ?
04:38:15 <apeter> *from/with
04:38:23 <aeng> apeter, only translators? not maintainers?
04:38:36 <camunoz> I think we need both perspectives
04:38:51 <apeter> mkim, aeng maybe both
04:38:54 <pravins> camunoz: +1
04:38:55 <apeter> camunoz, yes
04:39:13 <juhp> yes
04:39:29 <pravins> #agree Zanata survey we need to consider both maintainers and l10n.
04:39:38 <apeter> mkim, I do not have any particular questions in my mind now.. but can prepare a draft
04:39:38 <mkim> apeter, I agree. we would need different set of questions to ask
04:39:43 <apeter> exactly
04:39:44 <pravins> mkim: i saw one earlier survey of Zanata 2011
04:39:46 <pravins> #link
04:39:51 <pravins> #link #link http://blog-zanatatm.rhcloud.com/tag/survey/
04:40:03 <apeter> cool.. thanks pravins
04:40:04 <pravins> #undo
04:40:04 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x62c4f550>
04:40:31 <apeter> we can send the survey to fedora mailing lists
04:40:32 <pravins> mkim: do you think this survey can help as starting point for gathering questions?
04:40:58 <mkim> pravins, cool. I think its best if we create brand new questions this time for fedora community
04:41:12 <mkim> pravins, apeter: we can work with Luke - UX designer for Zanata project
04:41:24 <apeter> mkim, great
04:41:27 <mkim> he has done quite a lot of interviews with different users so he might have some good idea what to ask in what format
04:41:33 <mkim> I will get you guys connected
04:41:38 <aeng> +1
04:41:38 <apeter> perfect!! :)
04:41:42 <apeter> +1
04:41:43 <mkim> :)
04:42:01 <apeter> we need to decide a timeline too.. when do we need to conduct the survey
04:42:14 <mkim> we have zanata 3.7 getting released in a couple of weeks
04:42:21 <mkim> so it might be good to do the survey after the new release
04:42:22 <apeter> after F23 translations or before
04:42:28 <mkim> towards the end of June or early July?
04:42:46 <pravins> sounds good.
04:42:55 <camunoz> apeter, when is "after F23 translations"?
04:43:16 <apeter> as per schedule, Software Translation Deadline is 25 Aug
04:43:24 <apeter> https://fedoraproject.org/wiki/Releases/23/Schedule
04:43:34 <apeter> camunoz, :)
04:43:36 <camunoz> we want to get as many responses as possible, so we need to be careful not to send translators and manintaners a survey during crunch period
04:43:58 <camunoz> orthey might ignore us :)
04:44:08 <apeter> camunoz, yup.. guess in that case lets do it after 25th Aug ? noriko any thoughts ? :)
04:44:10 <pravins> camunoz: we can use fedoramagazine to promote our survey.
04:44:20 <pravins> #idea use fedoramagazine to promote survey
04:44:24 <apeter> pravins, +1
04:44:27 <mkim> pravins, +1
04:44:32 <noriko> well, can we open the survey after F23 GA?
04:44:32 <camunoz> sounds good to me pravins
04:44:43 <aeng> pravins, good to promote Zanata too
04:44:46 <pravins> #idea do survey around end of June or first week of July.
04:44:47 <mkim> let's gather the right questions to ask with lukebrooker before that
04:44:50 <juhp> noriko, that's end of Oct though...
04:44:55 <noriko> open longer, and then close after F23 GA, so that many experience can get in?
04:44:57 <mkim> and target to have the survey out after F23 translation - end of August
04:45:14 <noriko> Alpha period -= translators busy
04:45:21 <mkim> noriko, makes sense too
04:45:22 <noriko> Beta period = maintainer busy
04:45:28 <apeter> mkim, noriko agree
04:45:30 <mkim> we will need some time to prepare for the survey too
04:45:45 * noriko nods to mkim
04:45:47 <pravins> please help me to note action points :)
04:46:02 <apeter> lets get this survey August end , right guys
04:46:08 <pravins> yeah, its good to put more time in preparation.
04:46:13 <mkim> apeter, +1
04:46:18 <apeter> cool... :)
04:46:28 <aeng> pravins, where do you put the action point to?
04:46:30 <pravins> apeter: +1
04:46:55 <pravins> #agreed Zanata survey August end
04:47:06 <pravins> aeng: we just need to start with #action
04:47:34 <pravins> #chair aeng
04:47:34 <zodbot> Current chairs: aeng pravins
04:48:02 <pravins> #chair mkim juhp paragan apeter camunoz aeng
04:48:02 <zodbot> Current chairs: aeng apeter camunoz juhp mkim paragan pravins
04:48:13 <pravins> #chair fujiwarat Satya
04:48:13 <zodbot> Current chairs: Satya aeng apeter camunoz fujiwarat juhp mkim paragan pravins
04:48:22 <pravins> now we all can add action items with #action :)
04:49:31 <pravins> #action mkim and apeter followup with lukebrooker
04:49:53 <apeter> pravins, okay
04:49:54 <pravins> any other action items for zanata survey?
04:50:30 <pravins> ok, lets move ahead.
04:50:39 <pravins> #topic L10N sprints based on F23 - Ani
04:50:43 <pravins> again apeter :)
04:50:46 <apeter> ;)
04:51:53 <apeter> I all l10n communties we have active l10n sprints (online/live activities) either for whole language communities or individual communty conducting sprints for their respective language
04:52:05 <apeter> this is something I see not happening in Fedora community
04:52:14 <apeter> *s/I/In
04:52:38 <pravins> agree
04:52:41 <aeng> apeter, whats the workflow in fedora now for translations?
04:52:45 <apeter> So we can start L10n sprints for Fedora too.. lets start with online sprints
04:53:27 <pravins> i think noriko can help here :)
04:53:43 <apeter> Individual translators from community just contribute.. as a whole language communities has to become active
04:54:22 <paragan> aeng, I guess https://fedoraproject.org/wiki/L10N/Translate_on_Zanata
04:54:30 <noriko> sorry what does sprints mean here?
04:55:03 <pravins> noriko: aeng asked what is workflow for Fedora l10n.
04:55:07 <apeter> aeng, individuals contribute if they wish. Earlier releases Red Hat had inhouse translators for Indian languages. Now thats not the case. hence we need to promote such l10n activites for more contributions to Indic languages
04:55:12 <pravins> aeng: may be you can elaborate more for it :)
04:55:23 <apeter> noriko, sprint means.. we bring
04:55:38 <apeter> oops sorry(entered by mistake before completing the sentence)
04:56:02 <pravins> noriko: sprints means deciding some date and working together on completing l10n task.
04:56:15 <juhp> noriko, http://en.wikipedia.org/wiki/Sprint_%28software_development%29
04:56:16 <pravins> basically gathering together for achieving some goals :)
04:56:42 <noriko> ah, yes. I love that happens :-)
04:56:48 <apeter> noriko, bringing community people together on a channel and making them translate for a particular project. Here Fedora community.. bringing all Fedora translators from all languages together on a fedora channel and asking them to translate
04:56:54 <apeter> for a whole day the event could be
04:57:05 <apeter> :)
04:57:07 <pravins> #idea plan for l10n sprint for Fedora.
04:57:26 <pravins> apeter: noriko can i add action item for you, to work further on sprint plan?
04:57:35 <camunoz> I think that's a bit different from the software development idea of a "sprint"
04:57:42 <noriko> for translation, each team has coordinator and they do have their rule, so I think it might be separated from sprints?
04:58:01 <noriko> I agree to camunoz
04:58:19 <mkim> do you have a tools to track the sprint effort for fedora l10n? or just via IRC?
04:58:31 <noriko> to me sprints, update old wiki pages for translators etc,
04:58:51 <apeter> noriko, we can send across a mail to trans list on this sprint.. here sprint = localization event
04:59:01 <aeng> i think this is the first time fedora release without indic translator in house, whats the expectation of translations here? does the translation needs to meet certain percentage to release?
04:59:21 <apeter> sprint is here just bringing translators in and dong the translation work.. a dedicated event for translation
04:59:23 <apeter> only
04:59:29 <juhp> okay
04:59:46 <pravins> aeng: yeah, looks most of the things are not very clea.
04:59:47 <pravins> clear.
04:59:53 <pravins> We need to provide good documentation here.
05:00:02 <apeter> mkim, it will be just IRC.. and then we can compare the stats before sprint and after sprint for each langs
05:00:07 <aeng> agree. As much as as possible in terms of tooling
05:00:39 <pravins> i remember there was fix percentage of translation required to say particular language supported or not.
05:01:31 <pravins> noriko: i think we need to work further to improve documentation, if we want to more community people get involve here.
05:01:52 <noriko> pravins, I agree :-)
05:02:04 * tagoh_ reads logs
05:02:05 <mkim> pravins, I believe it was like 80% for kde.. before. so it would be good to find out the minimum percentage for fedora
05:02:16 <apeter> noriko, a small example of a mozilla l10n sprint for bengali language : https://birajkarmakar.wordpress.com/2015/05/20/event-report-bn-in-mozilla-l10n-sprint/
05:02:30 <apeter> I shall try pullng our few more examples and share with you all later
05:02:54 <aeng> perhaps try to coordinate with language coordinator (not sure fedora has that)?
05:02:57 <pravins> #action minimum percentage of translation to say language is supported or not.
05:03:11 <pravins> aeng: +1
05:03:27 <noriko> apeter, yup, I see similar in gnome-ja, libreoffice-ja as well :-)
05:03:41 <apeter> we can send across a mail to trans list to discuss on this idea and promote it
05:03:51 <apeter> noriko, cool..
05:04:29 <pravins> do we have language coordinator list for Fedora?
05:04:30 <apeter> encourage translators, decide on a date maybe a weekend.
05:04:51 <noriko> pravins, support or not mean?
05:05:35 <pravins> noriko: its means if we have 80% translation then its supported else it not supported.
05:05:37 <aeng> I can see some fedora account have the title "language coordinator"
05:05:42 <aeng> eh. https://fedoraproject.org/wiki/Kaio2012?rd=User:Kaio
05:05:44 <aeng> eg.
05:05:54 <noriko> apeter, this is my guess, but emea teams likely have already similar events their own off site.
05:06:00 <pravins> any would you like draft l10n sprint?
05:06:10 <pravins> apeter: :)
05:06:10 <camunoz> aeng, Zanata should also have that information
05:06:23 <apeter> :)
05:06:32 <apeter> yup shall draft and share the idea..
05:06:36 <pabs3> pravins: can you clarify what is meant by globalization in this context?
05:06:40 <noriko> pravins, what is the difference??
05:06:42 <tagoh_> noriko: good question. yeah, fedora isn't like rhel we need to clarify the terms of "support" if we use that word somewhere.
05:06:47 <pravins> apeter: great :)
05:07:39 <pravins> pabs3: its i18n and l10n of Fedora. To make Fedora accessible in worlds languages.
05:08:01 <noriko> pravins, apeter here is the list of coordinators.
05:08:03 <noriko> http://fedoraproject.org/wiki/L10N_Teams
05:08:28 <pravins> noriko: wow, thats useful.
05:08:36 <pravins> #link http://fedoraproject.org/wiki/L10N_Teams
05:08:53 <pravins> #action apeter to draft sprint proposal and send on mailing list for discussion
05:09:01 <apeter> thanks noriko .. I was looking for that ;)
05:09:07 <noriko> :-))
05:09:08 <aeng> noriko, awesome!
05:09:09 * pravins thinks we will not able to cover all the topics :)
05:09:18 <pravins> lets move ahead for next topic
05:09:23 <apeter> pravins, okay... shall do that
05:09:24 <apeter> cool
05:09:27 <pravins> #topic Translation deadline around Beta - Noriko
05:09:39 <pravins> noriko: please provide brief :)
05:09:57 <noriko> okay, this is just idea, and would like to hear the possibility from others with different perspective.
05:10:01 <noriko> the idea is that:
05:10:47 <noriko> current translation deadline happens early stage, so that we see silent string freeze break. If we can have deadline sometime in beta period, we have more time to translate with less string freeze break.
05:10:55 <noriko> what you think?
05:11:41 <pravins> for Fedora 22
05:11:42 <tagoh_> it may be up to translators. the original purpose to set early stage for deadline was to have enough time to accomplish translations right?
05:12:20 <pravins> Software String Freeze  is on  2015-02-24
05:12:23 <noriko> tagoh_, afaik, none of us involved for setting the deadline. it was discussed and set by FESCO.
05:12:33 <pravins> Software Translation Deadline   2015-03-24
05:12:51 <pravins> noriko: good point
05:12:58 <apeter> noriko, I agree
05:13:00 <pravins> we have paragan from FESCO here :)
05:13:06 <paragan> if there is any need to change in schedule
05:13:08 <juhp> how about making a proposal to Fesco then for F23
05:13:19 <paragan> we can talk first to Fedora PM and if needed to FESCo
05:13:39 <pravins> noriko: would you like to prepare proposal for same first?
05:13:54 <juhp> noriko, but String Freeze at Beta seems rather late
05:14:08 <pravins> tagoh_: +1
05:14:12 <noriko> sure I am happy to do that if others of g11n members think this is reasonable.
05:14:35 <juhp> not sure if there is enough time post-Beta to land all the translations
05:14:40 <noriko> juhp, string freeze can stay there, just deadline?
05:14:42 <juhp> by GA
05:14:44 <juhp> ah
05:15:00 <noriko> so deadline and re-package to move
05:15:12 <mkim> I believe noriko meant extending the translation deadline
05:15:13 <juhp> I see
05:15:24 <noriko> thanks mkim yes
05:15:33 <paragan> we already have one month gap
05:15:40 <juhp> okay, still I am not sure
05:15:42 <paragan> between string freeze and translation deadline
05:15:51 <juhp> paragan, maybe not enough
05:16:00 <paragan> I think that should be enough
05:16:10 <noriko> paragan, after deadline, we see certain number of silent string freeze breaks by developers.
05:16:14 <juhp> noriko, how long do you want?
05:16:26 <juhp> 6 weeks?
05:16:28 <pravins> We have  "Software Translation Deadline" before Beta, so can we have it before final freeze?
05:16:29 <noriko> not the length, even we translate 100%.
05:16:33 <pravins> noriko: good points.
05:16:44 <noriko> after the deadline developers break string freeze, it no longer 100%.
05:16:51 <juhp> ah
05:17:12 <juhp> but that seems separate to translation freeze
05:17:20 <tagoh_> so string freeze may be a bit early then?
05:17:20 <juhp> more like "extra time"
05:17:41 <pravins> tagoh_: yes, looks like.
05:17:45 <camunoz> noriko, we could investigate that problem from the tooling side as well
05:17:46 <noriko> I might feel better to develop draft and bring it back to this meeting, so that you all can see my point better
05:17:58 <juhp> noriko, sounds good :)
05:18:03 <paragan> I think string freeze by Alpha freeze is correct milestone for Fedora Schedule
05:18:28 <pravins> #action noriko to prepare draft for extending Translation deadline and send to mailing list.
05:18:31 <juhp> paragan, yeah but in practice there is a still a lot of churn post-Alpha
05:18:42 <noriko> paragan, a question, why developer break string freeze then?
05:19:03 <paragan> if we move translation deadline by Final freeze what we do if string freeze happens after that
05:19:24 <pravins> lets move to next topic
05:19:26 <pravins> #topic FLTG revive plan for Fedora 23 - Ani
05:19:27 <paragan> I think there is no hard control for developers to not introduce string freeze
05:19:42 * apeter thinks we can discuss about this next time.. as we are running out of time
05:19:59 <pravins> apeter: sure.
05:20:04 <juhp> paragan, right
05:20:13 <pravins> #agree to discuss FLTG topic in next meeting.
05:20:16 <tagoh_> noriko: guess because the release cycle is early? less time to Alpha after GA.
05:20:16 <noriko> paragan, gnome can include translation a night before of tarballs due.
05:20:37 <noriko> tagoh_, ypyp
05:21:17 <noriko> string freeze date can stay as is, deadline extended to catch up any breaks.
05:21:18 <apeter> yes noriko true
05:21:44 <pravins> Satya: i think good to discuss UTRRS also in next meeting, good to discuss QA related topic together. what do you think?
05:21:56 <tagoh_> noriko: assuming the break happens sounds funny though
05:22:25 <juhp> noriko, my understanding is that the translation deadline is to encourage landing translations in time for Beta - that should prevent fixing breakage though
05:22:28 <Satya> pravins, sure, no problem, i already has the points ready with me
05:22:31 <juhp> tagoh_, +1
05:22:33 <Satya> thanks!
05:22:41 <pravins> Satya: sure. thanks :)
05:22:51 <pravins> #agreed discuss UTRRS in next meeting.
05:23:15 <noriko> juhp, as we introduced zanata, I believe the possibility of breakage dramatically dropped comapring old days.
05:23:33 <juhp> noriko, maybe a second deadline for translation fixes?
05:23:41 <noriko> juhp, cool
05:23:43 <juhp> okay that's good
05:24:03 <pravins> liked the idea.
05:24:16 <noriko> thanks all, I will develop draft to show which include second deadline proposal.
05:24:17 <pravins> second deadline.
05:24:25 <pravins> noriko: sure, thanks :)
05:24:25 <juhp> btwn Beta and Final say
05:24:30 <pravins> moving to next topic
05:24:31 <pravins> #topic G11N Infrastructure (IRC, Wiki and Ticket etc.) - Pravin
05:24:34 <apeter> cool.. thats a good idea
05:24:37 <pravins> all need your input on this.
05:24:54 <pravins> presenting sending emails on trans, i18n, fltg and zanata list
05:25:04 <pravins> do you think its good to have g11n mailing list?
05:25:07 <juhp> #idea have a second translation deadline for translation fixes rather than moving the current Translation Deadline
05:25:21 <pravins> juhp: thanks :)
05:26:12 <pravins> #chair tagoh_
05:26:12 <zodbot> Current chairs: Satya aeng apeter camunoz fujiwarat juhp mkim paragan pravins tagoh_
05:26:17 <noriko> juhp, ypyp
05:26:28 <pravins> we have only 5 minutes left, please provide your opinions :)
05:26:39 <pravins> should we go for g11n mailing list?
05:27:00 <juhp> I think g11n list is a good idea probably but probably we will see a lot of cross-posting anyway in the shorter term for sure
05:27:27 <noriko> one disadvantage: non-subscriber of specicfic ml such as trans may miss out info...
05:28:11 <pravins> noriko: yeah, may be in initial days good to have other specific list also in cc.?
05:28:12 <tagoh_> we don't have so much traffics on the existing list to have g11n list?
05:28:16 <noriko> how about force them all members to join g11n automatically?
05:28:27 <pravins> yes, we can do it.
05:29:06 <juhp> well we can subscribe i18n and trans list to g11n list
05:29:14 <juhp> don't need to force anyone :)
05:29:22 <pravins> how about just creating alias?
05:29:29 <mkim> it would be good idea to have g11n list if as noriko said, if everyone is requested to subscribe to it, so that you can send one meeting invitation to one list, instead of multiple.
05:29:32 <pravins> juhp: good idea.
05:29:41 <pravins> sure.
05:29:59 <pravins> i think most of us agree to have list. so i will create list and ask other to join.
05:30:09 <pravins> #agree to have g11n mailing list.
05:30:17 <mkim> yeap and don't forget to advertise about #fedora-g11n channel , too
05:30:19 <juhp> though downside to my idea is more "noise" on the individual lists
05:30:22 <pravins> #action pravins to create g11n mailing list.
05:30:26 <pravins> mkim: +1
05:30:33 <apeter> +1
05:30:42 <juhp> so maybe separate list is okay
05:30:50 <pravins> juhp: sure.
05:31:12 <noriko> we must be careful to split ppl by creating more ml...
05:31:23 <pravins> is it fine if we extent for 5 minutes?
05:31:31 <pravins> i want to discuss on G11N FAD
05:31:38 <tagoh_> not sure how many posts we will see... no or less cross-posting at this moment though
05:32:29 <juhp> tagoh_, right
05:32:34 <pravins> tagoh_: yes.
05:32:46 <pravins> #topic G11N FAD - proposal Pravin
05:33:01 <pravins> mkim: noriko camunoz wanted to discuss this FAD idea
05:33:10 <pravins> we started discussing on this couple of months back.
05:33:11 <noriko> FAD stands for?
05:33:18 <pravins> Fedora activity day
05:33:23 <noriko> thanks :)
05:33:29 <pravins> #link https://fedoraproject.org/wiki/FAD_I18n_2015
05:33:55 <aeng> so its in somewhere?
05:33:59 <pravins> we were thinking initially to do it for i18n, then after discussing with Shao thought good to do it for g11n.
05:34:10 <mkim> okay. sounds great
05:34:17 <pravins> aeng: yes, we decided location as a Tokyo Japan earlier.
05:34:29 <pravins> Since most of the member were available locally and also we have Red Hat office there.
05:34:41 <pravins> But things might change if we want to do it for Fedora G11N.
05:34:53 <juhp> just a small hike from Brisbane ;)
05:34:59 <pravins> Fedora OSAS team normally give $5000 budget for this.
05:35:10 <mkim> I am all for tokyo :)
05:35:14 <apeter> :)
05:35:17 <pravins> its depends on approval from Fedora council.
05:35:25 <pravins> mkim: great.
05:35:36 <aeng> not sure if everybody can make it
05:35:49 <mkim> thanks for sharing the information. it would be good motivation and initiative for g11n team to get together for fedora activity
05:35:49 <pravins> aeng: one can attend remotely as well.
05:35:51 <noriko> +1 tokyo
05:36:01 <juhp> aeng, I am sure ;)
05:36:06 <pravins> i will request you to please add name to proposal.
05:36:18 * mkim nod
05:36:32 <pravins> aeng: yeah.
05:36:47 <pravins> we can work on budget requirement later for same.
05:36:52 <camunoz> pravins, to that one you linked?
05:36:58 <pravins> camunoz: yes.
05:37:01 <camunoz> k
05:37:18 <pravins> moving to last topic
05:37:26 <pravins> #topic Open Floor
05:37:45 <pravins> we dropped few topic today, lets discuss those in next meeting.
05:37:50 <pravins> when should we have next meeting?
05:38:02 <juhp> in 2 weeks?
05:38:15 <pravins> yeah 2 weeks looks reasonable to me as well.
05:38:26 <pravins> since we are just started good to meeting quickly.
05:38:32 <mkim> +1
05:38:32 <pravins> what others think?
05:38:38 <pravins> great.
05:38:47 <pravins> #agreed to meet after 2 weeks.
05:38:47 <paragan> 2 weeks
05:38:52 <tagoh_> +1
05:38:57 <pravins> thanks all for meeting.
05:39:06 <juhp> thanks pravins
05:39:11 <apeter> +1 praveenkumar
05:39:15 <pravins> lets discuss few points on mailing list :)
05:39:17 <pravins> #endmeeting