-
Notifications
You must be signed in to change notification settings - Fork 5
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
Request to publish SIG Issue Triage Guide #15
Comments
This feels like something that should be part of the community repro. All other SIGs can then reference it as required. As there was no public guide, we ended up writing our own. See:
Would be good to get these aligned with the common guide. |
Next Steps
|
@lmbr-pip submitted a PR to publish the guide to o3de/community: o3de/community#146 (review) He will message the SIGs to advertise the guide, and will close this issue. |
Delivered to community repro, this can be closed out. |
I'd like to publish the below SIG Issue Triage Guide, which outlines and standardizes the process SIGs should use to triage GitHub issues into their backlogs. This guide was initially published internally at Amazon with an open source perspective, and all SIGs are currently following the process outlined. I'd like to move this guide to an accessible location for all contributors to follow.
SIG Issue Triage Guide.pdf
The text was updated successfully, but these errors were encountered: