GitHub user Xuanwo created a discussion: Proposal of ASF Board Report for 2026-09
## 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, with high activity. Issues for the board: The OpenDAL PMC has approved the proposal to establish Reqsign as a standalone Apache top-level project. The suitable-name review was approved on 2026-09-07. The proposal awaits Board approval; Reqsign remains under the OpenDAL PMC during this process. ## Membership Data: Apache OpenDAL was founded on 2024-01-17. There are currently 40 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 1.7. Community changes since the last report: - Yuang Gao (yuang) was added as a committer on 2026-09-04 and welcomed publicly on 2026-09-07. - No new PMC members. The latest addition was Hao Jiang (dentiny) on 2026-06-02. ## Project Activity: OpenDAL has made the following releases since the last report: - Apache OpenDAL v0.58.0 on 2026-07-16. - Apache OpenDAL v0.58.1 on 2026-07-31. - Apache OpenDAL v0.58.2 on 2026-08-21. - Apache OpenDAL v0.59.0 on 2026-09-04. - Apache OpenDAL Reqsign v0.20.2 on 2026-07-10. - Apache OpenDAL Reqsign v0.20.3 on 2026-07-27. - Apache OpenDAL Reqsign v0.20.4 on 2026-08-04. - Apache OpenDAL Reqsign v0.20.5 on 2026-08-07. - Apache OpenDAL Reqsign v0.20.6 on 2026-08-24. Notable project activity this quarter: - Storage functionality expanded with S3 Express authentication, object restoration, conditional operations, a Google Cloud Storage gRPC service, and object composition. C++ and .NET bindings gained additional operation coverage, alongside continued Python and other binding improvements. - The project established shared specifications for behavior across language bindings and improved upgrade guidance and release validation for ecosystem integrations. - Package publishing moved to short-lived OIDC credentials for Rust, Python, Node.js, .NET, and Ruby. Work also began on automated source-candidate preparation and staging through the Apache Trusted Releases service. - Reqsign improved cloud credential handling and added AWS SigV4a and S3 Express support. Its proposed transition to a standalone project would give its community direct responsibility for releases, security, and governance. >From 2026-06-10 through the 2026-09-08 data collection, the main repository merged 340 pull requests, including 300 from 53 human contributors. The Reqsign repository merged 56 pull requests, including 46 from 8 human contributors. The remaining pull requests were dependency-bot updates. ## Community Health: ### Are there any risks to the sustainability of the project? OpenDAL remains active, with continued contributor participation and regular releases. Maintaining the cross-language and storage-service test matrix, reviewing contributions, and verifying release artifacts require sustained maintainer attention. Several release candidates needed packaging or license material corrections this quarter. The community is improving release checks and automation to reduce that workload. A weekly release cadence is under discussion; independent artifact verification and PMC votes remain necessary. Following the previous report's discussion of AI use, the project added an AI-assisted contribution policy. It requires meaningful human involvement, disclosure of material AI assistance, and verification of submitted claims. Service-specific bug reports require reproduction against the actual service. The human contributor remains accountable for the submission. These rules aim to protect reviewer attention while allowing useful AI-assisted work. ### Is the PMC capable of responding to security issues and performing releases if needed? Yes. Multiple PMC members participated in release verification and voting this quarter, supporting nine formal releases across OpenDAL and Reqsign. The PMC maintains a documented security reporting process and can coordinate with the ASF Security Team. Trusted publishing and stronger source-package checks also improve the release process. OpenDAL v0.59.1 is currently under vote to correct a missing changelog in the published opendal-core crate; it is not included in the release count above. ### Does the PMC need anything from the Foundation to improve on contributing to our mission of delivering software for the public good? The PMC seeks Board approval of the Reqsign TLP proposal and, following approval, Infrastructure support for the transition. As in the previous report, additional GitHub Actions capacity and access to advanced AI models would help with cross-platform validation and project maintenance. AI-assisted work remains subject to human review and the project's contribution policy. --- This report was prepared with AI assistance and reviewed before posting. Feedback and corrections are welcome before submission to the Board. GitHub link: https://github.com/apache/opendal/discussions/8255 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
