14:00:48 #startmeeting tsc 14:00:48 Meeting started Thu May 25 14:00:48 2017 UTC. The chair is CaseyODL. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:48 The meeting name has been set to 'tsc' 14:01:00 #chair phrobb 14:01:00 Current chairs: CaseyODL phrobb 14:01:12 #topic Roll Call 14:01:21 #info TSC Members please #info in 14:01:29 #info Jason Hunt, IBM 14:01:35 #info Ranny Haiby, Nokia 14:01:41 #info Roberto Kung Orange 14:01:44 #info Rajesh Gadiyar, Intel 14:01:46 #info Zhaoxing_Meng, ZTE 14:01:46 #info Chris Donley Huawei 14:03:02 #info Xinhui Li, VMware 14:03:20 #info Xiaojun Xie, China Telecom 14:04:32 #info edwarnicke 14:04:42 #info Alla 14:05:08 Is anyone else not getting audio from the zoom meeting? 14:05:22 hearing now 14:05:49 alla: OK... we are still marshalling 14:06:41 #info Stephen Terrill, Ericsson 14:07:35 #info Parviz Yegani 14:07:35 #info Lingli Deng, China Mobile 14:08:08 Recording is started 14:09:13 #topic Release Naming 14:10:52 #info gildas There are a few proposals that are shared in a Google Doc. 14:11:24 #info cdonley The Marketing Committee will weigh in after the TSC makes a selection. 14:12:08 Could someone pound #link the Google Doc? 14:12:11 There are only 12 Zodiac signs, I would forsee more than 12 Releases 14:12:37 #link https://lists.onap.org/pipermail/onap-tsc/2017-May/000585.html 14:12:44 bhedstrom: I think the Zodiac signs proposal was to start with the Chinese Zodiac, followed by the Western / European one 14:13:19 #link https://docs.google.com/spreadsheets/d/1Qc3PEbm1jpwQ8uHlFSngDnL4p1aAFYGOIT-6OCmONds/edit#gid=0 14:13:43 Right - that would cover 24 releases. 14:13:54 bh526r_: You are not #info in, so your #links are not being recorded. 14:14:10 good, come in again 14:14:28 #link https://lists.onap.org/pipermail/onap-tsc/2017-May/000585.html Mailing List where Mazin asked the entire community to vote. 14:15:04 #link https://docs.google.com/spreadsheets/d/1Qc3PEbm1jpwQ8uHlFSngDnL4p1aAFYGOIT-6OCmONds/edit#gid=0 Google Sheet tracking the Naming proposals. 14:15:48 Hello 14:17:04 #startvote Shall the TSC establish a vote for Release Naming using the TSC and Discuss email lists as the community members allowed to vote? -1, 0, +1 14:17:04 Begin voting on: Shall the TSC establish a vote for Release Naming using the TSC and Discuss email lists as the community members allowed to vote? Valid vote options are -1, 0, +1. 14:17:04 Vote using '#vote OPTION'. Only your last vote counts. 14:17:17 #vote +1 14:17:18 #vote +1 14:17:21 #vote +1 14:17:23 #vote +1 14:17:24 #vote +1 14:17:27 #vote +1 14:17:29 #vote +1 14:17:33 #vote +1 14:17:40 #vote +1 14:17:44 #vote +1 14:17:54 #vote +1 14:18:02 #endvote 14:18:02 Voted on "Shall the TSC establish a vote for Release Naming using the TSC and Discuss email lists as the community members allowed to vote?" Results are 14:18:02 +1 (11): RobertoK, alla, Zhaoxing_Meng, rajesh-intel, JasonHunt, xinhuili, edwarnicke, SteveT, cdonley, Dsauvageau, Lingli_Deng 14:18:06 #agree Mr. Robb will initiate a vote on the Discuss and TSC list for the community to select a Release Name Proposal. 14:18:48 #action phrobb or CaseyODL to initiate a vote on the TSC and Discuss list to select a Release Name Proposals. 14:19:42 #topic Project Reviews 14:19:59 #link to Release naming proposal: https://docs.google.com/spreadsheets/d/1Qc3PEbm1jpwQ8uHlFSngDnL4p1aAFYGOIT-6OCmONds/edit#gid=1437510030 14:20:37 gildas: You have to put the URL before the description. 14:20:44 Also, I linked it already. :) 14:21:17 great thanks CaseyODL 14:21:48 #info Lingli_Deng: We will be doing the first round of reviews 1 week before the meeting in Beijing. 14:22:12 #info Are there any new Proposals coming out, or are we safe to start reviewing? 14:23:33 #info Lingli_Deng: If you plan to make any substantial changes to your Project Proposal, please let us know. 14:24:47 One thing we can consider is putting the project proposal with git checkin in the future 14:25:05 #info What is the best way to provide feedback right now? 14:25:18 #info phrobb I will create a wiki page. 14:25:56 #action Phil / Casey to create a wiki page for the Project Proposal Feedback and Review. 14:27:08 #action Phil / Casey will annotate when each project proposal will be reviewed. 14:27:33 #topic Security Updates 14:30:14 #info SteveT: A good way to establish the Vulnerability team is to make them a subcommittee. This is how other projects do it. 14:30:48 #info SteveT: Asked if the TSC if they thought that was the right way to go forward. 14:31:32 #info edwarnicke: We should make clear that the Vulnerability Chair will ultimately responsible. 14:31:40 CaseyODL: Cool :) 14:32:37 #info Lingli_Deng: Are we recruiting for people to contribute to the two security teams? 14:33:20 #info SteveT : Yes we have a fairly stable group for the General security work. We do need more people for the Vulnerability Group. 14:34:58 #link https://wiki.onap.org/display/DW/Draft+ONAP+Vulnerability+Management SteveT shared the Draft proposal for the ONAP Vulnerability Management. 14:36:34 #info SteveT has a draft for a Security subcommittee. 14:37:14 #action SteveT will send out a formal draft of the Security Subcommittee proposal to the TSC for review. 14:39:09 #info SteveT I think it's important that the Security and Vulnerability management is handled within the Projects when they are established. The Security and Vulnerability will not be able to handle all of the code management. 14:39:25 #topic Architecture Subcommittee 14:39:48 #link https://wiki.onap.org/display/DW/Proposal+for+Architecture+Subcommittee <-- wiki page proposing an Architecture Subcommittee 14:40:34 thanks phil 14:41:18 #info The project proposal has been posted for almost 2 weeks. 14:42:06 #info Lingli_Deng This may have some overlap with the Use Case Subcommittee. 14:44:33 phrobb: We can always redefine Subcommittees when we form new ones or identify overlap and gaps. When a Use Case Subcommittee is formed, they will likely work closely together with the Architecture. 14:44:43 #info phrobb: We can always redefine Subcommittees when we form new ones or identify overlap and gaps. When a Use Case Subcommittee is formed, they will likely work closely together with the Architecture. 14:45:10 #info Yue asked why they don't merge. 14:45:57 #info phrobb The TSC can choose to do that later. But the scope for the Use Case Subcommittee has not yet been decided. 14:46:53 aren't detailed use case flows also part of the integration project scope? It does list in the scope "Service design for end-to-end release use cases" . 14:47:01 #info Alex stated that one committee will be very technical and one will not. I believe they will still be separate Committees. 14:49:37 #info Alex: It may be a good idea to build a RACI chart. 14:52:33 #info There were some questions regarding the scope of the Architecture Subcommittee. Mr. Robb proposed that he add language to the vote that requires a review of the Architecture Subcommittee when and if a Use Case Subcommittee is formed. 14:52:36 #vote +1 14:52:37 #startvote Shall the TSC form an Architecture Subcommittee as defined on the above wiki page. This subcommittee purpose will be reviewed and updated if/when a Use Case Subcommittee is formed? -1, 0, +1 14:52:37 Begin voting on: Shall the TSC form an Architecture Subcommittee as defined on the above wiki page. This subcommittee purpose will be reviewed and updated if/when a Use Case Subcommittee is formed? Valid vote options are -1, 0, +1. 14:52:37 Vote using '#vote OPTION'. Only your last vote counts. 14:52:39 #vote +1 14:52:43 #vote +1 14:52:44 #vote +1 14:52:53 #vote +1 14:52:53 #vote +1 14:52:54 #vote +1 14:52:56 #vote +1 14:52:59 #vote +1 14:53:15 #vote +1 14:53:15 #vote +1 14:53:15 #vote +1 14:53:17 #vote +1 14:53:29 #vote +1 14:53:43 #endvote 14:53:43 Voted on "Shall the TSC form an Architecture Subcommittee as defined on the above wiki page. This subcommittee purpose will be reviewed and updated if/when a Use Case Subcommittee is formed?" Results are 14:53:43 +1 (13): RobertoK, Xiaojun, alla, Zhaoxing_Meng, rajesh-intel, JasonHunt, xinhuili, edwarnicke, SteveT, cdonley, Dsauvageau, RannyHaiby, Lingli_Deng 14:54:09 #agree The TSC will form an Architecture Subcommittee. 14:54:38 #topic Modeling Group brief update 14:54:56 Reminder Phil, to take offline but we should start nominations for architecture sub-committee chair. 14:55:39 Is there a link to these slides? 14:58:10 #info Rittwik Shared a presentation on how the modeling team will provide guidance to each project. 15:00:29 #topic Beijing F2F 15:01:28 #info Yuan Shared the information regarding the location and draft agenda for the F2F Meeting in Beijing. 15:01:38 The ONAP Wiki has a calendar that could be used to define the F2F details 15:02:56 Question on the agenda. I assume we should have some slot for general TSC meeting as well. Very happy with focus on the projects though. Well done. 15:05:48 #topic cookies 15:05:58 #endmeeting