Open Source CMS Panel Links Sustainability to Digital Sovereignty

Representatives from Drupal, TYPO3, Contao and Neos discussed contributor pipelines, corporate participation, volunteer work, regulation and digital sovereignty at mittwald’s Head in the Cloud event, according to a LinkedIn article by Martin Helmich, head of developer relations at mittwald and board and product strategy lead at the TYPO3 Association.

For Drupal readers, the discussion is useful because it places CMS sustainability inside a wider public-sector technology debate. Public institutions can adopt open infrastructure, but that adoption becomes more durable when the projects behind the software have visible contribution models, long-term maintenance capacity and organisations willing to support the ecosystem. Helmich’s account gives the Drupal community a cross-CMS view of that problem.

According to Helmich, Baddý Sonja Breidert, CEO and co-founder of 1xINTERNET and chair of the Drupal Association, described Drupal as a mature global project where corporate and institutional contribution have become significant. Helmich contrasted that with Contao’s stronger dependence on volunteer work, while placing TYPO3 and Neos between those models. The comparison showed how open source CMS projects can share sustainability pressures while relying on different contribution cultures.

Drupal has a formal mechanism for part of that problem. Drupal.org’s documentation on contribution credit says organisational credits affect marketplace ranking and Drupal Certified Partner qualification. The system does not solve every sustainability issue, but it makes contribution visible and gives organisations a public incentive to support the project.

That point connects with the maker-taker argument made by Dries Buytaert, Drupal’s founder and project lead. In Balancing Makers and Takers to Scale and Sustain Open Source, published in 2019, Dries argued that open source projects need governance, coordination and incentive models that make contribution sustainable. In Solving the Maker-Taker Problem, published in 2024, he used Drupal’s contribution credit system as a model for recognising and incentivising contribution.

Digital sovereignty was another part of Helmich’s report from the panel. Helmich wrote that Baddý warned against reducing Drupal to a European open source identity, since Drupal is maintained by a global community of contributors and organisations. He also reported Joachim Nickel’s view that sovereignty is more about infrastructure, including where servers and data processing are located, than about excluding contributors based on geography.

The distinction matters because European policy now links open source to governance, procurement, maintenance and long-term sustainability. The EU Open Source Strategy describes a lifecycle approach covering research, market uptake, deployment, long-term maintenance and governance of critical open source components. It also calls for support for contributors, foundations, companies and users, along with viable open source business models and procurement practices that can strengthen the broader ecosystem.

The European Commission’s Drupal Community of Practice adds Drupal-specific context. It says the Drupal4Gov Conference, launched in 2026, brings together digital professionals, policymakers and Drupal community members from across Europe to exchange knowledge and explore how Drupal supports digital public services. The Community of Practice describes its work as promoting open, interoperable and reusable solutions in the public sector.

Regulation adds another layer. Helmich’s article says the panel discussed GDPR, accessibility requirements and the Cyber Resilience Act. Those areas increase the value of projects that can document decisions, sustain releases and support security and compliance work over time.

The Head in the Cloud panel brought several PHP-based open source CMS communities into one discussion about contribution, funding, regulation and sovereignty. For Drupal, the practical takeaway is not that digital sovereignty belongs to one region or one project. It is that open digital infrastructure becomes more credible when adoption, contribution, governance and maintenance are treated as connected responsibilities.