15:00:01 #startmeeting Weekly TSC meeting 15:00:01 Meeting started Tue Feb 28 15:00:01 2017 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:01 The meeting name has been set to 'weekly_tsc_meeting' 15:00:12 #topic rollcall 15:00:21 #chair rpaik 15:00:21 Current chairs: rpaik tallgren 15:00:24 #info Hongbo 15:00:25 #info Morgan Richomme 15:00:27 #info Fatih Degirmenci 15:00:49 #info Trevor Cooper 15:00:54 #info Tim Irnich 15:01:04 #info Ash Young (for Uli) 15:01:12 #info Tapio Tallgren 15:01:13 #info Brian Skerry 15:01:17 #info Jose Lausuch 15:01:23 #info Bryan Sullivan 15:01:34 #info Dan Radez (proxy Dave Neary) 15:01:59 #info Jack Morgan 15:02:06 #info Bin Hu 15:02:11 we have a quorum 15:02:20 #topic approval of previous minutes 15:02:30 #info Frank Brockners 15:02:31 #info no comments on minutes thus approved 15:02:32 #info Rossella Sblendido 15:02:39 #info Edgar StPierre 15:02:55 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-February28,2017 agenda for today's call 15:03:58 #info no other agenda proposed 15:04:44 #topic on-going items 15:04:54 #info rpaik: Aimee Ukasick is now PTL of Copper so please include her in quorum checks 15:05:07 #info Stuart Mackie 15:05:36 bryan_att the quorum is for TSC members (not PTLs) 15:06:04 rpaik: PTLs are TSC members AFAIK 15:06:29 #info 15:06:51 bryan_att: not in my case :) 15:07:05 bryan_att: not all PTLs are TSC members 15:07:30 frankbrockners: I thought we had changed that, but OK 15:07:30 #info reminder on project proposals for VINA/Bamboo/sampleVNF plus E-release naming survey 15:07:50 #info Julien 15:08:04 #info there's also an Etherpad for Dovetail 15:08:26 #topic Community Awards 15:08:42 #link https://etherpad.opnfv.org/p/Dovetail_Danube_Planning 15:09:04 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/015246.html email discussion on awards 15:09:17 #info rpaik presented the proposal for community awards, moving from time-based awards to release based one 15:10:14 #info The categories are mostly the same: interns category and community support have been added 15:11:34 #agree 15:11:40 #agree on the new release-based award process 15:11:41 #agree 15:11:48 #agree 15:12:00 #topic docs.opnfv.org update 15:12:16 #topic docs.opnfv.org update 15:12:41 #link docs.opnfv.org 15:14:03 #info Sofia discusses the migration to readthedocs and is looking for agreement on the Docs structure as can be found on docs.opnfv.org 15:15:27 #info also looking for feedback from the marketing team on the look & feel 15:18:02 #info project teams have been asked to restructure their repo's under /docs but the content should auto-populate in docs.opnfv.org 15:20:15 #info trevor_intel notes that the documentation should not be targeted for people that are already familiar with the project 15:22:04 #info discussion that it would make sense to divide the documentation for developers and users 15:25:59 #info #info Comment that the documentation page should use descriptive names like "functional testing" or "performance testing" instead of project names 15:26:08 #undo 15:26:08 Removing item from minutes: 15:26:17 #info Comment that the documentation page should use descriptive names like "functional testing" or "performance testing" instead of project names 15:27:20 #link http://docs.opnfv.org/en/latest/ 15:29:21 #info frankbrockners points out that currently OPNFV is deployed with scenarios so it is difficult to structure the documentation 15:32:43 #info consensus to continue with the currently proposed docs structure for the Danube release but can visit other options such as a separate page for developer documentation 15:34:15 #info morgan_orange notes that testing groups docs are also under opnfvdocs 15:34:57 #topic OpenStack PTG readout 15:37:34 #info jose_lausuch summarizes Interop WG meetings in Atlanta where he had a chance to discuss NFV reference test cases with the OpenStack community 15:37:50 #info I was there as well and have a couple of points to make also 15:40:11 #info jose_lausuch noted that having a developer focused events was helpful 15:41:23 #info bryan_att noted that OpenStack refstack didn't expand too much energy on "securing" the results 15:42:06 #info bryan_att pointed out that the OpenStack refstack includes features that are common in public OpenStack clouds but do not include all OPNFV features 15:43:01 #info adoption across many public clouds is a gate for inclusion in refstack; we will need to extend it until the features that opnfv depends upon (e.g. Congress) get widely adopted 15:43:51 #action jose_lausuch to send out a summary note to mailing lists 15:43:54 #info also they don't put too much emphasis on preventing gaming of the system - they think the SUT/distros will be inhibited from that 15:44:08 #topic Danube/E-release planning 15:45:41 #info dmcbride shares the data on MS6 compliance data 15:46:23 #info first requirement for MS6 is test case implementation (currently 9 projects have yet to report) 15:46:46 #info also re the interop challenge, it was clear that we probably would not have time to stand up a real NFV interop challenge test, though the Open-O team indicated they would work one for Open-O (the issue is that the interop challenge occurs on-stage, and *must* work flawlessly across a set of OS distros - much emphasis on that) 15:47:18 #info 2nd MS6 requirement is preliminary documentation (11 projects have yet to report) 15:48:16 #info some projects do not have test case requirements (but need to have documentation) 15:48:50 #info dmcbride requests PTLs to send the latest if not done already 15:49:17 #action dmcbride to post his slides on the wiki 15:50:50 #info for E-release timeline, dmcbride notes that proposal is to maintain 2.0/3.0 releases and the details can be found in the mailing list 15:53:52 #action rpaik to add E-release timeline vote plus CI/CD evolution topics to the TSC call next week 15:56:43 #topic graduation reviews 15:57:37 #info tallgren notes that graduation reviews is another mechanism for community recognition 15:57:42 #link https://wiki.opnfv.org/display/SWREL/E-River 15:58:05 #info E-release schedule proposal ^^ 16:00:41 #endmeeting