13:02:39 #startmeeting Acumos TSC Meeting 13:02:39 Meeting started Mon Jun 18 13:02:39 2018 UTC. The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:02:39 The meeting name has been set to 'acumos_tsc_meeting' 13:02:54 #topic Agenda 13:05:02 #info TSC roll call: Ofer, Jack, Zhengyuxuan, Pantelis, Nat 13:05:38 #info Last week's minutes were approved 13:05:47 #info Bryan Sullivan 13:06:57 #info Nat: add topics on update of the LF instance, and adding committer for the Azure client repo 13:07:48 #info Jack: adding to the agenda the creation of a policy for attendance (or named alternative) 13:08:41 #topic Status of open items 13:12:31 #topic Strategic Positioning (Pantelis) 13:14:06 #info 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. 13:14:40 #info Jack: re the potential relationship with TIP, who is involved in TIP that can track this? 13:15:39 #info Pantelis and Ofer will investigate and report to the TSC 13:15:59 #topic LF Marketplace refresh 13:16:59 #info Nat: looking for standing 2 or 4 week upgrade cycle; have May 10 installed, and ready to deploy June 11 13:18:26 #info 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 13:19:19 #info Nat: for now, propose once every 4 weeks with tests on the staging server, and important maint updates as needed 13:20:07 #info Vanessa: is the staging env a mirror of production (typically is) ? 13:20:57 #info Nat: it isn't identical but pretty close 13:23:54 #info Jack: Vanessa and LF team can deploy emergency fixes as needed 13:24:22 #info TSC agrees to the 4-week update cycle 13:25:07 #info Sachin: need a dedicated main window for updating the production instance 13:26:15 #inf Jack: Vanessa and team will work with you to schedule the maint window 13:26:36 #info Vanessa: 8PM Eastern time is recommended 13:27:19 #info the TSC agreed to the schedule for the main window 13:27:35 #topic Subcommittee reports 13:28:35 #info Ofer the Community commiittee is making progress, all items are in Jira 13:30:24 #info Jack: is the community aware of how to find the reqs and submit their input? we will be closing the req window next week. 13:31:34 #info Jack: following that the Arch committee will consider it; but we also need to identify which resources will drive the development 13:32:21 #info Jack: M2 will probably be extended to allow the Arch committee to discuss the items 13:33:38 #info Pantelis: have some questions about the use of Jira, and how projects define scrums 13:34:58 #info Vanessa: other projects typically do have their own sub-project (project, repo) structure in Jira so they can plan scrums etc 13:36:33 #info Jack: recommend that we enable the PTLs and projects to use those features 13:38:32 #info Bryan: this is typical in other projects, but there will be some effort to migrate the existing issues into projects 13:39:56 #info Jack: how do cross-project epics fit this plan? 13:40:22 #info Vanessa: we cold keep them at the "Acumos" project as the umbrella 13:45:46 #info Jack: the question is what do we need to change now? 13:46:12 #info Vanessa: recommend we make changes now 13:47:29 #info 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 13:48:18 #info Anwar: as a product there needs to be coordinated sprints between the component projects 13:48:58 #info Vanessa: we can also create scrum boards filtered for components 13:49:31 #info Jack: so we could use the current structure 13:51:00 #info Anwar: will work with Pantelis to drive the scrum board implementation using the current Jira structure 13:51:07 #topic Arch committee 13:51:58 #info Anwar: current reqs have been reviewed, input on priority is being collected, next is to determine which can be delivered based upon resources 13:53:08 #info Anwar: we also need to ensure the test team has a platform to test during the dev cycle, so factor that into the planning 13:53:42 #info Anwar: we also need the input/support of the release manager (when that role has been filled) 13:54:25 #info Jack: we really need someone to step up to support the release manager role 13:54:37 #topic New Items 13:55:02 #info Jack: we need a release manager volunteer to be very available and proactive 13:56:27 #info Jack: we have several projects without PTLs; looking for volunteers 13:56:52 #topic Jira Admin Rights 13:58:03 #info Scott: TSC needs to determine who has Jira Admin rights; we are talking about rights to customize Jira 13:58:54 #info Scott: also approval of new committers e.g. Phillipe as PTL of Onboarding wants to take on the role of committer 13:59:57 #info TSC agreed for Phillipe as committer 14:01:06 #info Nat: also need Santosh to be added to the other deploy repos as committer, for the deployment project 14:01:50 #info Vanessa: re Jira admin, this is at the project level only not overall, and that needs to be approved by the TSC 14:02:57 #info Jack: get the names on the agenda for next week, or via email 14:03:53 #info Vanessa: we could also use the IRC bot to record the votes on IRC 14:04:21 #endmeeting