17:02:38 <bryan_att> #startmeeting Acumos TSC Community Committee
17:02:38 <collabot_> Meeting started Tue Jun 19 17:02:38 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:38 <collabot_> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:02:38 <collabot_> The meeting name has been set to 'acumos_tsc_community_committee'
17:02:48 <bryan_att> #info Bryan Sullivan
17:02:51 <NAT_> # info
17:02:55 <aimeeu> #info aimeeu
17:03:03 <NAT_> # info NAT - TechM
17:06:27 <bryan_att> #info Topic: email from Ofer on the process
17:06:30 <bryan_att> #link https://lists.acumos.org/g/acumosaicommunity/topic/athena_release_community/21898531?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,21898531
17:08:54 <bryan_att> #info Manoop: have provided input in a spreadsheet, and am updating it
17:09:33 <bryan_att> #info Ofer: suggest we identify gaps in the input and discuss them to come to consensus
17:11:11 <bryan_att> #info Manoop: propose that the 3 lists we have so far (Manoop, Ofer, Phillipe) be compared and aligned, with rationales added as needed for the priority
17:12:21 <bryan_att> #info Ofer: suggest to compare the high priority items
17:15:22 <bryan_att> #info Manoop: re ACUMOS-1095, we have to set a goal otherwise the coverage will go down, not up
17:16:13 <bryan_att> #info Nat: agree, the question is what is the mandated #, and if a minimum bar e.g. 30% will work
17:16:42 <bryan_att> #info Manoop: devs don't ofter go above the minimum, and many then don't meet it either
17:17:15 <bryan_att> #info Nat: suggest to set a goal for 40%
17:25:08 <bryan_att> #info The team agreed that 40% is a reasonable goal for this release
17:27:02 <bryan_att> #info Ofer: next gap is ACUMOS-1091
17:27:22 <bryan_att> #info Manoop explained the rationale, and the team agrees to keep it at high
17:27:53 <bryan_att> #info Ofer: re ACUMOS-1079, do we have resources to implement this
17:28:38 <bryan_att> #info Manoop: the rationale is to be able to truthfully say we support multiple cloud envs for deployment
17:29:31 <bryan_att> #info Nat: Jack suggested we look to the cloud providers to help us with these deployers
17:30:19 <bryan_att> #info Nat: in the meantime we will focus on k8s and openstack as other cloud envs, and if the cloud providers etc come to the table we can support this, but for now it is low due to lack of resources
17:32:54 <bryan_att> #info Bryan: what the cloud providers really probably want is for Acumos to support their internal ML PaaS features; as long as we look at this as simply a place to launch Acumos models, it really may not add a lot of value for them
17:34:09 <bryan_att> #info Ofer: re ACUMOS-1071
17:34:40 <bryan_att> #info Kazi: AT&T and TechM are developing this, it's in progress and marked for the next release
17:35:42 <bryan_att> #info Ofer: re ACUMOS-1042, need more info
17:36:57 <bryan_att> #info Manoop: this one, and  ACUMOS-1040 (Provenance) relate to changes e.g. in authorship management under development by Chuxin and team
17:41:49 <bryan_att> #info Ofer: re ACUMOS-1085
17:42:27 <bryan_att> #info Manoop: this one supports the ability of modelers to test their models
17:43:54 <bryan_att> #info Ofer re ACUMOS-1082
17:45:43 <bryan_att> #info Bryan: this one is not needed per the latest discussion with Kazi - we have an approach under development that does not require any key exchange
17:52:46 <bryan_att> #info (discussion of various items that are already work in progress)
17:56:37 <bryan_att> #info Bryan: re ACUMOS-1010, we need to change the model deployment process to use triggered steps vs delay-based steps, since delay-based approach will ofteb fail in envs that do not meet the performance requirements in which the workable delay values were determined
17:56:52 <bryan_att> #topic Sprint Planning
17:58:47 <bryan_att> #info Farheen: (shares sprint planning slide)
18:03:13 <bryan_att> #info Bryan: suggest the diagram  be posted at https://wiki.acumos.org/display/REL/Sprint+Planning
18:08:12 <aimeeu> #info discussion on whether to have functionality demos in Community meeting - general opinion is Yes
22:35:46 <bryan_att> #endmeeting