Pruning GitHub labels

[sptramer]

Hello all!

We have had some discussions in the SIG meetings about a need to prune down the GitHub labels for o3de.org, and wow, there are a lot. Some of them are for O3DE specifically, some of them are used by partner companies, some of them are used by other SIGs, and we need to go through and classify which of these labels:

• Should be removed!
• Should be kept, renamed, or re-described!
• Should be added! (We have probably missed something useful.)

Overall, there are 157 existing labels, which is far too many.

Here's the label list:

kind/bug	Categorizes issue or PR as related to a bug.	#ff5050
kind/enhancement	Enhancement to an existing feature	#edb219
good-first-issue	Issue ready for a new contributor according to the help wanted guidelines.	#00cc00
help-wanted	Issue that needs help from a contributor. Must meet help wanted guidelines.	#cc0000
documentation		#0075ca
do-not-merge/in-review	Do not merge this PR. It is still being reviewed.	#ff6666
kind/reference	Reference materials for users.	#edb219
feature/atom	This item is related to the ATOM and 3D rendering subsystems.	#107777
feature/editor	This item is related to the editor subsystem.	#107777
kind/tutorial	Request for an official tutorial to be maintained in the O3DE docs.	#edb219
feature/gems	Content relating to the Gem system of O3DE.	#107777
feature/build	Content relating to CMake or the overall build system of O3DE.	#107777
feature/azcore	This item is related to the AZ core engine support libraries.	#107777
platform/macos	Issues affecting content related to macOS as a host or target platform.	#d876e3
platform/ios	Issues affecting content related to iOS/iPadOS as a target platform.	#d876e3
platform/linux	Issues affecting content related to Linux as a host or target platform.	#d876e3
platform/android	Issues affecting content related to Android as a target platform.	#d876e3
deprecated	Documentation requirements for deprecation/removal of components or APIs.	#0D78DB
needs-triage	Indicates an issue or PR lacks a `triage/foo` label and requires one.	#ededed
kind/sample	Content primarily focused on code samples.	#edb219
feature/audio	This item is related to the audio subsystem.	#107777
feature/docs-cleanup		#107777
rfc-feature		#006B75
platform/windows	Issues and PRs related to the windows platform.	#d876e3
committee/code-of-conduct	Denotes an issue or PR intended to be handled by the code of conduct committee.	#00cc66
committee/product-security	Denotes an issue or PR intended to be handled by the product security committee.	#00cc66
do-not-merge/contains-merge-commits	Indicates a PR which contains merge commits.	#ff6666
do-not-merge/cherry-pick-not-approved	Indicates that a PR is not yet approved to merge into a release branch.	#ff6666
dependencies	Pull requests that update a dependency file	#0066ff
do-not-merge/hold	Indicates that a PR should not merge because someone has issued a /hold command.	#ff6666
committee/steering	Denotes an issue or PR intended to be handled by the steering committee.	#00cc66
do-not-merge/invalid-commit-message	Indicates that a PR should not merge because it has an invalid commit message.	#ff6666
do-not-merge/invalid-owners-file	Indicates that a PR should not merge because it has an invalid OWNERS file in it.	#ff6666
do-not-merge/needs-kind	Indicates a PR lacks a `kind/foo` label and requires one.	#ff6666
do-not-merge/needs-sig	Indicates a PR lacks a `sig/foo` label and requires one.	#ff6666
do-not-merge/work-in-progress	Indicates that a PR should not merge because it is a work in progress.	#ff6666
feature-need/awaiting-more-evidence	Feature: Unknown importance. Possibly useful but not yet enough evidence to actually get it done	#ff9900
feature-need/immediate	Feature: Immediate. Must be actively worked on as someone's top priority right now.	#ff6666
feature-need/important-longterm	Feature: Important over the long term but may not be staffed May need multiple releases to complete	#ff9900
feature-need/important-soon	Feature: Must be staffed / worked on either currently or very soon ideally in time for next release	#ff9900
feature/2d-renderer	This item is related to the 2D renderer subsystems.	#107777
feature/ai	This item is related to the AI feature.	#107777
feature/animation	This item is related to the EmotionFX animation subsystem.	#107777
feature/ar-vr	This item is related to AR or VR features.	#107777
feature/asset-pipeline	This item is related to the asset-pipeline subsystem.	#107777
feature/cloud-service	This item is related to the cloud services.	#107777
feature/installer	This item is related to the installer feature.	#107777
do-not-merge/blocked-paths	Indicates that a PR should not merge because it touches files in blocked paths.	#ff6666
feature/lyshine	This item is related to the UI (lyshine)  feature.	#107777
feature/networking	This item is related to the client or server network code.	#107777
feature/physics	This item is related to the physics subsystem.	#107777
feature/prefabs	This item is related to the prefab system	#107777
feature/project-manager	This item is related to the project manager feature.	#107777
feature/python-bindings	This item is related to the python bindings.	#107777
feature/scripting	This item is related to the scripting tools.	#107777
feature/systems	This item is related to the systems feature.	#107777
feature/sdk	This item is related to the O3DE as an SDK initiative.	#006B75
feature/tech-art	This ticket represents cross functional tasks assigned to technical art.	#006b75
feature/viewport	This item is related to the viewport	#107777
feature/vegetation	This item is related to the Vegetation feature	#107777
feature/terrain	This item is related to the Terrain feature	#107777
feature/website	This is an issue with the website, not the content	#107777
kind/cleanup	Categorizes issue or PR as related to cleaning up code process or technical debt.	#edb219
feature/whitebox	This item is related to the whitebox feature.	#107777
kind/deprecation	Categorizes issue or PR as related to a feature/enhancement marked for deprecation.	#edb219
kind/design	Categorizes issue or PR as related to design.	#edb219
feature/trackview	This item is related to the Trackview and cinematic feature.	#107777
kind/documentation	Categorizes issue or PR as related to documentation.	#edb219
kind/automation	Categorizes issue or PR as related to automation	#edb219
kind/feature	Categorizes issue or PR as related to a new feature.	#edb219
kind/regression	Categorizes issue or PR as related to a regression from a prior release.	#edb219
kind/install	Categorizes issue or PR as related to the installers.	#edb219
kind/research	Task aimed at producing a research outcome rather than documentation.	#edb219
kind/test	Categorizes issue or PR as related to an test.	#edb219
needs-kind	Indicates a PR lacks a `kind/foo` label and requires one.	#ededed
needs-priority	Indicates a PR lacks a `priority/foo` label and requires one.	#ededed
needs-rebase	Indicates a PR cannot be merged because it has merge conflicts with HEAD.	#ededed
needs-sig	Indicates an issue or PR lacks a `sig/foo` label and requires one.	#ededed
needs-ux	This ticket requires UX to work on the design before it can be implemented.	#516CCE
platform/all	Issues and PRs related to all platforms.	#d876e3
pr-ready-to-merge	Indicates that a PR is ready to be merged.	#cc9900
priority/minor	Lowest priority. Work that may be scheduled	#ffdd66
priority/critical	Critical priority. Must be actively worked on as someone's top priority right now.	#ff7B44
priority/blocker	Highest priority. Must be actively worked on right now as it is blocking other work.	#B60205
priority/major	Major priority. Work that should be handled after all blocking and critical work is done.	#ff9900
release-blocker	Denotes a PR that is blocking the release from proceeding	#ff5050
sig/content	Categorizes an issue or PR as relevant to SIG Content.	#ccccff
review-required	A PR which requires review before merge.	#ededed
RTE	(Temp) Denotes an issue related to the Rev the Engine program	#A144F8
release-note-action-required	Denotes a PR that introduces potentially breaking changes that require user action.	#0000ff
sig/build	Categorizes an issue or PR as relevant to SIG Build.	#ccccff
sig/core	Categorizes an issue or PR as relevant to SIG Core	#ccccff
sig/docs-community	Categorizes an issue or PR as relevant to SIG Docs-Community.	#ccccff
sig/graphics-audio	Categorizes an issue or PR as relevant to SIG graphics-audio.	#ccccff
sig/network	Categorizes an issue or PR as relevant to SIG Network.	#ccccff
sig/platform	Categorizes an issue or PR as relevant to SIG Platform.	#ccccff
sig/release	Categorizes an issue or PR as relevant to SIG Release.	#ccccff
sig/security	Categorizes an issue or PR as relevant to SIG Security.	#ccccff
sig/testing	Categorizes an issue or PR as relevant to SIG Testing.	#ccccff
size/S	Denotes a PR that changes 10-29 lines ignoring generated files.	#e6e600
sig/ui-ux	Categorizes an issue or PR as relevant to SIG UI-UX.	#ccccff
size/L	Denotes a PR that changes 100-499 lines ignoring generated files.	#b3b300
size/XS	Denotes a PR that changes 0-9 lines ignoring generated files.	#ffff4d
size/M	Denotes a PR that changes 30-99 lines ignoring generated files.	#cccc00
size/XL	Denotes a PR that changes 500-999 lines ignoring generated files.	#ffff00
status/active	Indicates that an issue or PR is actively being worked on by a contributor.	#33cccc
size/XXL	Denotes a PR that changes 1000+ lines ignoring generated files.	#ffff99
status/approved	Indicates a PR has been approved by an approver from all required OWNERS files.	#66ff33
status/backlog	Indicates this is not actively being worked on and is in the backlog.	#ff3300
status/blocked	Issues or PRs that are blocked by other issues or PRs.	#ff3300
status/invalid	Issues and PRs that are invalid.	#ff3300
status/frozen	Indicates that an issue or PR should not be auto-closed due to staleness.	#ff3300
status/duplicate	Issues and PRs that are duplicates of other issues or PRs.	#33ccff
status/discuss	Issues opened for discussions and feedbacks.	#b0b0b0
status/investigation	Requires investigation to validate the issue.	#D8078D
status/needs-ux-review	The UX SIG needs to approve the UI/UX design for this feature before it can be merged.	#17F733
status/rotten	Denotes an issue or PR that has aged beyond stale and will be auto-closed.	#ff3300
status/needs-testing	An issue or PR that is ready for testing verification.	#17F733
status/stale	Denotes an issue or PR has remained open with no activity for 30 days and has become stale.	#ff3300
triage/accepted	Indicates an issue or PR is ready to be actively worked on.	#66ff33
triage/declined	Indicates an issue is not accepted	#B60205
status/ux-approved	The UX SIG has approved the UI/UX design for this feature.	#17F733
status/wont-do	Indicates an issue that can not or will not be worked on	#b0b0b0
triage/needs-information	Indicates an issue needs more information in order to triage	#ff9900
status/not-reproducible	Indicates an issue can not be reproduced as described.	#b0b0b0
ui-ux/in-design	This ticket requires UX to work on the design before it can be implemented.	#516CCE
WF1	This is a temporary label that will be removed once data conversion is complete	#999999
WF10	WF8 This is a temporary label that will be removed once data conversion is complete	#999999
WF2	This is a temporary label that will be removed once data conversion is complete	#999999
WF3	This is a temporary label that will be removed once data conversion is complete	#999999
WF5	This is a temporary label that will be removed once data conversion is complete	#999999
WF4	This is a temporary label that will be removed once data conversion is complete	#999999
WF9	This is a temporary label that will be removed once data conversion is complete	#999999
WF7	This is a temporary label that will be removed once data conversion is complete	#999999
WF6	This is a temporary label that will be removed once data conversion is complete	#999999
WF8	This is a temporary label that will be removed once data conversion is complete	#999999
kind/website	Categorizes an issue or PR as related to the website itself.	#edb219
kind/blog	Categorizes the issue or PR as related to a blog post.	#edb219
kind/video	Categorizes an issue as related to a video submission.	#edb219
kind/edit	Categorizes issue or PR as relating to content edits only.	#edb219
status/needs-edit	An issue or PR that requires editing from a Copy Reviewer.	#17F733
kind/media	Issue or PR related to only media in the documentation.	#edb219
kind/onboarding	Categorizes issue or PR as related to onboarding ("day one") workflows	#edb219
status/tech-approved	Technical reviewers have approved this PR.	#17F733
kind/content-architecture	Categorizes issue as PR as related to the presented structure of documentation.	#edb219
kind/broken-link	Categorizes an issue or PR as related to broken links.	#edb219
kind/bluejay	Categorizes issue or PR as related to the Bluejay Design System.	#edb219
project/pg	Issues or PRs related to the Programmer's Guide project.	#d93f0b
triage/split	Tickets which were determined to need to be split in triage.	#c5def5
sig/operations	Categorizes an issue or PR as relevant to SIG operations	#ccccff
feature/tools-ui	This item is related to the Tools UI, design system, or O3DE branding	#107777
status/blocked-on-dev	Documentation work that is blocked (or possibly blocked) on dev.	#006b75
feature/graphics/lighting		#107777
feature/testing		#BA1CBB
kind/contributing		#9AA8BB
kind/foundation	Must be addressed by the Linux Foundation governing entities.	#bfdadc
sig/simulation		#ccccff

[ShaunaGordon]

I know this is old, but to continue the discussion, since this hasn't happened yet, here are some of my thoughts on this, as a newcomer who's had to tag a bunch of stuff.

To Remove

• WF# - they're marked for removal anyway, this one should be a given
• documentation - that's...kind of a given when it's the docs repo
• kind/contributing - there's no description, and just...what?
• project/pg - I think that might be defunct at this point?
• ui-ux/in-design, status/ux-approved - Design stuff is extremely rare, I think, and more relevant to the main project than to docs
• release-note-action-required - main repo specific
• status/investigation - this seems kind of redundant with needs-triage. I propose the two be combined and the act of triage is validation
• feature-need/* - I don't know that we really do much of anything that would use these, that priority doesn't already handle
• status/stale, status/rotten - these appear related to automation, which doesn't seem to be part of the docs ticket management. What does stale/rotten even mean in this context? If it's not documented and it's part of the engine, it needs added at some point. If it's no longer part of the engine, then the ticket could just be closed.
• RTE - is this relevant anymore?
• pr-ready-to-merge - if it's intended to be used on PRs, it seems a bit noisy. If it's intended for tickets, could we automate its application based on whether the related PR has passed all its pre-merge checks? If not, it seems a bit cumbersome to have in general
• dependencies - I feel like this could be merged with kind/website
• review-required - all PRs need reviewed before merging, and we have tags for the specific people that need to review it as well as the "request review" GH feature
• rfc-feature - I don't know that this one's relevant to docs stuff, really

To Keep

• feature/* - In this context, they would mean "docs related to this feature." This allows contributors to filter on the things they're most familiar with
• kind/foundation - this is legal/organizational stuff and should be kept for things like copyright, trademark, and other matters
• sig/* - These can help the SIG members filter on their purview, and could be wired up to call attention of those SIG members for a ticket
• kind/* (except ones called out elsewhere) - these provide meta information about the kind of work needed
• good-first-issue - should probably be obvious, these are ones that new contributors can use to dip their toes in
• do-not-merge/* - these are good for flagging PRs. Could they tie into the merge restrictions and mechanically block merging when on a PR?

Unknown

• could triage/* and status/* be merged? The venn diagram for these look like they'd have a lot of overlap