Replies: 2 comments 2 replies
|
I think we can consider "graduate" reqsign from opendal to make things easier. |
2 replies
|
Mailing list thread: https://lists.apache.org/thread/o9l90w3j8gr1qwsknqskzscjwtj1dqbk |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Background
PR #818 adds an official website for Apache OpenDAL™ Reqsign under
website/. Today, Reqsign's public entry is primarily the repository README and docs.rs. As the project gains task-oriented documentation, provider capability pages, and download and community pages, it needs a stable canonical URL.Proposal
Use https://reqsign.opendal.apache.org/ as the canonical URL of the Reqsign website.
Reqsign remains a subproject governed by the Apache OpenDAL PMC, and the website's branding and footer state that relationship. This domain gives Reqsign a clear product and documentation entry point while keeping its connection to Apache OpenDAL explicit.
PR #818 keeps the Docusaurus
urlandbaseUrlconfigurable, so staging or a fallback deployment would not require a code redesign.Alternatives considered
The proposed domain does not currently have a public DNS record. After consensus, we can file an ASF INFRA request for DNS, TLS, and the publishing mapping.
Feedback requested
Are there any objections to using https://reqsign.opendal.apache.org/ as the canonical Reqsign website URL?
If there are no objections, I will keep this target in PR #818 and follow up with the required ASF Infra setup.
All reactions