Skip to content

Commit cef111a

Browse files
authored
Update “Contribute to the community” on TensorFlow.org
Will add link to SIG lists once new page is created
1 parent 99551a1 commit cef111a

File tree

1 file changed

+43
-87
lines changed

1 file changed

+43
-87
lines changed

site/en/community/contribute/community.md

Lines changed: 43 additions & 87 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,28 @@
22

33
An open source project isn't just about the code, it's also about the community of users, developers, writers, researchers, and other contributors. You can help grow and support this community.
44

5-
Please read the TensorFlow [Code and Collaboration governance](https://github.com/tensorflow/community/blob/master/governance/code-and-collaboration.md)
5+
Please read the TensorFlow [Code and Collaboration governance](https://github.com/tensorflow/community/blob/master/governance/code-and-collaboration.md).
66

77
## Community support
88

9-
Many people [ask questions about TensorFlow on Stack Overflow](https://stackoverflow.com/questions/tagged/tensorflow). Answering those questions and pointing people to the relevant documentation is a great service to the community.
9+
Many people [ask questions about TensorFlow on the TensorFlow Forum](https://discuss.tensorflow.org/). Answering those questions and pointing people to the relevant documentation is a great service to the community.
1010

1111
Some users also ask support questions as GitHub issues. We try to discourage this, as GitHub issues are not the best place to ask for technical support. However, if you notice these issues, you are encouraged to answer them and point people to the relevant documentation.
1212

13+
### TensorFlow Forum
14+
15+
The [TensorFlow Forum](https://discuss.tensorflow.org/) is a central platform for community discussion and support. It brings our community together to share ideas, best practices and use cases related to TensorFlow. We foster an open and welcoming environment according to the [TensorFlow Code of Conduct](https://discuss.tensorflow.org/faq).
16+
17+
The TensorFlow Forum is organized by categories, subcategories and tags. We encourage you to create an account and follow categories and tags of interest. When you create a new post, select the most appropriate [category or subcategory](https://discuss.tensorflow.org/categories) and [tags](https://discuss.tensorflow.org/tags) to help other users find your topic.
18+
19+
For more information on Discourse features, read the [Discourse New User Guide](https://meta.discourse.org/t/discourse-new-user-guide/96331).
20+
21+
### Become a Forum expert
22+
23+
Discourse uses [trust levels](https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/) to reward increasing levels of participation in the forum. The Forum facilitates learning by doing, letting you to collect [badges](https://discuss.tensorflow.org/badges) that are displayed on your profile. This is a great way to be recognized for helping fellow community members. The more you invest in helping community members, the more badges and forum tools you will unlock.
24+
25+
Certain groups, such as TensorFlow Team members and Machine Learning GDEs display a special icon for easier identification.
26+
1327
## Communication
1428

1529
The TensorFlow community has a number of formal and informal ways of keeping in touch.
@@ -18,95 +32,37 @@ The TensorFlow community has a number of formal and informal ways of keeping in
1832

1933
The primary communication about work on TensorFlow happens in the [TensorFlow repositories on GitHub](https://github.com/tensorflow). This is the place to discuss bugs, new features, and in-progress work.
2034

21-
<!--
22-
### Forums
23-
-->
24-
2535
### Mailing lists
2636

27-
Mailing lists are reserved for announcements and contributor conversation. They are not intended to provide technical support.
28-
29-
#### General TensorFlow lists
37+
Most communication happens on the TensorFlow Forum, however the following mailing lists are still used for announcements and contributor conversation. They are not intended to provide technical support.
3038

3139
* [[email protected]](mailto:[email protected]) — All major releases and important announcements are sent to this mailing group. We recommend that you join this list if you depend on TensorFlow in any way.
32-
* [[email protected]](mailto:[email protected]) — General discussion about TensorFlow development and direction.
3340
* [[email protected]](mailto:[email protected]) — Discussion for developers who are contributing to TensorFlow.
3441

42+
### Blog and social media
43+
44+
The [TensorFlow Blog](http://blog.tensorflow.org/) is full of great content both from our team at Google and the broader community. We'd love to hear what you have to say, so if you would like to submit an article for review, please contact the TensorFlow Developer Relations team.
45+
46+
On [Twitter](https://twitter.com/tensorflow) we share the latest and greatest from our community, and our [YouTube channel](https://www.youtube.com/tensorflow) has free educational content to help you create, understand and deploy models for a variety of applications.
47+
48+
## TensorFlow Community Spotlight
49+
50+
The TensorFlow Community Spotlight Program provides an opportunity to showcase your passion projects using TensorFlow. [Submit your project](https://services.google.com/fb/forms/tensorflowprojectrecognitionform/) for a chance to be featured and recognized on TensorFlow’s Twitter account.
51+
52+
Follow the [#TFCommunitySpotlight](https://twitter.com/hashtag/TFCommunitySpotlight?src=hashtag_click) hashtag and find out more about past winners [here](https://blog.tensorflow.org/2020/11/tensorflow-community-spotlight-program-update.html).
53+
54+
## User groups
55+
56+
[TensorFlow User Groups](https://www.tensorflow.org/community/groups) (or TFUGs, for short) are local communities of developers and researchers around the world. If you don’t have a TFUG in your country or city, we encourage you to start one by reaching out to [[email protected]](mailto:[email protected]).
57+
58+
## Events
59+
60+
The TensorFlow team hosts and supports events all around the world! If your TFUG is planning an upcoming event or meetup, please let our Community know by posting about it on the TensorFlow Forum under the [Events category](https://discuss.tensorflow.org/c/events/27).
61+
62+
If you’ve already held your event, please share feedback with us [here](https://docs.google.com/forms/d/e/1FAIpQLSdvb8c2ZFXxS05aX6dpUVZlfYA0WsFFq-sUAzjiohVKAQ1RLw/viewform)! Feel free to share recaps and recordings on the Forum as well.
63+
64+
## TensorFlow Certificate program
65+
66+
Demonstrate your proficiency in using TensorFlow to solve deep learning and ML problems. Advance your career and connect with developers who also have passed the exam on the [Certificate Network](https://www.tensorflow.org/certificate-network).
3567

36-
#### Project-specific lists
37-
38-
* [[email protected]](mailto:[email protected]) — If you are interested in contributing to the TensorFlow documentation, join this mailing list.
39-
* [[email protected]](mailto:[email protected]) — Discussion and collaboration around TensorFlow Hub.
40-
* [[email protected]](mailto:[email protected]) — General discussion about Magenta development and direction.
41-
* [[email protected]](mailto:[email protected]) — Community and collaboration around Swift for TensorFlow.
42-
* [[email protected]](mailto:[email protected]) — Discussion and peer support for Tensor2Tensor.
43-
* [[email protected]](mailto:[email protected]) — Announcements of new TensorFlow.js releases.
44-
* [[email protected]](mailto:[email protected]) — Discussion and peer support for TensorFlow.js.
45-
* [[email protected]](mailto:[email protected]) — Discussion and peer support for TensorFlow Lite.
46-
* [[email protected]](mailto:[email protected]) — Discussion and peer support for TensorFlow Probability.
47-
* [[email protected]](mailto:[email protected]) — Community discussion and support for TPU users.
48-
49-
50-
### Blog
51-
52-
We post regularly to the [TensorFlow Blog](http://blog.tensorflow.org/), with content sourced from both TensorFlow developers and the broader community. If you would like to submit an article for review, please contact the TensorFlow Developer Relations team.
53-
54-
### Social media
55-
56-
For news and updates from around the universe of TensorFlow projects, follow [@tensorflow](https://twitter.com/tensorflow) on Twitter. To watch TensorFlow-related content, check out our [YouTube](http://youtube.com/tensorflow/) channel.
57-
58-
### User groups
59-
60-
TensorFlow has many communities all over the world! For a complete listing, please refer to the [Community](https://www.tensorflow.org/community/groups) section on the TensorFlow website.
61-
62-
### Special Interest Groups (SIGs)
63-
64-
To enable focused collaboration on particular areas of TensorFlow, we host Special Interest Groups (SIGs). SIGs do their work in public. If you want to join and contribute, review the work of the group, and get in touch with the relevant SIG leader. Membership policies vary on a per-SIG basis.
65-
66-
67-
#### Current SIGs
68-
69-
As of January 2019, the current TF-SIGs are:
70-
71-
<table>
72-
<tr>
73-
<td><a href="https://groups.google.com/a/tensorflow.org/d/forum/addons">SIG Addons</a>
74-
</td>
75-
<td>Maintains a repository of contributions that conform to well-established API patterns, but implement new functionality not available in core TensorFlow.
76-
</td>
77-
</tr>
78-
<tr>
79-
<td><a href="https://groups.google.com/a/tensorflow.org/d/forum/build">SIG Build</a>
80-
</td>
81-
<td>Focuses on issues surrounding building, packaging, and distribution of TensorFlow.
82-
</td>
83-
</tr>
84-
<tr>
85-
<td><a href="https://groups.google.com/a/tensorflow.org/d/forum/io">SIG IO</a>
86-
</td>
87-
<td>Works on support for file systems and formats other than those in core TensorFlow (such as Apache Ignite FS, or Apache Hadoop SequenceFile), as subclasses of tf.data.Dataset and TensorFlow filesystems.
88-
</td>
89-
</tr>
90-
<tr>
91-
<td><a href="https://groups.google.com/a/tensorflow.org/d/forum/networking">SIG Networking</a>
92-
</td>
93-
<td>Maintains network fabrics and protocols not available in core TensorFlow.
94-
</td>
95-
</tr>
96-
<tr>
97-
<td><a href="https://groups.google.com/a/tensorflow.org/d/forum/tensorboard">SIG TensorBoard</a>
98-
</td>
99-
<td>Furthers the development and direction of TensorBoard and its plug-ins.
100-
</td>
101-
</tr>
102-
<tr>
103-
<td><a href="https://groups.google.com/a/tensorflow.org/forum/#!forum/rust">SIG Rust</a>
104-
</td>
105-
<td>Collaborates on the development of TensorFlow's Rust bindings.
106-
</td>
107-
</tr>
108-
</table>
109-
110-
If you believe there is a strong need for a new SIG,
111-
please read the [SIG playbook]() and get in touch with
112-
the TensorFlow Developer Relations Team.
68+
Stipends are available. See [more information](https://www.tensorflow.org/certificate) on the TensorFlow Certificate program.

0 commit comments

Comments
 (0)