dbt Slack is special. We currently have {{ n_slack_users }} data professionals in our Slack, many of whom genuinely love this community. It’s filled with smart, kind, and helpful people who share our commitment to elevating the analytics profession.
We are committed to maintaining the spirit of this community, and as such have written some guidelines to help new members understand how to best participate in our Slack.
You can read the full rules here, but here’s what you need to know before joining:
We want everyone to have a fulfilling and positive experience in dbt Slack and we are continuously grateful for your help in ensuring that this is the case.
The guidelines that follow are important, but transgressions around Slack etiquette are forgivable. This first rule, however, is serious–-we simply will not tolerate disrespectful behavior of any kind.
Everyone interacting in dbt Slack, codebase, issue trackers, and mailing lists are expected to follow the PyPA Code of Conduct. If you are unable to abide by the code of conduct set forth here, we encourage you not to participate in the community.
It’s important that we make it possible for members of the community to opt-in to various types of conversations. Our different Slack channels specifically exist for this purpose.
Make sure you check the available channels before sending a message. If you're unsure, try the #beginners channel.
Our best members show respect by taking the time to ask good questions. Good questions are thoughtful, well-researched, and include relevant details such as what you've tried, documentation you've read, and any error messages.
A thoughtful and well-researched post will garner far more responses than a low-effort one. See how to get the most out of the Slack for more information about how to ask a good question.
The majority of questions in dbt Slack get answered, though you may need to wait a bit. If you’re not getting a response, do not post the same question to multiple channels. Even though a question feels urgent, dbt Slack is not a customer service platform, it is a community of volunteers.
Keeping messages in public channels helps others in the community learn. Unless you have someone’s express permission, do not directly message members of our community.
This community is built for data practitioners to discuss the work that they do, the ideas that they have, and the things that they are learning. It is decidedly not intended to be lead generation for vendors or recruiters.
If you are a vendor or recruiter, please identify yourself accordingly in your Slack profile, and read more about how you can best participate in our community here.
The @channel and @here keywords in Slack are disabled for everyone except admins. If you make a post containing @channel or @here, nothing will happen.
We are also sensitive about tagging individuals for in-depth assistance with your question. There are thousands of data professionals in dbt Slack, constantly bombarding all of them with notifications does not support the long-term health of this community.
The best way to reduce noise in Slack is to use thread--they help us manage the variety of conversations more easily.