Already done. https://github.com/apache/incubator-weex/projects/1?add_cards_query=is%3Aopen
Best Regards, YorkShen 申远 Jan Piotrowski <[email protected]> 于2019年3月5日周二 下午7:22写道： > Great that we are on the same page here. > > Could someone from the PMC please request a project board on Github > being created at https://github.com/apache/incubator-weex/projects so > I can create a space to track all these TODO items regarding > incubation, compliance etc? We don't want to miss anything there. > Thanks. > > -J > > Am Di., 5. März 2019 um 07:33 Uhr schrieb Dan <[email protected]>: > > > > > Technically speaking, I or other Weex PPMC are not the owner of > weex.io, > > I can not ask EMAS team uses another domain as weex.io is not under my > or > > other PPMC's control. > > > > Yes, this domain name is currently managed in my hands. On the > construction > > of this website, the EMAS team gave us a lot of construction assistance, > so > > we provided a subdomain `emas.weex.io` to give the EMAS team to deploy > > their official website. > > > > > > > Actually, I think > > > https://cn.aliyun.com/solution/emas?spm=a2c7j.-zh-community-biz-emas.0.0.5daac8eecHbyWI > > already is an external website for EMAS - so this can probably just be > > listed under "Tools using Apache Weex" on the new Apache Weex website. > > > > That's ok, I will deploy a page to show this content, all > > the not-really-Apache-Weex things will put on this page, but for the > time > > being, the EMAS page may be mounted on `emas.weex.io` until a more > suitable > > domain name is found, and I will also push them to learn Apache Cordova > and > > Adobe Phonegap to re-edit the page content, I think it will take a > certain > > amount of time, and I can’t do it right away. > > > > Thanks, > > Dan > > > > 申远 <[email protected]> 于2019年3月4日周一 下午8:49写道： > > > > > Technically speaking, I or other Weex PPMC are not the owner of > weex.io, > > > I can not ask EMAS team uses another domain as weex.io is not under > my or > > > other PPMC's control. > > > > > > Actually, I think Dan may have the admin privilege of weex.io. > > > > > > What do you think, Dan? > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Jan Piotrowski <[email protected]> 于2019年3月1日周五 下午6:19写道： > > > > > >> Actually, I think > > >> > > >> > https://cn.aliyun.com/solution/emas?spm=a2c7j.-zh-community-biz-emas.0.0.5daac8eecHbyWI > > >> already is an external website for EMAS - so this can probably just be > > >> listed under "Tools using Apache Weex" on the new Apache Weex website. > > >> > > >> Am Fr., 1. März 2019 um 11:17 Uhr schrieb Jan Piotrowski < > > >> [email protected]>: > > >> > > > >> > I understood that, and that is exactly why EMAS can not be under one > > >> > of the official domains being used for Apache Weex. As weex.io is a > > >> > plain redirect, it will be considered as "part of Apache Weex" by > the > > >> > users. If EMAS uses the same domain, users will make the same > > >> > assumption here - which is not true. > > >> > > > >> > The content from http://emas.weex.io/zh/community/biz-emas.html > should > > >> > be extracted into its own website that does not share anything with > > >> > the Apache Weex project website. Something non Apache-Weex can't > just > > >> > copy the whole website and add a few pages, as this will greatly > > >> > confuse users. (If EMAS was historically available under that > domain, > > >> > of course all the old links can be redirected to its new domains so > > >> > they keep working.) > > >> > > > >> > EMAS can (and should! it's awesome something like that exists) of > > >> > course be listed on the official Apache Weex website as "enterprise > > >> > mobile development solution based on Apache Weex" or similar. > > >> > > > >> > Take Apache Cordova and Adobe Phonegap as an example. Apache Cordova > > >> > is https://cordova.apache.org/. Phonegap is https://phonegap.com/ > and > > >> > builds on Apache Cordova. It mentions Cordova on its website and > links > > >> > to Apache Cordova. > > >> > > > >> > But as with all other not-really-Apache-Weex things, the > > >> > differentiation has to be made 100% clear. Ther should be no > confusion > > >> > for users what is _Apache_ Weex and what is tools for or other > > >> > software built on Weex. > > >> > > > >> > -J > > >> > > > >> > Am Fr., 1. März 2019 um 03:16 Uhr schrieb 申远 <[email protected] > >: > > >> > > > > >> > > Technically speaking, EMAS is an enterprise mobile develop > solution > > >> based > > >> > > on weex, and I think the target users of EMAS are Chinese. > Actually, > > >> there > > >> > > is an entry[1] for EMAS in Chinese document. Besides that, there > is no > > >> > > difference between http://weex.apache.org and > http://emas.weex.io/ . > > >> > > > > >> > > And Weex projcet always declared that http://weex.apache.org or > > >> > > http://weex.io are the official homepage. > > >> > > > > >> > > [1] http://emas.weex.io/zh/community/biz-emas.html > > >> > > > > >> > > Best Regards, > > >> > > YorkShen > > >> > > > > >> > > 申远 > > >> > > > > >> > > > > >> > > Jan Piotrowski <[email protected]> 于2019年2月28日周四 下午10:08写道： > > >> > > > > >> > > > I don't understand. > > >> > > > > > >> > > > A "commercial eco system for weex" should not just mirror the > > >> complete > > >> > > > site, even (and especially!) if they add their own things. > > >> > > > Right now I have no idea what this really is when I go there, so > > >> this > > >> > > > should definitely be cleaned up. > > >> > > > > > >> > > > -J > > >> > > > > > >> > > > Am Do., 28. Feb. 2019 um 04:24 Uhr schrieb 申远 < > [email protected] > > >> >: > > >> > > > > > > >> > > > > EMAS is a commercial eco-system for weex, so this url[1] > should > > >> not be > > >> > > > > redirected to https:/weex.apache.org > > >> > > > > > > >> > > > > I have talked to guys of EMAS, they are using the source code > of > > >> > > > > incubator-weex-site [2] and some third-party content to build > the > > >> > > > website, > > >> > > > > while weex only use incubator-weex-site [2] > > >> > > > > > > >> > > > > [1] http://emas.weex.io/ > > >> > > > > [2] https://github.com/apache/incubator-weex-site/ > > >> > > > > > > >> > > > > Best Regards, > > >> > > > > YorkShen > > >> > > > > > > >> > > > > 申远 > > >> > > > > > > >> > > > > > > >> > > > > Jan Piotrowski <[email protected]> 于2019年2月28日周四 上午5:37写道： > > >> > > > > > > >> > > > > > Nice! > > >> > > > > > > > >> > > > > > Just found http://emas.weex.io/ which is not redirecting > yet. > > >> > > > > > > > >> > > > > > J > > >> > > > > > > > >> > > > > > Am Mi., 27. Feb. 2019 um 07:00 Uhr schrieb 申远 < > > >> [email protected]>: > > >> > > > > > > > > >> > > > > > > http://weex-project.io is also redirected to > > >> http://weex.apache.org > > >> > > > > > > > > >> > > > > > > Except for the following issue, I think we have done the > > >> relaunch > > >> > > > > > procedure > > >> > > > > > > of website: > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > - Google Search Console Account > > >> > > > > > > - Redirect http://weex.apache.org to > > >> https://weex.apache.org > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > Best Regards, > > >> > > > > > > YorkShen > > >> > > > > > > > > >> > > > > > > 申远 > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > Dan <[email protected]> 于2019年2月27日周三 上午11:53写道： > > >> > > > > > > > > >> > > > > > > > > The server should just be a Apache webserver (of > course!) > > >> that > > >> > > > can > > >> > > > > > > > accept .htaccess files to redirect non-http requests. > > >> > > > > > > > Super complicated example from Cordova: > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > >> > > > > > >> > https://github.com/apache/cordova-docs/blob/3c41a7d14192eb26c883c65fc63be303f811474e/www/.htaccess#L118-L130 > > >> > > > > > > > There should be much easier ways to achieve this. > > >> > > > > > > > > > >> > > > > > > > I will take a look and try to make weex.apache.org work > > >> with > > >> > > > non-http. > > >> > > > > > > > > > >> > > > > > > > Thanks, > > >> > > > > > > > Dan > > >> > > > > > > > > > >> > > > > > > > 申远 <[email protected]> 于2019年2月27日周三 上午11:08写道： > > >> > > > > > > > > > >> > > > > > > > > The check has passed now. > > >> > > > > > > > > > > >> > > > > > > > > Best Regards, > > >> > > > > > > > > YorkShen > > >> > > > > > > > > > > >> > > > > > > > > 申远 > > >> > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > Willem Jiang <[email protected]> 于2019年2月22日周五 > > >> 下午8:08写道： > > >> > > > > > > > > > > >> > > > > > > > > > FYI, there is a tool[1] to check if the website is > > >> following > > >> > > > the > > >> > > > > > Apache > > >> > > > > > > > > > rules. > > >> > > > > > > > > > Please take a look and fix them ASAP. The website > > >> issues need > > >> > > > to be > > >> > > > > > > > > > addressed before graducation. > > >> > > > > > > > > > > > >> > > > > > > > > > [1]https://whimsy.apache.org/pods.cgi/project/weex > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > Willem Jiang > > >> > > > > > > > > > > > >> > > > > > > > > > Twitter: willemjiang > > >> > > > > > > > > > Weibo: 姜宁willem > > >> > > > > > > > > > > > >> > > > > > > > > > On Fri, Feb 22, 2019 at 7:58 PM 申远 < > > >> [email protected]> > > >> > > > wrote: > > >> > > > > > > > > > > > > >> > > > > > > > > > > It seems like INFRA is not ok the mirror site in > > >> China. > > >> > > > > > > > > > > > > >> > > > > > > > > > > Anyway, I have updated the content of > > >> > > > https://weex.apache.org/, > > >> > > > > > > > which > > >> > > > > > > > > is > > >> > > > > > > > > > > the same as https://weex.io now. *As there is a > > >> > > > > > > > > > > privilege issue, https://weex-project.io/ < > > >> > > > > > https://weex-project.io/> > > >> > > > > > > > > is > > >> > > > > > > > > > not > > >> > > > > > > > > > > updated yet.* > > >> > > > > > > > > > > > > >> > > > > > > > > > > Later, I will redirect https://weex.io and > > >> > > > > > https://weex-project.io/ > > >> > > > > > > > to > > >> > > > > > > > > > > https://weex.apache.org/ using 302 redirection > and > > >> configure > > >> > > > > > robots. > > >> > > > > > > > > > > > > >> > > > > > > > > > > Feedback of the new design for > > >> https://weex.apache.org/ is > > >> > > > > > welcomed. > > >> > > > > > > > > > > > > >> > > > > > > > > > > Thanks > > >> > > > > > > > > > > > > >> > > > > > > > > > > Best Regards, > > >> > > > > > > > > > > YorkShen > > >> > > > > > > > > > > > > >> > > > > > > > > > > 申远 > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > Jan Piotrowski <[email protected]> > 于2019年2月20日周三 > > >> > > > 下午8:02写道： > > >> > > > > > > > > > > > > >> > > > > > > > > > > > Good question comment you posted on the INFRA > post. > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > I hope they will agree, that there is no > problem at > > >> all as > > >> > > > > > long as > > >> > > > > > > > > the > > >> > > > > > > > > > > > official website is at weex.apache.org. > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > -J > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > Am Mi., 20. Feb. 2019 um 09:48 Uhr schrieb 申远 < > > >> > > > > > > > [email protected] > > >> > > > > > > > > >: > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > But until this happens I think an absolutely > > >> practical > > >> > > > > > solution > > >> > > > > > > > > > would > > >> > > > > > > > > > > > > > be to use a second host in China with a > > >> separate domain > > >> > > > > > that > > >> > > > > > > > can > > >> > > > > > > > > > > > > > provide better speeds to Chinese users. It > just > > >> has to > > >> > > > > > show the > > >> > > > > > > > > > exact > > >> > > > > > > > > > > > > > same content as the official site (and be > > >> hidden from > > >> > > > > > search > > >> > > > > > > > > > engines > > >> > > > > > > > > > > > > > via robots.txt to not confuse them). INFRA > > >> should have > > >> > > > no > > >> > > > > > real > > >> > > > > > > > > > problem > > >> > > > > > > > > > > > > > with that (as it is a appropriate workaround > > >> for their > > >> > > > slow > > >> > > > > > > > > > response > > >> > > > > > > > > > > > > > times in China - and no branding stuff is > > >> ignored). > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > 1. Deploying the same content to two different > > >> host and > > >> > > > > > domains > > >> > > > > > > > is > > >> > > > > > > > > > what > > >> > > > > > > > > > > > we > > >> > > > > > > > > > > > > are planning to do until we understand it may > > >> still > > >> > > > break one > > >> > > > > > > > > domain > > >> > > > > > > > > > > > rule. > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > 2. According to > > >> > > > > > > > https://issues.apache.org/jira/browse/INFRA-17872 > > >> > > > > > > > > , > > >> > > > > > > > > > I > > >> > > > > > > > > > > > think > > >> > > > > > > > > > > > > INFRA have different point of view on separate > > >> domain > > >> > > > with > > >> > > > > > same > > >> > > > > > > > > > content. > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > 3. Personally speaking, I understand a world > wide > > >> CDN is > > >> > > > not > > >> > > > > > > > > > practical > > >> > > > > > > > > > > > now > > >> > > > > > > > > > > > > and sometimes one may give up a better > engineer > > >> solution > > >> > > > due > > >> > > > > > to > > >> > > > > > > > law > > >> > > > > > > > > > > > issue. > > >> > > > > > > > > > > > > From user points, we need to give a brief > > >> explanation of > > >> > > > the > > >> > > > > > > > > latency > > >> > > > > > > > > > > > > problem. > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > Best Regards, > > >> > > > > > > > > > > > > YorkShen > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > 申远 > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > Jan Piotrowski <[email protected]> > > >> 于2019年2月20日周三 > > >> > > > > > 上午2:24写道： > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Uh, the _domain name_ is not actually at all > > >> related > > >> > > > to the > > >> > > > > > > > speed > > >> > > > > > > > > > of > > >> > > > > > > > > > > > > > the site - the _hosting_ is. > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > My results for those two domains from > Germany, > > >> Berlin > > >> > > > for > > >> > > > > > > > > example: > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > C:\Users\Jan>ping weex.io > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Pinging weex.io [47.75.160.176] with 32 > bytes > > >> of data: > > >> > > > > > > > > > > > > > Reply from 47.75.160.176: bytes=32 > time=327ms > > >> TTL=46 > > >> > > > > > > > > > > > > > Reply from 47.75.160.176: bytes=32 > time=327ms > > >> TTL=46 > > >> > > > > > > > > > > > > > Reply from 47.75.160.176: bytes=32 > time=327ms > > >> TTL=46 > > >> > > > > > > > > > > > > > Reply from 47.75.160.176: bytes=32 > time=335ms > > >> TTL=46 > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Ping statistics for 47.75.160.176: > > >> > > > > > > > > > > > > > Packets: Sent = 4, Received = 4, Lost = > 0 > > >> (0% > > >> > > > loss), > > >> > > > > > > > > > > > > > Approximate round trip times in > milli-seconds: > > >> > > > > > > > > > > > > > Minimum = 327ms, Maximum = 335ms, > Average = > > >> 329ms > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > C:\Users\Jan>ping weex.apache.org > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Pinging weex.apache.org > [2a01:4f9:2a:185f::2] > > >> with 32 > > >> > > > > > bytes of > > >> > > > > > > > > > data: > > >> > > > > > > > > > > > > > Reply from 2a01:4f9:2a:185f::2: time=46ms > > >> > > > > > > > > > > > > > Reply from 2a01:4f9:2a:185f::2: time=46ms > > >> > > > > > > > > > > > > > Reply from 2a01:4f9:2a:185f::2: time=49ms > > >> > > > > > > > > > > > > > Reply from 2a01:4f9:2a:185f::2: time=46ms > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Ping statistics for 2a01:4f9:2a:185f::2: > > >> > > > > > > > > > > > > > Packets: Sent = 4, Received = 4, Lost = > 0 > > >> (0% > > >> > > > loss), > > >> > > > > > > > > > > > > > Approximate round trip times in > milli-seconds: > > >> > > > > > > > > > > > > > Minimum = 46ms, Maximum = 49ms, Average > = > > >> 46ms > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > So you should be aware that the actual > problem > > >> (Apache > > >> > > > > > server > > >> > > > > > > > is > > >> > > > > > > > > > slow > > >> > > > > > > > > > > > > > from China) is a different one that is now > > >> discussed > > >> > > > with > > >> > > > > > INFRA > > >> > > > > > > > > > (Can > > >> > > > > > > > > > > > > > project use a different domain). > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > The only real solution is for INFRA to use a > > >> world > > >> > > > wide CDN > > >> > > > > > > > that > > >> > > > > > > > > is > > >> > > > > > > > > > > > > > fast everywhere. > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > But until this happens I think an absolutely > > >> practical > > >> > > > > > solution > > >> > > > > > > > > > would > > >> > > > > > > > > > > > > > be to use a second host in China with a > > >> separate domain > > >> > > > > > that > > >> > > > > > > > can > > >> > > > > > > > > > > > > > provide better speeds to Chinese users. It > just > > >> has to > > >> > > > > > show the > > >> > > > > > > > > > exact > > >> > > > > > > > > > > > > > same content as the official site (and be > > >> hidden from > > >> > > > > > search > > >> > > > > > > > > > engines > > >> > > > > > > > > > > > > > via robots.txt to not confuse them). INFRA > > >> should have > > >> > > > no > > >> > > > > > real > > >> > > > > > > > > > problem > > >> > > > > > > > > > > > > > with that (as it is a appropriate workaround > > >> for their > > >> > > > slow > > >> > > > > > > > > > response > > >> > > > > > > > > > > > > > times in China - and no branding stuff is > > >> ignored). > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > -J > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Am Di., 19. Feb. 2019 um 12:57 Uhr schrieb > Myrle > > >> > > > Krantz < > > >> > > > > > > > > > > > [email protected] > > >> > > > > > > > > > > > > > >: > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > I've created an INFRA ticket: > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > >> https://issues.apache.org/jira/browse/INFRA-17872 > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > I won't promise that INFRA can solve > this, but > > >> > > > hopefully > > >> > > > > > > > > they'll > > >> > > > > > > > > > at > > >> > > > > > > > > > > > least > > >> > > > > > > > > > > > > > > look at it. > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Feel free to add any details you have. > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Best Regards, > > >> > > > > > > > > > > > > > > Myrle > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > On Tue, Feb 19, 2019 at 7:18 AM Dan < > > >> > > > [email protected] > > >> > > > > > > > > >> > > > > > > > > wrote: > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > Thanks, Jan, I will take a look at this. > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > Jan Piotrowski <[email protected]> > > >> > > > 于2019年2月18日周一 > > >> > > > > > > > > 下午6:15写道： > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > Cordova uses the npm package > `insight` for > > >> > > > > > telemetry, you > > >> > > > > > > > > > can see > > >> > > > > > > > > > > > > > more > > >> > > > > > > > > > > > > > > > > in these two files: > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > >> https://github.com/apache/cordova-cli/blob/master/src/telemetry.js > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > >> https://github.com/apache/cordova-cli/blob/master/src/cli.js > > >> > > > > > > > > > > > > > > > > The data being tracked is very > limited, > > >> and all > > >> > > > done > > >> > > > > > only > > >> > > > > > > > > > after > > >> > > > > > > > > > > > > > > > > explicit opt-in by the user. (You get > a > > >> prompt > > >> > > > when > > >> > > > > > you > > >> > > > > > > > > first > > >> > > > > > > > > > > > install > > >> > > > > > > > > > > > > > > > > Cordova). > > >> > > > > > > > > > > > > > > > > The dashboard itself is built on the > > >> Google > > >> > > > Analytics > > >> > > > > > > > data > > >> > > > > > > > > > source > > >> > > > > > > > > > > > > > that > > >> > > > > > > > > > > > > > > > > collects the data for pretty graphs. > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > One problem: I am under the impression > > >> that > > >> > > > Google > > >> > > > > > > > > Analytics > > >> > > > > > > > > > is > > >> > > > > > > > > > > > > > > > > blocked for good parts of Chinese > users, > > >> so > > >> > > > Cordova's > > >> > > > > > > > data > > >> > > > > > > > > > > > regarding > > >> > > > > > > > > > > > > > > > > usage in China is probably very > broken. > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > -J > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > Am Mo., 18. Feb. 2019 um 08:29 Uhr > > >> schrieb Dan < > > >> > > > > > > > > > > > [email protected] > > >> > > > > > > > > > > > > > >: > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > Hi Jan, > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > Thanks for getting back to me. > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > Your opinion has helped us a lot. We > > >> will > > >> > > > migrate > > >> > > > > > the > > >> > > > > > > > > > > > deployment > > >> > > > > > > > > > > > > > of the > > >> > > > > > > > > > > > > > > > > > document to weex.apache.org in > these > > >> two days. > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > BTW, do you know the detail about > how > > >> to do the > > >> > > > > > > > > user-track > > >> > > > > > > > > > > > bellow > > >> > > > > > > > > > > > > > the > > >> > > > > > > > > > > > > > > > > > apache way, I know the Cordova has > > >> > > > > > > > telemetry.cordova.io > > >> > > > > > > > > to > > >> > > > > > > > > > > > record > > >> > > > > > > > > > > > > > it, > > >> > > > > > > > > > > > > > > > > and > > >> > > > > > > > > > > > > > > > > > we also want to record the user's > > >> behavior in > > >> > > > the > > >> > > > > > > > > > weex-toolkit > > >> > > > > > > > > > > > to > > >> > > > > > > > > > > > > > help > > >> > > > > > > > > > > > > > > > us > > >> > > > > > > > > > > > > > > > > > better improve the tool experience. > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > Thanks, > > >> > > > > > > > > > > > > > > > > > Dan > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > Jan Piotrowski < > [email protected]> > > >> > > > > > 于2019年2月15日周五 > > >> > > > > > > > > > 下午7:42写道： > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > Besides what the rules say (which > I > > >> don't > > >> > > > really > > >> > > > > > > > know): > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > An apache.org domain has an > > >> incredible > > >> > > > effect on > > >> > > > > > > > > > > > credibility and > > >> > > > > > > > > > > > > > > > > > > trust. Apache is a really strong > > >> brand with > > >> > > > > > > > developers, > > >> > > > > > > > > > and > > >> > > > > > > > > > > > > > > > especially > > >> > > > > > > > > > > > > > > > > > > new projects like Weex can benefit > > >> from that. > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > (The project will be called > "Apache > > >> Weex" > > >> > > > anyway) > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > Apache Cordova owns the > cordova.io > > >> domain > > >> > > > and > > >> > > > > > uses > > >> > > > > > > > it > > >> > > > > > > > > > as a > > >> > > > > > > > > > > > > > redirect > > >> > > > > > > > > > > > > > > > to > > >> > > > > > > > > > > > > > > > > > > cordova.apache.org. That way we > can > > >> still > > >> > > > tell > > >> > > > > > > > people > > >> > > > > > > > > > to go > > >> > > > > > > > > > > > to > > >> > > > > > > > > > > > > > > > > > > "cordova.io", but on Google and > in > > >> user's > > >> > > > > > browser > > >> > > > > > > > > > everything > > >> > > > > > > > > > > > > > happens > > >> > > > > > > > > > > > > > > > > > > on apache.cordova.org. We also > have > > >> loads of > > >> > > > > > > > > subdomains > > >> > > > > > > > > > like > > >> > > > > > > > > > > > > > > > > > > blog.cordova.io issues.cordova.io > , > > >> > > > > > slack.cordova.io, > > >> > > > > > > > > > > > > > > > > > > telemetry.cordova.io and so on as > > >> shortcuts > > >> > > > > > which is > > >> > > > > > > > > > very > > >> > > > > > > > > > > > handy. > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > Using the domains you mentioned, > > >> weex.io > > >> > > > could > > >> > > > > > > > > redirect > > >> > > > > > > > > > to > > >> > > > > > > > > > > > > > > > > > > weex.apache.org, docs.weex.io > > >> redirects to > > >> > > > > > > > > > > > weex.apache.org/docs, > > >> > > > > > > > > > > > > > > > > > > blog.weex.io to > weex.apache.org/blog > > >> and so > > >> > > > on. > > >> > > > > > Then > > >> > > > > > > > > > > > cn.weex.io > > >> > > > > > > > > > > > > > > > could > > >> > > > > > > > > > > > > > > > > > > redirect to weex-project.io for > > >> easier > > >> > > > finding > > >> > > > > > of > > >> > > > > > > > the > > >> > > > > > > > > > > > Chinese > > >> > > > > > > > > > > > > > > > domain. > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > -J > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > On 15. Feb 2019, at 07:38, Dan < > > >> > > > > > > > [email protected]> > > >> > > > > > > > > > > > wrote: > > >> > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > Hi, Myrle/Willem, > > >> > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > Currently, we have a domain > name of > > >> > > > weex.io > > >> > > > > > and > > >> > > > > > > > want > > >> > > > > > > > > > to > > >> > > > > > > > > > > > use > > >> > > > > > > > > > > > > > it to > > >> > > > > > > > > > > > > > > > > > > replace > > >> > > > > > > > > > > > > > > > > > > > the previous weex-project.io > > >> domain name > > >> > > > for > > >> > > > > > the > > >> > > > > > > > > > following > > >> > > > > > > > > > > > > > > > reasons: > > >> > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > 1. The domain name is shorter > and > > >> easier to > > >> > > > > > > > remember. > > >> > > > > > > > > > > > > > > > > > > > 2. Apache's website has slower > > >> access to > > >> > > > the > > >> > > > > > > > > developer > > >> > > > > > > > > > in > > >> > > > > > > > > > > > > > China, so > > >> > > > > > > > > > > > > > > > > there > > >> > > > > > > > > > > > > > > > > > > > is a mirror website > weex-project.io > > >> for > > >> > > > > > Chinese > > >> > > > > > > > > > developer. > > >> > > > > > > > > > > > > > > > > > > > 3. We expect to support https on > > >> this > > >> > > > website > > >> > > > > > and > > >> > > > > > > > > > support > > >> > > > > > > > > > > > some > > >> > > > > > > > > > > > > > of > > >> > > > > > > > > > > > > > > > > our own > > >> > > > > > > > > > > > > > > > > > > > server functions, such as Q&A > > >> robots, > > >> > > > article > > >> > > > > > blog > > >> > > > > > > > > > posts, > > >> > > > > > > > > > > > etc. > > >> > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > I would like to ask if apache > has > > >> any > > >> > > > > > restrictions > > >> > > > > > > > on > > >> > > > > > > > > > this > > >> > > > > > > > > > > > > > > > > third-party > > >> > > > > > > > > > > > > > > > > > > > domain name, and look forward to > > >> hearing > > >> > > > from > > >> > > > > > you. > > >> > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > Thanks, > > >> > > > > > > > > > > > > > > > > > > > Dan > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > >> > > > > > >> > > > >
