==================================================== #acumos-meeting: Acumos Technical Steering Committee ==================================================== Meeting started by aimeeu at 13:03:07 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/acumos-meeting/2018/acumos-meeting.2018-05-14-13.03.log.html . Meeting summary --------------- * Roll Call (aimeeu, 13:03:26) * Meeting Minute Approval (aimeeu, 13:04:53) * (Nat-TechM, 13:05:46) * TSC members present: Jack Murray, Ofer Hermoni, Pantelis Monogioudis, Sachin Janorkar (aimeeu, 13:06:36) * Open Action Items (aimeeu, 13:07:20) * Community Document - roles definitions (aimeeu, 13:07:33) * Jack calls for approval of roles definitions (aimeeu, 13:07:50) * roles approved by voice vote (aimeeu, 13:08:08) * "Get-Started Guide" for Marketplace and Idea Collection Forum (aimeeu, 13:08:34) * Annie reminds the call that this topic is an outgrowth of a mailing list discussion (aimeeu, 13:09:09) * Sachin will lead the effort (aimeeu, 13:10:47) * Additional Jira Admin priviledges (aimeeu, 13:11:21) * Chris Lott requested this; he needs a backup in case he's gone (aimeeu, 13:12:51) * Jack asks if anyone object to having an additional admin; no one objects; TSC approves having an additional Jira admin (aimeeu, 13:14:24) * second Jira admin will be Bayyavarapu Sai Chand Shabarish from Tech Mahindra (aimeeu, 13:15:12) * Release Planning (aimeeu, 13:15:22) * Jamil Chawki's slide deck is presented (aimeeu, 13:15:45) * 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 (aimeeu, 13:16:54) * Jamil notes that for M0, we needs PTLs (aimeeu, 13:17:24) * Jack calls for discussion on how to put this in place (aimeeu, 13:18:32) * Jamil suggests approving the list of projects for Release A (aimeeu, 13:18:45) * Jack replies that the list of projects for Release A has already been approved but we need PTLs for each project (aimeeu, 13:19:19) * Discussion about Training and License Management projects; for Release A, these projects will form but not be part of the release (aimeeu, 13:20:42) * 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 (aimeeu, 13:21:50) * Jamil: suggests announcing to the mailing list the approved projects and call for PTLs (aimeeu, 13:22:35) * Jamil: suggests interim PTLs and then in a couple of months have PTL elections (aimeeu, 13:23:06) * Jack asks the LF the best way to manage this effort (aimeeu, 13:23:19) * Annie Fisher (LF) suggest putting a page on the wiki for projects and people wanting to volunteer to be PTL for a specific project (aimeeu, 13:24:50) * discussion around repositories per project; keep the PTL table simple (aimeeu, 13:29:40) * 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 (aimeeu, 13:31:27) * Jack: how do we handle release planning? where does it belong? Under Architecture? under Community? (aimeeu, 13:34:11) * Aimee: wouldn't Release planning be a joint effort between Product and Architecture committees? (aimeeu, 13:35:05) * Ofer +1 (aimeeu, 13:35:13) * discussion on PTL's input to timeline (aimeeu, 13:35:41) * Jack: Where does the Release Manager role "live" ?? (aimeeu, 13:36:09) * Manoop explains the Release Manager role in ONAP (aimeeu, 13:36:50) * Aimee: release manager in OPNFV is also an independent role, responsible to the TSC (aimeeu, 13:38:17) * Mike Dolan also weighs in with how a Release Manager role is handled in other communities (aimeeu, 13:39:17) * Jack asks Jamil Chawki if he'd like to take on the Release Manager role for at least the next few weeks (aimeeu, 13:39:47) * Jamil agrees (aimeeu, 13:39:57) * New Agenda Items (aimeeu, 13:40:42) * Jack summarizes recent discussions; strong consensus that Product/Community subcommittee is responsible for requirements (aimeeu, 13:41:47) * 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 (aimeeu, 13:42:44) * Pantelis: who will kickoff the Community subcommittee? (aimeeu, 13:43:15) * further discussion of Community subcommittee role and when requirements are finalized (aimeeu, 13:44:44) * consensus is that Requirements are an M1 deliverable (aimeeu, 13:45:28) * Jack: wants everyone to be aware that the Community subcommittee is also responsible for the Acumos instance marketplace.acumos.org - features and functionality (aimeeu, 13:46:54) * agenda item on upgrading code on the Community instance will be moved to next week (aimeeu, 13:47:48) * Jack explains the current weekly release build (aimeeu, 13:48:05) * Jack: the community needs to move forward with the architecture and security discussions (aimeeu, 13:49:42) * Acumos LF Environment refresh (aimeeu, 13:52:02) * several weeks behind in bug fixes and other patches (aimeeu, 13:52:16) * Jack asks if there are any concerns with scheduling an update (aimeeu, 13:52:50) * Non Author Code Review (aimeeu, 13:54:50) * this means that the author cannot merge his/her own code (aimeeu, 13:55:11) * Chris suggested we follow best practices from ONAP (aimeeu, 13:58:21) * Aimee offers counterpoint (aimeeu, 14:00:28) * Nat suggests we ensure that we have at least 2 committers for each repo (aimeeu, 14:00:52) * discussions ensues - lets offer guidance (aimeeu, 14:02:00) * Jack suggests revisiting this topic further down the road; we can remove "misbehaving" committers or educate them (aimeeu, 14:03:00) Meeting ended at 14:03:18 UTC. People present (lines said) --------------------------- * aimeeu (66) * collabot` (5) * Nat-TechM (4) * bryan_att (0) Generated by `MeetBot`_ 0.1.4