Re: Question about the website of weex
> > Sorry, did I miss part of the thread here? What "development tools and > others" are you talking about? Under the right side of the page [1], there is a list for weex tool. Except for Playground App, others are developed by third party developers. As such tools are useful and we cannot move all of them to Apache repos, we just list it in the page. [1] https://weex.apache.org/tools/playground.html Best Regards, YorkShen 申远 Jan Piotrowski 于2019年2月28日周四 下午10:13写道： > > Such tools are useful and attractive for users of Weex, and we need a > place > to list such tools in Weex eco system, ... > > Sorry, did I miss part of the thread here? What "development tools and > others" are you talking about? > > > As weex users are Android/iOS/JavaScript developers, they often choose > Gradle/Cocoapods/NPM to install the artifacts instead of source. But I > could list the artifacts and Gradle/Cocoapods/NPM link together in a > webpage later. > > This is of course no problem at all. But the original voting and > release process follows the required Apache way, when it is finished > the binaries or releases can of course be distributed in any way > useful to the users. See here for an example of the Cordova release > process: > https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#otherwise-publish-real-release-to-dist--npm > (pretty overcomplicated because of historical reasons, but you get the > idea) > > Am Do., 28. Feb. 2019 um 04:58 Uhr schrieb Willem Jiang > : > > > > When you send the announcement of the code release, you need to list > > the released artifacts just like this[1]. > > Here is dubbo release guidelines that you can take a look. > > > > [1]http://servicecomb.apache.org/release/ > > [2] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Feb 28, 2019 at 11:46 AM 申远 wrote: > > > > > > > > > > > But we can only host the downloads of the weex project, not the other > > > > tools which are built on top it. > > > > > > > > > Such tools are useful and attractive for users of Weex, and we need a > place > > > to list such tools in Weex eco system, which is important from our > users' > > > point. If there is a better place than https://weex.apache.org/ for > such > > > tools, I can move them. > > > > > > I cannot find the download the weex artifacts but only the weex IDE > > > > and playground. > > > > > > > > > As weex users are Android/iOS/JavaScript developers, they often choose > > > Gradle/Cocoapods/NPM to install the artifacts instead of source. But I > > > could list the artifacts and Gradle/Cocoapods/NPM link together in a > > > webpage later. > > > > > > BTW, once we vote the release, we need to distributed those release > > > > kit to Apache mirrors for the downloads of user. > > > > I don't think we did this step of work after the vote of weex 0.22.0 > > > > > > > > > I will move it later. I think I would propose the next release of weex, > > > which will give me a better understanding of the whole Apache release > > > procedure. > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Willem Jiang 于2019年2月28日周四 上午10:35写道： > > > > > > > Hi York, > > > > > > > > I know weex team put lot of effort to build the whole eco system, > from > > > > the runtime to development tools and others. > > > > But we can only host the downloads of the weex project, not the other > > > > tools which are built on top it. > > > > I cannot find the download the weex artifacts but only the weex IDE > > > > and playground. > > > > > > > > Could you explain it? > > > > > > > > BTW, once we vote the release, we need to distributed those release > > > > kit to Apache mirrors for the downloads of user. > > > > I don't think we did this step of work after the vote of weex > 0.22.0[1] > > > > > > > > [1] > > > > > https://lists.apache.org/thread.html/76f90754258431e48a6d86afedd3862b642320a43e3c96de4326a9cd@%3Cgeneral.incubator.apache.org%3E > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Tue, Feb 26, 2019 at 11:54 AM 申远 wrote: > > > > > > > > > > I will redirect weex.io, weex-project.io and all other domain to > > > > > weex.apache.org ASAP. > > > > > > > > > > Meanwhile, if there is any inappropriate content under apache > domain[1], > > > > > please let me know. > > > > > > > > > > So far, the following content is inappropriate: > > > > > > > > > >- https://weex.apache.org/zh/community/biz-emas.html > > > > > > > > > > > > > > > [1] https://weex.apache.org/ > > > > > > > > > > Best Regards, > > > > > YorkShen > > > > > > > > > > 申远 > > > > > > > > > > > > > > > Dan 于2019年2月26日周二 上午11:35写道： > > > > > > > > > > > sure, that will be remove soon, that’s my mistake, > > > > > > > > > > > > > 在 2019年2月26日，上午11:33，Willem Jiang 写道： > > > > > > > > > > > > > > It's not only about the domain name, but also about
Re: [DISCUSS] can we use weex.io as the short domain name for the apache project
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 于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 申远 : > > > > 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 于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 申远 : > > > > > > > > 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 于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 > > > > > > > > > > 申远 于2019年2月27日周三 上午11:08写道： > > > > > > > > > > > The check has passed now. > > > > > > > > > > > > Best Regards, > > > > > > YorkShen > > > > > > > > > > > > 申远 > > > > > > > > > > > > > > > > > > Willem Jiang 于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 申远 > 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 于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 申远 < > > > > > shenyua...@gmail.com > > > > > > >: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > But until this happens I think an absolutely practical > > > solution > > > > > > > would > > > > > > > > > > > be to use a second host in China with a separate domain > > > that > > >
Re: Question about the website of weex
> Such tools are useful and attractive for users of Weex, and we need a place to list such tools in Weex eco system, ... Sorry, did I miss part of the thread here? What "development tools and others" are you talking about? > As weex users are Android/iOS/JavaScript developers, they often choose Gradle/Cocoapods/NPM to install the artifacts instead of source. But I could list the artifacts and Gradle/Cocoapods/NPM link together in a webpage later. This is of course no problem at all. But the original voting and release process follows the required Apache way, when it is finished the binaries or releases can of course be distributed in any way useful to the users. See here for an example of the Cordova release process: https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#otherwise-publish-real-release-to-dist--npm (pretty overcomplicated because of historical reasons, but you get the idea) Am Do., 28. Feb. 2019 um 04:58 Uhr schrieb Willem Jiang : > > When you send the announcement of the code release, you need to list > the released artifacts just like this[1]. > Here is dubbo release guidelines that you can take a look. > > [1]http://servicecomb.apache.org/release/ > [2] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Feb 28, 2019 at 11:46 AM 申远 wrote: > > > > > > > > But we can only host the downloads of the weex project, not the other > > > tools which are built on top it. > > > > > > Such tools are useful and attractive for users of Weex, and we need a place > > to list such tools in Weex eco system, which is important from our users' > > point. If there is a better place than https://weex.apache.org/ for such > > tools, I can move them. > > > > I cannot find the download the weex artifacts but only the weex IDE > > > and playground. > > > > > > As weex users are Android/iOS/JavaScript developers, they often choose > > Gradle/Cocoapods/NPM to install the artifacts instead of source. But I > > could list the artifacts and Gradle/Cocoapods/NPM link together in a > > webpage later. > > > > BTW, once we vote the release, we need to distributed those release > > > kit to Apache mirrors for the downloads of user. > > > I don't think we did this step of work after the vote of weex 0.22.0 > > > > > > I will move it later. I think I would propose the next release of weex, > > which will give me a better understanding of the whole Apache release > > procedure. > > > > Best Regards, > > YorkShen > > > > 申远 > > > > > > Willem Jiang 于2019年2月28日周四 上午10:35写道： > > > > > Hi York, > > > > > > I know weex team put lot of effort to build the whole eco system, from > > > the runtime to development tools and others. > > > But we can only host the downloads of the weex project, not the other > > > tools which are built on top it. > > > I cannot find the download the weex artifacts but only the weex IDE > > > and playground. > > > > > > Could you explain it? > > > > > > BTW, once we vote the release, we need to distributed those release > > > kit to Apache mirrors for the downloads of user. > > > I don't think we did this step of work after the vote of weex 0.22.0[1] > > > > > > [1] > > > https://lists.apache.org/thread.html/76f90754258431e48a6d86afedd3862b642320a43e3c96de4326a9cd@%3Cgeneral.incubator.apache.org%3E > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Tue, Feb 26, 2019 at 11:54 AM 申远 wrote: > > > > > > > > I will redirect weex.io, weex-project.io and all other domain to > > > > weex.apache.org ASAP. > > > > > > > > Meanwhile, if there is any inappropriate content under apache domain[1], > > > > please let me know. > > > > > > > > So far, the following content is inappropriate: > > > > > > > >- https://weex.apache.org/zh/community/biz-emas.html > > > > > > > > > > > > [1] https://weex.apache.org/ > > > > > > > > Best Regards, > > > > YorkShen > > > > > > > > 申远 > > > > > > > > > > > > Dan 于2019年2月26日周二 上午11:35写道： > > > > > > > > > sure, that will be remove soon, that’s my mistake, > > > > > > > > > > > 在 2019年2月26日，上午11:33，Willem Jiang 写道： > > > > > > > > > > > > It's not only about the domain name, but also about the content[1]. > > > > > > That's the key issue, if we cannot drop clear line between the > > > > > > apache > > > > > > project and commercial product, the user could be confused. > > > > > > > > > > > > [1]http://weex.apache.org/zh/community/biz-emas.html > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > Twitter: willemjiang > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > On Tue, Feb 26, 2019 at 10:57 AM Dan wrote: > > > > > >> > > > > > >> The weex.io doesn't use to redirect the weex.apache.org now, we > > > have > > > > > >> discussed on the mail list about use weex.io as the short domain of > > > > > >> weex apache website, if it's ok, I will redirect all the weex.io > > > page > > > > > to > > > > > >> t
Re: [DISCUSS] can we use weex.io as the short domain name for the apache project
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 申远 : > > 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 于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 申远 : > > > > > > 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 于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 > > > > > > > > 申远 于2019年2月27日周三 上午11:08写道： > > > > > > > > > The check has passed now. > > > > > > > > > > Best Regards, > > > > > YorkShen > > > > > > > > > > 申远 > > > > > > > > > > > > > > > Willem Jiang 于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 申远 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 于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 申远 < > > > > shenyua...@gmail.com > > > > > >: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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. Accordi
