OpenSearch is now supported by The OpenSearch Software Foundation, a …

…project of The Linuux Foundation.

Signed-off-by: dblock <[email protected]>

.github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -1,6 +1,6 @@
 ---
-name: 🐛 Bug report
-about: Create a report to help us improve
+name: 🐛 Bug Report
+about: Create a report to help us improve.
 title: '[BUG]'
 labels: 'bug, untriaged'
 assignees: ''

.github/ISSUE_TEMPLATE/FEATURE_REQUEST_TEMPLATE.md

@@ -1,6 +1,6 @@
 ---
-name: 🎆 Feature request
-about: Request a feature in this project
+name: 🎆 Feature Request
+about: Request a feature in this project.
 title: '[FEATURE]'
 labels: 'enhancement, untriaged'
 assignees: ''

.github/ISSUE_TEMPLATE/PROPOSAL_TEMPLATE.md

@@ -1,6 +1,6 @@
 ---
 name: 💭 Proposal
-about: Suggest an idea for a specific feature you wish to propose to the community for comment
+about: Suggest an idea for a specific feature you wish to propose to the community for comment.
 title: '[PROPOSAL]'
 labels: proposal
 assignees: ''
@@ -10,19 +10,19 @@ assignees: ''
 _In a few sentences, describe the feature and its core capabilities._
 
 ### What users have asked for this feature?
-_Highlight any research, proposals, requests or anecdotes that signal this is the right thing to build. Include links to GitHub Issues, Forums, Stack Overflow, Twitter, Etc_
+_Highlight any research, proposals, requests or anecdotes that signal this is the right thing to build. Include links to GitHub Issues, Forums, Stack Overflow, Twitter, etc._
 
 ### What problems are you trying to solve?
-_Summarize the core use cases and user problems and needs you are trying to solve. Describe the most important user needs, pain points and jobs as expressed by the user asks above. Template: When \<a situation arises> , a \<type of user> wants to \<do something>, so they can \<expected outcome>. (Example: When **searching by postal code**, **a buyer** wants to **be required to enter a valid code** so they **don’t waste time searching for a clearly invalid postal code.**)_
+_Summarize the core use cases and user problems and needs you are trying to solve. Describe the most important user needs, pain points and jobs as expressed by the user asks above. Template: When \<a situation arises> , a \<type of user> wants to \<do something>, so they can \<expected outcome> (e.g. When **searching by postal code**, **a buyer** wants to **be required to enter a valid code** so they **don’t waste time searching for a clearly invalid postal code.**)._
 
 ### What is the developer experience going to be?
 _Does this have a REST API? If so, please describe the API and any impact it may have to existing APIs. In a brief summary (not a spec), highlight what new REST APIs or changes to REST APIs are planned. as well as any other API, CLI or Configuration changes that are planned as part of this feature._
 
 #### Are there any security considerations? 
-_Describe if the feature has any security considerations or impact. What is the security model of the new APIs? Features should be integrated into the OpenSearch security suite and so if they are not, we should highlight the reasons here._
+_Describe whether the feature has any security considerations or impact. What is the security model of the new APIs? Features should be integrated into the OpenSearch security suite and so if they are not, we should highlight the reasons here._
 
 #### Are there any breaking changes to the API
-_If this feature will require breaking changes to any APIs, ouline what those are and why they are needed. What is the path to minimizing impact? (example, add new API and deprecate the old one)_
+_If this feature will require breaking changes to any APIs, outline what those will be and why they are needed. What is the path to minimizing impact? (e.g. add new API and deprecate the old one)._
 
 ### What is the user experience going to be?
 _Describe the feature requirements and or user stories. You may include low-fidelity sketches, wireframes, APIs stubs, or other examples of how a user would use the feature via CLI, OpenSearch Dashboards, REST API, etc. Using a bulleted list or simple diagrams to outline features is okay. If this is net new functionality, call this out as well._

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,10 @@
 contact_links:
-  - name: OpenSearch Community Support
-    url: https://discuss.opendistrocommunity.dev/
-    about: Please ask and answer questions here.
-  - name: AWS/Amazon Security
-    url: https://aws.amazon.com/security/vulnerability-reporting/
-    about: Please report security vulnerabilities here.
+  - name: 💬 OpenSearch Community Slack Workspace
+    url: https://opensearch.org/slack.html
+    about: Chat with community members and maintainers here.
+  - name: 🤷 OpenSearch Community Forum
+    url: https://forum.opensearch.org/
+    about: Ask and answer OpenSearch usage questions here.
+  - name: 🔐 Report a Security Issue
+    url: https://github.com/opensearch-project/.github/blob/main/SECURITY.md
+    about: Please e-mail [email protected]. Do not create a public GitHub issue.

.github/workflows/bake_time.yml

@@ -11,10 +11,10 @@ on:
 
 jobs:
   baking_pull_request:
-    name: "Baking pull request..."
+    name: "Baking pull request ..."
     runs-on: ubuntu-latest
     steps:
     - uses: peternied/bake-time@v3
       with:
-        check-name: "Baking pull request..."
+        check-name: "Baking pull request ..."
         delay-hours: 48

.github/workflows/link-checker.yml

@@ -6,12 +6,12 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
-      - name: lychee Link Checker
+      - name: Lychee Link Checker
         id: lychee
         uses: lycheeverse/lychee-action@master
         with:
           args: --accept=200,403,429 "./**/*.md" "./**/*.txt"
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      - name: Fail if there were link errors
+      - name: Fail if there were link errors.
         run: exit ${{ steps.lychee.outputs.exit_code }}

ADMINS.md

@@ -46,14 +46,14 @@ Please note that maintainers typically do not have admin-level permissions in th
 
 ### Adopt Organizational Practices
 
-Adopt organizational practices documented in this repo, work in the open, and collaborate with other admins by opening issues before making process changes. Prefer consistency, and avoid diverging from practices in the opensearch-project rganization.
+Adopt organizational practices documented in this repo, work in the open, and collaborate with other admins by opening issues before making process changes. Prefer consistency, and avoid diverging from practices in the opensearch-project organization.
 
 ## New Repos
 
 There are currently two ways new repositories may appear in the opensearch-project organization: creating a new repo and adopting, or moving a repo from outside of the organization into it. The process is the same.
 
-The AWS Open Source Program Office (OSPO) currently owns and manages the opensearch-project organization, and has permissions to create a new repo. While the admins above have admin-level permissions, they do not have permissions to create new repositories or move repositories into the organization.
+The AWS Open Source Program Office (OSPO) currently owns and manages the opensearch-project organization, and has permissions to create a new repo. This will change shortly following the [formation of the OpenSearch Software Foundation](https://foundation.opensearch.org/). While the admins above have admin-level permissions, they do not have permissions to create new repositories or move repositories into the organization.
 
 All new repositories inside opensearch-project follow the [security response process](SECURITY.md), and therefore require an Amazon team to be engaged when necessary. If you wish to create a repository in this organization, or move a repository into opensearch-project, please contact one of the above-mentioned admins via the [#maintainers channel on the public Slack](https://opensearch.slack.com/archives/C05L60S4UBT).
 
-While the opensearch-project organization has adopted [opensearch-plugin-template-java](https://github.com/opensearch-project/opensearch-plugin-template-java), or [opensearch-project/opensearch-learning-to-rank-base](https://github.com/opensearch-project/opensearch-learning-to-rank-base) in the past, we generally encourage you to start and run with your open-source project outside of the organization, and only consider making it part of it when you wish to include your already very popular component or tool in the "official" distribution.
+While the opensearch-project organization has adopted [opensearch-plugin-template-java](https://github.com/opensearch-project/opensearch-plugin-template-java), or [opensearch-project/opensearch-learning-to-rank-base](https://github.com/opensearch-project/opensearch-learning-to-rank-base) in the past, we generally encourage you to start and run with your open-source project outside of the organization, and only consider making it part of it when you wish to include your already very popular component or tool in the "official" distribution. To request moving a repo into this organization, please open a proposal in your repo, have repo maintainers confirm they wish to move, and engage admins via the [#admin-requests channel on the public Slack](https://opensearch.slack.com/archives/C051CKVFB2A).

CONTRIBUTING.md

@@ -16,7 +16,7 @@
 
 ## Contributing to OpenSearch
 
-OpenSearch is a community project that is built and maintained by people just like **you**. We're glad you're interested in helping out. There are several different ways you can do it, but before we talk about that, let's talk about how to get started.
+OpenSearch, a member of non-profit Linux Foundation, is a community project that is built and maintained by people just like **you**. We're glad you're interested in helping out. There are several different ways you can do it, but before we talk about that, let's talk about how to get started.
 
 ## First Things First