Fedify: an ActivityPub server framework @fedify@hollo.social
Public

We're planning to reorganize our labels to better reflect '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 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.

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...

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...

github.com ยท GitHub

0
1
1

If you have a fediverse account, you can quote this note from your own instance. Search https://hollo.social/@fedify/019714ca-8179-7ebe-8965-47a25c152d6f on your instance and quote it. (Note that quoting is not supported in Mastodon.)

3
0
0