Skip to content

docs: Update slack issue-feed channel for triaging docs #12618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2024
Merged

docs: Update slack issue-feed channel for triaging docs #12618

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/triaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,8 @@ future.

There are a few different ways to triage issues:

1. You can look at the `#feed-web-sdk` channel in Slack. This channel will automatically receive a message every day in
the morning with issues that require triaging.
1. You can look at the `#feed-web-frontend` channel in Slack. This channel will automatically receive a message every
day in the morning with issues that require triaging.
2. You can look at the triage view in the GitHub Project Board: https://github.com/orgs/getsentry/projects/31/views/29
3. (Also for external contributors) You can filter by `Waiting for: Product Owner` label:
https://github.com/getsentry/sentry-javascript/issues?q=is%3Aopen+is%3Aissue+label%3A%22Waiting+for%3A+Product+Owner%22
Expand All @@ -37,8 +37,8 @@ If a user replies to an issue, leading to the label being re-applied, but no res
may also remove the label manually, which will also remove it from the triage list.

Working through the triage queue should have the highest priority of tasks. Especially issues that are reaching the top
of the triage queue (which is indicated in the `#feed-web-sdk` channel through a remaining time to triage) should be
prioritised. **This does not mean that you need to fix the issue immediately,** but that you should investigate and
of the triage queue (which is indicated in the `#feed-web-frontend` channel through a remaining time to triage) should
be prioritised. **This does not mean that you need to fix the issue immediately,** but that you should investigate and
categorize the issue as soon as possible. If an issue is hard to fix, an edge case, or otherwise unclear, feel free to
reply and put the issue in backlog. You may also encourage the user to contribute a PR themselves if we are unlikely to
find time to resolve the issue ourselves anytime soon.
Expand Down