|
| 1 | +# Creating SIG TF.js |
| 2 | + |
| 3 | +| Status | Proposed | |
| 4 | +:-------------- |:---------------------------------------------------- | |
| 5 | +| **RFC #** | |
| 6 | +| **Author(s) ** | Ping Yu ( [email protected]), Sandeep Gupta ( [email protected]) | |
| 7 | +| **Sponsor ** | Thea Lamkin ( [email protected]) | |
| 8 | +| **Updated** | 2020-09-16 | |
| 9 | + |
| 10 | +## Objective |
| 11 | + |
| 12 | +We propose to create a Tensorflow SIG to facilitate community-contributed components |
| 13 | +to tensorflow/tfjs. This document outlines the context goals, and engagement plan for |
| 14 | +the proposed Special Interest Group. |
| 15 | + |
| 16 | +## Context |
| 17 | + |
| 18 | +JavaScript is a very versatile and widely-used language. With TensorFlow.js, web application |
| 19 | +developers and JS developers can now use Machine Learning with TensorFlow in their JS |
| 20 | +applications. TensorFlow.js is the leading framework for ML in JavaScript with huge user growth |
| 21 | +(2.1M npm downloads, more than 2x YoY growth in the number of avg daily downloads). With the |
| 22 | +growth of the library, we now support an increasing number of use cases across a variety of |
| 23 | +platforms and backends, with many more models, use-cases, and applications. |
| 24 | + |
| 25 | +The core TensorFlow.js engineering team has been working on building the infrastructure and |
| 26 | +tooling to enable ML to run in JavaScript powered applications, as well as adding support for |
| 27 | +more types of models. TensorFlow.js has more than 220 contributors on GitHub which include many |
| 28 | +passionate contributors (individual developers, GDEs, and enterprise users) who have been active |
| 29 | +participants in the TensorFlow.js ecosystem. We want to accelerate the community involvement in |
| 30 | +the project to help continue meet the needs and help drive new directions for the project. |
| 31 | + |
| 32 | +## Goals & Objectives |
| 33 | + |
| 34 | +We welcome community contributions on any area of TensorFlow.js, but the SIG will be focused on |
| 35 | +the following goals: |
| 36 | +- Driving TensorFlow.js features for Server-side execution with tfjs-node. This will include |
| 37 | +building tooling and infra for end to end, production-ready ML with TensorFlow.js. |
| 38 | +- Developing features for specific platforms and deployments (eg. React Native, IoT and embedded |
| 39 | +devices, etc); |
| 40 | +- Building workflows for Transfer learning features for customizing models |
| 41 | +- Adding support for newer models and application areas (eg. NLP, RL, etc), and data analysis |
| 42 | +algorithms |
| 43 | +- Conducting research and implementing prototypes for client-side, privacy preserving ML and |
| 44 | +Federated Learning. |
| 45 | +- Identifying performance issues, tradeoffs, and requirements. |
| 46 | +- Model benchmarking across browsers, hardware and devices. |
| 47 | +- Model encryption. |
| 48 | +- Model visualization. |
| 49 | +- These projects will move towards community ownership as work streams mature. |
| 50 | + |
| 51 | + |
| 52 | +## Membership |
| 53 | + |
| 54 | +We encourage any developers working at the intersection of machine learning and web/JS |
| 55 | +applications to join and participate in the activities of the SIG. Whether you are working on |
| 56 | +advancing the platform, prototyping or building specific applications, or authoring new libraries, |
| 57 | +we welcome your feedback on and contributions to Tensorflow.js and its tooling, and are eager to hear |
| 58 | +about any downstream results, implementations, and extensions. |
| 59 | + |
| 60 | +We have multiple channels for participation, and publicly archive discussions in our user group and |
| 61 | +announcements mailing lists: |
| 62 | +- [email protected] -- our general mailing list that all are welcome to join ( [archive group ](https://groups.google.com/a/tensorflow.org/g/tfjs)) |
| 63 | +- [email protected] -- Announcement only mailing list for TF.js community ( [archive group ](https://groups.google.com/a/tensorflow.org/g/tfjs-announce)) |
| 64 | + |
| 65 | +We will create a new mailing list for TensorFlow.js SIG members. |
| 66 | + |
| 67 | +### Other Resources |
| 68 | +- Repository: https://github.com/tensorflow/tfjs |
| 69 | +- Documentation: https://www.tensorflow.org/js |
| 70 | + |
| 71 | +## Organization and Governance |
| 72 | +SIG project leads will be added to a SIG TF.js maintainers team on GitHub to streamline their |
| 73 | +contributions to tensorflow/tfjs. As specific ideas and work streams develop, we will explore creating |
| 74 | +new, community-owned repos that the SIG will drive. |
| 75 | + |
| 76 | +## Contacts |
| 77 | +### Project Lead(s): |
| 78 | +- Ping Yu (Google) |
| 79 | +- Sandeep Gupta (Google) |
| 80 | +- Ton Ngo (IBM): |
| 81 | + - Server side support (GPU, training) |
| 82 | + - End-to-end pipeline on Kubernetes (Kubeflow) |
| 83 | +- Ricky Cao (Alibaba) |
| 84 | + - Building tooling and infra for end to end, production-ready ML with TensorFlow.js. |
| 85 | + - Pipeline with transfer learning |
| 86 | + - Model Encryption |
| 87 | +- Ningxin Hu (Intel) |
| 88 | + - Benchmarking and performance optimization |
| 89 | +- Gant Laborde (Infinite Red) |
| 90 | + - Platforms (React and React Native) |
| 91 | + - Adding support for newer models and application areas (eg. NLP, RL, etc), |
| 92 | + - Model visualization |
| 93 | + |
| 94 | +### SIG members: |
| 95 | +- Adam Bouhenguel (Tesserai) |
| 96 | +- Clément Walter (IBM) |
| 97 | +- Eric Li (Alibaba) |
| 98 | +- Mrinal Mathur (ARM) |
| 99 | +- Patrick Haralabidis (Carlisle Homes) |
| 100 | +- Paul Van Eck (IBM) |
| 101 | +- Saswat Samal (Student) |
| 102 | +- Shivay Lamba (Metvy) |
| 103 | +- Ted Chang (IBM) |
| 104 | +- Va Barbosa (IBM) |
| 105 | +- YiHong Wang (IBM) |
| 106 | +- Zebai (Alibaba) |
| 107 | + |
| 108 | +### Administrative questions: |
| 109 | +- Thea Lamkin (Google): thealamkin at google dot org |
| 110 | +- Joana Carrasqueira (Google): joanafilipa at google dot org |
| 111 | +- tf-community at tensorflow dot org |
| 112 | + |
| 113 | +### Meeting cadence: TBD |
0 commit comments