search

notofonts / notobuilder

Python module for building Noto fonts
9 stars 0 forks source link

How to classify/prioritize Noto bugs? #3

Open davelab6 opened 3 years ago

davelab6 commented 3 years ago

Somewhat related to notofonts/notobuilder#2, how might we classify and prioritize the bugs we have coming in for all Noto projects, starting with those in this repo? :)

marekjez86 commented 3 years ago

@davelab6 : There's an existing process using one or more of the 239 Labels which can be found in https://github.com/googlefonts/noto-fonts/labels ... A test to check if we have all the labels that we need: What Label(s) would you assign this issue?

moyogo commented 3 years ago

We currently use 166 labels out of the 239 in open issues, and 197 labels in total with open and closed issues. Maybe we can have a look at the labels that are not used and remove a few.

The Script-*, Platform-*, Status-*, Priority-* labels are pretty well organized at the moment. Some of the others labels are not that clear.

I'm not sure if we have duplicates that serve the same function.

Generally, we may need to go through each issue and see if they need those labels.

Here are couple of ideas:

  1. We could add a series of difficulty labels, for example Difficulty-High, Difficulty-Medium, Difficulty-Low, I think there are a few issues that are low hanging fruit while others needs minor or major redesign. That would help looking at Priority-Critical, Priority-High that can be fixed easily.

  2. Another series of labels that is currently useful is the Type-Defect, Type-Enhancement, Type-Task for the type of fix needed. Maybe we should be more specific with Type-Defect-Features and Type-Defect-Glyphs (which wrong glyph(s) covers at the moment).

Otherwise, we can do a bit of normalization of labels. For example Android could be renamed Platform-Android to match the set Platform-Linux, Platform-MacOS, Platform-Windows. There's also FireFox-issue and Safari-Issue.