13:05:26 <bryan_att> #startmeeting Acumos TSC
13:05:26 <collabot_> Meeting started Mon Jun 11 13:05:26 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:05:26 <collabot_> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:05:26 <collabot_> The meeting name has been set to 'acumos_tsc'
13:06:24 <bryan_att> #info roll call: 5 TSC members present on the call, so we have quorum
13:07:53 <bryan_att> #info present Jack (AT&T), Ofer (Amdocs), Nat (TechM), Pantelis (Nokia), Jamil (Orange), Huawei
13:08:00 <bryan_att> #info Bryan Sullivan
13:08:13 <bryan_att> #topic Minutes approval
13:08:54 <bryan_att> #info The last two meetings' minutes were approved
13:09:06 <bryan_att> #topic Agenda
13:09:42 <bryan_att> #info Jamil: for the Paris meetup, there is a possibility to have a TSC meeting
13:10:09 <bryan_att> #topic Open Items
13:12:43 <bryan_att> #info Jack: On capture of metrics from the LF portal, Annie is working on getting stats collected
13:13:19 <bryan_att> #info Jack: the goal is to measure engagement of users and developers; our catalog is still small but we want to monitor it as it grows
13:13:47 <bryan_att> #info Jack: we all need to help promote the platform to grow the model catalog
13:14:57 <bryan_att> #info Jack: AT&T and TechM are sponsoring a dev challenge right now and will share most of the models  into the catalog when it is done
13:15:38 <bryan_att> #topic Nokia input to the project
13:16:54 <bryan_att> #info Pantelis: I sent a deck that was discussed on the roadmap and scope recommended for Acumos; some of the main ideas in that will need to be deferred post Release 1 as there is not enough time.
13:17:07 <bryan_att> #info Nat: that was the result of the discussion
13:17:58 <bryan_att> #info Jack: re cloud native (one of the items), we need to be sure we have a common understanding
13:18:54 <bryan_att> #info Pantelis: we mean that all components are extensible and replaceable, not just that the components run as containers
13:19:51 <bryan_att> #info Pantelis: e.g. some just want a CLI interface to a CMS, others want a more moderns frontend to manage the CMS and catalog
13:22:27 <bryan_att> #info Bryan: suggets that Pantelis explain this vision in more detail as there would be architecture implications of a true plug and play framework for component deployment
13:23:00 <bryan_att> #info Anwar: this is something that the Arch team call can take on
13:23:16 <bryan_att> #info Pantelis: will bring this to the Arch call
13:24:42 <bryan_att> info Jack: deployment into kubernetest (platform and models) are in the current proposed feature set for this release but it may take time to fully realize the potential of this, and consider Pantelis' input as well
13:24:58 <bryan_att> #topic Acumos LF Instance Update
13:26:27 <bryan_att> #info Nat: the last update was for the May 10  release. We are looking for approval fo the latest release but want to know what the ongoing plan will be (e.g. every 2 weeks). we want to stabilize the update plan, with ability to deploy fixes fast as needed.
13:28:34 <bryan_att> #info Jack: as background, under the LF we run the wiki etc for the project, and also the Acumos platform operated by LF. For the Acumos platform, we are continually improving the platform with bug fixes etc; the question is how often we update the Acumos LF instance.
13:29:03 <bryan_att> #info Jack: we have had one update since the March launch
13:30:56 <bryan_att> #info Nat: the current release has been published  (to clarify which build on https://wiki.acumos.org/display/REL/Weekly+Builds is being referred to)
13:32:29 <bryan_att> #info Jack: suggest that unless there are critical defects, that Nat come back next week with the specific version for approval, and also to finalize an ongoing plan for update; we are working on improvements at critical/high priority and want a plan for rolling them out.
13:32:53 <bryan_att> #info Jack: suggest that this be brought to the community committee also
13:33:14 <bryan_att> #topic Report of Subcommittees
13:34:38 <bryan_att> #info Ofer: last week we had two meetings, covering the new feature process and strawman feature set; then met later to put the items into Jira and sent out a note to the stakeholders to expand the descriptions there with more details for the items they are promoting.
13:35:49 <bryan_att> #info Ofer:  we will discuss them tomorrow in the community committee, and follow by discussion in the arch committee to estimate arch impact, followed by PTLs/team discussion of which is deliverable; finally we will bring this to the TSC for approval
13:36:02 <bryan_att> #info Ofre: the goal is to bring this to the TSC for approval by M1
13:36:24 <bryan_att> #info Nat: we also identified improvements on existing features
13:36:46 <bryan_att> #info Ofer: so the strawman plan is about both new features and imprvements\
13:37:40 <bryan_att> #info Pantelis: for training, the requirements will be captured in Jira; just checking whether this is the understanding
13:41:26 <bryan_att> #info Bryan: we are not creating project repos and Jira components until the new features are approved
13:43:20 <bryan_att> #info Jack: the Arch committee and PTLs will break down the requirements and enter Epics/Stories into Jira once the project is approvef
13:44:04 <bryan_att> #info Pantelis: we need to document the process for getting a feature into Jira
13:45:44 <bryan_att> #info Patelis: and assigning the feature to a component
13:46:19 <bryan_att> #info Topic Architecture Planning and Release Planning
13:46:58 <bryan_att> #info Anwar: we have started reviewing the reqs in the pipeline; covered about 1/3 of them in the last session.
13:47:52 <bryan_att> #info Anwar: we need an integrated sprint plan as well, working with release manager and PTLs
13:48:24 <bryan_att> #info Anwar: we need to decide when the TSC will vote on the new features; what we have right now is more than can be delivered in one release
13:48:41 <bryan_att> #info Anwar: is there  date for TSC approval?
13:48:52 <bryan_att> #info Ofer: this should be M1
13:49:34 <bryan_att> #info Jack: M2 is about the same time (functionality freeze); what we have to define is what are the real deliverables for these milestones?
13:50:31 <bryan_att> topic: Security Committee
13:52:13 <bryan_att> #info Jack: we don't have a permanent chair for this committee yet, and need someone to drive this in the temporary space; I propose that Bryan Sullivan help me with this in the short term, and organize a discussion around security, licensing/validation
13:53:28 <bryan_att> #topic Release Manager
13:54:20 <bryan_att> #info Details for M1/M2/M3 need to be described in more detail; this is a big role reporting to the TSC; someone needs to take on this bigger role and help drive the release planning\
13:55:08 <bryan_att> #info Jack: looking for someone to fill that role especially for the first release; anyone that can volunteer for this role is welcome to stand up here
13:56:40 <bryan_att> #info Jack: re projects without PTLs, how do we manage them? Some projects do not have PTLs yet,. By default the code committers will form the likely candidates, and in the meantime I am looking for committers to consider volunteering in the meantime
13:56:49 <bryan_att> #topic Acumos Day in Paris
13:58:07 <bryan_att> #info Jack: the question was whether there is support for a TSC meeting at the meetup in July 13th (Paris). I will not be able to attend.
13:59:15 <bryan_att> #info Jamil: we agreed earlier to have a 1-day meetup there; so the TSC can decide if it wants to have a meeting at the same time.
13:59:56 <bryan_att> #info Nat: TechM is also unable to support the meeting
14:00:22 <bryan_att> #info Pantelis: also likely not to be able to atttend
14:01:18 <bryan_att> #info Jamil: we are still considering whether we need a full-day meetup or a half-day with TSC the other half
14:01:32 <bryan_att> #info Jack: we will try to attend remotely
14:02:14 <bryan_att> #info Jack: does not seem enough attendance to hold a TSC meeting there
14:02:44 <bryan_att> #info Jack: remind all of the upcoming M1 deadline and encourage work to deliver it
14:02:49 <bryan_att> #endmeeting