The purpose of this document is to provide information regarding the communication channels for the OpenSearch Project. All communication is subject to the OpenSearch Code of Conduct. Please see CONTRIBUTING if you're interested in contributing to the project.
OpenSearch has a workspace on Slack to provide 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.
Join Workspace
- Visit the slack landing page on OpenSearch.org for information on registering your account. You will be required to enroll in two-factor authentication to ensure the best possible security of your account.
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.
- Feel free to update your profile photo to something unique to you. All profile photos are subject to the OpenSearch Code of Conduct policies.
- Optionally share your pronouns by adding them to the end of your Full Name in your profile. This way other participants will be able to see them and be respectful to your communication preferences. Please also be respectful of other participants’ pronouns.
After you join OpenSearch workspace you will be automatically added to the following channels:
- #announcements - Read only channel for overall project announcements. This may include critical security issues, releases, milestones or general information related to the OpenSearch Project community.
- #general - a channel for asking general questions. Based on the question or discussion users will mostly likely be directed to more specific channels based on the topics of interest.
- #random - consider this the water cooler in a face to face workspace. Feel free to introduce yourself to the community, share what you’re working on, or what you’re excited about learning with OpenSearch.
There are dedicated channels for the following (note that participants might be directed to more specific channels based on the nature of the discussion):
- #admin-requests - slack related feature requests and questions for the administration team.
- #alerting - Discussions and questions regarding alerting capabilities and use cases.
- #assistant-feedback - Feedback channel for the generative AI powered OpenSearch Assistant toolkit.
- #clients - Clients such as opensearch-java, opensearch-py, opensearch-hadoop.
- #cluster-manager - Discuss/brainstorm topics around cluster formation, cluster state publication & resiliency, decision making during index creation etc.
- #core - Primary channel for core OpenSearch. General questions and discussions about the core can be asked here.
- #dashboards - primary channel for Dashboards. General questions and discussions about dashboards can be asked here.
- #dashboards-ux - UX discussion for Dashboards.
- #dev - primary channel for development questions. This is a good place to start for participants interested in OpenSearch development but are not sure which channels to join.
- #devops - Developer operations, not to be confused with development. If you have a question about dev tooling, CI/CD, this is the place for you.
- #devrel - Developer relations discussion.
- #documentation - Discussions about documentation issues, requests, information gathering.
- #events - Discussion relating to OpenSearch and event.
- #general - General discussions and questions about the OpenSearch project. Not sure where to start? This is a good place and you may be directed to a more specific channel.
- #geospatial - All things Geo in OpenSearch and Maps in Dashboards.
- #indexing - Discussions around parsers, compression, merge strategies, flush/refresh settings, etc.
- #infra - primary channel for infra. General discussions, questions, or infra requests can be posted here.
- #ingest - Conversations, questions, and discussion related to ingesting data into OpenSearch.
- #k8s-operator - Discussions about the Kubernetes Operator.
- #maintainers - A channel for maintainers to discuss on efficiently maintaining repos. Discussions that lead to results in unilateral change (intentional or inadvertently) being codified, take them to the Maintainers forum category for long-term traceability.
- #migrations - Questions and discussions about migrating to OpenSearch or upgrading to new versions.
- #ml - Artificial Intelligence (AI) and/or Machine Learning (ML) and OpenSearch discussion.
- #observability - Observability (RUM, Synthetics, Trace Analytics) special interest group.
- #opensearchcon - OpenSearchCon related discussions and questions.
- #performance - Performance related discussions (e.g., benchmarks, regressions, opensearch-benchmarks repo).
- #plugins - Discussion of OpenSearch plugins and the future of extensibility.
- #random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
- #releases - Discussions related to planning, scheduling, go/no-go, and release related topics.
- #search - Search applications, relevance tuning, semantic search, Lucene, search features."
- #security - Discussions around core security and security plugin. DO NOT POST VULNERABILITIES. See SECURITY.md.
- #security-analytics - Share use-cases, issues you are facing, ideas, rules you may need help configuring or tweaking and most importantly discussing the feedback that will help security-analytics be better at solving for security workloads.
- #sql-ppl - All the Query Languages OpenSearch supports, including query planning and federation.
- #user-groups - User Groups program discussion. Learn about new meetings in your area, propose to speak at an upcoming meeting, find out more details on how to take part in or co-organize a User Group in your area.
- #vector-search - Discussions and questions regarding vector-search capabilities and use cases.
- 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.
- Slack conversations are not searchable outside the workspace. For this reason we encourage using the OpenSearch Discussion Forum 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, 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 for guidelines on handling security issues.