linghengqian opened a new issue, #35536: URL: https://github.com/apache/shardingsphere/issues/35536
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? - https://github.com/apache/shardingsphere/commit/d1ac2de4d1d61d78e06ef1abd08b4361c81e6bdb ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? - ShardingSphere-JDBC ### Expected behavior - The images on the `Members` documentation page are displayed normally. See https://shardingsphere.apache.org/community/en/team/ . ### Actual behavior - Due to changes in the ASF privacy policy, the images on the `Members` documentation page are no longer valid. See https://shardingsphere.apache.org/community/en/team/ . -  ### Reason analyze (If you can) - In March 2025, the ASF privacy policy changed. This resulted in PRs like https://github.com/apache/opendal/pull/5724 and https://github.com/apache/opendal/pull/5686. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. - Open https://shardingsphere.apache.org/community/en/team/ . ### Example codes for reproduce this issue (such as a github link). - Maybe not important. -- 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]
