14:00:31 #startmeeting OPNFV TSC 14:00:31 Meeting started Tue May 3 14:00:31 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:31 The meeting name has been set to 'opnfv_tsc' 14:00:37 #topic Roll Call 14:00:42 #info Chris Price 14:00:50 #chair rpaik 14:00:50 Current chairs: ChrisPriceAB rpaik 14:01:20 #info Tapio Tallgren 14:01:40 #info Uli Kleber 14:01:43 #info Gerald Kunzmann 14:01:45 #info Frank Brockners 14:02:54 #info Dave Neary 14:03:15 #info Morgan Richomme (IRC only) 14:03:16 #info Dirk Kutscher 14:03:24 #info Brian Skerry 14:03:33 we have a quorum now 14:03:41 morning 14:03:44 #topic Approval of previous minutes of meeting 14:03:54 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-April26,2016 previous meeting minutes 14:04:05 #info no comments received, minutes approved 14:04:07 #info Jonas Arndt 14:04:20 #topic Agenda Bashing 14:04:24 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-May3,2016 current agenda 14:06:02 #topic Highlights from the OpenStack summit 14:07:01 #info Bryan Sullivan 14:07:24 #info ChrisPriceAB met with the OpenStack infra team on Friday of the Summit last week 14:07:37 #info trying to make connections with the OPNFV infra team 14:07:42 thanks ray 14:08:05 #info uli-k notes that OpenStack and OPNFV have a very good relationship now 14:08:46 #info the openstack community are encouraging OPNFV members to bring ideas and discussions to them early to improve our ability to deliver features into openstack 14:10:04 #info bryan_att indicates there is a lot of synergy across our activities and operators activities. There is opportunity for further coordination in these forums 14:11:32 #info ildikov also describes key openstack members were attending OPNFV sessions to learn more an interact with OPNFV members, we should look to use this engagement to further collaborate 14:12:44 #info dneary noted that feedback from OpenStack was to approach them with a problem and collaborate with them on a solution 14:12:53 #info Edgar StPierre 14:13:38 #topic Design Summit update 14:13:47 #link https://wiki.opnfv.org/display/EVNT/Berlin+Design+Summit+Planning main design summit planning page 14:14:42 #info Julien 14:14:46 #link https://wiki.opnfv.org/display/EVNT/Proposals+for+Berlin+Design+Summit+Session session proposals page 14:15:50 Any themes preferred to be prioritized? 14:15:50 #info rpaik proposes to keep the proposal submissions open until the end of the month, approximately 27th of May. 14:17:22 E.g. What types of session proposals are preferred, e.g. Project intro/update, tech discussions, process/collab discussions, etc... Is there a preference 14:17:50 bryan_att: I think if we have a volunteer committee to help they should answer those questions. 14:17:59 So people don't just repropose the sessions that didn't make it into the main summit 14:18:33 #action rpaik to send call for volunteers to the mailing list for design summit planning 14:18:36 #info rpaik adds that there will be a "project track" in the main area for projects to present and discuss their objectives and activitiez.. 14:18:57 #info projectors will be availble in both rooms 14:19:11 My approach would be community voting on the sessions that did not make it into the main summit, and which were felt by the summit committee to be better for the design summit. 14:19:37 Since we have already done that first level of triage on likely the same subjects 14:19:42 Can we have a track for hardware acceleration topic like DPACC, ODP, OFP, DPDK? 14:20:51 #topic OPNFV Technical Governance Discussion 14:20:58 #one question any team is responsible for the infrastructure of the OPNFV use, like etherpad, Jira 14:21:40 Julien-zte: the OPNFV help desk is responsible 14:22:27 #bryan_att, thanks, I will propose suggestions there 14:22:33 Julien-zte you can open a ticket with email to opnfv-helpdesk@rt.linuxfoundation.org 14:22:57 Why wouldn't all be open? 14:22:57 thanks, rpaik 14:23:19 #info feedback can be sent to mailing lists or email community-feedback@opnfv.org 14:23:25 I would be concerned if there were private conversations in this 14:24:32 #info the email alias is for annonymous feedback if people are uncomfrotable providing feedback in public mailing lists 14:25:12 #topic Colorado planning and activities 14:25:47 #info dcmbride outlines that the project team is still working on the details of the milestones for Colorado. 14:26:10 #info the milestones are becoming clearer and some milestones are ready for settling upon. 14:26:26 #info detailed disucssions occur on the weekly release meeting 14:26:54 #link https://wiki.opnfv.org/display/meetings/Release release meeting wiki page 14:27:16 #info the release meetings are held on #opnfv-release IRC channel 14:27:47 #info the upcoming agenda for the release meeting will be maintained on the wiki page 14:28:10 #topic Colorado infrastructure cross project initiatives 14:32:01 #info ChrisPriceAB notes that we have a bit of a technical debt for OPNFV infrastructure 14:32:31 Did you paste a list? I don't see it 14:33:13 bryann_att, see the agenda page https://wiki.opnfv.org/display/meetings/tsc#TSC-May3,2016 14:34:20 #info suggestion to start a new wiki page for these infrastructure projects 14:36:52 #info shall we form a group or project for infrastructure? 14:37:12 it is out scope of Pharos 14:37:35 #info related to Pharos-164? 14:39:05 #action chrispriceab to reach out to the infra related teams to help establish a common wiki to track items such as these and begin a prioritization activity. 14:39:38 #info interns can also help with some of the initiatives and internship project proposals can be posted at https://wiki.opnfv.org/display/DEV/Intern-projects-page 14:39:41 we have already had some discussion about Pharos, Releng, Octopus(Infra) projects to start working together 14:40:14 #topic AoB 14:40:59 #info no other business identified. 14:41:03 #endmeeting