See URL with paste of IRC log. No point writing all that again, so read the log.
Leah, with all due respect, you can't have your cake and eat it too.
On the one hand, you're asking for highly skilled people to merge non-trivial patches relating to board ports (patches that I struggle to understand, despite experience with kernel and firmware development.)
On the other hand, you're saying that the barrier of entry is low, and you're then asking, "why is nobody joining us?"
The answer is twofold. For starters, the barrier of entry is indeed lower than perceived by the world, but it is much higher than perceived by you, since you've been doing it for years (Dunning-Kruger).
The other part is that every FLO project ever has had this problem. Unfortunately, chronic understaffing is largely universal among volunteer-driven projects, and it's quite common among commercial projects, too. The pools of "people who have the skills to work on low-level parts of Libreboot" and "people who are interested in helping Libreboot" are both incredibly small. True, there are probably people in the intersection who have not yet contributed. Maybe they're lurking on IRC. Maybe they even tested the waters and sent a PR. They're coming.
Everything in communications has an associated cost. Blowing up the message "Libreboot is understaffed" all over Reddit is not going to help people come. It'll backfire. In the best case scenario, we're ignored because water is wet -- name one project out there that is 1) non-trivial 2) fully staffed 3) not meddled by corporate or governmental special interests.
You are right. We do need more developers. But the solution isn't to send out a call-to-action or pretend the project is something it's not. It's to provide good documentation for developers and a warm working environment so developers will be inclined to contribute and keep contributing.
There aren't any "major organization issues that urgently need fixed". It's SNAFU.
I'll respond properly later but:
This is how we need to think, while working as hard as we can to do as I propose.
We can kick up a big fuss, and maybe get 1 or 2 extra developers if that. I'm not expecting to suddenly get an influx of devs.
For all that effort, getting an extra dev or 2 will make it all worthwhile.
What you're saying will be tested, after I implement what I have in mind.
My next response will be a pull request.
I believe that the immediate concerns were resolved (if not the long-term issues which will never be solved in any project, ever). Closing.