#acumos-meeting: Acumos TSC Meeting

Meeting started by bryan_att at 13:02:39 UTC (full logs).

Meeting summary

  1. Agenda (bryan_att, 13:02:54)
    1. TSC roll call: Ofer, Jack, Zhengyuxuan, Pantelis, Nat (bryan_att, 13:05:02)
    2. Last week's minutes were approved (bryan_att, 13:05:38)
    3. Bryan Sullivan (bryan_att, 13:05:47)
    4. Nat: add topics on update of the LF instance, and adding committer for the Azure client repo (bryan_att, 13:06:57)
    5. Jack: adding to the agenda the creation of a policy for attendance (or named alternative) (bryan_att, 13:07:48)

  2. Status of open items (bryan_att, 13:08:41)
  3. Strategic Positioning (Pantelis) (bryan_att, 13:12:31)
    1. Pantelis: Isee the recently developed support for kubernetes as a good thing, with opportunities to disaggregate the platform; this item can be taken off the standing agenda as there is now progress. (bryan_att, 13:14:06)
    2. Jack: re the potential relationship with TIP, who is involved in TIP that can track this? (bryan_att, 13:14:40)
    3. Pantelis and Ofer will investigate and report to the TSC (bryan_att, 13:15:39)

  4. LF Marketplace refresh (bryan_att, 13:15:59)
    1. Nat: looking for standing 2 or 4 week upgrade cycle; have May 10 installed, and ready to deploy June 11 (bryan_att, 13:16:59)
    2. Jack: this should be in scope for automated deployment under CI/CD; the options (e.g. from master or a branch) need to be worked out (bryan_att, 13:18:26)
    3. Nat: for now, propose once every 4 weeks with tests on the staging server, and important maint updates as needed (bryan_att, 13:19:19)
    4. Vanessa: is the staging env a mirror of production (typically is) ? (bryan_att, 13:20:07)
    5. Nat: it isn't identical but pretty close (bryan_att, 13:20:57)
    6. Jack: Vanessa and LF team can deploy emergency fixes as needed (bryan_att, 13:23:54)
    7. TSC agrees to the 4-week update cycle (bryan_att, 13:24:22)
    8. Sachin: need a dedicated main window for updating the production instance (bryan_att, 13:25:07)
    9. Vanessa: 8PM Eastern time is recommended (bryan_att, 13:26:36)
    10. the TSC agreed to the schedule for the main window (bryan_att, 13:27:19)

  5. Subcommittee reports (bryan_att, 13:27:35)
    1. Ofer the Community commiittee is making progress, all items are in Jira (bryan_att, 13:28:35)
    2. Jack: is the community aware of how to find the reqs and submit their input? we will be closing the req window next week. (bryan_att, 13:30:24)
    3. Jack: following that the Arch committee will consider it; but we also need to identify which resources will drive the development (bryan_att, 13:31:34)
    4. Jack: M2 will probably be extended to allow the Arch committee to discuss the items (bryan_att, 13:32:21)
    5. Pantelis: have some questions about the use of Jira, and how projects define scrums (bryan_att, 13:33:38)
    6. Vanessa: other projects typically do have their own sub-project (project, repo) structure in Jira so they can plan scrums etc (bryan_att, 13:34:58)
    7. Jack: recommend that we enable the PTLs and projects to use those features (bryan_att, 13:36:33)
    8. Bryan: this is typical in other projects, but there will be some effort to migrate the existing issues into projects (bryan_att, 13:38:32)
    9. Jack: how do cross-project epics fit this plan? (bryan_att, 13:39:56)
    10. Vanessa: we cold keep them at the "Acumos" project as the umbrella (bryan_att, 13:40:22)
    11. Jack: the question is what do we need to change now? (bryan_att, 13:45:46)
    12. Vanessa: recommend we make changes now (bryan_att, 13:46:12)
    13. Anwar: we discussed in the Arch call that to support agile, we need cross-project sprints defined in the development timeline; the Arch team recommended that we define the common sprint schedule now (bryan_att, 13:47:29)
    14. Anwar: as a product there needs to be coordinated sprints between the component projects (bryan_att, 13:48:18)
    15. Vanessa: we can also create scrum boards filtered for components (bryan_att, 13:48:58)
    16. Jack: so we could use the current structure (bryan_att, 13:49:31)
    17. Anwar: will work with Pantelis to drive the scrum board implementation using the current Jira structure (bryan_att, 13:51:00)

  6. Arch committee (bryan_att, 13:51:07)
    1. Anwar: current reqs have been reviewed, input on priority is being collected, next is to determine which can be delivered based upon resources (bryan_att, 13:51:58)
    2. Anwar: we also need to ensure the test team has a platform to test during the dev cycle, so factor that into the planning (bryan_att, 13:53:08)
    3. Anwar: we also need the input/support of the release manager (when that role has been filled) (bryan_att, 13:53:42)
    4. Jack: we really need someone to step up to support the release manager role (bryan_att, 13:54:25)

  7. New Items (bryan_att, 13:54:37)
    1. Jack: we need a release manager volunteer to be very available and proactive (bryan_att, 13:55:02)
    2. Jack: we have several projects without PTLs; looking for volunteers (bryan_att, 13:56:27)

  8. Jira Admin Rights (bryan_att, 13:56:52)
    1. Scott: TSC needs to determine who has Jira Admin rights; we are talking about rights to customize Jira (bryan_att, 13:58:03)
    2. Scott: also approval of new committers e.g. Phillipe as PTL of Onboarding wants to take on the role of committer (bryan_att, 13:58:54)
    3. TSC agreed for Phillipe as committer (bryan_att, 13:59:57)
    4. Nat: also need Santosh to be added to the other deploy repos as committer, for the deployment project (bryan_att, 14:01:06)
    5. Vanessa: re Jira admin, this is at the project level only not overall, and that needs to be approved by the TSC (bryan_att, 14:01:50)
    6. Jack: get the names on the agenda for next week, or via email (bryan_att, 14:02:57)
    7. Vanessa: we could also use the IRC bot to record the votes on IRC (bryan_att, 14:03:53)


Meeting ended at 14:04:21 UTC (full logs).

Action items

  1. (none)


People present (lines said)

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


Generated by MeetBot 0.1.4.