-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
APRIL 28 ISSUES TRIAGE SESSION #3258
Comments
I don't have permission to close/edit issues, but where I have some input I'll try to leave a comment for a member to act accordingly. See #3261 for example; I left a comment with a duplicate issue. 👍 |
Ok, GitHub is not really great at permissions granularity and so this is what we can do this time. Mention me in a comment and I'll do the trick, e.g. @bestander label bug, bug-resolution We want to categorize issues by the phase of Yarn installation, increase visibility of high priority issues and increase visibility of good issues for beginners. Also we want to close duplicates and incentivize the community members to provide steps to reproduce issues. |
Good example how to use me-as-a-service #3249 (comment) |
We'll use this task to coordinate triage session this Friday (28.04.2017).
15:30 BST - 17:30 BST
07:30 PT - 09:30 PT
10:30 EDT - 12:30 EDT
We need to add some order to the issues and are going to do our first group triage session.
Goals:
What we are planning to do:
Below I'll post a few templates that we can use to keep the tone positive.
We can use this issue for coordination, I'll be moderating it to remove outdated comments.
Also we can coordinate in the chat https://discordapp.com/invite/yarnpkg (does not require registration)
The text was updated successfully, but these errors were encountered: