22
33| Status | Proposed |
44:-------------- |:---------------------------------------------------- |
5- | ** RFC #** | |
5+ | ** RFC #** | 314 |
66| ** Author(s)
** | Jaeyoun Kim (
[email protected] ), Jing Li (
[email protected] ), Mike Liang (
[email protected] ), Shuangfeng Li (
[email protected] )
| 77| ** Sponsor
** | Thea Lamkin (
[email protected] )
| 8- | ** Updated** | 2020-10-23 |
8+ | ** Updated** | 2020-10-30 |
99
1010## What is this group for?
1111
@@ -23,8 +23,8 @@ each group to coordinate the contributions, run community events like contests,
2323and maintain the code quality through the review process. Each group has the
2424flexibility to operate differently.
2525
26- SIG is also a place for community discussions and sharing best practices of
27- using TensorFlow 2 for state-of-the-art research. Furthermore, SIG provides
26+ SIG Models is also a place for community discussions and sharing best practices of
27+ using TensorFlow 2 for state-of-the-art research. Furthermore, SIG Models provides
2828product feedback to help TensorFlow to be improved.
2929
3030## Who will be part of it?
@@ -70,7 +70,7 @@ We plan to have a mailing list
7070(
[ [email protected] ] ( https://groups.google.com/a/tensorflow.org/forum/#!forum/models ) ),
7171arrange a regular (e.g., monthly) video conference call rotated by the SIG
7272leads. We will also use a Gitter chat channel
73- (https://gitter.im/tensorflow/models ) for discussions.
73+ (https://gitter.im/tensorflow/sig- models ) for discussions.
7474
7575As we have multiple SIG subgroups, each subgroup may run meetings and events
7676using different modes of communication.
0 commit comments