16:56:51 #startmeeting tsc 16:56:51 Meeting started Thu Aug 28 16:56:51 2014 UTC. The chair is phrobb1. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:56:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:56:51 The meeting name has been set to 'tsc' 16:56:59 #info dmm 16:57:05 #link https://wiki.opendaylight.org/view/TSC:Main (TSC Call Agenda) 16:57:07 #info regXboi (partial so far) 16:57:36 #info Lenrow 16:57:38 #info Chris Price in attendance. 16:57:50 are we actually starting *early* today? 16:58:42 @tbachman no 16:59:06 * ChrisPriceAB define "early" 16:59:21 #topic TSC members please #info in 16:59:33 #info Chris Price 16:59:40 #info George Zhao for release 17:00:17 #info lenrow 17:00:34 * ChrisPriceAB with a d 17:01:40 #info regXboi now fully there 17:02:26 rex 17:02:30 * regXboi cringes but... 17:02:38 phrobb1: want to share the pen? 17:02:41 #chair edwarnicke regXboi gzhao Madhu 17:02:41 Current chairs: Madhu edwarnicke gzhao phrobb1 regXboi 17:02:45 regXboi: yes 17:02:46 ed, can you dial in 17:02:52 On my way 17:02:58 tbachman: you want in on the party? 17:03:03 :) 17:03:05 #info EdM_ 17:03:12 #info edwarnicke 17:03:14 #info Ivan Wood 17:03:21 #chair tbachman 17:03:21 Current chairs: Madhu edwarnicke gzhao phrobb1 regXboi tbachman 17:03:29 #topic Agenda Bashing 17:04:07 #info regXboi will be finding a proxy for next week as I will be on vacation 17:04:44 #link http://www.opendaylight.org/news/events 17:04:55 #undo 17:04:55 Removing item from minutes: 17:05:00 #info recording started 17:05:04 #topic Updates 17:05:19 #link http://www.opendaylight.org/news/events upcoming events 17:05:31 #info Chris Wright 17:05:54 Dave say yes please 17:07:51 #info TSC trying to orginaize a face-to-face meeting around the design summit 17:08:47 who’s the professor? 17:08:52 #info suggestion of a three hour meeting (cdub asks about a three hour tour) 17:09:18 #action phrobb1 to kick off something on the TSC list to discuss this 17:09:21 #undo 17:09:21 Removing item from minutes: 17:09:44 #action phrobb1 to kick off something on the TSC list to discuss possibility of TSC face-to-face during the design summit 17:09:54 #action phrobb1 to send call for topics for upcoming design summit to mailing list later today (8/28) 17:10:45 #info edwarnicke asks about unconference time being available 17:11:50 #info format for the summit might have a few sessions on topics of interest in the morning and close, with smaller breakout sessions 17:11:58 :) 17:13:00 #info phrobb1 says that the sessions on topics will be on *design* 17:13:12 * tbachman wonders what that looks like in meetbot html minutes 17:14:39 #info CASP3R_ says there is about a 90% pass rate on the integration tests 17:14:44 did I get that correct? 17:14:56 #topic At large elections 17:15:02 #info election closes tonight 17:15:10 only for the base_of13 suite tbachman 17:15:20 CASP3R_: thx 17:15:42 #info voting begins on Sept 1st, ands on Sept 15th 17:15:55 #info cutoff for nominations is 5pm PST today 17:16:24 #link https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit#gid=1136082068 17:16:36 #info correction: voting beings on 9/1 and *ends* on 9/15 17:16:47 regXboi: thx :) 17:16:50 #topic Update on Helium Release Status 17:17:15 #link https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit#gid=1136082068 current status 17:17:23 regXboi: beat me to it :) 17:18:59 * regXboi wonders how status can be green when API Frozen is red.... 17:19:23 * regXboi wonders or status can be yellow when API Frozen is red.... 17:19:36 * regXboi notes but I wonder about a lot :) 17:20:04 #info Defense4All has not reported status since M4 17:21:56 #info definition of Code Freeze created during Pre-M5 Developer Meeting == Code Freeze means that no new features/functionality are to be allowed into the Helium code base.  Only errors/bugs identified in the bugzilla system should be allowed.  The exceptions to this include new tests, and documentation.  Packaging, ie Karaf packaging must be completed by M5.  Errors/bugs found post M5 are still bugs and they may be cr 17:23:52 #info mlemay_away has created a Karaf tracking spreadsheet 17:23:58 #link https://docs.google.com/a/linuxfoundation.org/spreadsheets/d/12MWfLYNG_YO8pnUt5CrFD2xL1vHUXcmnUNrH-m6EdC0/edit#gid=0 17:29:11 #link https://docs.google.com/a/linuxfoundation.org/spreadsheets/d/16-SbSzdBzTXEk8lD6Q09zl-Ip8jBU3B8_BBqRPXGimg/edit#gid=0 <— Link to Documentation Tracking SS for Helium. Each project should provide info 17:30:24 #link https://wiki.opendaylight.org/view/CrossProject:Documentation_Group:Documentation_Guidelines <— Link to Documentation decision matrix for "what should each project document and where to put it" 17:31:09 #info George asks: should M5 date change from 9/1 to 9/2 as 9/1 is a U.S.A. holiday 17:32:23 #startvote shall the TSC change M5 date to Tuesday 9/2/2014? -1, 0, +1 17:32:23 Begin voting on: shall the TSC change M5 date to Tuesday 9/2/2014? Valid vote options are -1, 0, +1. 17:32:23 Vote using '#vote OPTION'. Only your last vote counts. 17:32:30 #vote +1 17:32:33 #vote 0 17:32:34 #vote +1 17:32:36 #vote +1 17:32:39 #vote +1 17:32:42 #vote +1 17:32:56 #vote +1 17:33:00 * ChrisPriceAB EMEA doesn't get such holidays! 17:33:14 ChrisPriceAB: you get all the other ones 17:33:19 #endvote 17:33:19 Voted on "shall the TSC change M5 date to Tuesday 9/2/2014?" Results are 17:33:19 0 (1): ChrisPriceAB 17:33:19 +1 (6): dlenrow, regXboi, dmm, edwarnicke, cdub, IvanWood 17:33:21 ChrisPriceAB: haha 17:33:22 :D 17:34:57 #info edwarnicke notes that mlemay_away has done much for the project at large to the detriment of his "reservation" project and it would be bad if "reservation" was removed from the release for being late to code freeze. 17:36:11 #info Madhu asks: with the long weekend and the need to finish karaf work for many projects, slipping to 9/5/2014 for M5 would be a better date for the project 17:38:03 #startvote shall the TSC change M5 to 9/4/214? -1, 0, +1 17:38:03 Begin voting on: shall the TSC change M5 to 9/4/214? Valid vote options are -1, 0, +1. 17:38:03 Vote using '#vote OPTION'. Only your last vote counts. 17:38:06 #vote +1 17:38:08 #vote 0 17:38:09 #vote +1 17:38:14 #vote +1 17:38:14 #vote +1 17:38:17 #vote +1 17:38:34 #vote +1 17:38:39 #endvote 17:38:39 Voted on "shall the TSC change M5 to 9/4/214?" Results are 17:38:39 0 (1): regXboi 17:38:39 +1 (6): dlenrow, dmm, edwarnicke, ChrisPriceAB, cdub, IvanWood 17:39:00 #info note: on that vote it is 9/4/2014 17:39:07 #agreed M5 will be changed to Thursday 9/4/2014 17:40:28 #topic karaf 17:42:26 #link https://wiki.opendaylight.org/view/Karaf:Step_by_Step_Guide wiki page describing how projects can “karaf” their project 17:47:24 #topic back to the Helium Release Status 17:47:31 #topic M5 redux 17:47:56 #info gzhao asked the TSC whether we should have projects in red status to report more frequently (e.g. daily) 17:48:14 #info question: for projects that are red, should the tsc require projects in "red" status to report frequently (such as daily)? 17:48:52 #action gzhao to ask projects to report daily nicely 17:49:14 #info gzhao asks what communication options/channels there are for projects that can’t be reached 17:50:31 #topic infrastructure 17:52:08 #info There are a lot of projects that are placing requests on infra the closer we get to the release. phrobb1 says we should try as a group to minize fires with roadmaps, and coming up with a method to ensure we have fair and consistent priorities for things that the infrastructure team works on, and to minimize thrashing of those resources. 17:52:54 #info One recommendation is to have an infra-specific discussion at the design summit for the projects 17:54:03 (sorry if I missed something — had phone call) 17:55:01 Tbachman: We voted to disband 17:55:05 #info there are some near-term needs, and the LF need some direction no priorities 17:55:07 dlenrow: :P 17:55:17 nice pics on twitters, btw :) 17:55:36 #info there needs to be an infrastrure discussion at the design summit to address "just in time" issues post Helium 17:55:58 #info which requires better proactive resource planning 17:56:30 regXboi: thx for the elaboration :) 17:56:36 #info regXboi wanders away for another meeting 17:56:46 regXboi: I’ll continue 17:57:10 regXboi: enjoy the vacation! 17:57:15 tbachman: thanks :) 17:57:25 * regXboi will be leaving ALL computers behind :) 17:57:30 complete darkness 17:57:32 :) 17:58:31 #action edwarnicke to create a list of infra priorities or delegate this task 17:59:43 #endmeeting