2026-04-24
The Drupal Slack black hole
So much valuable Drupal knowledge is being shared every day in Slack and disappearing just as fast. That concerns me.
Something has been bothering me for a while.
The Drupal Slack is incredibly active. The #drupal-ai channel, the core channels, the AI learners space. Every day, experienced people share insights, answer difficult questions, solve real problems. It's genuinely valuable.
And then it's gone.
Messages scroll away. Even when it's still there, it's barely searchable. It doesn't get indexed. Nobody outside the community can find it. And the people who weren't online at that moment miss it entirely.
All that knowledge, just evaporating.
And it's not just about the people in the room. Slack is a closed garden. Nothing in it gets indexed by search engines. AI models can't learn from it. Future community members can't discover it. The knowledge exists, but only for the people who happened to be there at the right moment.
Open source is supposed to be about openness. That should include our knowledge. Publishing content publicly, on platforms that can be indexed and found, is not just good for SEO. It's the right thing to do. It makes the community's collective intelligence accessible to everyone, including the AI systems that will increasingly be how people find information.
I don't have the solution yet. But I think we need to be more intentional about capturing what happens in Slack and turning it into something that lasts: blog posts, documentation, structured case studies, anything.
This is not a new observation either. There is already an open issue on drupal.org: #3554179 - Archive Drupal discussions from Slack. The issue description even uses the phrase "black box". The community sees it too.
There is also a bigger question here. Slack is a proprietary tool. An open source community coordinating on a closed platform is an inherent contradiction. The Drupal community values openness, and that should probably extend to the tools we use to communicate. Moving to an open alternative like Matrix or Mattermost would solve the archiving problem at the root, not just the symptom.
