Skip to content

Commit

Permalink
updated header for more clarity
Browse files Browse the repository at this point in the history
Signed-off-by: Mark Cohen <markcoh@amazon.com>
  • Loading branch information
macohen committed Dec 14, 2023
1 parent ea458ae commit 9491101
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions TRIAGE.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
# Triage in OpenSearch Core
## What Do We Do With These Labels Anyway?

Across all repositories in opensearch-project, we have a process called “triage.” The goal of this process is to make sure repository owners and maintainers check new issues to understand them. First - we learn if the issue is security related (e.g. CVE), second - we understand if we have enough information to act on the issue, third - we re-label or respond on the issue. During triage we do not work on these issues, but instead just try to get the issue to a next step. Because the OpenSearch core repository (https://github.com/opensearch-project/OpenSearch) has so many different functions with different sets of contributors working on these functions, repo owners decided to treat these functions like separate repositories when triaging to get through the backlog faster and have more focus. There are a few maintainers that do triage in public (see https://meetup.com/OpenSearch to join) and there will be more coming.
Expand Down

0 comments on commit 9491101

Please sign in to comment.