GitHub user Xuanwo edited a discussion: [VOTE] Establish Apache Reqsign as a top-level project
Hi all, Based on the prior community discussion in [apache/opendal-reqsign#821](https://github.com/apache/opendal-reqsign/discussions/821), the confirmed initial PMC and Chair discussion in [apache/opendal-reqsign#846](https://github.com/apache/opendal-reqsign/discussions/846), and the review in this thread, I am calling a vote on the proposal to establish Apache Reqsign as a standalone Apache top-level project. This single vote covers the proposal as a whole: the ASF Board resolution, the initial PMC, Zili Chen as the initial Chair, the transfer of the Reqsign subproject from Apache OpenDAL, and the transition plan below. The [suitable-name search for "Apache Reqsign"](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-258) remains in progress in parallel. This proposal uses the name "Apache Reqsign" subject to successful name approval. If the name review requires a material change, the revised proposal will return to the community before Board submission. ## Voting This is a procedural vote. Votes from Apache OpenDAL PMC members are binding; all other votes are advisory and welcome. The proposal passes by a simple majority of binding votes. The vote will remain open for at least seven days, through **2026-09-01 23:59 UTC**. Please cast your vote as: - **+1**: Approve the proposal - **+0**: No opinion - **-1**: Do not approve the proposal because... Please cast or confirm your vote after this formal vote has opened. Votes posted while this thread was still an RFC will not be counted automatically. ## Proposed ASF Board resolution ```text Resolution to Establish the Apache Reqsign Project from the Apache OpenDAL Reqsign Subproject X. Establish the Apache Reqsign Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to signing HTTP requests to cloud services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Reqsign Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Reqsign Project be and hereby is responsible for the creation and maintenance of software related to signing HTTP requests to cloud services; and be it further RESOLVED, that the office of "Vice President, Apache Reqsign" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Reqsign Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Reqsign Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Reqsign Project: * Chojan Shang <[email protected]> * Erick Guan <[email protected]> * Han Xu <[email protected]> * Hao Ding <[email protected]> * Hao Jiang <[email protected]> * Liuqing Yue <[email protected]> * Mingzhuo Yin <[email protected]> * Qinxuan Chen <[email protected]> * Zili Chen <[email protected]> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Zili Chen be appointed to the office of Vice President, Apache Reqsign, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Reqsign Project be and hereby is tasked with the migration and rationalization of the Apache OpenDAL Reqsign subproject; and be it further RESOLVED, that all responsibilities pertaining to the Apache OpenDAL Reqsign subproject encumbered upon the Apache OpenDAL Project are hereafter discharged. ``` ## Background and rationale Reqsign is an ASF-hosted Rust project for signing HTTP requests to AWS, Azure, Google, Huawei, Aliyun, Tencent, Oracle, and other cloud services without requiring full vendor SDKs. It already has a separate repository, release cycle, and users outside OpenDAL, including [uv](https://github.com/astral-sh/uv/blob/49e2fc5c821bb69a528308a036b17446bb5ab5a6/Cargo.toml) and [sccache](https://github.com/mozilla/sccache/blob/e9b15a35f7240a7edd1b9644583edb388c6cb5f9/Cargo.toml). Reqsign has been developed under the Apache OpenDAL PMC and ASF processes. Its provenance and IP review are recorded in the [OpenDAL Reqsign IP clearance](https://incubator.apache.org/ip-clearance/opendal-reqsign.html), and its source releases are published through the [Apache OpenDAL distribution area](https://archive.apache.org/dist/opendal/). The readiness assessment and remaining governance considerations are documented in [apache/opendal-reqsign#821](https://github.com/apache/opendal-reqsign/discussions/821). Establishing a focused PMC would give the distinct Reqsign community direct responsibility for releases, security, community growth, infrastructure, and Board reporting. ## Proposed transition plan After the ASF Board approves the resolution, the new PMC would coordinate with the OpenDAL PMC and ASF Infrastructure to: 1. Rename `apache/opendal-reqsign` to `apache/reqsign`, retaining repository history, issues, pull requests, and discussions. 2. Establish `reqsign.apache.org` and migrate the project website. 3. Create `[email protected]`, `[email protected]`, and `[email protected]`, then update repository notification routing. 4. Move source-release distribution, KEYS references, release metadata, and archive paths from the OpenDAL area to the Reqsign area. 5. Transfer GitHub release environments, crates.io publishing access, and other release credentials to the new PMC. 6. Establish the initial committer roster in coordination with the OpenDAL PMC while preserving contributor history and appropriate existing access. 7. Publish standalone governance, security, community, compatibility, and release documentation. 8. Add Apache Reqsign project metadata, including its DOAP entry, and begin the Board reporting schedule for a newly established TLP. 9. Update OpenDAL documentation and metadata to describe Reqsign as a related standalone ASF project rather than an OpenDAL subproject. Until the Board resolution is approved and the relevant infrastructure transition is complete, Reqsign remains an Apache OpenDAL subproject governed by the OpenDAL PMC. Best, Xuanwo GitHub link: https://github.com/apache/opendal/discussions/8138 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
