==================================
#acumos-meeting: Committee Kickoff
==================================


Meeting started by bryan_att at 15:01:18 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/acumos-meeting/2018/acumos-meeting.2018-04-17-15.01.log.html
.



Meeting summary
---------------

* Roll Call  (bryan_att, 15:02:28)
  * Bryan Sullivan  (bryan_att, 15:02:35)
  * Aimee Ukasick  (aimeeu, 15:02:58)
  * Pantelis Monogioudis  (pantelis_, 15:03:45)
  * 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)
    (bryan_att, 15:06:58)

* Agenda  (bryan_att, 15:08:02)
  * Main focus of today is to overview the committees as agreed by the
    TSC  (bryan_att, 15:10:27)
  * Bryan presents the draft info on the Arch committee  (bryan_att,
    15:18:19)
  * Pantelis: we need to define the major requirements as use cases as
    well  (bryan_att, 15:19:10)
  * ... e.g. cloud-native, e.g. components are extensible/replaceable
    (microservice-oriented)  (bryan_att, 15:20:20)
  * Ofer: there are 2 or more levels; product ownership (biz reqs),
    product development (translation into code)  (bryan_att, 15:23:19)
  * ... 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  (bryan_att, 15:24:11)
  * Anwar +1  (bryan_att, 15:24:37)
  * Anwar: we need to identify where is the product role  (bryan_att,
    15:25:32)
  * ... 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)  (bryan_att, 15:31:07)
  * Sachin: if we focus the commubity committee thus, who will define
    the release plan?  (bryan_att, 15:31:53)
  * Anwar: this is currently part of the community committee
    (bryan_att, 15:32:20)
  * Ofer: +1, this was my first thought  (bryan_att, 15:32:36)
  * Bryan: so the community committee defines what and when (release
    roadmap)  (bryan_att, 15:33:31)
  * Anwar: we should call it the "product committee"  (bryan_att,
    15:33:50)
  * Pantelis: the arch committee would address the implementation
    (bryan_att, 15:34:29)
  * Ofer: so we agree to separate product and requirements  (bryan_att,
    15:34:46)
  * Pantelis: +1  (bryan_att, 15:34:54)
  * Bryan: will update the wiki to match  (bryan_att, 15:36:56)
  * Nat TechM  (Nat, 15:38:30)
  * general agreement that we will need at least weekly calls for the
    committees to start  (bryan_att, 15:39:38)
  * Pantelis: we will contribute to the product committee  (bryan_att,
    15:41:16)
  *
    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  (bryan_att, 15:45:45)
  * 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.  (bryan_att, 15:50:30)
  * Ofer: is there a roadmap plan for the platform's features
    (bryan_att, 15:51:07)
  * 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  (bryan_att, 15:55:23)



Meeting ended at 16:00:39 UTC.



People present (lines said)
---------------------------

* bryan_att (31)
* collabot` (3)
* aimeeu (1)
* Nat (1)
* pantelis_ (1)
* ofer (1)
* sachin-TechM (1)



Generated by `MeetBot`_ 0.1.4