@smallcircles That's a great point! We definitely want to balance organization benefits with maintainer overhead. The goal is to make our workflow smoother, not more complex. We'll keep the system simple and only add labels that genuinely help contributors find relevant issues. Thanks for the perspective!

@fedify it is a very clean set in principle. You may gradually introduce as your workflow evolves. Some labels are a best match in combination with a kanban board, for instance.

But you must *want to* work like that. Countless github repo's have abandoned kanban's sitting in them.

PS. There are a number of recommended label sets out there (but: own workflow is what matters), like: https://seantrane.com/posts/logical-colorful-github-labels-18230/

One is a label best-practice website, but I cannot find it atm.