incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 申远 <shenyua...@gmail.com>
Subject Re: Fwd: [DISCUSS] can we use weex.io as the short domain name for theapache project
Date Mon, 18 Feb 2019 08:33:14 GMT
>
> 3. I don't think ASF websites are facing GFW issue.

ASF website is quite slow when accessing from China, I am not sure whether
this is a GFW issue or simply the server is on another continent without a
CDN.

We received complains about weex.apache.org from China mainland years ago,
so we deploy website to weex-project.io for fast access in China, as many
of our users are from China and there is CDN for weex-project.io .  If
there is a solution for this issue, please let me know.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu <wu.sheng@foxmail.com> 于2019年2月18日周一 下午3:52写道:

> Hi YorkShen
>
>
> From my understanding, weex project, including branding and logo, should
> be donated to ASF(at least before Graduation).
> The basic policy is, weex.apache.org should be the only official website
> for the project.
> And project's website should be hosted in Apache Infra.
>
>
> If you have others, let's say weex.io and weex-project.io, and run by
> your committers team, I suggest
> 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> convenience.
> 2. For the Chinese documents, if your committers/contributors maintain
> this, put it in `http://weex.apache.org/cn/`makes
> <http://weex.apache.org/cn/makes> sense.
> 3. I don't think ASF websites are facing GFW issue.
>
>
> If you want to publish another domain/website for ecosystem, you should
> avoid using `weex-`, `weex.`, to avoid branding issues.
> And I suggest you don't do that, because the community will be split.
>
>
> The following are just suggestions from my experiences.
> Blog(cn/en) post are popular in many Apache project, which could be easily
> supported by our CI hook in GitHub, also have post control and review.
> If you want helps from this, ping me or `dev@skywalking.apache.org`, we
> have done something.
>
>
> For Q&A robots, if you are running that on GitHub issue, a Robot account
> with project subscription should be good enough.
> If you want to do that at Website, I think it will be more complex.
>
>
> ------------------
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> ------------------ Original ------------------
> From:  "申远"<shenyuancs@gmail.com>;
> Date:  Mon, Feb 18, 2019 03:07 PM
> To:  "general"<general@incubator.apache.org>;
>
> Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> theapache project
>
>
>
> Hi, there
>
> I am a PPMC member of incubator-weex, there is some confusion about
> third-party domain and it seems like difficult to resolve in dev@ mailing
> list, maybe someone here could give a hand to solve the problem of domains.
>
> 1.I 'd like to know if there is a formal rule that projects should use
> xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
> 2. we have another domain  weex-project.io for fast access of Çhinese
> Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
> this against rules for apache project.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> ---------- Forwarded message ---------
> From: Dan <faterrole@gmail.com>
> Date: 2019年2月15日周五 下午2:39
> Subject: [DISCUSS] can we use weex.io as the short domain name for the
> apache project
> To: <dev@weex.incubator.apache.org>
>
>
> 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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message