Skip to content

Commit

Permalink
PR updates round 2
Browse files Browse the repository at this point in the history
Signed-off-by: Nicholas Walter Knize <[email protected]>
  • Loading branch information
nknize committed May 24, 2022
1 parent 860af64 commit 47e26c9
Showing 1 changed file with 18 additions and 17 deletions.
35 changes: 18 additions & 17 deletions COMMUNICATIONS.md
Original file line number Diff line number Diff line change
@@ -1,33 +1,31 @@
# OpenSearch Project Communication

- [Overview](#overview)
- [Slack](#public-slack)
- [Slack](#slack)
- [Getting Started](#getting-started)
- [Workspace Channels](#workspace-channels)
- [Tips](#tips)

## Overview

The purpose of this document is to provide references and information regarding
the communication channels for the OpenSearch Project. All communication is
subject to the [OpenSearch Code of Conduct](CODE_OF_CONDUCT.md). Please see
The purpose of this document is to information regarding the communication
channels for the OpenSearch Project. All communication is subject to the
[OpenSearch Code of Conduct](CODE_OF_CONDUCT.md). Please see
[CONTRIBUTING](CONTRIBUTING.md) if you're interested in contributing to the
project.

## Slack

OpenSearch has a workspace on [Slack](https://opensearch.slack.com) to provide
open communication channels for all people interested in OpenSearch.
open communication channels for anyone interested in OpenSearch.

The following guidelines include a Getting Started for steps to register and
setup the workspace along with tips for using the workspace. Please read through
these guidelines carefully and thoroughly. All communications and behavior on
the public slack workspace is subject to the
[OpenSearch Code of Conduct](CODE_OF_CONDUCT.md).
these guidelines carefully and thoroughly.

### Getting Started

_Join Us_
_Join Workspace_

* Register your account at https://opensearch.slack.com. You will be required
to enroll in two-factor authentication to ensure the best possible security
Expand All @@ -37,8 +35,7 @@ _Update Profile_

* You may add your interests or keywords in the “What I do” section of your
profile along with your Title and Company/Organization. This helps
participants network and connect with each other by common interests. No
anonymous display names are allowed.
participants network and connect with each other by common interests.
* Feel free to update your profile photo to something unique to you. All
profile photos are subject to the
[OpenSearch Code of Conduct](CODE_OF_CONDUCT.md) policies.
Expand Down Expand Up @@ -78,16 +75,20 @@ be directed to more specific channels based on the nature of the discussion):

### Tips

* Try to keep communications in the open - Not only does this facilitate better
* Try to keep communications in the open - not only does this facilitate better
sharing of information but back channeled discussions are not retained for
search among other community members.
* Use the [OpenSearch Discussion Forum](https://forum.opensearch.org) for
technical support discussions or, at least, open a summary discussion on the
forum so useful findings can be shared with the rest of the community.
* Slack conversations are not searchable outside the workspace. For this
reason we encourage using the
[OpenSearch Discussion Forum](https://forum.opensearch.org) for technical support
discussions or, at least, open a summary discussion on the forum so useful findings
can be shared with the rest of the community.
* Keep discussions organized - use threads to respond to comments inline instead
of posting to the entire channel.
* Expect asynchronous response time - do not assume immediate response time as
participants are likely in different time zones.
* Expect asynchronous response time - do not assume immediate response time,
or possibly any response at all. This is a community driven communication tool with
participants in different time zones. The workspace should not be treated as a
formal support or training tool.
* Protecting IP and legally protected information is your responsibility, this is
a public forum. Don’t presume anything said here will remain private.
* **DO NOT** post CVEs or Security issues publicly. See [SECURITY](SECURITY.md)
Expand Down

0 comments on commit 47e26c9

Please sign in to comment.