Proposal of ASF Board Report for 2026-03

[Xuanwo]

Description:

OpenDAL is an Open Data Access Layer that enables seamless interaction with
diverse storage services. Its development is guided by the vision "One Layer,
All Storage" and the following principles:

• Open Community
• Solid Foundation
• Fast Access
• Object Storage First
• Extensible Architecture

Project Status:

Current project status: Ongoing
Issues for the board: None

Membership Data:

Apache OpenDAL was founded on 2024-01-17 (a little over two years ago).
There are currently 36 committers and 22 PMC members in the project.
The committer-to-PMC ratio is roughly 1.6.

Community changes, past quarter:

• The project added one new committer during this quarter.
• The PMC roster remained unchanged during this quarter.

Project Activity:

• No new core stable release was cut in this quarter; the latest stable release remains v0.55.0, released on 2025-11-24.
• Development remained active, with 191 PRs merged from 47 authors between 2025-12-01 and 2026-03-10.
• The project continued modularization work by splitting more services and layers into separate crates and repositories so components can evolve at different paces.
• Major implementation work this quarter included reqsign v2 migrations across multiple services, continued .NET binding work, and new capabilities across Swift, S3, and local key-value backends.
• Weekly "This Week in OpenDAL" discussions continued on GitHub Discussions alongside ongoing community Q&A.

Community Health:

Are there any risks to the sustainability of the project?

OpenDAL remains healthy. While this quarter did not include a new core stable
release, the project maintained strong development velocity and broad
contributor participation. The project now has 36 committers and 22 PMC
members, and recent work shows continued progress on modularization,
integrations, and cross-language bindings.

OpenDAL continues to be used by multiple database systems and infrastructure
tools. The PMC's earlier decision to split more components into separate
repositories is translating into concrete engineering work, which should
improve long-term maintainability without reducing community cohesion.

Is the PMC capable of responding to security issues and

performing releases if needed?

Yes. The PMC has an established release process, has demonstrated the ability
to handle routine dependency maintenance, and continues to make coordinated
technical changes across services, layers, and bindings. If needed, the PMC
can organize releases and respond to security issues in a timely manner.

Does the PMC need anything from the Foundation to improve on

contributing to our mission of delivering software for the public good?

No requests at this time.