We're planning to reorganize our #GitHub labels to better reflect #Fedify's project structure! 🏷️

Currently using GitHub's default labels, but we want something more tailored to our needs—like component-specific labels (vocab, federation, actor, etc.), runtime tags (Deno/Node/Bun), and #ActivityPub compatibility tracking.

The proposal includes hierarchical labeling with categories like:

• type/ for bug, feature, documentation
• component/ for different parts of Fedify
• activitypub/ for interop issues with Mastodon, Misskey, etc.

We'd love your thoughts! What labels would be most helpful for contributors and maintainers?

Check out the full proposal: https://github.com/fedify-dev/fedify/issues/238.

#fedidev

@fedify I think most important that the labels are comfortable to the team(s) and the workflows they use.

While tags are neat to categorize they also incur maintainer overhead in applying them right. Plus instructing or enforcing others to use them appropriately. If it streamlines workflows, its all good.

They serve internal team more than external passer-by contributors. For instance Gitlab repo in terms of UX is one big cognitive overload to me, disencourages reader.

https://gitlab.com/groups/gitlab-org/-/epics/11247