Hi, Here’s one issue for reference: https://issues.apache.org/jira/browse/INFRA-18276
Could be helpful for redirecting traffic from seata.io to seata.apache.org Regards, Jun Liu > On Jan 9, 2024, at 9:32 AM, Qiufeng Liu <[email protected]> > wrote: > > Hi Community, > Here, to introduce you to how we ensure our project website's compliance with > Apache Software Foundation (ASF) policies and the related progress. > Disclaimer and trademarks (done): > Add a uniform footer displaying disclaimers and trademarks. > Domain name usage (planned): > Permanent redirect the old domain (seata.io) to the apache domain > (seata.apache.org) and synchronizes the adjustment of the domains referenced > in recent versions of the documentation. The domain name remains the same in > older versions of the documentation, with the permanent redirect ensuring the > correct jump. > Adherence to project naming conventions (doing): > Uniformly change the project name to 'Apache Seata (Incubating)' in prominent > locations (e.g., site title, article title, header, footer, etc.). > Website navigation optimization (done): > Refer to the 'Apache Project Branding > Policy'(https://www.apache.org/foundation/marks/pmcs#navigation > <https://www.apache.org/foundation/marks/pmcs#navigation >) to add relevant > links > Quality of English documentation (doing): > We are currently working on translations as we have previously focused on > Chinese documentation. > Display of user endorsements (doing): > Migrate this section from the home page to a separate page. > Looking forward to your participation! > Warm regards, > Qiufeng Liu > ------------------------------------------------------------------ > 发件人：Min Ji <[email protected]> > 发送时间：2024年1月6日(星期六) 17:49 > 收件人：dev<[email protected]> > 主 题：[discuss] Apache Seata (incubating) official website compliance > Hi Community, > Following the recent donation of Seata to the Apache Incubator, we are > reaching out to discuss an essential element of our incubation journey — > ensuring our project website's compliance with Apache Software Foundation > (ASF) policies. > Understanding the critical nature of this task, our team has been > dedicating considerable effort over the past few weeks to address various > compliance-related issues. We are glad to share that this concentrated > effort has led to substantial improvements. > To properly document and manage our compliance activities, we have > established a wiki page[1]. This resource focuses on the areas requiring > modifications and review in alignment with ASF guidelines, including: > - Domain name usage > - Adherence to project naming conventions > - Website navigation optimization > - Quality of English documentation > - Display of user endorsements ("Powered By") > - Correct usage of corporate logos > - Homepage presentation standards > Our goal through these revisions is not only to adhere strictly to ASF > standards but also to ensure our community and users have a clear and > informative experience when interacting with our project. > We invite you to join this ongoing discussion and contribute your valuable > insights. The detailed considerations and adjustments made are open for > review at the wiki[1]. > To further guide our efforts, we have been referring to specific ASF > documentation[2]. > Your feedback is critical to us as we aspire to achieve full compliance and > bolster Seata's growth within the Apache community. Please visit the > discussion link to offer your perspectives and suggestions. > Thank you for your continued support and active participation in ensuring > the success of Seata's incubation process. > [1]. https://github.com/apache/incubator-seata/discussions/6233 > <https://github.com/apache/incubator-seata/discussions/6233 > > <https://github.com/apache/incubator-seata/discussions/6233> > <https://github.com/apache/incubator-seata/discussions/6233> > > [2]. https://incubator.apache.org/guides/sites.html > <https://incubator.apache.org/guides/sites.html > > Warm regards, > Ji Min --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
