05:00:16 #startmeeting g11n 05:00:16 Meeting started Thu Oct 15 05:00:16 2015 UTC. The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:00:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:00:27 hi 05:00:39 hi 05:00:41 #meetingname G11N FAD schedule 05:00:41 The meeting name has been set to 'g11n_fad_schedule' 05:00:49 #topic agenda and roll call 05:00:53 hi juhp paragan :) 05:01:20 today we have to discuss second day schedule and it involved lots of hackathon topic, so involvement from all required. 05:01:26 #link https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE/edit#heading=h.zaws8k5zbj65 05:01:39 draft schedule available in above link. 05:01:51 #chair juhp paragan 05:01:51 Current chairs: juhp paragan pravins 05:03:06 anyone else around? tagoh_ fujiwarat noriko aeng ueno fujiwarat camunoz epico 05:03:13 hi 05:03:20 hi 05:03:22 yes 05:03:30 nice. 05:03:35 hi tagoh_ fujiwarat noriko :) 05:03:35 here 05:03:42 #chair tagoh_ fujiwarat noriko aeng 05:03:42 Current chairs: aeng fujiwarat juhp noriko paragan pravins tagoh_ 05:03:51 hi aeng :) 05:03:56 ㅗㅑ 05:03:58 ok lets see first topic. 05:03:58 hi 05:04:14 hi mkim :) 05:04:19 #topic first day schedule 05:04:30 We completed first day schedule in last weeks meeting. 05:04:38 its available on https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE/edit# 05:04:58 just added to topic, if there is any query, since few members were not present in last meeting. 05:05:02 any query? 05:05:48 btw should we add a meeting time outside the building due to the security reason? 05:06:14 I guess so 05:06:26 yeah. 05:06:48 tagoh_: so where at what time? 05:07:12 thought we agreed to meet at the station? 05:08:06 need to put time 05:08:10 yeah, station is fine. since few people were travelling. 05:08:14 09:30? 05:08:20 sounds good 05:08:22 just wondering is there any main contact number or person on the first day? 05:08:23 +1 05:08:23 yup 05:08:31 yeah.. just in case late 05:08:48 probably we could send out the final details to participants by email I think 05:08:54 can we get temporary pass for the building? 05:08:56 aeng, right 05:08:56 tagoh san's mobile? mkim 05:09:12 if tagoh_ san agree ;p 05:09:13 and mine 05:09:14 aeng: guess not 05:09:41 noriko: no problem 05:09:55 thanks1 05:10:04 hmm.. so station@9.30? or outside building ? 05:10:13 station I think 05:10:14 aeng: station. 05:10:17 thank you tagoh_ san juhp san 05:10:21 ok 05:10:24 is it sibuya station? 05:10:28 no 05:10:35 JR Ebisu Station 05:10:37 yeah, station is better. 05:10:48 upstairs exit 05:10:50 any particular exit number? 05:11:10 East exit 05:11:21 great.. im bad with direction 05:11:32 shall we put all the details into an email nearer the time I think 05:11:34 so 9:30 am Ebisu Station, East Exit upstairs 05:11:38 got it 05:11:42 aeng, just go up not down :) 05:11:46 lol 05:11:50 seriously 05:11:52 #agreed First day meet 9:30am At JR Ebisu Station East exit. 05:12:06 downstairs leads to the West exit 05:12:11 right 05:12:37 #info juhp and tagoh_ contact number will be provided later on email case any one miss. 05:12:39 there are a lot of shops above the station 05:13:18 should be fine... 05:13:26 Yeah, we will send email with more detail. 05:13:35 yup. Tahnks pravins 05:13:40 coming back to main topic :) 05:13:47 there are only two exists. so shouldn't be puzzled. 05:13:50 Any queries on first day schedule 05:13:52 exits even 05:13:52 ? 05:15:23 hi 05:15:31 hi epico :) 05:15:34 #chair epico 05:15:34 Current chairs: aeng epico fujiwarat juhp noriko paragan pravins tagoh_ 05:16:35 hi guys 05:16:45 hi apeter :) 05:16:52 hi pravins :) 05:16:54 I added basic details about the meeting points (for Sun and Tue) on the agenda doc 05:17:02 more precise details to follow 05:17:16 first day schedule looks good to me. 05:17:21 hoping same with others. 05:17:23 (Mon we should be able to just meet inside on the 5th floor) 05:17:35 moving to next day schedule. 05:18:08 #topic 2nd day (Mon) Schedule 05:18:48 just one thing about Monday - unfortunately we have to vacate the meeting-room for 1.5 hours in the afternoon since Red Hat needs the room for an internal meeting 05:19:09 juhp: at what time exactly? 05:19:51 and no other large room is unavailable it seems (I'll recheck if multiple smaller rooms could be used) except the common room which is quite large but little seating 05:20:04 pravins, 2:45-16:15 05:20:09 pravins, 14:45-16:15 05:20:24 aha, we can schedule break during same time 05:20:52 so some of us may have to stand around discussing etc in that break-room, which i booked for us 05:20:53 so maybe break at 14:30 for changing room. 05:21:08 yeah it is next door... 05:21:12 very cloes 05:21:14 close 05:21:45 in that case, no need to schedule 15 min break. 05:21:51 just we can move with laptops 05:22:02 yep 05:22:25 it will be a long "break"^W - well change of room/air :) 05:23:06 :) 05:23:30 Second day - First topic we dont have any option. Since we have to accommodate Time Zone changes with FPL. 05:23:52 so lets start working on next slot i.e. 11-13 05:24:35 I think we should discuss which projects we plan to work on that day 05:24:44 yeah. 05:24:53 I hope most people could focus or 1 or 2 the whole day 05:25:00 s/or/on 05:25:16 hackathon list is very big :) 05:25:54 can all please provide me list of topics, they want to work on during hackthon from list? 05:26:04 so, we can add it in schedule 05:26:18 we once made a list right pravins ? 05:26:36 thought we had it. :) 05:26:47 apeter: its in same document 3rd page. 05:26:58 should we invert the table or maybe add a new one under the schedule section listing each person 05:27:00 hahaha.. forgot to scroll 05:27:02 exactly 05:27:03 :) 05:27:19 and what they want to work on? 05:27:36 s/table/list/ 05:27:53 be careful one person can't be split into two session X-D 05:28:08 I think that will help to picture what things people are going to focus on 05:28:36 yes agree 05:28:39 noriko: :) 05:28:53 I am not sure yet if we need to schedule anything for Day 2 - I kind think it should be self-organizing 05:29:18 juhp: it can be self organized but at least we should add topic we are covering. or planning to work. 05:29:21 but it would be great to have a picture/some idea of what people are planning to do 05:29:38 yes, exactly 05:29:42 yeah hence my suggestion of a table with people in first column 05:29:49 and same time we are 15+ members 05:30:11 this is time where we need parallel groups 05:30:17 right 05:31:09 should we make one more small table for hackathon? or split column in same table. 05:31:13 so only thing is some people might want to work in two particular projects that day say - eg maybe some of the l10n people for example - and there it would be useful to schedule sessions to avoid clashes 05:31:22 Yes, it is better we can know what sessions are running when and where, so that any interested ppl can join? 05:31:35 yup 05:31:37 i think starting with a separate table would be easier overall 05:31:47 +1 05:32:01 may be just add more row there? 05:32:02 noriko, most projects may just run the whole day 05:32:06 aha nice. 05:32:14 juhp, oh, really?! 05:32:51 but juhp I see you here and there, many places. how come you can join? 05:33:53 noriko: yeah, that is going to be tricky but if we have one lead for each hackathon, there other members can move in between 05:34:05 s/there/then 05:34:12 noriko, that was show of interest 05:34:32 idea was today to get closer to real plans - I probably can't do all of those :) 05:34:33 juhp: one more column, time? 05:34:51 time and day 05:35:05 lets create a table and see how it goes 05:35:10 I thought for Mon 05:35:14 yes 05:35:30 yes, sounds nice. 05:35:52 I think we need to see the basic list first and then decide if we need more structure/scheduling 05:36:15 yup 05:36:18 sure. 05:36:27 i'd say it would be nice to make time frame rather than running all day, so that we can ask key persons to join. 05:36:48 but maybe nice to have a barcamp schedule board with slots that people can just book times 05:37:20 with room-name, maybe? 05:37:29 there is only one big room 05:37:37 and we sit in groups 05:37:49 so its easy to jump around too ;) 05:37:51 the room is large enough for > 50 people 05:37:59 oh, c... easier to move around :-D 05:38:04 :) 05:38:12 right 05:38:19 free movement 05:38:26 hahaha 05:38:55 :D 05:39:12 erm so you're listing projects not people... 05:39:16 anyway 05:39:36 * juhp will just let the self-organization happen :) 05:39:51 yeah lets list the projects and leave column for people. they can add their names :) 05:40:06 but pravins we already had that list... 05:40:23 apeter, right I was planning the opposite 05:40:40 juhp: but i think we are not going to cover all? 05:40:51 :) 05:40:58 right hence asking each person what they want to do 05:41:13 anyway it is fine I guess 05:41:18 yeah, i added mine stuff :) 05:42:49 let me ping all again. 05:43:30 aeng fujiwarat juhp noriko paragan pravins tagoh_ mkim please add topic you are interested in working and collaborating in table https://docs.google.com/document/d/1p2jAxbo778CvBbr0h6n9hICTkQh5rMmbKY7g0kdGUWE/edit# 05:43:33 is there any timeslot for each topics? so that we can schedule which topic to attend first and next? For example, Hackathon session 1 11:00-13:00, and second sessions etc? 05:43:51 will all the topics be on at the same time all day? 05:44:14 mkim: no, we should ideally schedule/plan. As you said. 05:44:23 mkim, you can add a time if you want on the right column 05:44:37 pravins, do you mean sessions, right? 05:44:48 I'v already added my self there. 05:44:58 yeah it might be good for Hackathon project leads to put the time slots? 05:45:11 so that participants can put the names down for multiple sessions without conflicts 05:45:46 +1 05:45:56 or should we make a barcamp-style schedule table? 05:46:16 * juhp is not sure if everyone knows about barcamp 05:46:41 juhp: yeah, it will help. 05:46:53 then we just need to make some virtual rooms (spaces) 05:46:54 so one time slot and hackathon topics happening parallel. 05:47:19 4 "large rooms" enough? 05:47:19 i see number of hackathon's can happen parallel. 05:47:48 yeah, 4 is good for now. May be we need to remove one if required. 05:47:50 no group is forced to use the rooms though? 05:48:10 so we might still lose info on what everyone will do 05:48:22 (hence why I wanted to individual list...) 05:49:16 its big room so we can simply divide groups in different corner ;) 05:50:41 hmm I see I inserted the tables in the wrong place nm... 05:50:41 pravins, if loosely scheduled time slot may help people move around? 05:51:48 yes 05:52:13 yup 05:53:52 (fixed) 05:54:17 juhp: thanks :) me changing little bit 05:56:43 looks nice, now we can easily identify conflict if one person involve in 2 topics at same time. 05:56:47 specifically lead 05:59:13 true (y) 06:00:05 * juhp supposes lead will report on final day in the "lightning presentations" 06:01:35 juhp: yes 06:02:07 how many are we? 06:02:22 me 06:02:32 I think we can have few more topic during same slot 06:02:34 in total I mean 06:02:41 15+ 06:03:01 Anish and Sundeep Z-P-Client can happen parallel in first session 06:07:41 I would like each/all person also individually to fill out the individual planned project list below to get a better overall picture of what everyone is planning to do there 06:07:58 * pravins liked the idea of table :) 06:08:08 pravins, early perhaps for Sundeep... 06:08:51 yeah, may be second half is good. 06:09:15 not sure if we need to schedule everything - but at potential clashes yes 06:09:39 people should be able to grab space/time when they want 06:09:51 s/at/at least/ 06:10:29 yeah, flexibility is required but i think lead will manage it. 06:11:46 everyone should be able to edit now 06:12:00 if you can't then please refresh 06:12:12 sorry it was on comment for non-shared people before 06:12:37 not sure if we need leads either everywhere :) 06:14:53 mkim, noriko ^ 06:15:00 about edit 06:16:54 so, now adding topic and scheduling hackathon, goes back to attendees item. 06:17:12 should we simply drop an email for it? and revisit on Wed? 06:17:28 any other things for second day schedule? 06:19:47 list interested hackathon in Projects? 06:20:26 yes. 06:20:34 okay, do it now. :) 06:21:33 schedule looks nice to me now. Clean and clear !! 06:21:40 cool 06:21:57 just one need to grab hackathon slots to avoid clashes in interested topics. 06:22:03 even if not that is fine. 06:26:15 #action All attendees please add your interested hackathon projects in schedule page. 06:28:42 guys, need to go offline now.. i will be looking at the doc tonight. Thanks pravins for organising this 06:29:44 aeng: no problem. 06:30:51 schedule looks good now. 06:31:03 #topic Open Floor 06:31:29 did we missed anything? else will close in couple of minutes 06:33:08 I guess still time but need to think about lunch arrangements too I guess soon 06:33:28 also I think we will have a FAD dinner one night 06:33:38 juhp: yeah, we have some budget available for that. 06:33:53 perhaps we can take that next week 06:33:55 I can help for them. just need how much budget we have at the end. 06:33:57 Need to work with you offline on budget before final work on that. 06:34:01 tagoh_, great! 06:34:08 yes 06:34:12 tagoh_: nice. Lets decide this in Wed. then. 06:35:04 thanks all for meeting closing now. We will have much better picture in coming Wed. meeting. 06:35:09 #endmeeting