13:53:09 #startmeeting TSC Aug 10 2017 13:53:09 Meeting started Thu Aug 10 13:53:09 2017 UTC. The chair is kennypaul. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:53:09 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:53:09 The meeting name has been set to 'tsc_aug_10_2017' 13:53:31 #chair phrobb, CaseyODL, SteveT 13:53:31 Current chairs: CaseyODL SteveT kennypaul phrobb 13:53:50 #topic rollcall 13:57:28 #info proxy Oliver Spatscheck AT&T 13:57:53 #info Xiaojun Xie, China Telecom 13:58:52 #info Sonu Sreenivasan, Intel, Covering for Rajesh Gadiyar 13:58:58 #info Alla Goldner, Amdocs 13:59:25 Ning So Reliance Jio 14:00:16 #info Susana Sabater, Vodafone 14:00:28 #info Ranny Haiby, Nokia 14:00:42 #info Chris Donley, Huawei 14:01:47 #info Stephen Terrill, Ericsson 14:02:01 #info proxy Giles Heron, Cisco 14:02:17 #info Arthur Berezin, Cloudify 14:05:43 #info Zhaoxing Meng, ZTE 14:06:11 #info Xinhui Li, VMware 14:06:22 #info Chengli proxy of Lingli, China Mobile 14:07:19 #info Zygmunt Lozinski - IBM on behalf of Jason Hunt 14:07:26 #info Eric Debeau proxy of Jamil Chawki, Orange 14:08:08 #topic "Upstream First" 14:12:55 #info Josef Reisinger is a Proxy for Jason Hunt of IBM 14:29:46 It seems the whole Release Planning process should identify features that require large amount of code changes. TSC approval would occur via all the milestones. 14:33:42 TNadeau_: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 14:33:57 sorry looks like the meeting is ongoing 14:34:21 #topic dev code enforcement 14:34:41 #info I have seen that the gerrit review does not always automatically add the required committers to a git review request. 14:39:59 #info http://wiki.onap.org/download/attachments/3245207/ONAP-DevelopmentBestPractices.pdf?api=v2 14:40:11 Thats a link to the presentation being discussed 14:41:14 #startvote Shall the TSC approve the Upstream development guidelines identified on slides 4 & 5 "ONAP Upstream Discussion Version 2.0"? +1, 0, -1 14:41:14 Begin voting on: Shall the TSC approve the Upstream development guidelines identified on slides 4 & 5 "ONAP Upstream Discussion Version 2.0"? Valid vote options are +1, 0, -1. 14:41:14 Vote using '#vote OPTION'. Only your last vote counts. 14:41:17 #vote +1 14:41:25 #vote +1 14:41:29 #vote +1 14:41:30 #vote +1 14:41:31 #vote +1 14:41:32 #vote +1 14:41:34 #vote +1 14:41:34 #vote +1 14:41:35 #vote +1 14:41:42 +1 14:41:44 #vote +1 14:41:47 #vote +1 14:41:48 #vote +1 14:41:50 #vote +1 14:41:54 #vote +1 14:42:07 #vote +1 14:42:19 #vote +1 14:42:25 #endvote 14:42:25 Voted on "Shall the TSC approve the Upstream development guidelines identified on slides 4 & 5 "ONAP Upstream Discussion Version 2.0"?" Results are 14:42:25 +1 (16): cdonley, RannyHaiby, alla, Susana, gilesheron, xinhuili, SteveT, ArthurBerezin, Chengli, kennypaul, DhananjayPavgi, Sonu, spatsch17, Xiaojun, Zhaoxing, EricDebeau 14:42:29 #info my for represents Josef Reusinger 14:47:20 #agreed TSC approve the Upstream development guidelines identified on slides 4 & 5 "ONAP Upstream Discussion Version 2.0 14:47:42 #topic blockers 14:48:07 #info move discussions to PTL mtg 14:48:25 #topic Sept. F2F meeting 14:50:21 #link https://lists.onap.org/pipermail/onap-tsc/2017-August/001540.html 14:51:57 #link https://wiki.onap.org/display/DW/September+26-28+Topics 14:53:52 #info we should find some time to have some testing sessions in the September Developer Day to solve some issues between various projects 14:56:55 #link https://www.regonline.com/ONAPDeveloperParis <-- Registration link 14:57:35 #topic Seed code migration to *.onap.org 15:00:18 #topic 5.4.1.4 15:02:56 #info Language to be voted upon in email: 15:03:18 #info Voting for a Chair or Vice-Chair is not limited to ONAP member companies. However only 1 Subcommittee member from each company, or group of related companies may vote in the election. 15:03:18 For the purpose of this document, “Related Company” shall mean any entity (Company-A) which controls or is controlled by another entity (Company-B) or which, together, is under the common control of a third party (Company-C), in each case where such control results from ownership, either directly or indirectly, of more than fifty percent of the voting securities or membership interests of the entity in 15:03:18 question; and “Related Companies” are entities that are each a Related Company as described above. 15:04:03 #endmeeting