Already done.
https://github.com/apache/incubator-weex/projects/1?add_cards_query=is%3Aopen
Best Regards,
YorkShen
申远
Jan Piotrowski 于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
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
> 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
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
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
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
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
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
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]
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:
>
>
>-
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
> 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
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.
>
>
Thanks for fixing the 404s and making the homepage editable.
> 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.
The server should just be a Apache webserver (of
>
> 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?
>
The homepage is generated by
https://github.com/apache/incubator-weex-site/blob/draft/docs/.vuepress/data/lang-en.js
on
draft
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
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
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
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
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
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
>
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
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
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
>
>
> 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
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
Sorry，I just came across this email.
I found you already sent the mail to the general mailing, I will reply
the mail there.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Feb 15, 2019 at 2:39 PM Dan wrote:
>
> Hi, Myrle/Willem,
>
> Currently, we have a domain name of weex.io and
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 wrote:
> Thanks, Jan, I will
Thanks, Jan, I will take a look at this.
Jan Piotrowski 于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
>
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
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
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
33 matches
Mail list logo
