Yarn: APRIL 28 ISSUES TRIAGE SESSION

Created on 26 Apr 2017  路  10Comments  路  Source: yarnpkg/yarn

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)

needs-discussion

Most helpful comment

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

  2. Triaged at least 112 open issues
    screen shot 2017-04-28 at 8 34 45 pm

Great job everyone!

All 10 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
@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

Good example how to use me-as-a-service https://github.com/yarnpkg/yarn/issues/3249#issuecomment-298015831

I claim issues #153 - #499

I take #781 - #510

claiming #958 - #1060

claiming #1073 - #1291

claiming #2987 - #3044

2986-#2804

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

  2. Triaged at least 112 open issues
    screen shot 2017-04-28 at 8 34 45 pm

Great job everyone!

Was this page helpful?
0 / 5 - 0 ratings