17:17:59 <bryan_att> #startmeeting Acumos TSC Community (Product) Committee
17:17:59 <collabot_> Meeting started Tue May 29 17:17:59 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:17:59 <collabot_> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:17:59 <collabot_> The meeting name has been set to 'acumos_tsc_community__product__committee'
17:18:23 <bryan_att> #chairs bryan_att, aimeeu
17:18:28 <bryan_att> #chair bryan_att, aimeeu
17:18:28 <collabot_> Current chairs: aimeeu bryan_att
17:18:58 <bryan_att> #topic Process for requirements
17:19:34 <bryan_att> Jamil: recommend requirements (features etc) come from the community (product) committee
17:19:56 <bryan_att> #info Jamil: recommend requirements (features etc) come from the community (product) committee
17:20:11 <bryan_att> #info Nat: agree
17:21:45 <bryan_att> #info strawman of requirements are on the etherpad at https://etherpad.acumos.org/p/release-plan-athena
17:22:31 <bryan_att> #info Jack: recommend that M1 be focus of the community committee; as of M2 the arch committee can do the detailed planning
17:23:59 <bryan_att> #info Bryan: see the existing role/process input on the wiki https://wiki.acumos.org/display/ACCOM and https://wiki.acumos.org/display/AR
17:25:10 <bryan_att> #info Ofer: skeptical at this point for the role of the community committee for R1 - for R2 it's more feasible to do M1 planning
17:26:23 <bryan_att> #info Jack: we should still have discussion about what can be done until Sept
17:26:56 <bryan_att> #info Jack: we should be able to document what will be possible in the release as of Oct
17:27:20 <bryan_att> #info Jamil: Nokia (Pantelis) presented an orchestrator use case
17:27:56 <bryan_att> #info Ofer: that was discussed in this meeting earlier
17:28:50 <bryan_att> #info Kazi: how to define orchestrator
17:30:13 <bryan_att> Bryan: as Pantelist described it, the orchstrator manages the  lifecycle for the model from deployment through its entire  production life\
17:30:23 <bryan_att> #info Bryan: as Pantelist described it, the orchstrator manages the  lifecycle for the model from deployment through its entire  production life\
17:30:54 <bryan_att> s/Pantelist/Pantelis/
17:31:26 <bryan_att> #info Jack: we will need to address the lifecycle of models vs predictors
17:31:45 <bryan_att> #info Jamil: we can talk about use cases for ML/AI here, not just for the platform functionality
17:32:39 <bryan_att> #info Jamil: recommend we discuss 2-3 use cases for the platform in this committee
17:33:16 <bryan_att> #info Bryan: that is in scope of this committee AFAIU
17:34:09 <bryan_att> #info Jack: we need to determine for the release to be successful, what does it need to do/support to meet the success criteria, e.g. # of models in the marketplace, # of active organizations, etc
17:35:20 <bryan_att> #info Bryan: where are the success criteria defined ?
17:35:44 <bryan_att> #info Jack: they need to be related to the proposed features as addressing some larger goal
17:36:25 <bryan_att> #info Bryan: so where are those larger goals  defined?
17:37:10 <bryan_att> #info Ofer: we started to consider such things with Pantelis' input paper about orchestration
17:39:20 <bryan_att> #info Jack: what are people wanting from the current platform is what we need to determine
17:40:29 <bryan_att> #info Jack: this is essentially a product requirements spec, e.g. what Acumos is (a place to onboard and share models), and a way to increase use/reuse of models by the community
17:41:15 <bryan_att> #info Jack: what is the #1 thing we need to do to grow the community? make it easy to onboard, find models, motivate people to contribute here vs somewhere else
17:41:56 <bryan_att> #info Jack: we need to kick off the licensing work though it will not be complete for R1; we can release a spec for licensing at least
17:42:11 <bryan_att> #info Jack: not all deliverables need to be finished software
17:42:51 <bryan_att> #info Jack: also we need to improve lifecycle mgmt
17:43:19 <bryan_att> #info Jack: also how to safeguard model sharing (protect from malware, unclear provenance, ...)
17:43:48 <bryan_att> #info Jack: we currently have a validation function in the seed code
17:46:07 <bryan_att> #info Bryan: there is current content re validation goals on the wiki, e.g. see  https://wiki.acumos.org/display/SEC/Security+Scanning on the Security committee page https://wiki.acumos.org/display/SEC/Security+Home
17:46:25 <bryan_att> #info Jamil: also we need to consider model portability, to other standards etc
17:47:02 <bryan_att> #info Jack: if these ideas can be broken down, the arch team can consider how they can be implemented
17:47:29 <bryan_att> #info Jack: we have till June 18 to complete a requirements plan
17:48:07 <bryan_att> #info Jack: maybe grouping re M1/2/3 is not ideal; code freeze as of July 16 gives 1.5 months test time
17:48:37 <bryan_att> #info Jack: how much testing time is needed post-freeze? we do continual test and intend to increase code coverage
17:49:13 <bryan_att> #info Anwar: as long as IST and E2E testing have adequate time, it's ok. We will need a few weeks for E2E testing.
17:49:46 <bryan_att> #info Jack: code freeze is 7/16 and 9/3 for test complete, so 1.5 months
17:50:08 <bryan_att> #info Jack: what is in RC0 that takes a month?
17:50:35 <bryan_att> #info Jamil: to complete system test for the use cases we agreed to support
17:50:58 <bryan_att> #info Jack: so from 7/16 to 10/8 is all testing time
17:52:48 <bryan_att> #info Jamil: 7/16 is M3 (API freeze), 9/4 is M4 (code freeze). RC0 is 10/8 (E2E functional test complete), RC1 could be for E2E use case testing
17:53:41 <bryan_att> #info Jack: we should document the release plan on the wiki
17:54:21 <bryan_att> #info Bryan: I will add the latest info from Jamil into a release page for Athena under the release space
17:55:10 <bryan_att> #info Ofer: from what we discussed today, we can progress on these calls with enough participation; but skeptical on what we can get completed for the 1st release
17:55:26 <bryan_att> #info Jamil: we can target a spec for license management
17:56:46 <bryan_att> #info Bryan: we need to document the features at the least (example will be put on the wiki)
17:57:28 <bryan_att> #info Ofer: may have issues with availability to move this forward
17:57:47 <bryan_att> #info Jack: we need a team to work with Ofer to move this forward
18:00:00 <bryan_att> #info Bryan: we need the projects and PTLs to define/document what they intend for new features, so the community committee can review those plans and comment
18:00:46 <bryan_att> #info Jack: feel free to reach out to us to help build that architecture team to work on the features and related product goals
18:01:50 <bryan_att> #info Jack: recommend Ofer kick off a document about the process of documenting requirements
18:01:53 <bryan_att> #endmeeting