github: Make sure that the labels/issue tracker workflow is optimal about go-cloud

[cflewis]

One thing should be an in-progress label.

[cflewis]

OK, I've set up a series of labels.

backlog: Things that we've triaged but found we have no time right now.
bug/cleanup/dupe/enhancement: obvious.
in progress: label you can use to note that you're actively working on it, if that's helpful
needs discussion: label for more discussion or clarifications are required.

As issues come in, those that are untriaged have no label and no milestone. We can search for those using is:issue is:open no:label no:milestone. I suggest we look over them every sprint plan to get them out of the needing triage queue.

Triaged issues have labels or milestones, ideally both.

Assigning to @shantuo and @zombiezen for discussion.

[cflewis]

I modified cleanup -> code health, so it makes it more clear testing is past of that label.

We should also maybe put "needs discussion" into our triage review.

[zombiezen]

SGTM in general. One nit: instead of a "backlog" label, we could follow the overall Go project's lead and use an "Unplanned" milestone. That way, we can see any untriaged issue just by looking at ones that don't have a milestone attached.

I'm less sure about "needs discussion" as a label. This sounds more like an issue of "assign to person to make decision or provide input". I can imagine something like "requires more info" as a label to mean "can't complete triage without more information from reporter".

[cflewis]

backlog -> Unplanned is fine with me.

requires more info and needs discussion I don't see any difference apart from wording, but needs discussion is slightly shorter 😄 If you feel strongly I'll change the name.

[zombiezen]

"Discussion" implies presenting arguments, whereas "info" implies presenting data. The latter is what I think would be needed from a workflow standpoint. needs info would work, with a description to the effect of "More information needed from the reporter before the issue can be triaged."

[zombiezen]

What I'm thinking the decision set for triage is the following:

1. Close issue (duplicate, WAI, nonsense)
2. Move to a milestone (including Unplanned)
3. Label as needs info. On next visit to this issue, repeat decision process.

[cflewis]

Spoke offline.

Keep dupe. Rename to needs info. Unplanned milestone as previously documented.

[zombiezen]

We should likely document this in CONTRIBUTING.md or some other such doc in the repo.

[cflewis]

Good plan. I'll wait for @shantuo 's signoff then I'll do it.

…

On Fri, May 25, 2018 at 10:28 AM Ross Light ***@***.***> wrote: We should likely document this in CONTRIBUTING.md or some other such doc in the repo. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACqvDgr1e5CfgE_e3_JaxNQZFu9ooqOks5t2D9VgaJpZM4UMx64> .

[shantuo]

SGTM, with one question:

needs info is requesting from the reporter. I wonder if we would want a needs decision? The reason is that some issue relates to developer experience which are not straightforward. We sometimes need to consult devrel and pm to make the decision and I don't see any of the current label covers this case.

[zombiezen]

I would add one more action in that case:

4. Assign to another team member for triage, adding an explicit comment that is what they are seeking.

[cflewis]

I think we have a good idea about what to do for now, we can also fiddle with things later.