Naming is another issue. Although following the DataFusion story we can keep release the software as "reqsign", following ASF INFRA settings, the repo would be "opendal-reqsign".
> • To add new services in opendal, users must first enable service support in reqsign and then update reqsign within opendal. To be clear, is it a distinguished requirement of OpenDAL, or the requirement of service foo? They are quite different, means if projects other than OpenDAL has the same requirements can "must first enable service support in reqsign and then update reqsign". Best, tison. Xuanwo <[email protected]> 于2024年3月26日周二 21:26写道： > Hello, everyone. > > I start this thread to discuss the donation of reqsign < > https://github.com/Xuanwo/reqsign> to the opendal project. > > Context > > reqsign <https://github.com/Xuanwo/reqsign> is a rust lib of signing HTTP > requests without heavy SDKs. opendal uses reqsign to sign nearlly all http > based services. And opendal is the biggest user of reqsign. > > Motivation > > • Nearly all reqsign contributors are also opendal contributors. They > appear to be almost the same community. > • To add new services in opendal, users must first enable service support > in reqsign and then update reqsign within opendal. > • By integrating reqsign into opendal, the community can develop features > more rapidly. > Drawback > > • reqsign is not included in opendal and does not share its vision. For > instance, reqsign can be utilized for AWS EC2, which opendal does not > support. > • reqsign has its own GitHub workflow. The donation process might be > challenging. > Discussion > > What are your thoughts on this? Do you believe it's beneficial for the > opendal community to support maintaining reqsign? Would you be interested > in helping maintain reqsign? > > Xuanwo > >
