imbajin commented on PR #493: URL: https://github.com/apache/hugegraph-doc/pull/493#issuecomment-5732450435
## TODO — ASF Kapa / hCaptcha privacy and CSP follow-up This is recorded separately so it does not block the OINK implementation or dedicated staging validation. Related Apache examples found today: - [Apache Fluss PR #3760](https://github.com/apache/fluss/pull/3760) uses Kapa's `data-consent-required`, disables analytics cookies, and adds the Kapa/reCAPTCHA domains to the ASF `.htaccess` CSP. - [Apache ShenYu website PR #1131](https://github.com/apache/shenyu-website/pull/1131) documents locale/dark-mode integration, disabled analytics cookies/fingerprinting, and CSP entries for the widget, proxy, and bot-protection domains. - [Apache Iceberg issue #13934](https://github.com/apache/iceberg/issues/13934) tracks Kapa's Open Source Program as a project-level adoption discussion. - [Apache SkyWalking issue #12407](https://github.com/apache/skywalking/issues/12407) records removal of Kapa at the request of the ASF Policy team, so production approval must not be assumed from staging availability. - [Apache Fluss issue #3206](https://github.com/apache/fluss/issues/3206) is a useful reminder that a deployed widget still needs a real browser smoke test. Follow-up questions for ASF Privacy/Infra: 1. Is the Kapa/hCaptcha integration allowed on `hugegraph-oink.staged.apache.org` before a separate ASF approval? 2. If staging is allowed, which exact production domains and CSP directives must be approved before `hugegraph.apache.org` is enabled? 3. Does Kapa need a separate source group / website integration approval for EN and CN? Current implementation keeps the native search path independent, requires an explicit same-origin consent action before any third-party request, and leaves Kapa source-group activation plus production privacy/CSP approval as a clearly tracked acceptance item. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
