13:03:07 #startmeeting Acumos Technical Steering Committee 13:03:07 Meeting started Mon May 14 13:03:07 2018 UTC. The chair is aimeeu. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:03:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:03:07 The meeting name has been set to 'acumos_technical_steering_committee' 13:03:19 #chair bryan_att aimeeu 13:03:19 Current chairs: aimeeu bryan_att 13:03:26 #topic Roll Call 13:04:53 #topic Meeting Minute Approval 13:05:46 #info 13:06:36 #info TSC members present: Jack Murray, Ofer Hermoni, Pantelis Monogioudis, Sachin Janorkar 13:06:53 # info NAT - TechM 13:07:20 #topic Open Action Items 13:07:33 #topic Community Document - roles definitions 13:07:50 #info Jack calls for approval of roles definitions 13:08:08 #info roles approved by voice vote 13:08:34 #topic "Get-Started Guide" for Marketplace and Idea Collection Forum 13:09:09 #info Annie reminds the call that this topic is an outgrowth of a mailing list discussion 13:10:47 #info Sachin will lead the effort 13:11:21 #topic Additional Jira Admin priviledges 13:12:51 #info Chris Lott requested this; he needs a backup in case he's gone 13:14:24 #info Jack asks if anyone object to having an additional admin; no one objects; TSC approves having an additional Jira admin 13:14:37 Jira Admin 13:14:40 Recommending - Bayyavarapu Sai Chand Shabarish from Acumos LF Application Instance support team member as 2nd LF Jira Admin • Linux Foundation ID : SaiShabarish • Full Name : Bayyavarapu Sai Chand Shabarish • TechM mail ID : SB00109369@TechMahindra.com 13:15:12 #info second Jira admin will be Bayyavarapu Sai Chand Shabarish from Tech Mahindra 13:15:22 #topic Release Planning 13:15:45 #info Jamil Chawki's slide deck is presented 13:16:54 #info Jack: we need to adjust the dates on Jamil's slide desk; need to work through intermediate dates; need a plan for Milestone Zero if the Milestone Zero start date is to be May 21 13:17:24 #info Jamil notes that for M0, we needs PTLs 13:18:32 #info Jack calls for discussion on how to put this in place 13:18:45 #info Jamil suggests approving the list of projects for Release A 13:19:19 #info Jack replies that the list of projects for Release A has already been approved but we need PTLs for each project 13:20:42 #info Discussion about Training and License Management projects; for Release A, these projects will form but not be part of the release 13:21:50 #info Jack notes that there hasn't been much feedback around appointing PTLs; it's difficult to pick PTLs from a pool broader than AT&T and Tech Mahindra when the project is just starting out 13:22:35 #info Jamil: suggests announcing to the mailing list the approved projects and call for PTLs 13:23:06 #info Jamil: suggests interim PTLs and then in a couple of months have PTL elections 13:23:19 #info Jack asks the LF the best way to manage this effort 13:24:50 #info Annie Fisher (LF) suggest putting a page on the wiki for projects and people wanting to volunteer to be PTL for a specific project 13:29:40 #info discussion around repositories per project; keep the PTL table simple 13:31:27 #info Manoop Talasila suggests people who are interested send an email; Jack suggests keeping this interim PTL process simple - people should put their names on the wiki 13:34:11 #info Jack: how do we handle release planning? where does it belong? Under Architecture? under Community? 13:35:05 #info Aimee: wouldn't Release planning be a joint effort between Product and Architecture committees? 13:35:13 #info Ofer +1 13:35:41 #info discussion on PTL's input to timeline 13:36:09 #info Jack: Where does the Release Manager role "live" ?? 13:36:50 #info Manoop explains the Release Manager role in ONAP 13:38:17 #info Aimee: release manager in OPNFV is also an independent role, responsible to the TSC 13:39:17 #info Mike Dolan also weighs in with how a Release Manager role is handled in other communities 13:39:47 #info Jack asks Jamil Chawki if he'd like to take on the Release Manager role for at least the next few weeks 13:39:57 #info Jamil agrees 13:40:42 #topic New Agenda Items 13:41:47 #info Jack summarizes recent discussions; strong consensus that Product/Community subcommittee is responsible for requirements 13:42:44 #info Ofer: yes, this subcommittee will be responsible for gathering requirements from Community, stakeholders; subcommittee will then present requirements to TSC for approval in a release 13:43:15 #info Pantelis: who will kickoff the Community subcommittee? 13:44:44 #info further discussion of Community subcommittee role and when requirements are finalized 13:45:28 #info consensus is that Requirements are an M1 deliverable 13:46:54 #info Jack: wants everyone to be aware that the Community subcommittee is also responsible for the Acumos instance marketplace.acumos.org - features and functionality 13:47:48 #info agenda item on upgrading code on the Community instance will be moved to next week 13:48:05 #info Jack explains the current weekly release build 13:49:42 #info Jack: the community needs to move forward with the architecture and security discussions 13:52:02 #topic Acumos LF Environment refresh 13:52:16 #info several weeks behind in bug fixes and other patches 13:52:50 #info Jack asks if there are any concerns with scheduling an update 13:53:33 #info Nat Subramanian: no concerns, but we need scheduled code pushed to the LF instance 13:54:19 #undo 13:54:19 Removing item from minutes: 13:54:29 Nat Subramanian: no concerns, but we need scheduled code pushes to the LF instance 13:54:50 #topic Non Author Code Review 13:55:11 #info this means that the author cannot merge his/her own code 13:58:21 #info Chris suggested we follow best practices from ONAP 14:00:28 #info Aimee offers counterpoint 14:00:52 #info Nat suggests we ensure that we have at least 2 committers for each repo 14:02:00 #info discussions ensues - lets offer guidance 14:03:00 #info Jack suggests revisiting this topic further down the road; we can remove "misbehaving" committers or educate them 14:03:10 #end meeting 14:03:18 #endmeeting