RFC: Create SIG TFX-Addons

[theadactyl]

This RFC will be open for comments until March 16, 2021.

Create SIG TFX-Addons

Status	Proposed
RFC #	363
Author(s)	Robert Crowe (robertcrowe@google.com), Thea Lamkin (thealamkin@google.com)
Sponsor	Zhitao Li (zhitaoli@google.com), Mihai Maruseac (mihaimaruseac@google.com)
Updated	2021-03-02

Overview

We propose to create SIG TFX-Addons to facilitate community contributions of community-supported software and tools which can be used with TFX to build a production ML solution. This RFC outlines the context, goals, and engagement plan for the proposed Special Interest Group.

[theadactyl]

I think that's still a WIP, but we are happy to borrow heavily from the Addons model.

…

On Wed, Mar 10, 2021 at 1:27 PM Sergii Khomenko ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In rfcs/20210302-sig-tfx-addons.md <#363 (comment)>: > +We encourage any developers working in production ML environments, infrastructure, or applications to join and participate in the activities of the SIG. Whether you are working on advancing the platform, prototyping or building specific applications, or authoring new components, templates, libraries, and/or orchestrator support, we welcome your feedback on and contributions to TFX and its tooling, and are eager to hear about any downstream results, implementations, and extensions. + +We have multiple channels for participation, and publicly archive discussions in our user group mailing list: +- ***@***.*** – our general mailing list that all are welcome to join (archive group: https://groups.google.com/a/tensorflow.org/g/tfx) +- ***@***.*** – Google group for core team (to be created) + +We will create a new mailing list for TFX SIG members. + +Other Resources +- SIG Repository: http://github.com/tensorflow/tfx-addons (to be created) +- Documentation: https://www.tensorflow.org/tfx + +## Organization and Governance +A central Github repo will be created under the [TensorFlow organization](https://github.com/tensorflow) for individual SIG projects and contributions. The central repo will also contain overall SIG documents and resources, which will be managed by the TensorFlow team. Individual contribution projects will begin as proposals to the SIG, and once approved a folder will be created for the project, and project leaders assigned permissions to manage the folder. **Projects will be led, maintained, and be the responsibility of community project leaders. Google and the TensorFlow team will not provide user support or maintenance for contributed addons. The TFX team will support community maintainers in SIG operations and contribution infrastructure.** + +Categories of projects will be grouped under folders at the top level of the central SIG repo, including folders for components and examples. Individual projects will be assigned a new folder under the proper category folder, where all project materials will live. For all community-contributed projects the source of truth will be those project folders. Project leaders will be identified using OWNERS files at the top level of their project folder. New project leaders will be recruited for abandoned projects, or if new leaders are not found then projects will be deprecated and archived. Statistics will be generated and reported per-project. What is the lifecycle of such proposals/projects? Addons had quite well-defined sustainability - https://github.com/tensorflow/community/blob/master/rfcs/20190308-addons-proxy-maintainership.md#periodic-review — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#363 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABREJVIYEHBBKF7BZFDLLBLTC7P4XANCNFSM4YPZTLEQ> .