community/slack

Slack Guidelines

Slack is the main communication platform for Kubeflow outside of our mailing lists. It’s important that conversation stays on topic in each channel, and that everyone abides by the Code of Conduct. Community members should all expect to have a positive experience.

Chat is searchable and public. Do not make comments that you would not say on a video recording or in another public space. Please be courteous to others.

@here and @channel should be used rarely. Members will receive notifications from these commands and we are a global project - please be kind. Note: @all is only to be used by admins.

To join the Kubeflow Slack, click this Invitation to Kubeflow workspace

Code of Conduct

The Kubeflow Code of Conduct applies throughout the project, and includes all communication mediums.

Admins

(by Slack ID)
@Igor Mameshin

To connect: please reach out in the #admins channel, mention one of us in the specific channel where you have a question, or DM (Direct Message) one of us privately.

Admin expectations and guidelines

• Adhere to Code of Conduct
• Take care of spam as soon as possible, which may mean taking action by making members inactive
• Moderating and fostering a safe environment for conversations
• Bring Code of Conduct issues to the Steering Committee
• Create relevant channels and list Code of Conduct in new channel welcome message
• Help troubleshoot Slack issues
• Review bot, token, and webhook requests
• Be helpful!

Creating channels

Please submit a PR to Slack Channels with the name and description for a new channel. You can also contact #admins group with your request to create a new channel.

Channels are dedicated to working groups, sub-projects, community topics, and related programs/projects.

Channels are not:

• company specific; e.g. a channel named for a cloud provider must be used for conversation about Kubeflow-related topics on that cloud, and not proprietary information of the provider.
• private unless there is an exception: code of conduct matters, mentoring, security/vulnerabilities, or steering committee.

All channels need a documented purpose. Use this space to welcome the targeted community: promote your meetings, post agendas, etc.

We may make special accommodations where necessary.

Escalating and/or reporting a problem

Join the #admins channel or contact one of the admins via DM directly and describe the situation. If the issue can be documented, please take a screenshot to include in your message.

Bots, tokens, and webhooks

Bots, tokens, and webhooks are reviewed on a case-by-case basis. Expect most requests will be rejected due to security, privacy, and usability concerns. Bots and the like tend to make a lot of noise in channels.

Please join #admins channel and have a discussion about your request before requesting the access.

Admin moderation

Be mindful of how you handle communication during stressful interactions. Administrators act as direct representatives of the project, and need to maintain a very high level of professionalism at all times. If you feel too involved in the situation to maintain impartiality or professionalism, that’s a great time to enlist the help of another admin.

Try to take any situations that involve upset or angry members to DM or video chat. Please document these interactions for other Slack admins to review.

Content will be automatically removed if it violates code of conduct or is a sales pitch. Admins will take a screenshot of such behavior in order to document the situation. The community takes such violations extremely seriously, and they will be handled swiftly.

Deactivating accounts

For reasons listed below, admins may deactivate individual Slack accounts. Due to Slack’s framework, it does not allow for an account to be banned or suspended in the traditional sense. Read Slack’s policy on this.

• Spreading spam content in DMs or channels
• Not adhering to the Code of Conduct in DMs or channels
• Overtly selling products, related or unrelated to Kubeflow

Specific channel rules

In the case that certain channels have rules or guidelines, they will be listed in the purpose or pinned docs of that channel.

DM (Direct Message) conversations

Please do not engage in proprietary company specific conversations in the Kubeflow Slack instance. This is meant for conversations related to Kubeflow open source topics and community.

Proprietary conversations should occur in your company communication platforms. As with all communication, please be mindful of appropriateness, professionalism, and applicability to the Kubeflow community.

---

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.