Hi Ovilia, Re: #1, That is a good question and one which Huawei has offered some cloud services before for the foundation. If you had a server in China, would you want to run to have it mirror the site and use a different URL like zh.echarts.apache.org and https://echarts.apache.org/zh would redirect to that site? That might be a simple solution to your need. We can ask fundraising to talk to Huawei and see if they will grant credits for us. If you would like me to spearhead this, just discuss with the pmc and if the PMC would like this, designate me to talk to Fundraising. We have a perfect program for this and like I said, I know Huawei has offered to help with exactly these type of issues.
Re: #7 Google Analytics at the moment is fine but there are tracking concerns and the Apache VP of Privacy has just been re-filled. Things like GDPR and data breaches are really shaking things like this up so I don't have an easy answer other than for now, I think it's fine because of what it's used for. Regards, KAM On 2/21/2019 5:45 AM, Ovilia wrote: > (1) We could provide a https://echarts.apache.org/zh for Chinese > language users. But the loading time for Chinese users to access the > Apache server is quite slow. > We did the following experiment: > A computer in China access the following web page without cache and proxy: > https://echartsjs.com/option.html#title takes 3.17 seconds. > image.png > while http://echarts.apache.org/option.html takes 8.81 seconds, which > is almost 3 times of server in China. > image.png > > Considering many of the developers are in China, this loading time > could be annoying. So would it be possible for Apache to provide a > server in China so that we could use for https://echarts.apache.org/zh > , or we could provide a server for it. Would that be OK? > If not, we would like to use https://echartsjs.com for the > Chinese version and make http://echarts.baidu.com redirect to it. > > (5) I'm not sure what the answer to the question "who is responsible > for ..." to be. Yes, I have the passwords to these websites. > https://gallery.echartsjs.com/editor.html is a community tool to host > user-generated charts online, for others to view and edit. > I guess we need to add Apache ECharts (incubating) > to https://twitter.com/EChartsJs and https://www.weibo.com/echarts . Anything > else we need to pay special attention to? > > (7) These logging files are used for tracking website access, exactly > as Google Analytics. Would that be illegal? > > (8) As about "Top links are not coming from the Apache repos", where > is this > "https://raw.githubusercontent.com/ecomfe/echarts/4.1.0/dist/echarts.simple.min.js";? > > Zhang Wenli > http://zhangwenli.com > > > On Wed, Feb 20, 2019 at 11:38 AM Ovilia <[email protected] > <mailto:[email protected]>> wrote: > > Thanks Dave for your detailed request. > We will work on it and keep you posted. > > Zhang Wenli > http://zhangwenli.com > > > On Wed, Feb 20, 2019 at 6:15 AM Dave Fisher <[email protected] > <mailto:[email protected]>> wrote: > > I wanted to provide guidance on moving the ECharts website to > Apache. Both the Chinese site and the English site need to be > hosted on the echarts.apache.org <http://echarts.apache.org> > domain and have the source stored in GitHub(GitBox) in the > apache/incubator-echarts-website repository. There is work to > do and that will include some that is mandated by Apache policies. > > (1) Move echarts.baidu.com <http://echarts.baidu.com> > <http://echarts.baidu.com/>. [1][3] > > The target here is likely to be something like > echarts.apache.org/zh <http://echarts.apache.org/zh> > <http://echarts.apache.org/zh> and echarts.apache.org/en > <http://echarts.apache.org/en> <http://echarts.apache.org/en> > with echarts.apache.org/ <http://echarts.apache.org/> > <http://echarts.apache.org/> being smart (or dumb) about > picking the best for the user. Once the project has that in > place then a redirection rule should be added to > echarts.baidu.com <http://echarts.baidu.com> > <http://echarts.baidu.com/> to properly permanently redirect > any url to the same resource on echarts.apache.org > <http://echarts.apache.org> <http://echarts.apache.org/>. > > The IPMC expects to see movement on this via pull requests > soon. If there are any differences in support between the > Baidu served site and what Apache provides then please let us > ASAP. > > (2) Required navigation links for Apache Projects. [2] > > You must include links to www.apache.org > <http://www.apache.org> <http://www.apache.org/> along with > the Apache License and other requirements. See [2] > > (3) Proper attribution of trademarks is required. [4] > > You have this mostly correct on the English site. > > (4) The Download page needs to follow release distribution > policy [5] > > Specifically, you must describe where to find the release > using the Apache mirror system. This mirrors > https://dist.apache.org/repos/dist/release/incubator/echarts/ > <https://dist.apache.org/repos/dist/release/incubator/echarts/> > and a LUA file is provided to select the closest mirror. You > must point to the KEYS file and describe how to verify the > download using the asc, and sha512 found there. > > Also, once the Release is approved the RC artifacts should be > renamed to remove the RC designation. > > (5) Who is responsible for these resources and if it is the > PPMC then each will need discussion. > > (a) https://gallery.echartsjs.com/editor.html > <https://gallery.echartsjs.com/editor.html> > (b) https://twitter.com/EChartsJs > <https://twitter.com/EChartsJs> (where there’s no indication > it’s an ASF project and links to ecomfe.github.io > <http://ecomfe.github.io> <http://ecomfe.github.io/>) > (c) https://www.weibo.com/echarts > <https://www.weibo.com/echarts> (similar) > > (6) Links and pages. > > (a) At the bottom of the main page the link is to a Baidu.com > mailing list. This must be changed to point users and > developers to [email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>>. > (b) Also the GitHub link must point directly to > https://github.com/apache/incubator-echarts/ > <https://github.com/apache/incubator-echarts/> > (c) On the builder.html the email capture should be replaced > with information or link to the project mailing list page. > (d) Contributions and FAQ page should include references to > the mailing lists. > (e) Top links are not coming from the Apache repos. [6] > > (7) User logging is likely not necessary and may be illegal in > many countries and it should be removed in many locations. > These include: > > (a) Looks like user tracking via a hm.baidu.com > <http://hm.baidu.com> <http://hm.baidu.com/> link on several > pages. Please remove. > (b) another tracker in log.js again pointing to > echarts.baidu.com <http://echarts.baidu.com> > <http://echarts.baidu.com/> [7] > > (8) On the Builder please explain which release files are used > and where they are sourced. > > Your Mentors are here to help! > > Hat tip to Justin Mclean for uncovering several of these issues. > > Best Regards, > Dave > > [1] https://www.apache.org/foundation/marks/pmcs#websites > <https://www.apache.org/foundation/marks/pmcs#websites> > [2] https://www.apache.org/foundation/marks/pmcs#navigation > <https://www.apache.org/foundation/marks/pmcs#navigation> > [3] https://www.apache.org/foundation/marks/pmcs#nonapache > <https://www.apache.org/foundation/marks/pmcs#nonapache> > [4] https://www.apache.org/foundation/marks/pmcs#attributions > <https://www.apache.org/foundation/marks/pmcs#attributions> > [5] https://www.apache.org/dev/release-distribution.html > <https://www.apache.org/dev/release-distribution.html> > [6] > > https://raw.githubusercontent.com/ecomfe/echarts/4.1.0/dist/echarts.simple.min.js > > <https://raw.githubusercontent.com/ecomfe/echarts/4.1.0/dist/echarts.simple.min.js> > [7] > > https://github.com/apache/incubator-echarts-website/blob/asf-site/js/log.js > > <https://github.com/apache/incubator-echarts-website/blob/asf-site/js/log.js> > -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
