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.

Sign up for GitHub

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

Jump to bottom

Add mapping of area labels and the team assignment in a file #20082

Open
benoitf opened this issue Jul 6, 2021 · 3 comments
Open

Add mapping of area labels and the team assignment in a file #20082

benoitf opened this issue Jul 6, 2021 · 3 comments
Assignees
@l0rd
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@benoitf
Copy link
Contributor

benoitf commented Jul 6, 2021

Is your task related to a problem? Please describe.

Today, when doing triaging, some labels are applied and then there are some Red Hat teams handling these labels.

Labels there are outdated:
/~https://github.com/eclipse/che/wiki/Labels

so if we store it in the repository we can update CONTRIBUTING.md automatically (or the wiki) from this definition.

Describe the solution you'd like

Add labels with their description, including areas and the teams being assigned.

Also, rename teams by adding redhat prefix

Describe alternatives you've considered

Additional context
@benoitf benoitf added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jul 6, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jul 6, 2021
@mshaposhnik mshaposhnik added area/dev-experience severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 6, 2021
@tolusha
Copy link
Contributor

tolusha commented Jul 7, 2021

@benoitf
Does it mean that all issues will be updates with team label ?

@benoitf
Copy link
Contributor Author

benoitf commented Aug 2, 2021

@tolusha sorry, just seeing your comment now.

No, issues will stay like this it's just that it'll be possible to see the current mapping between areas and teams.
Team assignment is usually done only when a team is working on it. (because team may change the scope, someone else can take the issue before, etc)

@che-bot
Copy link
Contributor

che-bot commented Jan 29, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 29, 2022
@benoitf benoitf added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 29, 2022
@l0rd l0rd self-assigned this Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@l0rd l0rd

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@benoitf @l0rd @tolusha @mshaposhnik @che-bot