Who owns the stack? Why Europe writes the open source but doesn't govern it
Europe writes half the open source stack. It controls almost none of it—and the 2026 Technological Sovereignty Package just made that gap official.
Why it matters
The EU's push for AI and tech sovereignty collides with a structural reality: European developers dominate open-source contributions but lack governance power over the projects that matter. The summit conversation exposes the mismatch between contribution volume and strategic control.
The key facts
9 to knowEuropean Commission's 2026 Technological Sovereignty Package integrated AI, cloud, semiconductors, and open source into unified strategy
Open Source Summit Europe 2026 convened to debate what 'sovereignty' means operationally
Europe's open-source contribution is quantitatively high but governance/control is structurally limited
Question raised: who owns the stack when contributors and controllers are different entities
European Commission 2026 Technological Sovereignty Package bundles AI, cloud, semiconductors, and open source into one strategy
Day one of Open Source Summit Europe 2026 focused on defining 'technological sovereignty'
Core tension: Europe writes open-source code but does not govern its development, maintenance, or strategic direction
No disclosed metrics on European open-source contribution share or governance representation
No specific policy announcements or timelines disclosed in article
Go to the source
diginomicadiginomica.com
Publisher excerpt: The European Commission's 2026 Technological Sovereignty Package pulled AI, cloud, semiconductors and open source into one strategy. Day one of Open Source Summit Europe 2026 asked: what does being sovereign actually look like?