Proposal of ASF Board Report for 2026-06

[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. There are currently 39 committers
and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 1.7.

Community changes, past quarter:

• Hao Jiang (dentiny) was added as committer on 2026-03-30
• Fatorin was added as committer on 2026-04-03
• Krisztian Szucs was added as committer on 2026-05-28
• Hao Jiang (dentiny) was added as PMC member on 2026-06-02

Project Activity:

OpenDAL has the following releases since the last report:

• Apache OpenDAL Reqsign v0.20.0 was released on 2026-03-23
• Apache OpenDAL v0.56.0 was released on 2026-05-01
• Apache OpenDAL v0.57.0 was released on 2026-06-01
• Apache OpenDAL Reqsign v0.20.1 was released on 2026-06-01

Notable project activity this quarter:

• The Rust core has been split into a facade crate plus smaller core, service,
  and layer crates. This makes service and layer development more independent
  while preserving the user-facing facade.
• The community continued to improve OpenDAL's cross-language bindings,
  including Ruby publication work, .NET binding work, Python and Node.js API
  coverage, Java platform support, and Go/C layer support.
• The core APIs gained richer operation metadata, including copy/read metadata,
  copier support, and service-operation labels for HTTP metrics.
• Storage service coverage and behavior continued to expand, including
  Volcengine TOS, GooseFS, OPFS, Hugging Face improvements, user-defined
  metadata support, and stronger S3-compatible service behavior.
• Apache OpenDAL Reqsign delivered two releases, adding Volcengine TOS support,
  Google external account credential providers, expanded Aliyun OSS support, and
  dependency hygiene improvements.

Since 2026-03-18, the main OpenDAL repository merged 264 pull requests from 43
contributors and closed 91 issues. The opendal-reqsign repository merged 42 pull
requests from 6 contributors.

Community Health:

Are there any risks to the sustainability of the project?

OpenDAL remains in good health. The project continues to receive steady code,
documentation, release, CI, and binding contributions from both existing
committers and new contributors. The main repository currently has more than
5,100 GitHub stars and more than 760 forks, and development velocity remained
steady throughout the quarter.

The PMC is also continuing to grow the committer pipeline. The vote to add
Trim21 as a committer has passed and an invitation has been sent; the roster
change is still pending acceptance and ASF account completion.

Is the PMC capable of responding to security issues and performing releases if needed?

Yes. The PMC continues to make regular Apache releases for both OpenDAL and
OpenDAL Reqsign, and release processes are documented and repeatable. The PMC is
also capable of responding to security reports and coordinating with the ASF
Security Team when needed.

Does the PMC need anything from the Foundation to improve on contributing to our mission of delivering software for the public good?

The PMC would benefit from more GitHub Actions runner capacity for the large
cross-platform CI matrix, especially for release validation and behavior tests
across storage services and language bindings.

PMC members would also benefit from access to token quota for state-of-the-art
AI models. We expect to use this for project maintenance work such as code
review assistance, issue triage, release preparation, documentation updates, and
debugging complex cross-language or cross-service failures.

[github-actions[bot]]

Mailing list thread: https://lists.apache.org/thread/4zmglwtt6g5hcwjykshsr9thzlqmwkdl