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

JUNE 20 ISSUES TRIAGE SESSION #3676

Closed
bestander opened this issue Jun 20, 2017 · 8 comments
Closed

JUNE 20 ISSUES TRIAGE SESSION #3676

bestander opened this issue Jun 20, 2017 · 8 comments

Comments

@bestander
Copy link
Member

bestander commented Jun 20, 2017

We'll use this task to coordinate triage session this Tuesday (20.06.2017).
See our previous session #3258.

We need to add some order to the issues and are going to do our first group triage session.

Goals:

  • Reduce the number of duplicated issues by grouping them by category first
  • Close non actionable issues
  • Prioritize important issues over the rest

What we are planning to do:

  • categorize by issue type (bug, discussion)
  • categorize bugs by phase (configuration, resolution, fetching, linking, scripts)
  • label high priority issues
  • label issues good for beginners
  • close issues with no steps to reproduce them. Too many issues, too little time developers can spend on each, with no repro steps the issue will hang there for a long time

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)

@bestander
Copy link
Member Author

bestander commented Jun 20, 2017

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
@bestander duplicate #xxxx

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.

These are the tags we want to use
screen shot 2017-04-28 at 3 38 09 pm
screen shot 2017-04-28 at 3 37 22 pm

To claim a set of issues just run this search:
https://github.com/yarnpkg/yarn/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20-label%3Atriaged%20, pick a random page and write a comment a section of issues you are going to parse through.

@bestander
Copy link
Member Author

Inviting everyone new as well as our regulars: @rally25rs, @gsklee, @torifat, @BYK, @arcanis.
Anyone who has time to give issue some developer eyes and understand if it is a duplicate or requires repro steps please join.

I'll start morning PDT.

@rally25rs
Copy link
Contributor

Also if you hit any [bug-high-priority] bugs, consider adding them to the v1 project.

@rally25rs
Copy link
Contributor

I'll try to triage page 12. Not sure how much time I'll have today though...

@bestander
Copy link
Member Author

claiming #3612 - #3679

@bestander
Copy link
Member Author

claiming #3566 - #3670

@bestander
Copy link
Member Author

claiming #3488 - #3689

@bestander
Copy link
Member Author

Good results - no more untriaged issues in May - June.

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

No branches or pull requests

3 participants