You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of working on streamlining our issue triage and management process, the large number of unused labels is getting in the way. It will be easier to properly label issues without too many extraneous choices.
Proposal
The high level goals of the cleanup are:
Clean up extra Area: labels we don't use
Keep all component tags, these are valuable
Clean up priority and status, move from Pri 0-3 to Important/Urgent
Avoid various nice to have labels, labels should be important for working with and following up on issues
Some top level changes/suggestions:
Move from sending questions to stack overflow to use discussions in github
Remove Priority 0-3, replace with only high priority
From a workflow standpoint, we should focus on getting issues to "Status: Fix Proposed", "Status: Future Consider", or saying No to the change (for right now) and closing the issue.
We also should make better use of "Help Wanted" and "Good First Issue" labels
Labels to keep
Label
count
Comment
Area: Accessibility
175
Keeping the common areas
Area: Build System
34
Area: Documentation
58
Area: Packaging
4
Area: Performance
9
Area: Samples
1
Area: Testing
10
Area: Theming
21
Area: Typescript
4
Area: UI Builder
3
Area: Website
27
AutoMerge
Needed for bot
Community Contribution
This is for things that the community is doing
Component: *
Keep all of these
During snap
1
Keep for now
External
Fabric 5
Fabric 6
2
Fabric 7
9
Fluent UI react-northstar
90
Fluent UI reactf
265
Fluent UI v8
30
Good First Issue 🏆
4
Use this for simple issues good for new contributors
Help Wanted ✨
9
We need to use this more to tag issues that are ready for someone to pickup and fix
High Contrast
16
Issue Pinged
8
Needs: Actionable Feedback 🕵️♀️
1
Keeping the main "needs" labels
Needs: API Breaking Change
Change to just "Breaking Change"
Needs: Attention 👋
10
Needs: Author Feedback
Needs: Backlog review
301
Needs: Design 🎨
41
Needs: Discussion 🙋
93
Needs: Investigation
222
Needs: Project Propsoal
1
Needs: Triage 🔍
33
Package: azure-themes
2
Package: charting
53
Package: codemods
Package: dashboard
Package: date-time
14
Package: experiments
8
Package: file-type-icons
Package: fluent-theme
Package: keyboard-key
Package: mdl2-theme
Package: merge-styles
16
Package: migration
Package: react-hooks
Package: styling
2
Package: tslint-rules
1
Package: tsx-editor
3
Package: utilities
5
Partner Ask
1
PR: API Modified
7
Is this a bot thing?
PR: Possible Perf Regression 🐌
2
Pri: Important
Add this for important work that needs to get done
Pri: Urgent
Add this for urgent work that has a time component
Resolution: By Design
Resolution: Can't Repro
2
Resolution: Duplicate
Resolution: External
3
Resolution: Not An Issue
Resolution: Won't Fix
Screen-size: small-screen
1
Shield Examples
1
Status: Blocked
11
Status: Do Not Merge 🚫
4
Status: Fix Proposed
6
New label for issues with recomended fixes
Status: Fixed
7
Status: Future Consider
1
New label for issues we won't consider right now
Status: In PR
17
Status: No Recent Activity
1
Theme Designer
8
Rename -> Area: Theme Designer
Type: Bug 🐛
245
Type: Documentation
12
Type: Epic
13
Type: Feature
295
Type: Regression 🌩🌩
2
Type: RFC
3
v8 snap: needs cherry-pick
8
Keep for now
v8 snap: potential conflict
1
Keep for now
web-components
5
Labels to Remove
Label
count
Proposal
A11yUsable
4
Remove - Track accessibility in ADO mainly
Area: AMD Modules
Remove not used
Area: Animation
Remove not used
Area: Deprecation
Remove not used
Area: DevExp
5
Remove not used
Area: Fabric Bot
Remove not used
Area: Fluent
5
Remove not used
Area: Fonts
8
Remove not used
Area: Foundation
1
Remove not used
Area: Icons
24
Remove use Component: Icon
Area: Internationalization
Remove not used
Area: JS Styling
5
Remove not used
Area: Keros
Remove not used
Area: Narrator
51
Remove - Don't need to query on these issues
Area: NVDA
8
Remove - Don't need to query on these issues
Area: RTL
4
Remove
Area: Slots/Tokens Conversion
1
Remove
Area: SPFx / Rush-Stack
Remove
Area: SSR
4
Remove
Area: Strict Mode
Remove
Area: VoiceOver
6
Remove
AT: JAWS
2
Remove
Azure
6
Remove -> Partner Ask
Contribution Candidate
15
Change -> Help Wanted
dependencies
Remove
Needs: Behavior Breaking Change
1
Merge with API Breaking change -> "Breaking Change"
Needs details
Remove
Needs Dev Input
9
Remove
Needs: Prototyping
2
Remove
Platform: Chrome Android
5
Remove
Platform: Chrome
5
Remove
Platform: Firefox
1
Remove
Platform: IE11
4
Remove
Platform: Microsoft Edge
17
Remove
Platform: Safari
6
Remove
Priority 0: Blocking
Remove
Priority 1: ASAP
5
Remove
Priority 2: Normal
60
Remove
Priority 3: Fit and finish
23
Remove
Stack Overflow
2
Remove use Discussions update new issue template
Theme: Dark
2
Remove
Type: Cleanup
33
Remove
Type: Question ❔
22
Remove use discussions
v6
Remove
WCAG 2.1
7
Remove
Follow up
Update issue template to remove stack overflow mention
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Trying out posting an RFC in discussions let's see how this goes
Contributors: @paulgildea, @JustSlone
Review requested: @chrisdholt (web-components), @jurokapsiar (react-northstar)
Problem statement
As part of working on streamlining our issue triage and management process, the large number of unused labels is getting in the way. It will be easier to properly label issues without too many extraneous choices.
Proposal
The high level goals of the cleanup are:
Some top level changes/suggestions:
Labels to keep
Labels to Remove
Follow up
Beta Was this translation helpful? Give feedback.
All reactions