When do issues go to the 'New' colum in a particular dashboard sig ?

thoth-station / core

Using Artificial Intelligence to analyse and recommend Software Stacks for Artificial Intelligence applications.

https://thoth-station.github.io/

GNU General Public License v3.0

28 stars 25 forks source link

When do issues go to the 'New' colum in a particular dashboard sig ? #431

Closed VannTen closed 1 year ago

VannTen commented 1 year ago

Problem statement

As a (new !) Thoth developer, I don't quite get the part of the Scrum process where we choose (in sig meetings) which issues to discuss and estimate. Is is everything in the 'New' column of the dashboard of the SIG ? (In that case, when do we add to the new column ? Should I just add an issue to a Sig dashboard when doing /sig ?

High-level Goals

[ ] Document the issue life cycle from creating the issue to putting it in a SIG dashboard.

Proposal description

The 'Issue life cycle' section in TermsAndConditionsForTheScrum could be enriched just a tiny bit.

Additional context

The answer is probably obvious. ^ Well, in that case the next person won't need to ask :).

/kind documentation

goern commented 1 year ago

'new' is used for all the good ideas that are just 'a one-liner', things that are unrefined or could be done, or nice to have... this is similar to 'stakeholder backlog' of https://github.com/orgs/open-services-group/projects/21

after refining the issue/card, it should move to (product) backlog, and adhere to certain quality criteria described in the T&C document.

@schwesig @codificat

goern commented 1 year ago

@VannTen does that answer your question?

goern commented 1 year ago

/sig user-experience /priority critical-urgent /triage accepted

VannTen commented 1 year ago

Yes. I intended to close the issue with #435, that's a leftover. Thanks !

/close

sesheta commented 1 year ago

@VannTen: Closing this issue.

In response to [this](https://github.com/thoth-station/core/issues/431#issuecomment-1209427120): > >Yes. >I intended to close the issue with #435, that's a leftover. >Thanks ! > >/close > > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

VannTen commented 1 year ago

'new' is used for all the good ideas that are just 'a one-liner', things that are unrefined or could be done, or nice to have... this is similar to 'stakeholder backlog' of https://github.com/orgs/open-services-group/projects/21 So basically, every single opened issue should be put in a new column of one SIG, right ? Could we say this maps to the needs-triage label ?

after refining the issue/card, it should move to (product) backlog, and adhere to certain quality criteria described in the T&C document. That part was clear.