yujunjun/datahub
2
0
Fork 0
mirror of https://github.com/datahub-project/datahub.git synced 2025-06-27 05:03:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(slack): update to Slack guidelines (#5504)

Browse Source
This commit is contained in:
Maggie Hays 2022-07-27 13:10:35 -05:00 committed by GitHub
parent 2d68097ff4
commit d407904f66
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 33 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
docs/slack.md
View File

@ -2,24 +2,43 @@
The DataHub Slack is a thriving and rapidly growing community - we can't wait for you to join us!
[Sign up here](https://slack.datahubproject.io) to join us on Slack and to subscribe to the DataHub Community newsletter. Already a member? [Log in here](https://slack.datahubproject.io).
_[Sign up here](https://slack.datahubproject.io) to join us on Slack and to subscribe to the DataHub Community newsletter. Already a member? [Log in here](https://slack.datahubproject.io)._
## Slack Guidelines
In addition to our [Code of Conduct](CODE_OF_CONDUCT.md), we expect all Slack Community Members to respect the following guidelines:
### Make use of threads
Threads help us keep conversations contained and help us ensure we help you find a resolution and get you the support you need.
Use threads when posting long messages and large blocks of code and/or stack trace - it is a MASSIVE help for us to keep track of the large volume of questions across our various support channels.
### Do not post the same question across multiple channels
If you're having a tough time getting the support you need (or aren't sure where to go!), please DM [@Maggie](https://datahubspace.slack.com/team/U0121TRV0FL) for support
### Do not solicit members of our Slack
The DataHub Community exists to collaborate with, learn from, and support one another. It is not a space to pitch your products or services directly to our members via public channels, private channels, or direct messages.
We are excited to have a growing presence from vendors to help answer questions from Community Members as they may arise, but we have a strict 3-strike policy against solicitation:
1. First occurrence: We'll give you a friendly but public reminder that the behavior is inappropriate according to our guidelines.
2. Second occurrence: We'll send you a DM warning that any additional violations will result in removal from the community.
3. Third occurrence: We'll delete or ban your account.
We reserve the right to ban users without notice if they are clearly spamming our Community Members.
## Navigating DataHub Slack
Lets get you settled in --
Lets get you settled in --
- **Head over to [#introduce-yourself](https://datahubspace.slack.com/archives/C01PU1K6GDP) to, well, introduce yourself!** We’d love to learn more about you, what brings you here, and how we can support you
- **Not sure how to start?** You guessed it, check out [#getting-started](https://datahubspace.slack.com/archives/CV2KB471C) - we’ll point you in the right direction
- **Head over to [#introduce-yourself](https://datahubspace.slack.com/archives/C01PU1K6GDP) to, well, introduce yourself!** We'd love to learn more about you, what brings you here, and how we can support you
- **Not sure how to start?** You guessed it, check out [#getting-started](https://datahubspace.slack.com/archives/CV2KB471C) - we'll point you in the right direction
- **Looking for general debugging help?** [#troubleshoot](https://datahubspace.slack.com/archives/C029A3M079U) is the place to go
- **Need some live support from the Core DataHub Team?** Join us during our 2xWeek Office Hours via Zoom! Check out [#office-hours](https://datahubspace.slack.com/archives/C02AD211493) for more details
- **Looking for ways to contribute to the DataHub project?** Tell us all about it in [#contribute](https://datahubspace.slack.com/archives/C017W0NTZHR)
- **Have suggestions on how to make DataHub better?** We can’t wait to hear them in [#feature-requests](https://datahubspace.slack.com/archives/C02FWNS2F08)
- **Looking for ways to contribute to the DataHub project?** Tell us all about it in [#contribute](https://datahubspace.slack.com/archives/C017W0NTZHR)
- **Have suggestions on how to make DataHub better?** We can't wait to hear them in [#feature-requests](https://datahubspace.slack.com/archives/C02FWNS2F08)
- **Excited to share your experience working with DataHub?** [#show-and-tell](https://datahubspace.slack.com/archives/C02FD9PLCA0) is the perfect channel for you
- **Need something else?** Reach out to [@Maggie](https://datahubspace.slack.com/team/U0121TRV0FL) - our Community Product Manager
### Slack Best Practices
Please keep in mind these Slack best-practices --
- **Make use of threads** for addressing specific questions/topics, and when posting large blocks of code - it helps us keep our channels and conversations organized
- **Avoid posting the same question in multiple channels** - if you’re having a tough time getting the support you need (or aren’t sure where to go!) please DM [@Maggie](https://datahubspace.slack.com/team/U0121TRV0FL) for support
- **Need something else?** Reach out to [@Maggie](https://datahubspace.slack.com/team/U0121TRV0FL) - our Community Product Manager