05:00:14 #startmeeting TSC weekly meeting 05:00:14 Meeting started Tue Oct 25 05:00:14 2016 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic. 05:00:14 The meeting name has been set to 'tsc_weekly_meeting' 05:00:26 #chair rpaik ChrisPriceAB 05:00:26 Current chairs: ChrisPriceAB rpaik tallgren 05:00:49 #topic Roll call 05:00:58 #info Bryan Sullivan 05:01:00 #info Tapio Tallgren 05:01:12 #info Bin Hu 05:01:29 #info Mark Beierl (Proxy for Edgar StPierre) 05:02:03 #info Uli 05:02:08 #info Frank Brockners 05:02:32 #info Morgan 05:02:45 #info rprakash 05:03:39 #info Maryam Tahhan 05:04:21 #topic agenda bashing 05:04:48 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-October25,2016 agenda for the call today 05:05:19 #info Fatih Degirmenci 05:06:12 no new agenda topic 05:06:31 #info no feedback on previous minutes thus approved 05:06:32 #topic Colorado 2.0 status 05:08:20 #info at this point we have 2 scenarios for Colorado 2.0 but neither seem to have documentations associated 05:13:12 #info test result for the SFC isn't fully clear (whether it's good or bad) and ONOS scenario doesn't include Yardstick results 05:15:16 #info dmcbride will need to check with PTLs on the latest status for both scenarios 05:17:00 #info Jack Morgan 05:17:04 #info discussion on keeping both 2.0 and 3.0 releases for Danube and beyond and the consensus that the overhead is low for maintaining monthly releases 05:21:03 #agree to approve Colorado 2.0 release pending follow-up with PTLs by 5pm CET on October 26th 05:22:46 #action dmcbride to send an email update to the TSC members by email tomorrow after 5pm CET 05:23:41 #topic Danube milestone 1 05:23:41 #topic Danube update 05:23:45 #undo 05:23:45 Removing item from minutes: 05:25:03 #info dmcbride still waiting on 8 projects for Milestone 1 documentation 05:26:05 #topic SFQM project scope/name change 05:28:18 #info mtahhan notes that this was announced on mailing list prior to discussion at the Weekly community call 05:31:33 #info mtahhan notes previous focus of the project was on networking traffic 05:32:39 * bryan_att +1 for barometer as a name! 05:33:25 #info project team will start developing plugins for collectd 05:36:12 #info project planning has also started for the Danube release 05:36:36 +1 for baromoter 05:37:22 #info mtahhan notes that the committers for the project will remain the same 05:37:32 #info IMO the work so far on the integration for VES has been very successful as I noted in my email on the VES demos at OpenStack. Adding a general focus on that framework for other collection systems is a good idea, especially if we can avoid having to implement the plugins multiple times, i.e. there be a way for us to connect the plugins to VES or other 05:37:32 backends without having to duplicate too much of the code. 05:37:34 #info the SFQM scope change was announced to the TSC on 12-October-2016 05:39:07 thanks ChrisPriceAB... 05:41:30 #info hongob 05:41:38 #info hongbo 05:42:22 * ChrisPriceAB likes barometer as well. :) 05:43:06 #vote Approve scope change for SFQM project 05:43:19 #startvote Does TSC approve SFQM scope change and name change to Barometer (-1, 0, +1)? 05:43:19 Begin voting on: Does TSC approve SFQM scope change and name change to Barometer (-1, 0, +1)? Valid vote options are Yes, No. 05:43:19 Vote using '#vote OPTION'. Only your last vote counts. 05:43:35 #vote +1 05:43:38 #vote +1 05:43:43 #vote +1 05:43:44 #vote +1 05:43:48 #vote +1 05:43:50 #vote +1 05:43:50 #vote +1 05:43:53 #vote +1 05:43:53 #vote +1 05:43:54 #vote +1 05:44:07 #endvote 05:44:07 Voted on "Does TSC approve SFQM scope change and name change to Barometer (-1, 0, +1)?" Results are 05:44:20 * ChrisPriceAB just wants to note we had used the 2 week period to provide an opportunity for people to review, shortening the period due to lack of early objection may not serve that purpose. (Although in this case the adjustment is obvious.) 05:44:33 #info TSC approves scope & name change for SFQM 05:44:57 #topic discussion on merging existing OPNFV projects 05:46:20 autdio is in out due to spotty hotel wifi 05:47:22 do we need to change/update the project life cycle process? 05:47:54 #info there was a question on how project teams can propose merging two projects (kvmfornfv and ovs) 05:47:58 https://www.opnfv.org/developers/technical-project-governance/project-lifecycle 05:48:36 #info proposal is to post the proposal on mailing list for 2 weeks prior to coming to the Technical Community/TSC meetings 05:48:47 ok, thanks 05:49:48 #topic contribution guidelines 05:51:20 #link https://wiki.opnfv.org/display/DEV/Contribution+Guidelines 05:51:35 #info morgan_orange has added additional text on license & copyright on the above page 05:53:15 #info "Headers must be applied to all contributed code. " -> "Headers must be applied to all contributed code, where possible. Known exceptions are..." 05:53:31 #info discussion on 3rd party directory for non-Apache2 license files, copyright on empty files, and some additional clarification on copyright header 05:54:29 #info "(c) " -> "(c) " (It is mandatory for the copyright owner to be identified. 05:54:59 #info I'll add comments on the wiki. 05:55:21 +1 to improving the Dev pages in general 05:55:33 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111 05:55:49 #info MANO WG report out 05:56:29 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111 slide set for the current status 05:59:45 #endmeeting