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, documentationcomponent/for different parts of Fedifyactivitypub/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.
github.com
Reorganize repository labels to better fit Fedify project structure · Issue #238 · fedify-dev/fedify
Problem Currently, the Fedify repository uses GitHub's default labels, which don't reflect the specific needs and structure of the Fedify project. These generic labels make it difficult to: Categor...