What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2026-09-16 | Appointed Zili Chen | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2026-09-16 | Establish the Apache Reqsign Project | action without a meeting | approved |
## Description: Apache Reqsign is a Rust library for signing HTTP requests to cloud services and obtaining the credentials needed to authenticate them. It supports multiple cloud providers without requiring their full SDKs and can be used independently or through projects such as Apache OpenDAL. ## Project Status: Current project status: New, with ongoing development. Issues for the board: None. This is the first Board report for Apache Reqsign, established as a top-level project on 2026-09-16 after operating as a subproject of Apache OpenDAL for years. The community is completing the transition to independent project infrastructure and governance. ## Membership Data: Apache Reqsign has 9 committers and 9 PMC members, at a 1:1 ratio. Zili Chen serves as the initial PMC Chair. The initial PMC was appointed on 2026-09-16. All initial PMC members previously served on the OpenDAL PMC. There have been no additional committer or PMC appointments since establishment. ## Project Activity: Work during this initial reporting period has focused on the TLP transition and maintaining release continuity: - The repository was renamed from apache/opendal-reqsign to apache/reqsign. Repository notification configuration now directs discussions to dev@reqsign.apache.org and development notifications to commits@reqsign.apache.org. - Project branding, repository references, security contacts, and release documentation have been updated for Apache Reqsign. Separate development and release distribution areas, including a Reqsign KEYS file, are in place. Work on the project website remains outstanding. - Version 0.20.7 was released on 2026-09-25 under the Apache OpenDAL Reqsign name and through the OpenDAL distribution area during the transition. No release under the standalone Apache Reqsign name has been made as of this report. - That release expanded cloud credential support, including Aliyun role assumption, caller-provided identity tokens for AWS, Azure, and Google, and Google service-account impersonation. It also improved credential handling and expanded tests against live Azure and Google services. ## Community Health: ### Are there any risks to the project's sustainability? The community remains active, and the new PMC brings together contributors already involved in Reqsign development and release review under OpenDAL. The main sustainability risk is the concentration of day-to-day development and release preparation in a small number of maintainers. Broadening routine review and release management across the new PMC, and encouraging additional contributors to take on these roles, remain priorities. ### Is the PMC capable of responding to security issues and performing releases if needed? Yes. Members of the new PMC have experience preparing, reviewing, and approving Reqsign releases under OpenDAL. The 0.20.7 release received three binding approval votes from members of the new PMC. The project has a documented release process and security policy. Security reports are directed to private@reqsign.apache.org, with the ASF Security Team available for coordination. ### Does the PMC need anything from the Foundation to improve on contributing to our mission of delivering software for the public good? No additional requests at this time beyond routine Infrastructure coordination to complete the TLP transition.