Ask HN: How do we coordinate open source initiatives?
Problem: This place we live is messed up. Most of our resources are committed to driving profits and that's a bad metric for things like climate, governance, education, etc. One can commit financial resources to charities and institutions to try and help this situation, but it's difficult to have this make a good material difference for a lot of reasons.
Solution: I have a set of skills that can create tangible, immediate value in the form of usable software that fixes problems for people.
New Problem: Building consumer-usable software requires a diverse skillset. I don't have all the skills necessary to create secure, cross-os-compatible, easy-to-use software. Engaging in such an endeavor requires the coordination of many individuals, which is typically done by using money, which I don't have enough of to run a startup (and I don't think the profit-driven model is capable of solving these problems in the long run anyway, so investors are right out).
I've seen plenty of instances where this happens kind of naturally - you build a tiny version of the thing you want to see and make it minimally viable and over time, other folks using it add features and work. But there are some problems that can't be bootstrapped this way - for example, I would love to see OSS attempts at solving local LLM development (which you can't start small).
What does HN know about coordinating efforts to build software "for the common good, and for the love of software"?