Comments (13)
One thing should be an in-progress label.
from go-cloud.
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.
from go-cloud.
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.
from go-cloud.
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".
from go-cloud.
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.
from go-cloud.
"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."
from go-cloud.
What I'm thinking the decision set for triage is the following:
- Close issue (duplicate, WAI, nonsense)
- Move to a milestone (including Unplanned)
- Label as
needs info
. On next visit to this issue, repeat decision process.
from go-cloud.
Spoke offline.
Keep dupe. Rename to needs info
. Unplanned milestone as previously documented.
from go-cloud.
We should likely document this in CONTRIBUTING.md or some other such doc in the repo.
from go-cloud.
from go-cloud.
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.
from go-cloud.
I would add one more action in that case:
- Assign to another team member for triage, adding an explicit comment that is what they are seeking.
from go-cloud.
I think we have a good idea about what to do for now, we can also fiddle with things later.
from go-cloud.
Related Issues (20)
- blob/gcsblob: anonymous bucket access follow up to #3302 HOT 1
- runtimevar: support `env` url HOT 2
- blob/azureblob: Using a SAS token results in "Signature fields not well formed" HOT 3
- Using AWS, how do we enable compression and decompression of upload and dwonload? HOT 5
- blob/s3: Support Server Side encryption settings in bucket url HOT 2
- docstore/mongodocstore: pauses before getMore HOT 3
- docstore/gcpfirestore: ought to support non-default databases HOT 4
- S3 Blob Incompatibility with AWS S3 Issues? HOT 3
- docstore: should support (in) comparison operator HOT 3
- pubsub: support NATS jetstream HOT 1
- pubsub/awssnssqs: duplicate key in map literal HOT 3
- blob/s3: Add content length parameter in signing URL HOT 3
- pubsub/azuresb: support workload identity auth method HOT 3
- secrets/hashivault: read token from file HOT 3
- pubsub/azuresb: sending a message when unauthorized hangs HOT 1
- New Project: Docstore Query Gen for Go CDK HOT 1
- RabbitPubSub Queue Connection Closes Unexpectedly with FailedPrecondition Error HOT 2
- all: Request for new tag including 'Offset' feature in docstore HOT 1
- docstore/mongodocstore: Error update with only unset or increment modifier (recurring issue)
- pubsub/ AWS MSK Support HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-cloud.