15:56:57 <bryan_att> #startmeeting Acumos TSC
15:56:57 <collabot`> Meeting started Tue Mar 27 15:56:57 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:56:57 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:56:57 <collabot`> The meeting name has been set to 'acumos_tsc'
15:57:03 <valderrv> #info valderrv
15:58:23 <bryan_att> #info Bryan Sullivan
15:59:49 <bryan_att> #chair bryan_att
15:59:49 <collabot`> Current chairs: bryan_att
16:01:00 <bryan_att> #topic Scott Nicolas intros the agenda
16:01:53 <bryan_att> #info Agenda: welcome, TSC organization, release roadmaps, communication channels, infra
16:02:09 <bryan_att> #info  there are 8 members of the TSC for this first meeting
16:03:33 <bryan_att> #info (intros of those in the room)
16:09:30 <bryan_att> #info 8 TSC members Ofer Hermoni Amdocs, Jack Murray AT&T, Wang Yi Baidu, Ying Long Xia Huawei, Pantelis Monogioudis Nokia, Sachin Janokar TechM, Xialong Zhu Tencent
16:10:02 <bryan_att> s/Ying Long/ Yinglong/
16:11:44 <valderrv> Zoom Meeting Link - https://zoom.us/j/137231283
16:15:25 <bryan_att> s/infra/meeting cadence/
16:16:24 <bryan_att> #info members of the TSC dialing in: Yinglong  Xia, Huawei
16:16:35 <bryan_att> #topic TSC Organization
16:17:06 <bryan_att> #info Scott turns floor over to AT&T and TechM to discuss seed code contribution
16:19:04 <bryan_att> #info Jack Murray : AT&T and TechM have made a seed code contribution, now in repos and the wiki, along with tools for building the project, and have deployed an initial root node for the community at market.acumos.org. AT&T and TechM have shared an initial set of models there to illustrate model publication and federation. The contributions are Apache-2.0 licensed.
16:20:35 <bryan_att> #info ... the Acumos day yesterday was intended to intro the attendees to the community and goals for Acumos. Many members are expected to leverage such solutions internally across a broad set of applications.
16:22:54 <bryan_att> #info Sachin Janokar: our vision for Acumos was a collaborative way to solve the need for ML-based solutions.
16:23:59 <bryan_att> #info Jack: a couple of things to share in kicking off: (1) we need an approach of at least two releases per year (a stable release branch from what is a continually developed master).
16:25:01 <bryan_att> #info ... the first release is proposed to be called "1.0". What we name these is something to be discussed, e.g. greek gods (but not cities).
16:28:27 <bryan_att> #info ... (2) the overall TSC organization, shown in a word document shared by Jack with a proposal of sub-committees and projects
16:29:40 <bryan_att> info ... the subcommittees: architecture (use cases), security (functionality, policies, compliance), acumos community (releases, model management, catalog growth, policies)
16:30:25 <bryan_att> #info ... projects: Integration and Test (Test Use Cases, Release Management, CI/CD process)
16:31:53 <bryan_att> #info Q on the catalog growth re the role of the Marketing committee (or the LFDL board): answer as proposed is a collaboration of the TSC and BOD committees
16:32:43 <bryan_att> #info Raj: where will owners of Model contributions be tracked?
16:33:40 <bryan_att> #info Jack: under the community; the architecture committee could track use cases and associate to models contributed by members
16:34:39 <bryan_att> #info Raj: I see one track as enhancing the platform; another being modeler communities that want to just onboard their models
16:35:15 <bryan_att> #info: Jack I see the proposed Acumos.org driving both of those goals
16:36:44 <bryan_att> #info projects (continuing):  Acumos Portal and UX (end-to-end use csaes, roles, search, ratings)
16:37:05 <bryan_att> info ... Model Onboarding (new modeling methods, optimizations)
16:37:39 <bryan_att> #info Catalog, Data Model, Data Management (federation, validation and compliance)
16:38:32 <bryan_att> #info ... Training (Data Management, Data Handling, Acceleration, Cloud)
16:38:48 <bryan_att> #info Design Studio (Microservices)
16:39:04 <bryan_att> #info Deployment (local, cloud)
16:39:15 <bryan_att> #info Common Services (new)
16:39:58 <bryan_att> #info ... Model Onboarding (new modeling methods, optimizations)
16:40:53 <bryan_att> #info ... this is related to but a different spin to the proposal on the wiki that Manoop and Bryan worked on: https://wiki.acumos.org/display/AC/Acumos+Architecture+Mapping+to+Repos+Jira+etc
16:41:58 <bryan_att> #info Ofer: maybe data management better called "data set management"
16:42:44 <bryan_att> #info Jack: Data Management along with Catalog etc was meant to capture the ability to contribute data sets to the catalog, e.g. for training
16:43:46 <bryan_att> #info ... the main goals of this proposal is to result in a small number of standalone projects
16:44:19 <bryan_att> #info ... training should be a primary area for Acumos, though very much a work in progress
16:45:57 <bryan_att> #info (projects continued): Documentation
16:46:32 <bryan_att> #info Common Services (microservice generation, download, import.export)
16:46:45 <bryan_att> #info License Management
16:47:05 <bryan_att> #info OAM&P (installation, logging, metrics)
16:47:30 <bryan_att> #info Paul: is license management about software, the models, or both
16:48:00 <bryan_att> #info Jack: the models
16:48:23 <bryan_att> #info Nat: the platform is Apache 2.0
16:48:55 <ChrisPriceAB> hi folks, maybe a little late but whats the link for the conference call?
16:48:59 <bryan_att> #info Jack: the platform is Apache 2.0; we have to consider how to address other software we need to integrate with
16:49:11 <bryan_att> https://zoom.us/j/137231283
16:49:22 <bryan_att> good luck hearing
16:50:28 <bryan_att> #info (? ZTE) where are the datasets from and how associated with companies
16:50:41 <ChrisPriceAB> Thanks Bryan.
16:51:32 <bryan_att> #info Jack: Datasets fall under those associated with a model, and those contributed to broader work. Some datasets may be referenced, others contributed ala software. LF has indicated a different project re establishing guidellines for dataset sharing
16:52:23 <bryan_att> #info Scott: are considering two licenses focused on data; one a Apache 2.0 and another a copyleft based license. Do we anticipate a lot of data contributions>
16:52:56 <bryan_att> #info Jack: we expect data associated with models, but not all of that will be public data
16:53:34 <bryan_att> #info Pantellis: we expect there to be data available of sufficient size to effectively test the platform
16:54:17 <bryan_att> #info Jack: we expect the databroker to enable connecting models to external data, referenced for training purposes or as an example
16:54:42 <bryan_att> #info Raj: the availability of training datasets will be important
16:55:21 <bryan_att> #info Jack: we want to promote all model contributors to provide training datasets, not necessarily large but adequate
16:55:46 <Guest83150> Nat - TechM
16:55:47 <bryan_att> #info ... that said we need to manage the amount of data being replicated across portals
16:56:20 <bryan_att> #info (Q on the phone): if I have a model to contribute how do I get that into the marketplace?
16:57:22 <bryan_att> #info Jack: the federation capability of the platform is intended to support that, as long as systems implement the federation API e.g. as an Acumos portal instance or some other Acumos compliant system
16:58:12 <bryan_att> #info (Q on the phone): If I have an internal marketplace I may want to use an Acumos instance as a gateway to publish models into the ecosystem
16:58:33 <bryan_att> #info Sachin: what about runtime envs to allow devs to download and use models locally?
16:59:17 <bryan_att> #info Jack: we will support public clouds and internal openstack/k8s etc cloud envs as a launch target
17:00:03 <bryan_att> #info ... other enhancements might be one click setup of toolkit-specific test/training envs on a workstation for example
17:00:39 <bryan_att> #info ... training envs will likely provide some local options, e.g. a GPU cluster dedicated to training
17:01:26 <bryan_att> #info Nagib (Intel): how can Q's get answered about the platform
17:02:21 <bryan_att> #info Jack: stack overflow, Jira, IRC etc. These are the common channels used in open source.
17:02:55 <bryan_att> #info ... mail lists etc
17:04:02 <bryan_att> #info new mail lists are setup and accessible thru the Acumos website
17:06:30 <bryan_att> #info Bryan: See  https://wiki.acumos.org/display/INFRA/Project+Infrastructure for a full list of the communication and collaboration tools
17:07:08 <bryan_att> #info Jim (IBM): is this the list for Acumos or LFDL? what is the process for adding projects to LFDL?
17:07:40 <bryan_att> #info Jack: talk to Scott about new projects under LFDL, and shared committees e.g. BOD, TAC, Marketing, etc
17:08:03 <bryan_att> #info Jack: critical success factor will be federation of existing marketplaces into Acumos
17:08:38 <bryan_att> #info Jack: at the booth we will show a demo of federating with an ONAP instance Catalog service
17:09:19 <bryan_att> #info Jack: other suggestions?
17:09:35 <bryan_att> #info Pantelis: suggest the OAM and Integration and Test
17:09:46 <bryan_att> #info ... be integrated?
17:10:05 <bryan_att> #info Jack: they are already a big project
17:11:52 <bryan_att> #info Bryan: putting these into a single project would mix roles and technical focus - they are probably better separate
17:12:36 <bryan_att> #info Jack: AT&T will probably contribute some lab space for testing
17:13:37 <bryan_att> #info Bryan: also the TSC should consider the need/approach to a community lab program ala the OPNFV Pharos program: https://wiki.opnfv.org/display/pharos/Community+Labs
17:13:56 <bryan_att> #info Jack: back to Scott, how do we position for success?
17:14:13 <bryan_att> #info Chris: meeting cadence assumed to be weekly?
17:14:58 <bryan_att> #info Jack: maybe initially weekly, then evolving to a TSC alternating with projects,weekly
17:15:43 <bryan_att> #info Jack: we need to call for votes on TSC chair, release roadmap, committees, etc
17:18:16 <bryan_att> #info Scott: TSC chair election process would be run by email with a nomination period, statement of intent and bio, and run the vote pretty quickly.  I propose a nomination period opening now and ending next Tuesday, with voting thru next Friday.
17:19:24 <bryan_att> #info Ofer: what other positions should we consider?
17:20:16 <bryan_att> #info Jack: any need for a co-chair position?
17:20:47 <bryan_att> #info Sachin: how do we form the committees?
17:21:01 <bryan_att> #info Jack: we vote on the committees and let them form
17:22:36 <bryan_att> #info Susan: Yes - so is the other location reserved? should we expect to see the code at https://github.com/acumos sometime?
17:23:31 <bryan_att> #resoution The TSC agrees that the project repos should be sync'd with the github account
17:23:56 <bryan_att> #info Scott: calls for TSC agreement on the process for TSC Chair election
17:24:17 <bryan_att> #info The TSC agreed with the proposed process for TSC Chair election
17:25:40 <bryan_att> #info Scott: should the project approve the project structure Jack has proposed?
17:26:07 <bryan_att> #info The TSC agrees to the project structure as proposed by Jack
17:26:45 <bryan_att> #info Scott: should the project implement a bi-annual release schedule?
17:29:06 <bryan_att> #info The TSC agrees a bi-annual release schedule
17:39:29 <bryan_att> #info Bryan: shows the wiki page https://wiki.acumos.org/display/AC/Acumos+Architecture+Mapping+to+Repos+Jira+etc where the association of projects to repos, and links to where to find where who are the committers etc
17:41:04 <bryan_att> #info Jack: suggest that those who want to contribute to the committees reach out to Annie to express interest and get connected to the mail list etc where the committees will  collaborate
17:44:26 <bryan_att> #info Bryan: suggests we have (1) TSC meetings; (2) project meetings; (3) Community-wide meetings ala the Model that has worked well in OPNFV
17:46:26 <bryan_att> #info Pantelis: asks for clarification of use of Slack
17:47:22 <bryan_att> #info Jack: it seems that we would incur some additional costs now for Slack integration with IRC etc, so it appears we will better focus direct communication on IRC
17:47:58 <bryan_att> #info Pantelis: what about integration with Github etc for notifications of issues, etc
17:49:41 <bryan_att> #info Bryan: github will be a mirror, but generally I don't think we would expect it to be a way that issues etc are brought in, if we focus users and others on JIRA or other avenues e.g. Stackoverflow for input. Also there is strong integration with Git/Gerrit and IRC that should provide needed notifications.
17:51:02 <bryan_att> #info Scott: the TSC will meet in 2 weeks at April 9th 6AM Pacific time.
17:51:54 <bryan_att> #info Bryan: we will post these minutes and future TSC meeting schedule, agendas, etc on a Wiki space/page created for that, and send out the links to the lists etc.
17:52:00 <bryan_att> #endmeeting