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

APRIL 28 ISSUES TRIAGE SESSION #3258

Closed
bestander opened this issue Apr 26, 2017 · 10 comments
Closed

APRIL 28 ISSUES TRIAGE SESSION #3258

bestander opened this issue Apr 26, 2017 · 10 comments

Comments

@bestander
Copy link
Member

bestander commented Apr 26, 2017

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:

  • 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)

@rally25rs
Copy link
Contributor

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. 👍

@bestander
Copy link
Member Author

bestander commented Apr 28, 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

@bestander
Copy link
Member Author

Good example how to use me-as-a-service #3249 (comment)

@bestander
Copy link
Member Author

I claim issues #153 - #499

@arcanis
Copy link
Member

arcanis commented Apr 28, 2017

I take #781 - #510

@bestander
Copy link
Member Author

claiming #958 - #1060

@torifat
Copy link
Member

torifat commented Apr 28, 2017

claiming #1073 - #1291

@bestander
Copy link
Member Author

claiming #2987 - #3044

@arcanis
Copy link
Member

arcanis commented Apr 28, 2017

#2986-#2804

@bestander
Copy link
Member Author

I'll close the task as the triage session is finished.
But if anyone wants to continue, just keep tagging me to close or tag the issues.

Results:

  1. Closed 88 issues
    Open Issues before:

screen shot 2017-04-28 at 3 53 48 pm

Open Issues after:

screen shot 2017-04-28 at 8 33 20 pm

  1. Triaged at least 112 open issues

screen shot 2017-04-28 at 8 34 45 pm

Great job everyone!

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

5 participants