@RyunoKi Many people have already mentioned that the community around a project is a major factor. So some ideas (a bit hard to implement but still): there could be a filter "by types of contributions needed" (requires tracking which projects have i.e. open issues with labels "for begginers", "first contribution" etc), which ones have translation platforms (my first contribution ever was translating diaspora* strings).
@RyunoKi Maybe also Fedi projects can submit to you themselves what they need via a form or an issue to your repo. Some need frontend help like Friendica, others - community development, text, documentation, security audits, design contributions, etc.
I want fedi.builders to be a view on fedi projects. It's better to channel ideas into delightful lists or similar.
My vision is something like https://whatcanidoformozilla.com but for Fediverse.
So I'm stumbling into this direction.
Right now, I am waiting for a PR to be merged that will clean up some erroneous formatting.
I was thinking about it.
If it won't be part of that delightful list I'm consuming here, I could query GitHub (which hasn't been given up on by most projects yet) for additional information.
However, this being a static build I'd need to have a cronjob to have somewhat up-to-date information.
Client-side queries would result in rate limits, I suppose.
Might be an idea to build shields.io badges 🤔
Especially soft criteria like culture are hard to determine programmatically.
I could look for presence of certain files like CONTRIBUTE.md.
But mentoring etc is next to impossible if not done manually.
@RyunoKi Yes, my idea is hard to automate. Alas, many things in Fedi need manual labour. Even delightful lists are curated manually ;) I think a Fedi board where Fedi maintainers can post about their current needs (logo, translations, text, code contributions) is a nice thing to have. Focused calls for help would be appealing to those who might want to help but hesitate where to start. Can be published via Fedi, using special tag, then aggregated same way as search.flockingbird.social does.
> Even delightful lists are curated manually
I have this long-standing idea to essentially reverse the burden of manual aggregation and only have a Review workflow. A Push rather than Pull Publish/Subscribe like process.
Mentioned the idea in many places, but will transfer to Social Coding forum. It lends itself for federation and has numerous use cases.
This is one of the places: https://socialhub.activitypub.rocks/t/federating-the-murmurations-protocol/1701
(Note: Murmurations only demonstrates the concept)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!