14:00:16 #startmeeting TSC weekly meeting 14:00:16 Meeting started Tue Nov 1 14:00:16 2016 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:16 The meeting name has been set to 'tsc_weekly_meeting' 14:00:28 #chair rpaik ChrisPriceAB 14:00:28 Current chairs: ChrisPriceAB rpaik tallgren 14:01:00 #info Tapio Tallgren 14:01:07 #info Bin Hu 14:01:15 #info Edgar StPierre 14:01:19 #info Brian Skerry 14:01:20 #info Ash Young (for Uli) 14:01:43 #info Jack Morgan 14:01:49 #info Mingjiang 14:01:52 #info Fatih Degirmenci 14:02:19 #info Hongbo tian 14:02:20 #info dneary 14:02:38 #info Bryan Sullivan 14:02:51 #topic approval of minutes 14:03:15 #info previous minutes approved due to no feedback 14:03:33 #topic agenda bashing 14:03:47 #info Trevor Cooper 14:03:52 #info Jonas Arndt 14:03:58 we now have a quorum 14:04:20 #info Stuart Mackie 14:05:52 #info Chris Price (running a little late) 14:06:19 #info potential topic next week would be common configuration file and scenario naming 14:06:24 I thought we were also going to discuss the Vision today 14:07:18 #info Vision topic deferred as Morgan is out today 14:09:22 #info a reminder that Summer Time (Europe)/Daylight Savings Time (US) comes to an end 14:09:38 #topic Board meeting update 14:10:17 #info the first half of the Board meeting on October 28th was a joint session with the TSC 14:10:38 #info the meeting started with an update from the End User Advisory Group 14:12:27 #info Project Health Metrics showing project activities was presented 14:12:58 #info bryan_att presented the MANO WG presentation that was distributed to mailing lists 14:13:40 #info tallgren led the discussion on OPNFV architecture and there will be a follow-up in the December Board meeting 14:14:41 #info goals and vision for the Danube release can be discussed as a follow-up to the architecture discussion in December 14:15:42 #info another topic was collaboration among LF networking projects (OPNFV, fd.io, ODL, etc.) 14:16:52 #info ChrisPriceAB and frankbrockners have the action item to start conversation with various Boards to come back with a proposal 14:18:08 #info during the Board meeting there was an overview of Board committees. when C&C had their report out, there was a consensus that there needs to be better alignment among testing projects 14:19:32 #info decision was made to dissolve the Strategic Planning Committee 14:20:40 #info OPNFV values & goals were also discussed and this was followed up with membership engagement discussion 14:21:45 #info bryan_att is working on a scenario mapping/graphic and is looking for an appropriate wiki page to post 14:23:39 #info there is an ask to the TSC to get to the next level of detail on OPNFV architecture 14:24:47 +1 get things rolling in an open and collaborative manner. (wiki is good for that) 14:25:18 #info discussion on where we could collaborate on a common document for the OPNFV architecture 14:26:55 #action tallgren will start a wiki page as a start and announce on mailing list 14:27:09 #topic Termination review for Resource Scheduler 14:27:20 #topic termination review for RS 14:27:39 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=7769828 14:28:36 #link https://lists.opnfv.org/pipermail/opnfv-tsc/2016-October/003089.html termination review request e-mail 14:29:22 #info Mingjiang discussed the original motivation for RS but noted that it has not been active since the Brahmaputra release 14:30:06 #info Mingjiang also notes that no coding/documentation work has been done and a better home for this project maybe OpenStack 14:30:43 #info ttallgren asks if there were items from the project that should be recognised. 14:30:58 #info there has been no output from the project in the OPNFV repo 14:31:14 * ChrisPriceAB thinks we need a vote to capture the closure of the project 14:31:37 * dneary agrees 14:31:53 #startvote Does the TSC approve terminating the Resource Scheduler project? (-1, 0, +1) 14:31:53 Begin voting on: Does the TSC approve terminating the Resource Scheduler project? Valid vote options are , -1, 0, +1, . 14:31:53 Vote using '#vote OPTION'. Only your last vote counts. 14:32:02 #vote +1 14:32:07 #vote +1 14:32:07 #vote +1 14:32:08 #vote +1 14:32:08 #vote +1 14:32:10 #vote +1 14:32:11 #vote +1 14:32:13 #vote +1 14:32:14 #vote +1 14:32:15 #vote +1 14:32:22 #vote +1 14:32:31 #endvote 14:32:31 Voted on "Does the TSC approve terminating the Resource Scheduler project?" Results are 14:32:31 +1 (11): dneary, ashyoung, bryan_att, hongbo1, tallgren, bin_, StuartMackie, fdegir, bjskerry, edgarstp, jmorgan1 14:32:42 yeah I've got it 14:33:18 thanks for working with the community and we will continue to consume the open stack code in any case. :) 14:33:36 rpaik: I can help with Archived concepts in the wiki 14:34:00 I think that would be useful mbeierl, most projects maintain an "archived projects" area. 14:34:46 #info rprakash 14:35:00 #action rpaik to work with mbeierl on the archive projects area 14:35:28 #topic graduation reviews 14:36:11 #link https://www.opnfv.org/developers/technical-project-governance/project-lifecycle OPNFV project life cycle 14:36:16 #info rpaik outlines that as OPNFV matures we should turn our attention to graduation reviews for our mature projects like functest and pharos. 14:36:52 #info all projects today are in an "incubation phase" and some of our projects would seemto qualify for graduation. 14:37:25 looking forward to a "graduated" polo shirt ;) 14:37:36 +1 14:37:37 #info the process for graduating is described on the project life cycle page, requiring a 2 week presentation prior to TSC review 14:38:38 #info discussion on what it means to for a project to "graduate" 14:39:13 * ChrisPriceAB thinks jmorgan1 has enough free clothing!!! 14:39:20 It moves on to college 14:43:59 #info I'm unsure whether the focus on this is worth the time on the call; can the ask be better explained first on the list? 14:45:20 #action rpaik to start a mailing list discussion on graduation reviews (e.g. purpose, expectations, etc.) 14:46:08 #topic Colorado + Danube release planning and activities 14:46:08 #topic Colorado and Danube planning and activities 14:46:14 hehe 14:46:14 :-) 14:46:22 #undo 14:46:22 Removing item from minutes: 14:46:49 #info Colorado 2.0 has been pushed out to November 10th, 2016 14:47:14 tallgren, If you're talking about defining core OPNFV in terms of scenarios, there is a related topic, which is that scenarios are not under the TSC 14:47:55 and scenario's are essentially a release project artifact rather than a technology development activity. 14:48:17 #info dmcbride notes that one of the scenarios is dependent on Fuel and the Fuel team needed more time 14:48:53 #info there's also a possibility of including fd.io scenario on Colorado 2.0 14:50:50 #agree TSC acknowledges pushing the Colorado 2.0 date to November 10th, 2016 14:51:01 #info there are no changes to Colorado 3.0 release 14:52:05 #info Milestone 1 for Danube was last week and 34 projects have submitted their release plans 14:53:00 #info Movie team expressed their intent to participate 2 days after the deadline. TSC had no objections on this 14:55:21 #info dmcbride will also be discussing 2.0 plus 3.0 releases in his release meeting 14:56:14 #info discussion on intercepting Ocata release by delaying the Danube release by about a month 14:59:01 Would we be able to support newton in some scenarios ? 15:00:10 #link mano meeting will be weekly starting Wednesday this week : https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111 15:00:12 #action rpaik to start an email thread on Ocata and PTG 15:00:40 #endmeeting