SUSE Cuts Jobs as AI Grows, E2E Fuels Open Source Testing and Drupal Seeks Sustainable Support

Robert Jacobi: Welcome to Open Channels News. I’m your host, Robert Jacobi. Today, 3 stories about what happens when the economics of software start changing faster than the organizations behind it. SUSE is cutting jobs as AI and automation reshape its business. A Polish startup has raised millions to make sure AI-generated software actually works. And Drupal is asking a question that every open source community eventually has to confront. Who pays for all the work that keeps the project alive? Different stories, same underlying issue. Automation can make software cheaper to produce, but does not magically eliminate the cost of quality, maintenance, or people. So let’s start with the people.

Our first story. Enterprise Linux company SUSE is reducing its global workforce by 10%. According to reporting summarized by Fosswire from Phoenix, CEO Dirk-Peter van Leeuwen told employees that AI and automation are changing how the industry operates and that the company needs to adjust. SUSE had already offered voluntary separation packages in September. Apparently not enough employees took them to reach the company’s target. So the next step is involuntary layoffs with notifications beginning November 4th.

Now SUSE is not some experimental AI startup. This is a longstanding enterprise Linux business with SUSE Linux Enterprise, Rancher for Kubernetes management, and NeuVector for container security. It also has a relationship with the openSUSE community. That makes this worth watching. When a company says automation is changing its staffing requirements, there are 2 very different possibilities. One is that it generally needs fewer people to deliver the same value. The other is that it’s betting it can do more with less before that bet has even been proven. Those aren’t the same things.

For customers, the question is practical. Will support responsiveness, product quality, security maintenance, and release schedules stay where they need to be? And for open source communities, there’s an additional concern. Commercial vendors do more than sell subscriptions. They employ people who work on upstream code, maintain infrastructure, and keep complicated projects moving. If those teams shrink, the effect can reach beyond the company’s payroll. We should not assume every cut translates directly into less community support, but we do not have that level of detail here. 10% is substantial, and the industry’s favorite phrase, AI-driven efficiency, deserves scrutiny when it comes with real people losing jobs. The measure of success is not how many positions a company eliminates, it’s whether the software and the ecosystem are actually stronger afterward.

And that brings us to the other side of automation. The Recursive reports that Warsaw and San Francisco-based E2E has raised €7 million in seed funding for an open-source software testing framework. That brings its total funding to just over €8 million. The founders, Szymon Rybczak i Oskar Kwaśniewski, originally built an AI testing agent under the name TesterArmy. But after working with customers, they decided the problem wasn’t just adding AI to existing testing tools. They wanted to rebuild the framework itself.

Here’s a simple version. AI can generate code very quickly. Awesome. But generating code and knowing that it works are 2 completely different things. A feature can look correct, compile correctly, and still fail the moment a real customer clicks the wrong button, uses an unusual browser, or checks out with an unexpected payment method. And when agents are producing more code than people can reasonably review line by line, verification becomes the bottleneck.

According to the company, since its October 1st launch, the framework has passed 1 million downloads, earned more than 12,500 GitHub stars, and run more than 10 million tests. Those are company-reported numbers, but they point to significant early interest. What’s interesting is the business model. The framework is intended to remain free and open source, including commercial use. The company plans to make money from testing infrastructure, enterprise deployments, and services. It’s a familiar open source playbook. Make the tool broadly useful, then charge for the operational value around it. The new funding is supposed to help expand engineering, grow the community, and build large-scale testing infrastructure planned for 2027.

A little bit of irony, AI is helping developers write more code, and that creates an opportunity for a company focused on checking whether that code is any good. Maybe the future isn’t just prompt engineering, maybe it’s verification engineering. Because faster software development is only progress if it actually works.

And finally, Drupal is revisiting one of the oldest arguments in open source. Everyone benefits, but relatively few organizations do most of the work. The Drop Times highlights figures published by the Drupal Association showing that in 2024, just 219 of the 1,440 organizations active on drupal.org accounted for 96% of recorded contributions. Think about that. A relatively small group is carrying almost all of the documented contribution activity. And this is definitely not unusual in open source. But it’s a problem if the ecosystem keeps growing while responsibility stays concentrated.

Drupal Association interim CEO Tiffany Farriss has outlined 2 proposals. One would broaden Drupal’s certification and recognition program to include different kinds of participants, makers, patrons, and advocates, not just traditional agency contributors. The other would establish a dedicated maintainers fund so organizations without engineering capacity could still financially support the people doing the maintenance. Neither proposal has been implemented. And the distinction matters. This is a discussion about how Drupal might evolve its contribution model, not an announcement that a new funding system is already in place.

It also brings us back to Dries Buytaert’s makers and takers argument. If your company builds a business on open source software, what do you owe the project? Code, money, documentation, community support, something else. I don’t think there’s one answer for every company. A small agency and a multinational platform do not have the same resources. And writing a check does not automatically replace the value of technical stewardship. But doing absolutely nothing while expecting a healthy, secure, constantly improving platform is not a sustainable strategy either. The tricky part is designing a system that rewards meaningful participation without turning open source into a club where the biggest check gets the loudest voice. Drupal’s challenge is to broaden responsibility, while protecting the independence and openness that made the project valuable in the first place.

Let’s see how they connect. SUSE is trying to change the cost of producing and supporting enterprise software. E2E is building a business around the quality checks that become more important as AI produces code faster. And Drupal is asking how to distribute the ongoing cost of maintaining software that thousands of businesses depend on. In each case, somebody has to do the work. AI may change who does it, how quickly it gets done, and what customers are willing to pay for it, but it does not erase the need for testing, support, maintenance, or accountability. Open source has never meant that software costs nothing. It means we have choices about how software is built, shared, and sustained. And those choices are getting more important, not less.

That’s it for today’s Open Channels News. I’m Robert Jacobi. Be open and stay secure.