Replies: 12 comments 5 replies
|
Mailing list thread: https://lists.apache.org/thread/b4tlm4vcbzknr0sjq6z0jzppyr565l2y |
|
+1 Why not just call a vote to reduce paper work :D The consensus has already softly reached in the previous thread. |
|
+1 (binding) I support establishing Apache Reqsign as a standalone ASF top-level project, including the proposed Board resolution, initial PMC, Chair, transfer from Apache OpenDAL, and transition plan. |
|
+1 binding |
|
+1 |
|
+1 binding |
|
+1 binding |
|
+1 binding |
|
+1 binding |
|
+1 binding |
|
+1 binding |
|
The vote has concluded and passed. Binding votes:
Advisory votes:
The Apache OpenDAL PMC has approved the proposal to establish Apache Reqsign as a standalone ASF top-level project, subject to successful completion of the suitable-name review as stated in the vote. The next steps are to complete the name review and prepare the Board resolution for submission. Thanks to everyone who reviewed and voted. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
Based on the prior community discussion in apache/opendal-reqsign#821, the confirmed initial PMC and Chair discussion in apache/opendal-reqsign#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" 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:
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
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 and sccache.
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, and its source releases are published through the Apache OpenDAL distribution area.
The readiness assessment and remaining governance considerations are documented in apache/opendal-reqsign#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:
apache/opendal-reqsigntoapache/reqsign, retaining repository history, issues, pull requests, and discussions.reqsign.apache.organd migrate the project website.dev@reqsign.apache.org,private@reqsign.apache.org, andcommits@reqsign.apache.org, then update repository notification routing.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
All reactions