17:03:03 <bryan_att> #startmeeting Acumos TSC Community (Product) Committee
17:03:03 <collabot_> Meeting started Tue Jun 12 17:03:03 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:03:03 <collabot_> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:03:03 <collabot_> The meeting name has been set to 'acumos_tsc_community__product__committee'
17:03:39 <NAT_> # info NAT - TechM
17:04:51 <bryan_att> #info Bryan Sullivan
17:06:02 <bryan_att> #topic Release Feature Input
17:07:06 <bryan_att> #info Ofer: last week we discussed the input on the etherpad https://etherpad.acumos.org/p/release-plan-athena
17:08:19 <bryan_att> #info Ofer: also we sent an email https://lists.acumos.org/g/acumosaicommunity/topic/athena_release_community/21898531?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,21898531 which describes the result and next steps
17:09:38 <bryan_att> #info Ofer: in this meeting we will start reviewing the features that are included with some details, with further steps per the email
17:10:12 <bryan_att> #info The community committee will review all new feature descriptions, and provide an advisory vote on for each, on what work (e.g., analysis, design, implementation) seems essential for this release, to proceed to assessment of architectural impact etc. (as below)
17:10:40 <bryan_att> #info The architecture committee will assess (rough estimate) the impact to the architecture and related components for each feature determined essential by the community
17:11:02 <bryan_att> #info Respective PTLs and team SMEs will assess (rough estimate) the resources needed to implement the new features recommended by the community, and improvements as determined to be essential by the PTLs and teams for the components/etc. in scope of the project
17:11:17 <bryan_att> #info A subset of the recommended feature/improvement work items will be reviewed and approved by the TSC for the release
17:15:26 <bryan_att> #info Bryan: suggest to go thru the new features from the etherpad first; then the pre-existing items from Jira, and determine whether they are defined enough (or still valid) for further assessment by the Arch committee
17:16:27 <bryan_att> #info Rueben: we also need a broader end-user focused description of the goals so we end up with a cohesive product
17:20:55 <bryan_att> #info ACUMOS-1099; no objection to level of details, the ask is understood but questionable as to what can be delivered in this release
17:22:39 <bryan_att> #info ACUMOS-1098: Use Cases for Testing  - we need more info from Jamil
17:24:11 <bryan_att> #info ACUMOS-1096 Automating functional test cases for every component  - we need more info on what work will relate to this goal
17:27:48 <bryan_att> #info ACUMOS-1095 Sonar 50% code coverage requirement on every repo - similar - we need more input but no objection
17:29:08 <bryan_att> #info ACUMOS-1094 Security of the platform - relates to Jira items Bryan will link, with wiki refs
17:30:50 <bryan_att> #info ACUMOS-1093 Baseline performance criteria by identifying and measuring current performance of the components - needs to be aligned with ACUMOS-1092 Performance benchmarking on critical Operations  - and further explained
17:31:37 <bryan_att> #info ACUMOS-1092 Performance benchmarking on critical Operations  - see above
17:33:51 <bryan_att> #info ACUMOS-1091 Single logging system across components and generating usage reports - need more details but this is existing work in progress
17:34:29 <bryan_att> #info CUMOS-1089 RBAC: Role and Privilege based Operations - need more details
17:35:25 <bryan_att> #info ACUMOS-1088 Lifecycle management of model in production - Bryan will link Pantelis's input and earlier notes
17:37:08 <bryan_att> #info ACUMOS-1087 Deploy model to kubernetes environment - details exist, and will be discussed in the Deployment project team meeting - also relates to ACUMOS-1086 Deploy to local environment
17:38:21 <bryan_att> #info ACUMOS-1086 Deploy to local environment and ACUMOS-1081 Deploy model to Google cloud platform ( GCP)  - similar to above
17:38:45 <bryan_att> #info ACUMOS-1079 Deploy Model to AWS similar to above
17:43:12 <bryan_att> #info ACUMOS-1077 Licensing - need input from Rueben on licensing goals and areas of functionality in scope
17:43:56 <bryan_att> #info Bryan: this is also one of those items that is probably roadmapped but we expect some work in this release to define the goals
17:44:52 <bryan_att> #info Rueben: there is a big community aspect for that - we need to focus on the intent of the community
17:45:18 <bryan_att> #info Reuben: and we need vendor input on this as well
17:46:03 <bryan_att> ACUMOS-1076 	Private federation - details provided, no objection
17:47:30 <bryan_att> #info ACUMOS-1075 Model interchange using other standards - Bryan will link the input from Jamil
17:49:58 <bryan_att> #info ACUMOS-1072 Train model - Pantelis will have the 1st meeting on this project (Training) next week - also earlier analysis from AT&T will be described at a high level (scope of work)
17:51:15 <bryan_att> #info ACUMOS-1071 Support Directed Acyclic Graph - based Composite Solution Creation - aka support Split and Join Semantics  - Kazi added a note "We have designed this feature and the User Stories are in JIRA. AT&T and Tech M teams are working on the development of this issue."
17:55:14 <bryan_att> #info ACUMOS-1044 Acumos project scanning for license/vulnerability - also relates  ACUMOS-1041 Model scanning for license, vulnerability - details are provided on the wiki
17:58:01 <bryan_att> #info Anwar: how do we want to proceed on approval - it will take some time to go thru these and balance the priorities and resources - we can expect that a small subset of items will be deliverable for Nov
17:59:11 <bryan_att> #infoi Anwar: so if the community priorities and the arch priorities can be assessed, and then the TSC can vote on those recommendations
18:01:14 <bryan_att> #info Bryan: I can provide a form for collecting input from the committees
18:02:04 <bryan_att> #info Anwar: Arch session is thurs - we will use the time for discussion
18:03:14 <bryan_att> #info Ofer agree that a form to provide input is useful - but we need more info where possible
18:03:35 <bryan_att> #info Bryan to send out a form for input and use by the communities
18:06:53 <bryan_att> #endmeeting