Loading0%
Henri Kuiper

Henri Kuiper

20:51 · 09/11/2026

An Open Letter Back: Connect, Don't Consolidate

An Open Letter Back: Connect, Don't Consolidate

Some ramblings on community, fragmentation, collaboration and why bringing people together matters more than bringing organisations together.

Steven Dickens recently published an interesting An Open Letter to the Mainframe Community: It's Time to Pull Together. Having watched the discussion around GS Forge and some of the wider conversations taking place in our ecosystem, I found myself agreeing
with quite a bit of what he said.

And it really got me thinking.

This is actually one of the reasons we founded Mainframe Society in the first place.

I agree that the mainframe world needs a clearer front door. If you're new to the platform, or coming from another part of the technology industry, it can be surprisingly difficult to work out where to start, which communities to join and where the real conversations are
happening.

But I'm not entirely convinced that the answer is to make everything look the same, or that having different organisations and communities is, in itself, the problem.

I actually think our diversity is one of our biggest strengths.

We don't have a community problem. We have a connection problem.

SHARE, GS Forge, Guide Share Europe, regional user groups, open-source projects, vendors, podcasts, newsletters, Slack groups, LinkedIn communities and independent voices all bring something different to the table.

They have different histories, audiences, personalities and purposes.
Some are focused on deep technical knowledge sharing. Others are about networking, education, advocacy, open source or simply bringing people together.

That's not something I'd be particularly keen to throw away.

Think about the people behind all these initiatives. Many of them are volunteers. People giving up their evenings, weekends and personal time to organise events, write articles, maintain projects, record podcasts, answer questions and help the next generation find their way into the platform.

That is an incredible amount of passion and goodwill.

I don't think we should look at all that effort and conclude that the answer is to consolidate everything into fewer organisations.

The problem isn't that we have too many communities. It's that we don't connect them well enough.

We often make people work too hard to find each other. We compete for the same attention, sponsorship and attendance instead of making it easier for people to move between communities, discover new opportunities and get involved.

We have plenty of rooms. We just don't have enough connecting corridors.

Consolidation isn't the same as collaboration

This is probably where I disagree most with the idea that we need to consolidate the mainframe ecosystem.

I'm not against consolidation where it makes sense. There are certainly opportunities to reduce duplication, share resources and make better use of everyone's time and money.

But I think we need to be careful about what we're actually trying to achieve.

We shouldn't have to dissolve decades of history, experience and identity to work better together.

SHARE doesn't need to become GS Forge. GS Forge doesn't need to become GSE. And independent communities shouldn't have to disappear because a bigger organisation wants to own the conversation.

Different organisations can coexist, collaborate and complement each other.

In fact, that's exactly what I'd like to see more of.

A stronger community of communities.

A shared front door. Better signposting. A common calendar. More cross-promotion. Easier ways for people to discover the right group, event, project or conversation for them. And yes, perhaps one or two major gatherings that give the wider ecosystem a centre of gravity.

But none of that requires everyone to wear the same shirt.

The missing connecting layer

That's very much the thinking behind Mainframe Society.

Not to compete with the communities that already exist. Not to become another organisation fighting for a slice of the same pie. And certainly not to tell people where they should belong.

It's about making it easier for people to connect, learn and lead.

To bring people together who might otherwise never have crossed paths. To give independent voices, smaller communities and new initiatives a place to be discovered. And to help all the great things already happening across this ecosystem reach a much wider audience.

I think there's a missing connecting layer in our ecosystem.

Consider some simple questions:

  • • Where does a student go when they want to discover the mainframe world?
  • • How does an independent developer get their open-source project in front of the right people?
  • • How does someone new to the industry discover the user groups, events and people worth following?
  • • How does a regional community reach people outside its own geographical bubble?
  • • How do we make sure that a great podcast, technical article or community initiative doesn't disappear into someone's LinkedIn timeline?

These aren't necessarily problems that SHARE, GSE, GS Forge or any other individual organisation should solve on its own.

They're ecosystem problems.

And I believe there's real value in having something that helps connect those dots.

Not another gatekeeper. Not another layer of governance. Not another organisation deciding who gets a seat at the table.

Just a place that helps people find the table in the first place.

A few more ramblings...

There's something else that I think gets lost in these discussions.

A community isn't an organisation. It's people.

Organisations provide structure. They organise events, manage memberships, arrange sponsorships and provide platforms for people to meet. All important things.

But the actual community exists beyond those structures.

It's the person answering a question on LinkedIn. The developer sharing a little tool they've been working on. The sysprog helping a student with their first JCL job. The person recording a podcast after work. The conference speaker sharing something they've learned. The volunteer who spends their Saturday making sure an event actually happens.

Some of the most valuable contributions to our ecosystem don't come from organisations with big budgets, formal memberships or conference halls.

They come from individuals.

And I'd hate to see us create a structure that accidentally makes those people feel less relevant.

We should be making it easier for them to participate, not harder.

I'd also argue that we sometimes underestimate how intimidating the mainframe world can look from the outside. We talk about attracting new talent, getting students interested and making the platform more accessible. But then we present them with a dozen different organisations, acronyms, events and communities and expect them to figure it all out.

We need to make the first step easier.

And once someone takes that first step, we should be welcoming them into an ecosystem where people actively help them discover the next opportunity.

That's not something you achieve by simply merging conference calendars.

It's culture. It's attitude. It's people being willing to share their audience, their knowledge and their connections.

We should be building bridges, not walls.

I also think there's a huge opportunity for vendors and sponsors here.

Everyone has limited budgets. Everyone is competing for attention. And yes, the current event landscape can make that complicated.

But imagine a more connected ecosystem where organisations actively promote each other's events, where independent initiatives get visibility, where vendors can engage with communities throughout the year rather than only at the next big conference.

That's a much healthier proposition for everyone.

More collaboration doesn't mean less competition. It means making the overall ecosystem more attractive, more accessible and ultimately more valuable.

And perhaps that's something we should be selling a little more confidently when we talk about the mainframe platform itself.

We have an incredibly strong technical ecosystem. We have decades of knowledge, an increasingly vibrant open-source community, new generations of developers and engineers, and people doing genuinely exciting things with this platform.

We should be just as proud of our community as we are of our technology.

So, where do we go from here?

I don't pretend to have all the answers. And I certainly don't think Mainframe Society has all the answers either.

But I do think we need to have this conversation.

We need to stop looking at every new community initiative as another competitor. We need to stop measuring success purely in terms of membership numbers, conference attendance or social media followers.

And we need to start asking how we can help each other succeed.

A newcomer should be able to walk through one welcoming door and discover many different rooms inside. Each with its own character, expertise and people. And the people in those rooms should be happy to point them towards the next one.

That's what a healthy community looks like to me.

So I'd genuinely like to hear from people across the ecosystem.

Community organisers, vendors, open-source maintainers, independent content creators, newcomers and the old-timers who've been around since punch cards were fashionable.

Who is connecting all these dots today?

What are we missing? What would make it easier for you to connect with the wider mainframe ecosystem? What could your organisation do differently? And what could we all do together?

Agree, disagree, challenge the idea or suggest something completely different. That's exactly the kind of conversation I'd like to see happening.

Because the mainframe community doesn't need less personality.

It needs more connection.

And perhaps it's time we started acting like one big community, without having to become one big organisation.


Henri Kuiper is co-founder and CTO of Mainframe Society. These are personal thoughts and opinions, not an official position on behalf of every organisation mentioned.

0
Updated 09/11/2026