[Meta] Labels for enhancement categories

[DNin01]

It can sometimes be useful to see what kind of enhancement certain issues are making.

We can add labels to help separate issues into categories of changes:

• category: accessibility (Addresses an accessibility issue)
• category: feature (A new feature or improvement to a feature)
• category: ux (An improvement to the user experience)
  etc.

This discussion will be used to talk about how we should go about adding these category labels, if this is something we're all interested in. It might even help us better prioritize issues that need attention based on what kinds of changes they make.

[Hans5958]

Why not doing it on scope:?

[mxmou]

We already have scope: design, so I think it would make sense to add scope: accessibility.

[DNin01]

We already have scope: design, so I think it would make sense to add scope: accessibility.

Alright, then! I've gone ahead and did that.

[WorldLanguages]

Just created a scope: performance label too.

[DNin01]

I went ahead and made a scope: user experience label as well.

[WorldLanguages]

@DNin01 Nice one. I have thought of that one multiple times but never actually created it.

[DNin01]

A type: checklist label could also be helpful, maybe?

[Hans5958]

A more usual word would be a "megathread". But that works too.

[DNin01]

I think status: needs discussion might be useful too. We could, for example, use it in PRs without issues.

[Samq64]

why not? There are already a bunch of PRs that are stalled because of that, even ones with linked issues.

[DNin01]

Done!

[DNin01]

Would having a label for string changes be a good idea?

How would we describe strings to someone who doesn't know, by the way?

[WorldLanguages]

No idea

[DNin01]

Some sort of "response to update" label might help us separate issues that have to do with Scratch updates, too.

[WorldLanguages]

Yeah, but good luck finding a way to name this label 🤔

[Hans5958]

You can do scope: upstream. Upstream here refers to something related to what we depend, such as Scratch itself, browser bugs that we can't do anything (looking at you, Apple), and something related to our libraries. This includes anything regarding to Manifest v3.

[DNin01]

Done!

[DNin01]

What do you think of a slightly brightened color for the scope: addon Related to one or multiple addons and scope: addon.json About the addon.json file structure labels?
#f26ad0 → #fd76d8?

Might help with text contrast in light mode?

[DNin01]

I've finally went ahead and updated it.

[DNin01]

And maybe we should change the color of status: invalid Issue or PR is invalid from #b60205 to #cfd3d7 or a less distracting shade of red? Invalid issues aren't really supposed to be eye candy.

[BroJac5246]

And maybe we should change the color of status: invalid Issue or PR is invalid from #b60205 to #cfd3d7 or a less distracting shade of red? Invalid issues aren't really supposed to be eye candy.

Maybe it should be a less distracting shade, but red definitely feels like the right color.

[DNin01]

What do you think about a DevEx (developer experience) label? Would it be useful? We have scope: documentation Related to docs located on the repository. Mind that Scratch Addons Docs is available on website-v2. and scope: meta Related to the meta of the development (repository, store, etc) but sometimes DevEx-related issues don't get those labels.

[WorldLanguages]

sure

[DNin01]

Or maybe it can be a generalized "scope: development" label for everything related to how we develop, likely mostly comprising of DevEx stuff.

[DNin01]

scope: development Related to developing, documentation, DevEx, etc.

[DNin01]

Just created a platform: mobile Related to compatibility with touch screen devices label.

[DNin01]

I have changed the color of the scope: from turbowarp Things to import from TurboWarp label from #c5def5 to #ff4c4c.

[Samq64]

Yeah I know I was joking about the other labels

[mxmou]

Firefox could have a gradient if GitHub supported that.

[WorldLanguages]

lol

[WorldLanguages]

Worth considering: a label specifically for CSS/layout issues (we have scope: design but we rarely use it for CSS bugs in the Scratch editor addons and so on)

[DNin01]

Worth considering: a label specifically for CSS/layout issues (we have scope: design but we rarely use it for CSS bugs in the Scratch editor addons and so on)

Could be called "scope: style" or "scope: styling"?

[DNin01]

Clarified the Manifest V3 labels:

- mv3: breaking changes (Manifest v3 breaking changes)
- mv3: transition (Changes we'd need to make to keep us with manifest v3)
+ mv3: breaking changes (Forwards-incompatible changes that must be made to upgrade to Manifest V3)
+ mv3: transition (Forwards-compatible changes we can make anytime before the upgrade to Manifest V3)

[WorldLanguages]

Those labels are so old they kind of lost their meaning, but the change looks fine
A few years back I thought Google would be better at this

[Samq64]

I added scope: addon compatiblity Compatiblity issue between two or more addons for compatibility issues between multiple addons. Feel free to adjust it.

[DNin01]

Should we change the color of scope: addon.json About the addon.json file structure to something like mint green? Being pink currently, when trying to triage quickly, it can be easily mistaken for the scope: addon Related to one or multiple addons label.

[WorldLanguages]

Sure, change it

[DNin01]

Done.