Slack Code of Conduct

By taking part in OPIN’s community discussions on Slack, you are agreeing to this Code of Conduct.

The purpose of the OPIN Slack community is to allow members to talk about all aspects of OPIN’s activities in general. This is the place to ask (and answer) questions, post ideas and discoveries, and encourage one another.

To achieve this, we strive to keep the community a positive space that can be enjoyed by all, and we ask every member of the community to be respectful of this space and one another at all times.

Use Appropriate Language

Be kind to one another! Please avoid posting personal attacks, threats, profanity, or sexually-explicit language in your activities within the community. If you feel that there is inappropriate activity happening on Slack and don’t feel comfortable addressing it directly, please let us know as soon as possible.

Avoid Repeated Direct Messages and Tagging

To help keep the community a welcoming place for all, please refrain from sending direct messages or tagging other community members who have requested not to be contacted. If you direct message or tag someone, they are not obligated to respond. Likewise, if you are tagged in a post or direct messaged, you are not obligated to respond. If the issue persists, or if the message is inappropriate in nature, please refrain from engaging in the conversation and let us know.

In particular, please refrain from tagging anyone on a new post; instead we ask that you just address your post to the channel as a whole, and leave it for anyone there to respond. Channels are intended to be a public forum, rather than an individual's office hours. For the same reason, please also refrain from asking questions in a direct message, unless the other person has explicitly offered to provide such support. Direct messages are best suited for more personal social interactions.

The main valid reason to tag someone is to continue a pre-existing conversation with them, and particularly when responding to a question that they have asked. Please do not abuse this function, as repeated tagging of someone who has assisted you may reduce their willingness to continue to do so.

Please note that this rule includes advisors as well. Our industry advisors are all invited to become community members, but are not expected to provide any support in this capacity. When on Slack, please treat the advisors as you would any other community member.

Avoid illegal activity

Do not post anything that can be construed as advising others to break the law. In particular, do not post links to pirated content, and do not provide advice on illegal bypassing of software security protection. On the other hand, general discussions of software security are welcome.

Confidentiality and Intellectual Property

Please do not post or link to any private information (your own or others’). This includes credit card numbers, passwords, product/API keys or any sensitive personally identifiable information, such as social security numbers, address, etc. Please do not post anything that may be considered the intellectual property of someone else or of a company. Take particular care when posting screenshots of your desktop.

Avoid Marketing

You are welcome to post links to documents, tools, products or services that you think would be useful to the work or projects of the OPIN Lab, but please refrain from blatant advertising, marketing or any kind of spam. In particular, posting affiliate links to third-party services such that clicking on the link or buying the services within would directly or indirectly financially benefit the poster is prohibited, due to the potential conflict of interest. On the other hand, posting a link to your own site, is fine.

No soliciting

Our Slack community is intended as a place for discussions and collaboration opportunities. Soliciting business from fellow members, however, can lead to conflicts of interest, and our Slack channel is not the place for this.

Take care when following any advice

Community posts might include advice on laws, regulations, insurance or technical topics. This sort of advice is provided by community members as-is, without any liability. Consider any such advice carefully, and ask for clarification as needed; any potential damage or loss of data resulting from following advice is your own responsibility.

Remember, each post only reflects the views and opinions of its author, and you as a community member are solely responsible for anything you post.

Access to the Slack Community

In order to create a positive and productive communication environment for members, we restrict Slack usage to active community members and members of the OPIN Innovation Lab. If your company/employer stops being a member, your access to Slack will be removed.

Access to the OPIN Slack Community is only made available to the following:

Active members of the OPIN community.

Members of the OPIN Innovation Lab.

Violation of this Code of Conduct

“Two Strikes, You’re Out!”

If you violate any portion of the Slack Code of Conduct, regardless of whether or not you violated the same section repeatedly or a combination of sections on different occasions, your access to Slack will be removed.

You will be notified of each strike against the Code of Conduct. We will explain what section of the Code of Conduct has been violated, citing the particular behaviour that resulted in a strike.

1st Strike: Slack message warning.

2nd Strike: An email or Slack message to confirm removal from the Slack Community.

If we find that your behaviour on Slack is inappropriate, but it does not fall under a section stated in the Slack Code of Conduct, you will receive a “pre-strike warning” Slack message, notifying you of the behaviour. This is not a strike. A new section will then be added to the Code of Conduct to encompass this behaviour. Any violation of this new section by you or others in the future will be considered a strike.

General posting guidelines

Write a one-line title that summarizes your discussion topic.

A one-line title is the first thing other Slack members will see, and if your title isn't interesting, they won't read the rest. You want to grab their attention so it’s important to:

Treat your title like an elevator pitch.

Spelling, grammar, and punctuation are important!

As a rule of thumb, don’t assume that the reader has prior background knowledge.

Proofread before posting!

Before you hit send, take a moment and read through your message from start to finish. Pretend you're seeing it for the first time: does it make sense? Do a final check on your title - does it still make sense? If so, hit send!

Make the most of Slack’s search functionality

If you have a question, keep in mind that you can use Slack to search for previously posted questions and answers on a topic of your choice by using the Slack search bar.

Overview of our main Slack channels


New to Slack and don’t know where to start? Head over to the #introduce-yourself channel!

You can introduce yourself to your fellow coursemates by telling them a bit about yourself and what you’re most excited to learn on the course! It’s a great way to establish a sense of community with other new developers!


Creative Commons License
This document is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License