MariaDB announces Call for Participation for M-Ecosystem Devroom at FOSDEM 2027
The M-Ecosystem Devroom at FOSDEM 2027 invites technical contributions covering the broader landscape of MySQL, MariaDB, and related database projects.
Summary
The MariaDB Foundation has officially opened the Call for Participation (CfP) for the M-Ecosystem Devroom at FOSDEM 2027. This event, scheduled for January 31, 2027, in Brussels, marks an evolution from the previous 'MariaDB, MySQL & Friends' format to a broader scope encompassing the entire interconnected database ecosystem.
The devroom aims to provide a neutral technical forum for developers, DBAs, and maintainers working on various implementations including MySQL, MariaDB, Percona Server, VillageSQL, and AliSQL. It focuses on sharing knowledge regarding shared protocols, storage engines, and common technical challenges faced by these diverse but related projects.
Technical scope of the M-Ecosystem Devroom
- Database Internals: Proposals are sought for deep dives into query optimizers, execution plans, storage engine architectures, indexing strategies, and memory management.
- High Availability and Replication: The scope includes replication protocols, clustering solutions, failover mechanisms, and cross-implementation replication compatibility.
- Operational Tooling: Technical presentations are encouraged regarding database connectors, proxies, backup/restore utilities, observability, and deployment automation via containers.
- Emerging Workloads: The devroom specifically highlights interest in vector search for AI workloads, hybrid transactional/analytical processing (HTAP), and JSON/document-oriented data handling.
- Interoperability and Security: Focus areas include protocol compatibility between different implementations, authentication/authorization, encryption, and vulnerability management.
Why it matters
By consolidating various MySQL-derived projects under a single technical umbrella, the devroom facilitates better interoperability and knowledge transfer between competing and complementary database implementations. This collaborative approach can lead to improved shared tools, more stable migration paths, and faster resolution of common architectural challenges across the open-source database landscape.
Original reference: mariadb.org →