The Great Expectations Slack is designed to provide a quick and efficient way for community members to ask questions, share ideas, connect with each other, and receive support from both GX staff and other users. This guide outlines an overview of the available slack channels and their uses, tips for asking questions in the slack, and additional guidelines to keep in mind when interacting in the slack.
To ensure that GX community spaces remain a positive and productive environment for all members, we have developed this GX Community Code of Conduct to outline the standards of behavior and communication we expect from all members.
Not in the GX Community Slack yet? Join our slack with this link!
Slack channels
Below are the different slack channels in which the community can ask questions, stay up-to-date on GX updates, and interact with one another.
| Channel name | Description |
|---|---|
| Announcements |  Updates and news from the Great Expectations team! Have something you think is announcement worthy? DM Josh Zheng. Posts are read-only; non-Admins may comment on the thread of an announcement. |
| #chitchat |  A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels. Memes also acceptable.  |
| Contributing |  For previous, current and prospective contributors to talk about potential contributions and to help each other with contributions. |
| #data-quality-discussions | A space for posing questions and starting discussions around data quality, GX, or industry trends. |
| #events |  A space for sharing and discussing upcoming events in the data space! |
| #gx-cloud-support |  A place for questions from users with questions about GX Cloud. |
| #gx-community-support | A place for questions from users with questions about GX Core. Ask questions after reviewing docs, discourse, & this How to Get Your Questions Answered post. Note: Questions posted in the GX Discourse forum will be prioritized before questions posted into Slack. For more information on what is supported, see the GX integration support policy. |
| #gx-feedback |  Have ideas or feedback related to the product or the GX documentation? Let us know here! |
| #gx-releases |  Announcements about GX releases! Only the GX team are meant to post in this channel. Non-Admins may comment on the thread of an announcement. |
| #gx-share |  Discussion about GX-related projects: from code snippets and techniques to blog posts and videos. If you have a GX related project you’d like to show off, or stumble onto something cool you’d like to share, this is the place to share it! |
| #integration-airflow | Discussions related to the Great Expectations Airflow provider and running GE in Airflow |
| #integration-partners |  A place for our ecosystem partners to coordinate and collaborate with us. |
| #introductions |  Welcome to the community; introduce yourself here! |
| #job-board |  Looking to hire someone in the GX community? Post your job here. |
| #tools-and-services |  Let us know about cool tools and services. Note: too much self-promotion can lead to your message being deleted and a warning. See Promoting Products or Services section below for more information. |
Temporary channels
Additionally, we may occasionally create channels that are meant to be temporary. Below are examples of temporary channels that would be archived after their intended use has passed:
| Channel name | Description |
|---|---|
| #event-(event-name) | If there is a lot of interest from our community in an event (e.g. an upcoming data conference), we may create temporary event-specific channels for community members going to connect before and during the event. |
Community code of conduct
To ensure that GX community spaces remain a positive and productive environment for all members, we have developed this GX Community Code of Conduct to outline the standards of behavior and communication we expect from all members.
Slack-specific
Use threading
If you have multiple messages to post on the same topic, please use Slack’s Reply in thread feature. Publishing multiple channel-level posts for the same question makes it harder to keep track of what needs to be answered.
Don’t tag GX employees in posts
We ask that folks do not tag GX employees directly. If incoming questions fall within what we support here at GX, they will be triaged by a support engineer. See our Get Support page for more details on where to post.
Don’t DM GX employees directly with questions.
Similar to the above guideline, we ask that you do not DM GX employees with your questions; instead, post to support channels.
Powered by you
This site is operated by your friendly local GX team and you, the community. If you have any feedback about how things should work here, start a new thread in gx-feedback and let’s discuss!
Terms of use
Our Community Terms of Use describes your (and our) behavior and rights related to content, privacy, and laws. To use this service, you must agree to abide by our Community Terms of Use.