Join the DataLakeHouse.io Community

Introduce yourself to your new peers, ask questions, and share what you know. The DataLakeHouse Community is where data professionals & analytics engineering lives and grows, and you’re a part of it!

First, some reasonable guidelines…

 

#1: The unbreakable rule: be respectful

We want everyone to have a fulfilling and positive experience in DataLakeHouse 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 DataLakeHouse Slack, codebase, issue trackers, and mailing lists are expected to follow the 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.

 

#2: We use the right channel

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.

 

#3: We ask good questions

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 Slack for more information about how to ask a good question.

 

#4: We avoid double-posting

The majority of questions in DataLakeHouse 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, DataLakeHouse Slack is not a customer service platform, it is a community of volunteers.

 

#5: We keep it in public channels

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.

 

#6: Do not solicit members of our Slack

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.

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.

If you are a vendor or recruiter, please identify yourself accordingly in your Slack profile.

 

#7: We don’t demand attention with @channels or @here, or by tagging individuals

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 many data professionals in DataLakeHouse Slack, constantly bombarding all of them with notifications does not support the long-term health of this 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.

 

#8: We ❤️ threads

The best way to reduce noise in Slack is to use threads — they help us manage the variety of conversations more easily  ٩(。•́‿•̀。)۶

——————————————–

 

Thanks for reading the guidelines!

Thank you for your help in ensuring the positive nature of our community. We’re glad to have you with us. Click the link below to get your DataLakeHouse Community Slack invite.