15:01:18 <bryan_att> #startmeeting Committee Kickoff
15:01:18 <collabot`> Meeting started Tue Apr 17 15:01:18 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:18 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:01:18 <collabot`> The meeting name has been set to 'committee_kickoff'
15:02:28 <bryan_att> #topic Roll Call
15:02:35 <bryan_att> #info Bryan Sullivan
15:02:58 <aimeeu> #info Aimee Ukasick
15:03:45 <pantelis_> #info Pantelis Monogioudis
15:05:42 <sachin-TechM> Brian, Sachin from TechM joined
15:05:47 <ofer> I'm here
15:06:58 <bryan_att> #info Attending also Chris Lott (AT&T), Guancong Liu (ZTE), Jitendra Sapariya (Telstra), Ofer Hermoni (Amdocs), Pantelis Monogioudos (Nokia), Sachin Janokar (TechM) , Ken Kristiansen (AT&T)
15:08:02 <bryan_att> #topic Agenda
15:10:27 <bryan_att> #info Main focus of today is to overview the committees as agreed by the TSC
15:18:19 <bryan_att> #info Bryan presents the draft info on the Arch committee
15:19:10 <bryan_att> #info Pantelis: we need to define the major requirements as use cases as well
15:20:20 <bryan_att> #info ... e.g. cloud-native, e.g. components are extensible/replaceable (microservice-oriented)
15:21:59 <bryan_att> ... goals to support how industry will/want to use Acumos, e.g. "model mgmt across 1000s of targets"
15:23:19 <bryan_att> #info Ofer: there are 2 or more levels; product ownership (biz reqs), product development (translation into code)
15:24:11 <bryan_att> #info ... unsure if one can address both; initial intent for the community was to provide the implementation guidance, but overall we need to separate product mgmt from engineering
15:24:37 <bryan_att> #info Anwar +1
15:25:32 <bryan_att> #info Anwar: we need to identify where is the product role
15:31:07 <bryan_att> #info ... we could focus the "community" committee as the "product" committee, owner of the product requirements, which addresses the platform needs and growth of the community/ecoystem "product" (model catalog)
15:31:53 <bryan_att> #info Sachin: if we focus the commubity committee thus, who will define the release plan?
15:32:20 <bryan_att> #info Anwar: this is currently part of the community committee
15:32:36 <bryan_att> #info Ofer: +1, this was my first thought
15:33:31 <bryan_att> #info Bryan: so the community committee defines what and when (release roadmap)
15:33:50 <bryan_att> #info Anwar: we should call it the "product committee"
15:34:29 <bryan_att> #info Pantelis: the arch committee would address the implementation
15:34:46 <bryan_att> #info Ofer: so we agree to separate product and requirements
15:34:54 <bryan_att> #info Pantelis: +1
15:36:56 <bryan_att> #info Bryan: will update the wiki to match
15:38:30 <Nat> #info Nat TechM
15:39:38 <bryan_att> #info general agreement that we will need at least weekly calls for the committees to start
15:41:16 <bryan_att> #info Pantelis: we will contribute to the product committee
15:45:45 <bryan_att> #info https://wiki.acumos.org/display/AC/Acumos+Architecture+Mapping+to+Repos+Jira+etc shown as an update of the repos/committers and proposed changes to the project structure
15:50:30 <bryan_att> #info Bryan: recommend that there be a focus on firming up the projects, supporters, in a dedicated meeting for that. Will propose this to the TSC.
15:51:07 <bryan_att> #info Ofer: is there a roadmap plan for the platform's features
15:55:23 <bryan_att> #info Ofer: suggest that we create a high level  description of what we want the platform etc to be and when, and break down to use cases/requirements on the wiki and as docs
16:00:39 <bryan_att> #endmeeting