#acumos-meeting: Acumos TSC Community Committee

Meeting summary

1. 1. Bryan Sullivan (bryan_att, 17:02:48)
   2. aimeeu (aimeeu, 17:02:55)
   3. Topic: email from Ofer on the process (bryan_att, 17:06:27)
   4. https://lists.acumos.org/g/acumosaicommunity/topic/athena_release_community/21898531?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,21898531 (bryan_att, 17:06:30)
   5. Manoop: have provided input in a spreadsheet, and am updating it (bryan_att, 17:08:54)
   6. Ofer: suggest we identify gaps in the input and discuss them to come to consensus (bryan_att, 17:09:33)
   7. 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 (bryan_att, 17:11:11)
   8. Ofer: suggest to compare the high priority items (bryan_att, 17:12:21)
   9. Manoop: re ACUMOS-1095, we have to set a goal otherwise the coverage will go down, not up (bryan_att, 17:15:22)
   10. Nat: agree, the question is what is the mandated #, and if a minimum bar e.g. 30% will work (bryan_att, 17:16:13)
   11. Manoop: devs don't ofter go above the minimum, and many then don't meet it either (bryan_att, 17:16:42)
   12. Nat: suggest to set a goal for 40% (bryan_att, 17:17:15)
   13. The team agreed that 40% is a reasonable goal for this release (bryan_att, 17:25:08)
   14. Ofer: next gap is ACUMOS-1091 (bryan_att, 17:27:02)
   15. Manoop explained the rationale, and the team agrees to keep it at high (bryan_att, 17:27:22)
   16. Ofer: re ACUMOS-1079, do we have resources to implement this (bryan_att, 17:27:53)
   17. Manoop: the rationale is to be able to truthfully say we support multiple cloud envs for deployment (bryan_att, 17:28:38)
   18. Nat: Jack suggested we look to the cloud providers to help us with these deployers (bryan_att, 17:29:31)
   19. 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 (bryan_att, 17:30:19)
   20. 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 (bryan_att, 17:32:54)
   21. Ofer: re ACUMOS-1071 (bryan_att, 17:34:09)
   22. Kazi: AT&T and TechM are developing this, it's in progress and marked for the next release (bryan_att, 17:34:40)
   23. Ofer: re ACUMOS-1042, need more info (bryan_att, 17:35:42)
   24. Manoop: this one, and ACUMOS-1040 (Provenance) relate to changes e.g. in authorship management under development by Chuxin and team (bryan_att, 17:36:57)
   25. Ofer: re ACUMOS-1085 (bryan_att, 17:41:49)
   26. Manoop: this one supports the ability of modelers to test their models (bryan_att, 17:42:27)
   27. Ofer re ACUMOS-1082 (bryan_att, 17:43:54)
   28. 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 (bryan_att, 17:45:43)
   29. (discussion of various items that are already work in progress) (bryan_att, 17:52:46)
   30. 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 (bryan_att, 17:56:37)
   
   
2. Sprint Planning (bryan_att, 17:56:52)
   1. Farheen: (shares sprint planning slide) (bryan_att, 17:58:47)
   2. Bryan: suggest the diagram be posted at https://wiki.acumos.org/display/REL/Sprint+Planning (bryan_att, 18:03:13)
   3. discussion on whether to have functionality demos in Community meeting - general opinion is Yes (aimeeu, 18:08:12)

Action items

1. (none)

People present (lines said)

1. bryan_att (34)
2. collabot_ (3)
3. aimeeu (2)
4. NAT_ (2)