Open ronniegeraghty opened 1 month ago
Assigning this to @JimSuplizio since he'll do this work, but it's important that @jsquire provide input and @ronniegeraghty should probably run this change past all the language leads as well.
Well, this opens up the question: If we're going to go through all of this, can we PLEASE stop doing a 2-label system? The whole pink+yellow classification is difficult to work with and causes issues. I think everyone (especially @joshfree ) would love to see us adopt a consistent format with a single label.
For example, something like:
area-service-bus
area-service-bus-mgmt
would be better than
service: Service Bus
+ plane: Data
service: Service Bus
+ plane: Mgmt
and can we stop treating color as significant?
Also, @ronniegeraghty - be aware that this overhaul will invalidate all the ML models for the AI service. If we just rename in place, I can retrain and we won't lose confidence. If we make the more wholistic change that I'm advocating for, we'll end up needing to do some scripting to fix up the old issues so that we can retrain.
Attempting to bridge the problem by adding a prefix to the label description so people can search the description prefix.
I've assigned this to both @ronniegeraghty and myself because, if this ends up getting done, the work won't be just on my plate.
Add prefixes to issues labels related to their type.
Examples:
issue-addressed
->workflow: issue-addressed
Mgmt
->Plane: Mgmt
Service Bus
->Service: Service Bus
Concerns:
Proper Syntax:
Updating GitHub Action rules: