opensearch-project / opensearch-project/.github

[FEATURE] Document what untriaged label means and what typically happens during triage

Open
#102 7 comments 0 reactions 1 assignee View on GitHub

@minalsha is already working on this.

Since Nov 3, 2022.

documentation enhancement help wanted
Dominant language
No language data
Stars
41
Forks
74
Avg merge
3d 19h
Merged PRs (30d)
1

Description

Is your feature request related to a problem?

In https://github.com/opensearch-project/.github/blob/main/MAINTAINERS.md#triage-open-issues we talk about triaging issues. But what is it?

What solution would you like?

Add to https://github.com/opensearch-project/.github/blob/main/MAINTAINERS.md#triage-open-issues. I think we want to say that:

  1. Triage is a regular thing that teams do (with an example like security - provide link - that does it in the open).
  2. All new issues get an untriaged label.
  3. Triage means looking at all issues that say "untriaged" are looked at. Confirmed as valid as feature requests or bugs, belonging to this repo, etc.
  4. Untriaged label removed.
  5. Doesn't mean anyone will ever promise to work on this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.