Skip to content
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.

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

Add more notes on triage #17550

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Add more notes on triage #17550

merged 1 commit into from
Dec 19, 2024

Conversation

seanbudd
Copy link
Member

Summary of the issue:

To improve objectivity in the triage process, community members are discouraged from self-triaging their own issues. As employees, we generally do not triage our own issues either.

To prevent interfering in NV Access's workflow, clarifications around closing tickets need to be improved.
Tickets which are pending a response from NV Access should not be closed, to help ensure a response is given.

@seanbudd seanbudd requested review from a team as code owners December 19, 2024 02:12
Copy link
Member

@SaschaCowley SaschaCowley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reads well, thanks @seanbudd

@SaschaCowley SaschaCowley merged commit e2eaab6 into master Dec 19, 2024
5 checks passed
@SaschaCowley SaschaCowley deleted the moreTriageNotes branch December 19, 2024 06:12
@github-actions github-actions bot added this to the 2025.1 milestone Dec 19, 2024
@CyrilleB79
Copy link
Collaborator

Recently, you have asked to avoid closing issues that are on milestone (#3208 (comment)). Finally this request does not appear in general triage rules. Has this criterion been finally withdrawn? Or is it an oversight?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants