You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently went through every open Issue and set its Type and labels by hand. The result is useful, but this should not become a recurring maintenance job.
I think the labels should mean:
help wanted: more contributors are welcome. It stays even when the Issue has an assignee.
good first issue: suitable as someone’s first Maka contribution. It does not have to be easy, and assignment does not remove it.
Assignee: the current primary owner. Other contributors can still coordinate and help.
This keeps suitability separate from availability. Contributors looking for unclaimed work can add no:assignee to their search.
For automation, I suggest starting small:
Set Bug, Feature, or Task directly from the Issue Form.
Use a normal GitHub Action to keep Type and the bug / enhancement labels consistent.
If we add AI triage later, let it suggest help wanted and good first issue with a short reason. A maintainer reviews the suggestion before it changes the Issue.
This would not add area labels, stale handling, automatic comments, assignment, or closure.
Questions:
Are these label meanings correct?
Should semantic labels always require review, at least initially?
Is Type and label synchronization enough for the first implementation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We recently went through every open Issue and set its Type and labels by hand. The result is useful, but this should not become a recurring maintenance job.
I think the labels should mean:
help wanted: more contributors are welcome. It stays even when the Issue has an assignee.good first issue: suitable as someone’s first Maka contribution. It does not have to be easy, and assignment does not remove it.This keeps suitability separate from availability. Contributors looking for unclaimed work can add
no:assigneeto their search.For automation, I suggest starting small:
bug/enhancementlabels consistent.help wantedandgood first issuewith a short reason. A maintainer reviews the suggestion before it changes the Issue.This would not add area labels, stale handling, automatic comments, assignment, or closure.
Questions:
Related: #2441, #4070, #4160.
Drafted with OpenAI Codex at the contributor’s direction and reviewed by the contributor of record.
All reactions