#acumos-meeting: Acumos TSC

Meeting started by bryan_att at 13:05:26 UTC (full logs).

Meeting summary

    1. roll call: 5 TSC members present on the call, so we have quorum (bryan_att, 13:06:24)
    2. present Jack (AT&T), Ofer (Amdocs), Nat (TechM), Pantelis (Nokia), Jamil (Orange), Huawei (bryan_att, 13:07:53)
    3. Bryan Sullivan (bryan_att, 13:08:00)

  2. Minutes approval (bryan_att, 13:08:13)
    1. The last two meetings' minutes were approved (bryan_att, 13:08:54)

  3. Agenda (bryan_att, 13:09:06)
    1. Jamil: for the Paris meetup, there is a possibility to have a TSC meeting (bryan_att, 13:09:42)

  4. Open Items (bryan_att, 13:10:09)
    1. Jack: On capture of metrics from the LF portal, Annie is working on getting stats collected (bryan_att, 13:12:43)
    2. 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 (bryan_att, 13:13:19)
    3. Jack: we all need to help promote the platform to grow the model catalog (bryan_att, 13:13:47)
    4. 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 (bryan_att, 13:14:57)

  5. Nokia input to the project (bryan_att, 13:15:38)
    1. 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. (bryan_att, 13:16:54)
    2. Nat: that was the result of the discussion (bryan_att, 13:17:07)
    3. Jack: re cloud native (one of the items), we need to be sure we have a common understanding (bryan_att, 13:17:58)
    4. Pantelis: we mean that all components are extensible and replaceable, not just that the components run as containers (bryan_att, 13:18:54)
    5. Pantelis: e.g. some just want a CLI interface to a CMS, others want a more moderns frontend to manage the CMS and catalog (bryan_att, 13:19:51)
    6. 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 (bryan_att, 13:22:27)
    7. Anwar: this is something that the Arch team call can take on (bryan_att, 13:23:00)
    8. Pantelis: will bring this to the Arch call (bryan_att, 13:23:16)

  6. Acumos LF Instance Update (bryan_att, 13:24:58)
    1. 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. (bryan_att, 13:26:27)
    2. 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. (bryan_att, 13:28:34)
    3. Jack: we have had one update since the March launch (bryan_att, 13:29:03)
    4. Nat: the current release has been published (to clarify which build on https://wiki.acumos.org/display/REL/Weekly+Builds is being referred to) (bryan_att, 13:30:56)
    5. 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. (bryan_att, 13:32:29)
    6. Jack: suggest that this be brought to the community committee also (bryan_att, 13:32:53)

  7. Report of Subcommittees (bryan_att, 13:33:14)
    1. 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. (bryan_att, 13:34:38)
    2. 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 (bryan_att, 13:35:49)
    3. Ofre: the goal is to bring this to the TSC for approval by M1 (bryan_att, 13:36:02)
    4. Nat: we also identified improvements on existing features (bryan_att, 13:36:24)
    5. Ofer: so the strawman plan is about both new features and imprvements\ (bryan_att, 13:36:46)
    6. Pantelis: for training, the requirements will be captured in Jira; just checking whether this is the understanding (bryan_att, 13:37:40)
    7. Bryan: we are not creating project repos and Jira components until the new features are approved (bryan_att, 13:41:26)
    8. Jack: the Arch committee and PTLs will break down the requirements and enter Epics/Stories into Jira once the project is approvef (bryan_att, 13:43:20)
    9. Pantelis: we need to document the process for getting a feature into Jira (bryan_att, 13:44:04)
    10. Patelis: and assigning the feature to a component (bryan_att, 13:45:44)
    11. Topic Architecture Planning and Release Planning (bryan_att, 13:46:19)
    12. Anwar: we have started reviewing the reqs in the pipeline; covered about 1/3 of them in the last session. (bryan_att, 13:46:58)
    13. Anwar: we need an integrated sprint plan as well, working with release manager and PTLs (bryan_att, 13:47:52)
    14. 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 (bryan_att, 13:48:24)
    15. Anwar: is there date for TSC approval? (bryan_att, 13:48:41)
    16. Ofer: this should be M1 (bryan_att, 13:48:52)
    17. Jack: M2 is about the same time (functionality freeze); what we have to define is what are the real deliverables for these milestones? (bryan_att, 13:49:34)
    18. 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 (bryan_att, 13:52:13)

  8. Release Manager (bryan_att, 13:53:28)
    1. 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\ (bryan_att, 13:54:20)
    2. 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 (bryan_att, 13:55:08)
    3. 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 (bryan_att, 13:56:40)

  9. Acumos Day in Paris (bryan_att, 13:56:49)
    1. 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. (bryan_att, 13:58:07)
    2. 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. (bryan_att, 13:59:15)
    3. Nat: TechM is also unable to support the meeting (bryan_att, 13:59:56)
    4. Pantelis: also likely not to be able to atttend (bryan_att, 14:00:22)
    5. Jamil: we are still considering whether we need a full-day meetup or a half-day with TSC the other half (bryan_att, 14:01:18)
    6. Jack: we will try to attend remotely (bryan_att, 14:01:32)
    7. Jack: does not seem enough attendance to hold a TSC meeting there (bryan_att, 14:02:14)
    8. Jack: remind all of the upcoming M1 deadline and encourage work to deliver it (bryan_att, 14:02:44)


Meeting ended at 14:02:49 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bryan_att (64)
  2. collabot_ (3)


Generated by MeetBot 0.1.4.