You run npm install daily but never think about the humans behind them. Should that change?
Here's a hard truth nobody wants to say out loud:
The open-source community you talk about on LinkedIn? It's mostly extractive now.
We all stand on the shoulders of giants. Every project you ship, every startup you build ... it's built on packages and tools that real people poured their nights and weekends into. For free.
But here's what keeps me up: how many of those maintainers do you actually KNOW?
Not their GitHub handle. Not their README. I mean their story. Their face. The late nights debugging edge cases nobody thanked them for. The coworkers who told them to get a "real job."
We built an industry on generosity and normalized never saying thank you.
Somewhere in your node_modules right now, there's a solo dev in a small apartment keeping a library alive that your production app depends on. They haven't been paid in months. Nobody's looking at their issues.
And you shipped on Friday and called it a win.
That uncomfortable feeling? That should mean something.
FOSSY is my attempt to fix this ... to make the invisible visible, to connect the people building the tools with the people using them as humans, not users.
But I can't do it alone. I don't want FOSSY to be another directory that just lists repos.
So here's my real question:
What should ABSOLUTELY be in FOSSY that no other FOSS directory has?
What would make you visit every week? What would make you stop treating open-source like a vending machine and start treating it like a community?
Don't let me build something hollow. Tell me what would make this matter.
What does FOSSY need to be, for real?

Replies