Re: [DISCUSS] Language used in Mail/Github/etc..

[申远]

After considering the current situation and the international goal of Weex,
I'd like to answer Chinese question both in English and Chinese with the
following template. I will give responses with the following template for
one month or more, after that maybe we will have a better idea of the
language problem.

感谢你的反馈，Weex目前是隶属于Apache Software
Foundation的项目，因此在Gtihub渠道我们鼓励使用英文反馈问题。下面我将使用Google
Trasnlate将你的问题翻译成英语，并以英语回答。

Question description here


Answer The question here.

Best Regards,
YorkShen

申远


Jan Piotrowski  于2019年2月22日周五 下午9:48写道：

> After further thinking about it I think I agree with Myrle:
> If you can answer a Chinese issue in Chinese, just do so.
> If you want, you can translate both question and answer to English
> manually or automatically as well.
> I don't read any Chinese, so I would definitely have to translate to
> English and then write my response in English. As a service (and
> respect) to the user I then also might translate my response to
> Chinese automatically and post that as well.
>
> Real rules on languages will probably only be required for formal
> discussions and votes here on the mailing list.
>
> -J
>
> Am Fr., 22. Feb. 2019 um 09:38 Uhr schrieb Willem Jiang
> :
> >
> > It may relate to audience which we are target. If the target audience
> > doesn't speak English it could be challenge for him to get the answer
> > in English. It's natural to fill strange if you just see a bunch of
> > Chinese sitting together using their unfluent English talk to each
> > other.
> >
> > But as you may not know there could be other people who try to find
> > information in the mailing list by using the search engine.   As an
> > apache project, there are lots of potential users who speak English,
> > using English to answer the question could help them to understand the
> > who pictures more easily.
> >
> > Most of Chinese developer can read and write English document, as we
> > spend more than 6 years to study English. I don't think it could be a
> > blocker for us to build the community by answering the question in
> > English. But we need to keep in mind that the discussion we have is
> > not just for us, it's could for the community to catch up later.
> >
> > FYI, there are some discussions[1] years ago about using IM (such as
> > QQ and WeChat) and Chinese, you may take a look at them.
> >
> > [1]
> https://www.mail-archive.com/general@incubator.apache.org/msg57192.html
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Feb 22, 2019 at 4:05 PM 申远  wrote:
> > >
> > > >
> > > > I saw some people using Google Translate to translate the question,
> > > > then repost the question in English before answering. That makes it
> > > > clear(er), that English is the preferred language and also allows
> > > > people like me to participate.
> > >
> > >
> > > I used to paste the result of Google Translate from Chinese question to
> > > English, then answer it in English, until I realized that the users who
> > > post the question may not understand my answer in English, which
> doesn't
> > > fulfill the goal of helping user at all. Besides, from our users'
> point,
> > > choosing a language the original user may not understand by
> deliberately
> > > may be a arrogant behavior.
> > >
> > > Maybe I should answer Chinese Question with English and then Google
> > > translate back to English, which is still a little wired and
> complicated
> > > though.
> > >
> > > Best Regards,
> > > YorkShen
> > >
> > > 申远
> > >
> > >
> > > Willem Jiang  于2019年2月22日周五 上午10:48写道：
> > >
> > > > I think using the English to discuss is consider for more audiences
> > > > across the world,  with the help of translator service it's not big
> > > > challenge for the average chinese developer to get involved.
> > > > We could set up a rule in the mailing list or gitter to discuss the
> > > > question in English. From my experience it's a big first step to
> build
> > > > the  internationalized community.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Thu, Feb 21, 2019 at 12:21 PM 申远  wrote:
> > > > >
> > > > > As we all know, there are many users of Weex are Chinese.
> > > > >
> > > > > As a result, there are many user expresses their opinion using
> Chinese in
> > > > > Github . What
> should
> > > > we do
> > > > > under this situation?
> > > > >
> > > > > 1. Answering their question with English, which is wired as
> original post
> > > > > is Chinese. Moreover, it may be a little arrogant as answering
> Chinese
> > > > > question with English shows the person written the answer
> understand
> > > > > Chinese but somehow choose a language(English) deliberately the
> original
> > > > > poster may not understand.
> > > > >
> > > > > 2. Answering questions with Chinese, which is a easy work for me
> and
> > > > other
> > > > > Chinese users. But other users that who doesn't 

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[Dan]

Hi, Jan

> I am fine with editing any .yml or .json files that include the
content, but the headline "Cross Platforms" has to come from somewhere
in this repo, right?

I have created a pull request to support edit homepage date, see  [docs]
support edit homepage data
, after the pull
request merged, you can edit the data file to change the homepage content.

> One thing I would advise is that you make all non-https requests
redirect to the https version as soon as possible.

we can not control the Apache server to force redirect all non-https
requests to the https version, so, now we can just replace manually, I will
check it through automated means.

> Old links that are listed in Google like e.g.
https://weex.apache.org/references/ also _have_ to be redirected to
the content's new location as quickly as possible. That is one of
those things that destroys existing traffic to websites on relaunches.
(https://www.google.com/search?client=firefox-b-d=site%3Aweex.apache.org
- 217 pages that show mostly a 404 right now)

I am do it now, will be fixed today.

> Have you already created a Google Search Console account for the site?
If not, someone should do so. I would be happy to look at the reports
being generated and give advice how to fix any possible problems.

After finish all the below jobs, I will study how to deploy  Google Search
Console account on the site.

Thanks,
Dan

Jan Piotrowski  于2019年2月25日周一 下午9:18写道：

> I am fine with editing any .yml or .json files that include the
> content, but the headline "Cross Platforms" has to come from somewhere
> in this repo, right?
>
> One thing I would advise is that you make all non-https requests
> redirect to the https version as soon as possible.
>
> Old links that are listed in Google like e.g.
> https://weex.apache.org/references/ also _have_ to be redirected to
> the content's new location as quickly as possible. That is one of
> those things that destroys existing traffic to websites on relaunches.
> (https://www.google.com/search?client=firefox-b-d=site%3Aweex.apache.org
> - 217 pages that show mostly a 404 right now)
>
> Have you already created a Google Search Console account for the site?
> If not, someone should do so. I would be happy to look at the reports
> being generated and give advice how to fix any possible problems.
>
> -J
>
> Am Mo., 25. Feb. 2019 um 12:50 Uhr schrieb Dan :
> >
> > Hi, Jan
> >
> > We deployed an automated server build system for building the content of
> > weex.apache.org, the homepage is not a pure HTML file that can be easily
> > edited.
> >
> > If you have any advice about this page, please let me know, I will
> improve
> > it later.
> >
> > Maybe some of the content can be built from a data file on the
> > incubator-weex-site 
> repo.
> >
> > Thanks,
> > Dan
> >
> > Jan Piotrowski  于2019年2月25日周一 下午6:11写道：
> >
> > > Yeah, the homepage is unfortunately missing that button ;)
> > > As the content is still in the `draft` branch, I also can't just
> > > search for a sub string of the headlines to fine the page that
> > > represents the homepage - could you please point me to the correct
> > > file?
> > >
> > > -J
> > >
> > > Am Mo., 25. Feb. 2019 um 10:59 Uhr schrieb 申远 :
> > > >
> > > > There are two options.
> > > >
> > > > 1. On the bottom of each page, there is a button called *Edit this
> > > page.* Just
> > > > click it, then you will be navigated to the right branch and file on
> the
> > > > github.
> > > > 2. If you prefer do things manually, Go to draft branch of
> > > > https://github.com/apache/incubator-weex-site/tree/draft.
> > > >
> > > > I normally prefer the first choice unless I have to write a totally
> new
> > > > article.
> > > >
> > > > BTW, the following approach is described in the docs, too. Ref
> > > >
> > >
> https://weex.apache.org/guide/contribute/how-to-contribute.html#contribute-code-or-document
> > > >
> > > > Best Regards,
> > > > YorkShen
> > > >
> > > > 申远
> > > >
> > > >
> > > > Jan Piotrowski  于2019年2月25日周一 下午5:46写道：
> > > >
> > > > > Nice.
> > > > >
> > > > > Which is the repository and branch to send PRs with typo fixes etc
> to?
> > > > >
> > > > > Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 <
> shenyua...@gmail.com>:
> > > > > >
> > > > > > Hi, there
> > > > > >
> > > > > > I had fix the 404 error and updated the website of
> weex.apache.org,
> > > > > which
> > > > > > content should be the same as weex.io now. I will configure a
> 302
> > > > > > redirection later, which will make all the mirror site redirects
> to
> > > > > > weex.apache.org.
> > > > > >
> > > > > > Best Regards,
> > > > > > YorkShen
> > > > > >
> > > > > > 申远
> > > > > >
> > > > > >
> > > > > > 申远  于2019年2月22日周五 下午8:46写道：
> > > > > >
> > > > > > > As there is a wired 404 problem under Apache domain, which
> works
> > > fine
> > > > > > > under weex.io domain, I have to revert all the changes on
> > > > > 

Re: Question about the website of weex

[申远]

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
> >> the weex.apache.org.
> >>
> >> Thanks,
> >> Dan
> >>
> >> Willem Jiang  于2019年2月26日周二 上午10:51写道：
> >>
> >>> There is angry user github issue[1] about he wants his use case code
> back.
> >>>
> >>> So I get a close look of the weex.io website, it looks there are some
> >>> Alibaba's content[2] in the site.  As weex is donated to ASF, and ASF
> >>> in vendor neutral organization. We cannot mix the commercial content
> >>> with Apache project in the same site.
> >>>
> >>> I'm not sure if the PPMC member are knowing about this things, can you
> >>> explain it and let work on an solution together.
> >>>
> >>> [1]https://github.com/apache/incubator-weex-site/issues/325
> >>> [2]http://emas.weex.io/zh/community/biz-emas.html
> >>>
> >>> Willem Jiang
> >>>
> >>> Twitter: willemjiang
> >>> Weibo: 姜宁willem
> >>>
>
>

Re: Question about the website of weex

[Dan]

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
>> the weex.apache.org.
>> 
>> Thanks,
>> Dan
>> 
>> Willem Jiang  于2019年2月26日周二 上午10:51写道：
>> 
>>> There is angry user github issue[1] about he wants his use case code back.
>>> 
>>> So I get a close look of the weex.io website, it looks there are some
>>> Alibaba's content[2] in the site.  As weex is donated to ASF, and ASF
>>> in vendor neutral organization. We cannot mix the commercial content
>>> with Apache project in the same site.
>>> 
>>> I'm not sure if the PPMC member are knowing about this things, can you
>>> explain it and let work on an solution together.
>>> 
>>> [1]https://github.com/apache/incubator-weex-site/issues/325
>>> [2]http://emas.weex.io/zh/community/biz-emas.html
>>> 
>>> Willem Jiang
>>> 
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>> 

Re: Question about the website of weex

[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
> the weex.apache.org.
>
> Thanks,
> Dan
>
> Willem Jiang  于2019年2月26日周二 上午10:51写道：
>
> > There is angry user github issue[1] about he wants his use case code back.
> >
> > So I get a close look of the weex.io website, it looks there are some
> > Alibaba's content[2] in the site.  As weex is donated to ASF, and ASF
> > in vendor neutral organization. We cannot mix the commercial content
> > with Apache project in the same site.
> >
> > I'm not sure if the PPMC member are knowing about this things, can you
> > explain it and let work on an solution together.
> >
> > [1]https://github.com/apache/incubator-weex-site/issues/325
> > [2]http://emas.weex.io/zh/community/biz-emas.html
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >

Re: Question about the website of weex

[Dan]

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
the weex.apache.org.

Thanks,
Dan

Willem Jiang  于2019年2月26日周二 上午10:51写道：

> There is angry user github issue[1] about he wants his use case code back.
>
> So I get a close look of the weex.io website, it looks there are some
> Alibaba's content[2] in the site.  As weex is donated to ASF, and ASF
> in vendor neutral organization. We cannot mix the commercial content
> with Apache project in the same site.
>
> I'm not sure if the PPMC member are knowing about this things, can you
> explain it and let work on an solution together.
>
> [1]https://github.com/apache/incubator-weex-site/issues/325
> [2]http://emas.weex.io/zh/community/biz-emas.html
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>

Question about the website of weex

[Willem Jiang]

There is angry user github issue[1] about he wants his use case code back.

So I get a close look of the weex.io website, it looks there are some
Alibaba's content[2] in the site.  As weex is donated to ASF, and ASF
in vendor neutral organization. We cannot mix the commercial content
with Apache project in the same site.

I'm not sure if the PPMC member are knowing about this things, can you
explain it and let work on an solution together.

[1]https://github.com/apache/incubator-weex-site/issues/325
[2]http://emas.weex.io/zh/community/biz-emas.html

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[Jan Piotrowski]

I am fine with editing any .yml or .json files that include the
content, but the headline "Cross Platforms" has to come from somewhere
in this repo, right?

One thing I would advise is that you make all non-https requests
redirect to the https version as soon as possible.

Old links that are listed in Google like e.g.
https://weex.apache.org/references/ also _have_ to be redirected to
the content's new location as quickly as possible. That is one of
those things that destroys existing traffic to websites on relaunches.
(https://www.google.com/search?client=firefox-b-d=site%3Aweex.apache.org
- 217 pages that show mostly a 404 right now)

Have you already created a Google Search Console account for the site?
If not, someone should do so. I would be happy to look at the reports
being generated and give advice how to fix any possible problems.

-J

Am Mo., 25. Feb. 2019 um 12:50 Uhr schrieb Dan :
>
> Hi, Jan
>
> We deployed an automated server build system for building the content of
> weex.apache.org, the homepage is not a pure HTML file that can be easily
> edited.
>
> If you have any advice about this page, please let me know, I will improve
> it later.
>
> Maybe some of the content can be built from a data file on the
> incubator-weex-site  repo.
>
> Thanks,
> Dan
>
> Jan Piotrowski  于2019年2月25日周一 下午6:11写道：
>
> > Yeah, the homepage is unfortunately missing that button ;)
> > As the content is still in the `draft` branch, I also can't just
> > search for a sub string of the headlines to fine the page that
> > represents the homepage - could you please point me to the correct
> > file?
> >
> > -J
> >
> > Am Mo., 25. Feb. 2019 um 10:59 Uhr schrieb 申远 :
> > >
> > > There are two options.
> > >
> > > 1. On the bottom of each page, there is a button called *Edit this
> > page.* Just
> > > click it, then you will be navigated to the right branch and file on the
> > > github.
> > > 2. If you prefer do things manually, Go to draft branch of
> > > https://github.com/apache/incubator-weex-site/tree/draft.
> > >
> > > I normally prefer the first choice unless I have to write a totally new
> > > article.
> > >
> > > BTW, the following approach is described in the docs, too. Ref
> > >
> > https://weex.apache.org/guide/contribute/how-to-contribute.html#contribute-code-or-document
> > >
> > > Best Regards,
> > > YorkShen
> > >
> > > 申远
> > >
> > >
> > > Jan Piotrowski  于2019年2月25日周一 下午5:46写道：
> > >
> > > > Nice.
> > > >
> > > > Which is the repository and branch to send PRs with typo fixes etc to?
> > > >
> > > > Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 :
> > > > >
> > > > > Hi, there
> > > > >
> > > > > I had fix the 404 error and updated the website of weex.apache.org,
> > > > which
> > > > > content should be the same as weex.io now. I will configure a 302
> > > > > redirection later, which will make all the mirror site redirects to
> > > > > weex.apache.org.
> > > > >
> > > > > Best Regards,
> > > > > YorkShen
> > > > >
> > > > > 申远
> > > > >
> > > > >
> > > > > 申远  于2019年2月22日周五 下午8:46写道：
> > > > >
> > > > > > As there is a wired 404 problem under Apache domain, which works
> > fine
> > > > > > under weex.io domain, I have to revert all the changes on
> > > > weex.apache.org .
> > > > > > I will publish it again when I find out what is happening here.
> > > > Meanwhile,
> > > > > > one may take https://weex.io as the preview version of new weex
> > > > website
> > > > > > before the republish.
> > > > > >
> > > > > > Sorry for the inconvenience.
> > > > > >
> > > > > > 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.
> > > > > >> >

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[Dan]

Hi, Jan

We deployed an automated server build system for building the content of
weex.apache.org, the homepage is not a pure HTML file that can be easily
edited.

If you have any advice about this page, please let me know, I will improve
it later.

Maybe some of the content can be built from a data file on the
incubator-weex-site  repo.

Thanks,
Dan

Jan Piotrowski  于2019年2月25日周一 下午6:11写道：

> Yeah, the homepage is unfortunately missing that button ;)
> As the content is still in the `draft` branch, I also can't just
> search for a sub string of the headlines to fine the page that
> represents the homepage - could you please point me to the correct
> file?
>
> -J
>
> Am Mo., 25. Feb. 2019 um 10:59 Uhr schrieb 申远 :
> >
> > There are two options.
> >
> > 1. On the bottom of each page, there is a button called *Edit this
> page.* Just
> > click it, then you will be navigated to the right branch and file on the
> > github.
> > 2. If you prefer do things manually, Go to draft branch of
> > https://github.com/apache/incubator-weex-site/tree/draft.
> >
> > I normally prefer the first choice unless I have to write a totally new
> > article.
> >
> > BTW, the following approach is described in the docs, too. Ref
> >
> https://weex.apache.org/guide/contribute/how-to-contribute.html#contribute-code-or-document
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > Jan Piotrowski  于2019年2月25日周一 下午5:46写道：
> >
> > > Nice.
> > >
> > > Which is the repository and branch to send PRs with typo fixes etc to?
> > >
> > > Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 :
> > > >
> > > > Hi, there
> > > >
> > > > I had fix the 404 error and updated the website of weex.apache.org,
> > > which
> > > > content should be the same as weex.io now. I will configure a 302
> > > > redirection later, which will make all the mirror site redirects to
> > > > weex.apache.org.
> > > >
> > > > Best Regards,
> > > > YorkShen
> > > >
> > > > 申远
> > > >
> > > >
> > > > 申远  于2019年2月22日周五 下午8:46写道：
> > > >
> > > > > As there is a wired 404 problem under Apache domain, which works
> fine
> > > > > under weex.io domain, I have to revert all the changes on
> > > weex.apache.org .
> > > > > I will publish it again when I find out what is happening here.
> > > Meanwhile,
> > > > > one may take https://weex.io as the preview version of new weex
> > > website
> > > > > before the republish.
> > > > >
> > > > > Sorry for the inconvenience.
> > > > >
> > > > > 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 

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[Jan Piotrowski]

Yeah, the homepage is unfortunately missing that button ;)
As the content is still in the `draft` branch, I also can't just
search for a sub string of the headlines to fine the page that
represents the homepage - could you please point me to the correct
file?

-J

Am Mo., 25. Feb. 2019 um 10:59 Uhr schrieb 申远 :
>
> There are two options.
>
> 1. On the bottom of each page, there is a button called *Edit this page.* Just
> click it, then you will be navigated to the right branch and file on the
> github.
> 2. If you prefer do things manually, Go to draft branch of
> https://github.com/apache/incubator-weex-site/tree/draft.
>
> I normally prefer the first choice unless I have to write a totally new
> article.
>
> BTW, the following approach is described in the docs, too. Ref
> https://weex.apache.org/guide/contribute/how-to-contribute.html#contribute-code-or-document
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski  于2019年2月25日周一 下午5:46写道：
>
> > Nice.
> >
> > Which is the repository and branch to send PRs with typo fixes etc to?
> >
> > Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 :
> > >
> > > Hi, there
> > >
> > > I had fix the 404 error and updated the website of weex.apache.org,
> > which
> > > content should be the same as weex.io now. I will configure a 302
> > > redirection later, which will make all the mirror site redirects to
> > > weex.apache.org.
> > >
> > > Best Regards,
> > > YorkShen
> > >
> > > 申远
> > >
> > >
> > > 申远  于2019年2月22日周五 下午8:46写道：
> > >
> > > > As there is a wired 404 problem under Apache domain, which works fine
> > > > under weex.io domain, I have to revert all the changes on
> > weex.apache.org .
> > > > I will publish it again when I find out what is happening here.
> > Meanwhile,
> > > > one may take https://weex.io as the preview version of new weex
> > website
> > > > before the republish.
> > > >
> > > > Sorry for the inconvenience.
> > > >
> > > > 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/  > >
> > > >> 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. 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 

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[申远]

There are two options.

1. On the bottom of each page, there is a button called *Edit this page.* Just
click it, then you will be navigated to the right branch and file on the
github.
2. If you prefer do things manually, Go to draft branch of
https://github.com/apache/incubator-weex-site/tree/draft.

I normally prefer the first choice unless I have to write a totally new
article.

BTW, the following approach is described in the docs, too. Ref
https://weex.apache.org/guide/contribute/how-to-contribute.html#contribute-code-or-document

Best Regards,
YorkShen

申远


Jan Piotrowski  于2019年2月25日周一 下午5:46写道：

> Nice.
>
> Which is the repository and branch to send PRs with typo fixes etc to?
>
> Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 :
> >
> > Hi, there
> >
> > I had fix the 404 error and updated the website of weex.apache.org,
> which
> > content should be the same as weex.io now. I will configure a 302
> > redirection later, which will make all the mirror site redirects to
> > weex.apache.org.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > 申远  于2019年2月22日周五 下午8:46写道：
> >
> > > As there is a wired 404 problem under Apache domain, which works fine
> > > under weex.io domain, I have to revert all the changes on
> weex.apache.org .
> > > I will publish it again when I find out what is happening here.
> Meanwhile,
> > > one may take https://weex.io as the preview version of new weex
> website
> > > before the republish.
> > >
> > > Sorry for the inconvenience.
> > >
> > > 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/  >
> > >> 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. 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  于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:
> > >> > > > >

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[Jan Piotrowski]

Nice.

Which is the repository and branch to send PRs with typo fixes etc to?

Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 :
>
> Hi, there
>
> I had fix the 404 error and updated the website of weex.apache.org, which
> content should be the same as weex.io now. I will configure a 302
> redirection later, which will make all the mirror site redirects to
> weex.apache.org.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> 申远  于2019年2月22日周五 下午8:46写道：
>
> > As there is a wired 404 problem under Apache domain, which works fine
> > under weex.io domain, I have to revert all the changes on weex.apache.org .
> > I will publish it again when I find out what is happening here. Meanwhile,
> > one may take https://weex.io as the preview version of new weex website
> > before the republish.
> >
> > Sorry for the inconvenience.
> >
> > 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/ 
> >> 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 申远 :
> >> > > >
> >> > > > >
> >> > > > > 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  于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 

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

[申远]

Hi, there

I had fix the 404 error and updated the website of weex.apache.org, which
content should be the same as weex.io now. I will configure a 302
redirection later, which will make all the mirror site redirects to
weex.apache.org.

Best Regards,
YorkShen

申远


申远  于2019年2月22日周五 下午8:46写道：

> As there is a wired 404 problem under Apache domain, which works fine
> under weex.io domain, I have to revert all the changes on weex.apache.org .
> I will publish it again when I find out what is happening here. Meanwhile,
> one may take https://weex.io as the preview version of new weex website
> before the republish.
>
> Sorry for the inconvenience.
>
> 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/ 
>> 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 申远 :
>> > > >
>> > > > >
>> > > > > 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  于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