05:06:34 <pravins> #startmeeting FAD schedule planning
05:06:34 <zodbot> Meeting started Thu Oct  8 05:06:34 2015 UTC.  The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot.
05:06:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
05:06:44 <paragan> hi
05:06:51 <pravins> #meetingname FAD schedule planning
05:06:51 <zodbot> The meeting name has been set to 'fad_schedule_planning'
05:07:01 <pravins> #chair juhp paragan aeng
05:07:01 <zodbot> Current chairs: aeng juhp paragan pravins
05:07:20 <pravins> hi all  :)
05:07:54 <pravins> hoping we will come up with first schedule draft in today's meeting :)
05:08:27 <aeng> pravins: have you got the link to the doc?
05:08:32 <juhp> tagoh_, around?
05:08:56 <pravins> aeng: I worked on earlier on one draft
05:09:00 <pravins> its available on https://ethercalc.org/g6f8rg28bz
05:09:21 <juhp> oh no not ethercalc ;o)
05:09:39 <pravins> can someone quickly migrate it to google sheet? and share link here
05:09:55 <pravins> juhp: sorry, i did not got time to migrate it. :(
05:10:08 <tagoh_> hi
05:10:13 <pravins> hi tagoh_ :)
05:10:17 <pravins> #chair tagoh_
05:10:17 <zodbot> Current chairs: aeng juhp paragan pravins tagoh_
05:10:20 <juhp> ah this is the old "draft"?
05:10:28 <pravins> yes
05:10:32 <juhp> do we need it?
05:10:39 <pravins> we just need to change start time and end time there.
05:10:45 <mfabian> Hi!
05:10:53 <pravins> juhp: may be not, we can just refer it.
05:10:57 <Jobava> what is the channel for the meeting?
05:11:18 <pravins> Jobava: here itself. :)
05:11:36 <aeng> 'Zanata Feedback survey, not sure it needed 1 hour
05:11:38 <pravins> but today's meeting more focused on G11N FAD schedule planning.
05:12:04 <juhp> https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE
05:12:14 <pravins> aeng: i think lets first create outline and then simply insert topics as per time required.
05:12:16 <juhp> is our current doc
05:12:25 <Jobava> pravins: it would be nice to receive deadline dates via email, I can't seem to find where those are listed when I want to look for them
05:12:45 <Jobava> for L10n at least
05:13:05 <juhp> Jobava, dates for ?
05:13:08 <pravins> Jobava: you mean reminder of meeting bit earlier?
05:13:33 <Jobava> juhp: string freezes (English and localized) for the upcoming versions of Fedora
05:14:53 <juhp> Jobava, what would be a good topic for the regular G11n meeting
05:15:17 <juhp> this is a planning meeting the upcoming FAD in Tokyo
05:15:36 <Jobava> another topic: projects in Zanata to prioritize, I guess: anaconda and the website?
05:15:50 <juhp> Jobava, and that meeting is on #fedora-meeting
05:16:10 <Jobava> ehm, pravins?
05:16:22 <juhp> Jobava, sorry but can we discuss this after this meeting?
05:16:29 <pravins> Jobava: appreciated issues you raised, we will discuss those soon. :)
05:16:42 <pravins> coming back to FAD
05:16:45 <paragan> Jobava, this is planning meeting for FAD
05:17:02 <Jobava> pravins: also, mention the actual irc network and channel in the "reminder" email, please :)
05:17:43 <aeng> i think he does mentioned #fedora-g11n
05:17:56 <aeng> anyway.. can we continue on FAD topics?
05:18:00 <pravins> yes
05:18:02 <juhp> aeng, the Fedora G11n meeting is on #fedora-meeting
05:18:06 <pravins> Jobava: sure, will take care.
05:18:20 <pravins> First idea: We should keep on all days scope for two parallel sessions.
05:18:37 <pravins> i.e. Meeting room 1 and meeting room 2
05:18:48 <pravins> just saying for now, let it  be available
05:18:57 <juhp> hmm
05:19:11 <aeng> hows the booking of rooms?
05:19:18 <juhp> it is a large room - I dunno if we need to physically split rooms
05:19:26 <juhp> tagoh_, for 40 people?
05:19:27 <pravins> so any time during scheduling if we find, that we can schedule parallel session, we can do it.
05:19:31 <tagoh_> juhp: yes
05:19:56 <juhp> tagoh_, and some of Monday the other room is taken I think?
05:20:00 <aeng> possible to have splitting tables?
05:20:07 <Jobava> oh, what does FAD stand for?
05:20:15 <juhp> Fedora Activity Day
05:20:58 <tagoh_> given we have parallel sessions, do we need to have duplicate facilities for both sessions like a projector etc?
05:21:33 <tagoh_> juhp: yes, only one room we can book for Monday.
05:21:40 <pravins> tagoh_: i think other can be without projector. space to gather 6-8 people.
05:21:49 <juhp> and that is the main hackathon day
05:21:57 <aeng> yup.. just need to work with what we got at that time
05:21:58 <juhp> so basically we can't split
05:22:18 <juhp> unless the other room is available in the afternoon??
05:22:31 <tagoh_> juhp: unlikely
05:23:47 <juhp> s/40/24/
05:24:01 <tagoh_> maybe more flexible for Sunday and Tuesday though
05:24:02 <pravins> at least for now, lets make 2 column in schedule one for main room and other for breakout session.
05:24:17 <juhp> so basically it is one very large room that /can/ be split into 2 I understand (24+34)
05:24:30 <pravins> aha
05:24:39 <juhp> pravins, I still don't get what you want to split out
05:24:51 <juhp> all the hackathon will be many parallel sessions :)
05:25:18 <juhp> the general sessions are supposed to be common for all
05:25:41 <juhp> I am not opposed to break-sessions - but just wondering what they will be :)
05:26:23 <juhp> and back to the rooms: we have *one* of those split rooms booked for 3 days
05:26:35 <juhp> tagoh_, the one for 24 iirc?
05:27:23 <juhp> as tagoh_ said on the holidays we can use all the space of the combined rooms
05:27:41 * juhp hasn't actually seen the partitioning...
05:28:00 <juhp> ah
05:28:08 <aeng> his offline?
05:28:13 <tagoh_> juhp: yes, 24 is what we booked
05:28:24 <juhp> pravin_s, welcome back
05:28:34 <pravin_s> oops sorry.
05:28:40 <pravin_s> i just want provision before we start actual scheduling.
05:28:50 <pravin_s> it will help i think
05:29:15 <juhp> if it is needed
05:30:14 <pravins> ok, no problem.
05:30:15 <aeng> both doc https://ethercalc.org/g6f8rg28bz and https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE is different
05:30:16 <juhp> ok sure
05:30:18 <pravins> lets go ahead.
05:30:26 <juhp> aeng, completed
05:30:34 <juhp> the ethercalc is very old
05:30:38 <juhp> completely
05:30:40 <aeng> ok
05:30:55 <pravins> should i create table at the bottom of page for scheduling?
05:31:04 <pravins> in the google doc?
05:31:19 <pravins> I think Top will be good.
05:32:40 <juhp> okay
05:33:32 <pravins> basically i am trying to replicate same structure as ethercalc to doc.
05:34:02 <pravins> We are starting from 10am, right?
05:34:07 <aeng> Guys, i need to go offline now... will visit the doc later.
05:34:20 <aeng> will look at the document later
05:34:37 <pravins> make sense?
05:34:42 <pravins> aeng: sure.
05:36:12 <juhp> pravins, yes
05:36:37 <juhp> I would particularly like some discussion on the hackathon
05:37:06 <juhp> Day 1 and Day 3 seem clearer - though we might still want to revise some of the common sessions
05:37:49 <pravins> yeah, maybe presentation in first 15-20 min and then discussions.
05:38:08 <pravins> Hangout with FPL looks good on second day, first session.
05:40:29 <pravins> going good on docs :)
05:40:38 <apeter> hi guys.. sorry was away
05:41:11 <pravins> apeter: no problem, please follow https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE/edit#
05:41:16 <pravins> #chair apeter
05:41:16 <zodbot> Current chairs: aeng apeter juhp paragan pravins tagoh_
05:41:22 <apeter> thanks pravins , checking the link
05:41:37 <pravins> juhp: if we have 2 back to back sessions on L10N and I18N.
05:41:56 <pravins> i think Fedora G11N might take less time.
05:45:20 <apeter> there should be a break for 10 min between the sessions other than lunch break :)
05:46:02 <pravins> apeter: good point, yeah may be one before lunch and one after lunch. Tea break type.
05:46:26 <apeter> yes 10-15 min max
05:46:53 <apeter> before lunch by aroung 11:30
05:47:13 <apeter> and after lunch by aroud 3:30 or 4
05:48:23 <juhp> aha
05:51:58 <apeter> guess we can have the first break at 11:30 as we start the sessions only by 10. what say ?
05:53:37 <apeter> and lunch break is till 2 pm. so we can have the tea break post lunch around 4pm?
05:53:42 <tagoh_> btw as I mentioned earlier, we couldn't book the larger room for Day 2 morning. it is available since 11am though, please keep in mind that we need to have a break prior to 11am and move to the larger room.
05:54:20 <pravins> tagoh_: i was thinking to have first session "Hangout with FPL" on second day.
05:54:39 <pravins> do you think its possible?
05:54:44 <pravins> around 10am JST?
05:56:06 <tagoh_> it might be less than 1 hour if we are planning to start at 10am. if it is okay, then yes.
05:56:38 <pravins> yeah, we are planning for 30min.
05:56:49 <tagoh_> good then
06:01:15 <juhp> I think we can worry about the exact times later - it is not a conference :)
06:01:32 <juhp> so hackathon could start at 11am ;)
06:02:08 <juhp> tagoh_, ah
06:02:39 <pravins> first day schedule looks nice.
06:02:49 <juhp> tagoh_, I don't see how it helps - the room is not available at 10am right?
06:03:05 <juhp> maybe we could do the hangout in the Breakout room?
06:03:29 <pravins> Do we have projector there?
06:03:49 <tagoh_> juhp: not really, we have booked alternative room and projector is also available.
06:04:08 <juhp> tagoh_, ah yes
06:04:15 <pravins> nice !!
06:04:19 <juhp> upstairs right?
06:04:26 <tagoh_> yes
06:05:30 <tagoh_> need to take care of the timeline itself not to sit down over time.
06:05:37 <juhp> right
06:05:39 <tagoh_> that's it
06:05:41 <juhp> should be fine
06:05:53 <juhp> I think Matt will want to go to bed :)
06:07:17 <pravins> yeah, 1 hr will be more than sufficient
06:07:20 <juhp> yep
06:07:33 <juhp> I think we can finish with tea break even probably
06:07:36 <pravins> as juhp said, we can be more flexible if any session gets over earlier. :)
06:07:41 <pravins> yeah.
06:08:52 <juhp> it is Sunday night for him
06:08:55 <pravins> looks nice now.
06:09:29 <pravins> any queries on first day schedule apeter tagoh_ paragan noriko ?
06:09:30 <pravins> https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE/edit#
06:09:56 <noriko> sorry have had PM with Jobava
06:09:58 <noriko> let me check
06:10:23 <tagoh_> pravins: lgtm
06:10:34 <paragan> looks good
06:10:47 <juhp> should we remove Participants column?  well maybe later
06:11:26 <pravins> yeah, at present everyone is there.
06:12:05 <pravins> Most of the topics on first day are like - status update and brain storming on new ideas.
06:12:21 <pravins> good start
06:13:11 <noriko> pravins, I can't see the topic for new software deadline proposal discussion...
06:13:29 <juhp> noriko, it is part of the l10n session I would suggest
06:13:47 <juhp> does it need a whole session?
06:14:22 <pravins> noriko: yeah, just mention it in session and work on it during hackthon.
06:14:29 <apeter> the 1st day schedule looks good to me
06:15:07 <juhp> noriko, how about now? :)
06:15:15 <juhp> so we don't forget
06:16:02 <pravins> :)
06:16:21 <pravins> points raised in first day, will be useful for second day hackthon.
06:16:38 <pravins> from schedule, now it looks we need to do lots of pre-FAD work to be it fruitful.
06:17:30 <pravins> lets discuss on 2nd day?
06:17:54 <juhp> maybe next week?
06:18:17 <pravins> yeah, no problem
06:18:19 <pravins> we have some time.
06:18:42 <juhp> maybe I can delete the "Sessions" part for Day 1 and Day 3 - I think they are all reflected in the Schedule now?
06:19:06 <pravins> yes, if every session is covered in scheduled.
06:19:12 <juhp> well can be done later anyway
06:19:21 <juhp> let's leave it a week for reference
06:19:21 <pravins> if not, let it be there. It will help us to understand topic missed.
06:19:26 <pravins> due to limited time.
06:19:48 <juhp> yeah I don't think anything missing
06:20:11 <pravins> yes, first day straight forward looks, good :)
06:20:33 <juhp> yes not sure if we need any scheduling for Hackathon but it might be helpful for those that want to join more than one Hackathon project
06:20:38 <pravins> more sharing/overlap going to happen on second day :)
06:20:58 <juhp> some people probably want to work whole day on one project
06:21:04 <juhp> right
06:21:14 <juhp> maybe we just let it happen :)
06:21:18 <noriko> juhp, I like to ask more opinions from different aspect, where I can't think of
06:21:29 <juhp> noriko, ?
06:21:38 <pravins> juhp:  hmm
06:21:47 <noriko> the topic for new software deadline proposal discussion...
06:22:06 <juhp> noriko, how much time does it need?
06:22:10 <noriko> it will give impact to entire fedora project schedule.
06:22:20 <juhp> noriko, I don't feel l10n discussion time is enough?
06:22:25 <noriko> 30min to 1hour max,
06:22:26 <juhp> erm
06:22:32 <juhp> noriko, you don't feel l10n discussion time is enough?
06:22:39 <juhp> hmm
06:22:53 <juhp> is there so much to discuss?
06:23:08 <noriko> juhp, sorry which slot or time you are pointing?
06:23:11 <noriko> day1?
06:23:20 <juhp> a smaller session might be more effective?
06:23:24 <pravins> hackthon just let it happen is fine and good. But at least when it will happen, we should have in schedule/report :)
06:23:35 <pravins> same time, if we have it in schedule may be other interested people can join it.
06:23:40 <juhp> noriko, Day 1 11:15
06:23:42 <noriko> no no, if it can be included in day 1  the topic for new software deadline proposal discussion...
06:23:57 <juhp> happy?
06:24:00 <noriko> yes, that is fine, thanks :-)
06:24:02 <juhp> okay
06:24:04 <noriko> yes, happy :-D
06:24:11 <juhp> :)
06:26:53 <pravins> noriko: i feel on first day add overall L10N activities in Fedora and mention pain points
06:27:03 <pravins> second day be more specific on each topic in hackthon.
06:27:42 <noriko> oki, thanks pravins
06:28:04 <pravins> lets close meeting now, and work on second day in next meeting
06:28:16 <pravins> would like to see more people in scheduling 2nd day schedule.
06:28:25 <pravins> if nothing more will close in couple of meeting.
06:29:15 <juhp> +1
06:29:28 <noriko> pravins, one thing pls
06:29:37 <pravins> noriko: yes.
06:30:01 <noriko> can we open this draft planning to the community? especially ppl in Japan?
06:30:10 <noriko> so that they can start planning to join any of the session?
06:30:55 <pravins> noriko: yes, its already open.
06:31:04 <noriko> oki, any session restricted in terms of head count to attend?
06:31:45 <pravins> noriko: definitely we have head count limitations.
06:32:00 <pravins> and as you know we have no more budget
06:32:08 <pravins> 5-10 more people are fine.
06:32:12 <juhp> noriko, we can't have a 100 people there but a few is okay
06:32:15 <juhp> right
06:32:29 <noriko> hehe, juhp no I don't think so.
06:32:33 <juhp> :)
06:32:47 <juhp> I know we'll probably be lucky to get so many
06:32:49 <pravins> yes and i think if they mention there interest in bit advance, it will help us to plan resources.
06:32:57 <juhp> right
06:33:03 <noriko> k, will let me try, and I may control the number if needed.
06:33:07 <juhp> noriko, people will need to "register"
06:33:28 <noriko> juhp, oh, good. any registration page?
06:33:48 <juhp> noriko, I mean like pravins said - we need some idea in advance that they are coming
06:34:23 <noriko> does that mean, say they should have something to say at the session, yes?
06:34:24 <juhp> so no open invitations I think - but please invite specific Fedora l10n people from the community :)
06:34:31 <juhp> noriko, not really :)
06:34:32 <pravins> noriko: ask them to send email to either me, juhp tagoh_ , may be you can be in cc for those email.
06:34:58 <pravins> then, we will update FAD page.
06:35:08 <noriko> juhp, it is tough.
06:35:22 <juhp> noriko, but if you want some of them to join your l10n session say it is okay
06:35:24 <noriko> I can't filter out people, who to send and who to not.
06:35:55 <noriko> juhp, if I say it is ok to join, then that person will say in twitter.
06:36:04 <noriko> will/sorry/may
06:36:05 <juhp> noriko, well I don't know best approach - at least we should restrictive to Fedora Contributors basically I think
06:36:15 <juhp> hmm
06:36:20 <noriko> thye are all contributors.
06:36:36 <noriko> basically translators.
06:36:36 <juhp> how many people?
06:36:47 <juhp> how about direct mail? :)
06:36:48 <noriko> they are also gnome and other community translators.
06:37:11 <juhp> noriko, how many came last time?
06:37:40 <noriko> juhp, i only heard from two person atm. but if I give 'yes' only those two. but keep silence to the others. it isn't unfair?
06:38:15 <noriko> I think last time in tokyo was 15-20?
06:38:29 <juhp> noriko, how about asking people to reply to you privately if they are interested
06:38:33 <juhp> noriko, I think that is too many
06:38:53 <juhp> personally
06:39:04 <juhp> hmm
06:39:20 <pravins> yeah. We cant accommodate all :(
06:39:21 <juhp> it will change the dynamic of the FAD I feel
06:39:27 <noriko> juhp, I don't think that number would come, rather a few would be realistic.
06:39:47 <noriko> but still the inviation/information need to be open doesn't it?
06:39:47 <juhp> noriko, so a few observers/participants is fine I think
06:40:05 <juhp> also this time it will be in English - it could also be a factor
06:41:20 <noriko> I like to open the invitation to all members at tras-ja list, and will receive interests a few. that is my assumption.
06:41:22 <noriko> however
06:41:33 <noriko> if I hear more than manageable, I can control.
06:41:55 <noriko> well, I would say it is number restricted and discuss who to come.
06:42:09 <noriko> does that OK?
06:42:34 <pravins> yes.
06:42:41 <noriko> :-)
06:42:51 <pravins> mention in email itself, we have very few slots available.
06:43:00 <noriko> thanks pravins yes I will do so.
06:43:12 <pravins> i.e. 3-5, so first come first serve or who are present active contributors.
06:43:27 <noriko> got it.
06:43:53 <pravins> noriko: more do plan some activity with participants.
06:44:17 <pravins> thanks noriko :)
06:44:27 <pravins> thanks all for meeting closing now.
06:44:53 <juhp> great
06:45:20 <pravins> #endmeeting FAD Schedule planning