docs: added slack community guidelines (#10209)

* refactor: added slack community guidelines

* Some tweaks!

* busting cache to pass tests!

* Implemented excellent feedback
This commit is contained in:
Srini Kadamati 2020-06-30 23:20:09 -04:00 committed by GitHub
parent 1606d80490
commit c3cd63a2e8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 34 additions and 0 deletions

View File

@ -109,6 +109,40 @@ supported databases can be found
* [Join Community Slack](https://join.slack.com/t/apache-superset/shared_invite/enQtNDMxMDY5NjM4MDU0LWJmOTcxYjlhZTRhYmEyYTMzOWYxOWEwMjcwZDZiNWRiNDY2NDUwNzcwMDFhNzE1ZmMxZTZlZWY0ZTQ2MzMyNTU)
* [Mailing list](https://lists.apache.org/list.html?dev@superset.apache.org)
## Slack Community Guidelines
If you decide to join the [Community Slack](https://join.slack.com/t/apache-superset/shared_invite/enQtNDMxMDY5NjM4MDU0LWJmOTcxYjlhZTRhYmEyYTMzOWYxOWEwMjcwZDZiNWRiNDY2NDUwNzcwMDFhNzE1ZmMxZTZlZWY0ZTQ2MzMyNTU), please adhere to the following rules:
**1. Treat everyone in the community with respect.**
- We strive to make this community a warm place for people from all industries, use cases, geographies, and backgrounds. Harassment of any kind is not acceptable and wont be tolerated.
- Please follow the guidelines as outlined in the Superset Community [code of conduct here](https://github.com/apache/incubator-superset/blob/master/CODE_OF_CONDUCT.md).
**2. Use the right channel.**
- Channels are an effective way to organize and focus discussions while also empowering members to opt-in to the types of content theyre interested in. When questions are posted or discussions are started in the wrong channel, it dilutes the trust of the members in the channel and, more practically, makes it harder for your questions to be answered.
**3. Ask thoughtful questions.**
- Were all here to help each other out. The best way to get help is by investing effort into your questions. First check and see if your question is answered in [the Superset documentation](https://superset.incubator.apache.org/faq.html) or on [Stack Overflow](https://stackoverflow.com/search?q=apache+superset). You can also check [Github issues](https://github.com/apache/incubator-superset/issues) to see if your question or feature request has been submitted before. Then, use Slack search to see if your question has already been asked and answered in the past. If you still feel the need to ask a question, make sure you include:
- The steps youve already taken
- Relevant details presented cleanly (text stacktraces, formatted markdown, or screenshots. Please dont paste large blocks of code unformatted or post photos of your screen from your phone)
- The specific question you have or the specific type of help you're seeking
**4. Avoid double posting**
- This Slack community is not a customer support channel and all members are here voluntarily. If you arent getting a response to a question you have, make sure you look at rules 1, 2, and 3. Its also worth remembering that there may not be someone in the community who has the context to help you out.
**5. Communicate openly**
- Unless you have explicit permission from the person, please avoid sending direct messages to individuals. Communicating in public channels ensures that were all respecting each others attentions and we can scalably moderate our communication to mitigate harassment or discrimination. Do not use direct messages to pitch products and services. If you are receiving unwelcome direct messages, please notify an admin.
**6. Practice good Slack hygiene by using threads for discussions and emojis for light reactions.**
- The medium is the message. Slack can foster a warm, collaborative, and organized community when used effectively. We want to respect peoples attentions (thread notifications > channel notifications > DM notifications) and we want to improve information density (a member should be able to browse and explore many convo threads, not just see one thread discussed in a top level channel).
## Contributor Guide