In open source, we celebrate the visible things. New contributors joining. First pull requests. Community growth. Another release shipped. Those things are easy to measure, easy to share, and easy to feel good about.
What is much harder to see is the silence left behind when someone quietly disappears. No goodbye post. No dramatic exit. Just someone who used to be around every week suddenly no longer there.
And too often, nobody notices. Or worse, people notice and assume someone else will reach out.
The Story We Tell Ourselves
Most communities tell themselves the same comforting story. People get busy. Life changes. Priorities shift. And sometimes that is absolutely true. But not always.
Sometimes people leave because they are exhausted. Sometimes they are frustrated. Sometimes they feel ignored, unheard, or worn down by constant conflict. Sometimes something difficult is happening in their personal life that has nothing at all to do with the project. And sometimes they simply drift away because nobody made them feel they would be missed if they did.
The important thing is not to assume we know the reason. Because when we stop asking questions, we stop seeing people as people and start seeing them only through the work they produce.
This Is Not a Leadership Problem
It is easy to place all responsibility on leadership. Leaders do carry responsibility, especially in understanding the health of a community beyond spreadsheets, release schedules, and contribution metrics.But this cannot only be the job of leaders.
Communities are not companies. They are networks of relationships.If someone you used to work with disappears, you do not need permission from a team lead or a board member to ask how they are doing. You do not need a policy document before sending a message that says: "I haven’t seen you around lately. I hope you’re okay."
That responsibility belongs to all of us.Because the truth is simple: people are far more likely to stay connected to a community when they believe somebody would notice if they vanished.
We Notice Activity More Than Absence
Open source projects are very good at measuring output. Commits. Issues closed. Meetings attended. Pull requests merged. But communities are not healthy simply because activity exists.
A person can slowly burn out in full view of everyone while still appearing productive. Another can quietly disappear and leave almost no trace at all because the systems we build are designed to track contributions, not contributors.
That is not usually caused by cruelty. Most of the time it happens because everyone is busy. Volunteers are balancing jobs, families, health, and life outside the project.
But good intentions do not change the outcome. If nobody notices when people disappear, then eventually people begin to feel worthless.
And once people start feeling worthless, communities slowly lose the human connection that made them communities in the first place.
The Kindest Thing Is Simply Asking
Not every disappearing volunteer wants to come back. Not everyone wants to explain what happened. And that is okay.
Reaching out is not about demanding answers or convincing someone to return. It is about reminding them that their value was never limited to the work they produced. A simple message can matter more than people realise.
Not because it solves burnout or fixes structural problems overnight, but because it shows care. It tells someone they were seen. For people going through difficult moments in their personal lives, that small act of kindness can mean far more than we ever know.
Silence Creates Blind Spots
When communities never check in on the people who disappear, they lose more than volunteers. They lose understanding.
Patterns of burnout remain invisible. Bad practices continue unchecked. People who felt excluded or discouraged leave quietly, and the community convinces itself everything is fine because the work still gets done.
Over time, that creates a culture where replacing people becomes normal, but caring for them does not. That is not sustainable. And it is not healthy.
Community Means More Than Collaboration
Open source projects like Joomla describe themselves as communities, but that word should mean something beyond shared tasks and common goals.
A real community notices absence. Not in a controlling or invasive way, but in a human way.
It understands that volunteers are not resources to consume until they burn out. They are people giving their time, energy, knowledge, and emotional investment to something they care about.
The least we can do is care back.
So What Should Change?
Not everything needs to become a formal process. This is not about creating welfare committees, mandatory check-ins, or new layers of bureaucracy.
- It is about culture.
- It is about normalising the idea that everyone shares responsibility for looking out for one another.
- If someone disappears and you knew them, send the message.
- If someone seems quieter than usual, ask how they are.
- If a former contributor crosses your mind, let them know they are remembered.
Not because you expect anything in return. Just because communities should not only celebrate people when they are productive. They should also care about them when they are absent.
That small shift in mindset could make a bigger difference than any new feature or governance reform ever will.
