12:51:03 <kennypaul> #startmeeting TSC, 2017-09-27-F2F 12:51:03 <collabot`> Meeting started Wed Sep 27 12:51:03 2017 UTC. The chair is kennypaul. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:51:03 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic. 12:51:03 <collabot`> The meeting name has been set to 'tsc__2017_09_27_f2f' 12:51:31 <kennypaul> #chair phrobb, SteveT 12:51:31 <collabot`> Current chairs: SteveT kennypaul phrobb 12:51:47 <kennypaul> #topic rollcall 12:53:39 <Huabing_Zhao> #info Huabing Zhao, Proxy of Zhaoxing Meng, ZTE 12:58:17 <JasonHunt> #info Jason Hunt, IBM 13:03:05 <SteveT> #info Stephen Terrill, Ericsson 13:03:23 <RannyHaiby> #info Ranny Haiby, Nokia 13:05:15 <frankbrockners> #info Frank Brockners, Cisco 13:06:03 <cdonley> #info Chris Donley Huawei 13:09:19 <ArthurBerezin> #info, Arthur Berezin, Cloudify 13:11:07 <AayushJio> #info aayush bhatnagar Reliance Jio 13:11:18 <SteveT> #topic Opening and Agenda 13:11:29 <jamil> #info jamil for Orange 13:11:51 <phrobb> #info Mazin of AT&T is present 13:12:45 <phrobb> #info Alla of Amdocs is present 13:13:13 <phrobb> #info Lingli of China Mobile is present 13:14:28 <SteveT> #topic Beijing Release Calender Proposal 13:14:36 <SteveT> #info presented by Gildas 13:14:50 <Susana> #info Susana Sabater Vodafone 13:19:06 <SteveT> #info 6 month release would imply May 24 release for Beijing. 13:30:14 <SteveT> #info Question was raised whether we should support also an additional Amasterdam release. 13:30:44 <SteveT> #info Question - could we testing earlier? 13:31:20 <SteveT> #info The response was that we can 13:33:19 <SteveT> #info Target M1 for architecture and S3P reqs 13:36:37 <SteveT> #info Question: Do we maintain Amsterdamn or not. We need to decide what to do for vulnerabilities as well. 13:37:47 <SteveT> #info Start with code integration as earlier as possible (3 months??). 13:38:42 <SteveT> #info Need to decide on what is a release and do we branch. i.e. what is the branching strategy. 13:40:07 <SteveT> #info Extend the period between api freeze and code freeze by bringing earlier 13:41:57 <phrobb> #info Lingli asks if it is possible to offset the projects so that those projects that are depended upon hit API freeze sooner then those that depend on them. 13:43:51 <SteveT> #info Consider API freeze based on dependancy graph. e 13:47:56 <SteveT> #info Discussion about branching. Need to be very selective about the defects to print and bring from the main branch into the amasterdam release. Then there was a proposal that we should not have maintanance of Amsterdamn. 13:51:52 <SteveT> #info there was a proposal that a team could decide its branching strategy (i.e. when it decides what is master and what is "release". 13:52:39 <SteveT> #info Consider that SONAR works of the latest update. 13:53:56 <SteveT> #info When considering the branching strategy, need to consider whether allowing people to play with a version and fix the bugs. 13:55:11 <SteveT> #info Will come back to in the TSC Oct 5th. 13:58:00 <SteveT> #info As additional information, there is a separation of component releases from ONAP release 14:00:52 <SteveT> #info There is the comment that the Casablanca release will not be November, we should bring it into say Septebmer to align with oh 14:01:00 <SteveT> #topic Release Versioning 14:01:44 <SteveT> #info Release version proposal was presented by Jamil. 14:02:04 <cdonley> #info correction - not LATE November. Possibly Sept to align with ODL/OPNFV/etc. or early Nov. TBD. 14:07:51 <SteveT> #info proposal is the Symantec versioning (x.y.z). 14:08:33 <SteveT> #there was a comment that we even if we go for this strategy, we need to be careful about when to provide a minor release in anycase due to the work it implies. 14:10:31 <SteveT> #info If approved we need to update and reflect the minor releases in the planning. 14:13:06 <SteveT> #info Helen raised that there has been a proposal for a project to release independently. This means that a project can release without having a "ONAP" release. 14:13:49 <SteveT> #info Helen raised that the integration infrastructure supports independent project release. 14:14:01 <phrobb> #info comment made recommending that we build a release plan and tools to allow components that don't have child dependents to release totally orthogonally from the ONAP release. ONAP could lead this type of flexibility 14:19:51 <phrobb> #info Gildas notes that devs don't like to work on main./bugs on stable release. Others note that bug fixes often happen in master and are cherry-picked to stable branch 14:25:17 <JasonHunt> fyi, was the meeting started in IRC? 14:26:13 <SteveT> #info updated proposal will be presented to TSC next week. 14:28:16 <SteveT> #topic diversity and upstream culture 14:33:29 <SteveT> #info There was a question about how to handle the 36 hour rule on commits. The conclusion was that it was ok to abandon the committ at that stage. 14:33:43 <SteveT> #topic December F2F 14:35:03 <SteveT> #info The December meeting will be both a ONAP developer meeting as well as a ONAP user meeting. 14:35:29 <SteveT> #info It is on 11-13 December, Santa Clara. 14:37:07 <SteveT> #info Aside from Beijing focus, there will be videos etc to address vacation. There is also a consideration of a Hackathon. 14:40:55 <SteveT> #info Correction Aside from Beijing focus, there will be videos etc to address end users. There is consideration of a hackathon on the first day. 14:44:31 <SteveT> #info There was a suggestion for a hackfest of the developers working on the projects as well. 14:48:05 <SteveT> #info Next opportunity would be is in March. 14:48:33 <SteveT> #info consider other universities and getting ONAP univeristy material adopted in the universities. 14:52:28 <SteveT> #info There was a suggestion from the modelling committee to suggest a 1 day workshop with SDOs. 14:52:44 <SteveT> #topic ONAP marketing 15:02:14 <SteveT> #info Marking update was presented 15:08:08 <SteveT> #info If it is a for profit event using ONAP. Inform LF. 15:08:23 <SteveT> #info What about also targeting enterprise industry events. 15:13:04 <SteveT> #info what about the December OPNFV plugfest? 15:14:08 <SteveT> #info - response was that we were trying to colocate the ONAP F2F in december with the OPNFV plugfest. It wasn't fesible. 15:14:21 <SteveT> #topic Reward 15:16:29 <SteveT> #info different awards a suggested . Company, information, .... 15:17:58 <SteveT> #info For those that feel strongely about the awards, inform Mazin. 15:18:40 <SteveT> #info Apply the awards in the Dec F2F meeting 15:19:42 <SteveT> #topic Lessons Learned 15:20:18 <SteveT> #info Due to lack of time, Eric and Catherine were requested to distribute the work. 15:20:23 <SteveT> #topic AOB 15:20:57 <SteveT> #info Reminder. sub-committee coordinoators to provide weekly update. 15:22:52 <SteveT> #topic Functional Requirements for R2 15:23:20 <SteveT> #info Alla presented the functional requirements for R2 there were a summary of the UC work. 15:30:58 <SteveT> #info This identifies what is considered as important. Further work is required to dig into what is the gap from Release 1 15:33:27 <SteveT> #info integration with thirdparty controllers is interacting with 15:40:46 <kennypaul> #endmeeting