Then it seems like we have a solution satisfy the need of ASF Brand
Managemet, Weex Users and the maintainer of editor.weex.io @Hanks Zhang
<zhanghan...@gmail.com> .

I think this is the best we could do considering the situaion.

Best Regards,
YorkShen

申远


Hanks Zhang <zhanghan...@gmail.com> 于2019年11月27日周三 下午3:10写道:

> I support using xxx.dotwe.org instead of editor.weex.io if it really has
> the branding issue. The candidate domain name could be editor.dotwe.org
> or v2.dotwe.org.
>
> Technological speaking, redirect editor.weex.io to the new domain in DNS
> is feasible. However, the dotwe.org is not under my control, but maybe I
> can find the one who is able to configure it.
>
> Best Regards,
> Hanks
>
> 申远 <shenyua...@gmail.com> 于2019年11月27日周三 上午11:42写道:
>
>> From the information I have, the server of editor.weex.io will be
>> offline by the end of Dec, 2019 if we don't migrate to the new data center.
>> While the domain name could be alive until Nov, 2020 if we don't pay for it.
>>
>> I will not judge the domain name decsion made by ASF brand management,
>> but I think it would satisfy ASF brand management, Apache Weex user, Apache
>> Weex Committer, domain owner and server maintainer like you until Nov, 2020
>> if we pay for the server and binding the server to a new domain name, like
>> xxxx.dotwe.org.
>>
>> IMO, this is the best solution we have now, though I don't know what we
>> shall do if domain is controlled and misused by third-party after Nov, 2020.
>>
>> Best Regards,
>> YorkShen
>>
>> 申远
>>
>>
>> 申远 <shenyua...@gmail.com> 于2019年11月26日周二 下午7:10写道:
>>
>>> I think the concerns from ASF is mainly on domain part, as the domain
>>> weex.io does lead some confusion. Is domain of http://dotwe.org/vue on
>>> under your control? Could we create redirect editor.weex.io to
>>> xxxx.dotwe.org through http 301 redirect or DNS CNAME ?
>>>
>>> IMNAL, but I think backend-server is not againts any rules of ASF, we
>>> just need to pay for the bill every year, just like the domain name. @Hanks
>>> Zhang <zhanghan...@gmail.com> I know you're planning to migrate the
>>> server to another data-center due to some technical reason, but this is OK
>>> with ASF's rules according to my undersing.
>>>
>>> Best Regards,
>>> YorkShen
>>>
>>> 申远
>>>
>>>
>>> Hanks Zhang <zhanghan...@gmail.com> 于2019年11月26日周二 下午4:29写道:
>>>
>>>> In my opinion, both close weex.io or migrate the server to ASF's VM is
>>>> not a good idea, the cost is too expensive.
>>>>
>>>> For the branding issue of the domain, I think we can register a new
>>>> domain name to replace the editor.weex.io, and redirect the legacy
>>>> domain to the new one. Currently, the weex.io domain is under my
>>>> GoDaddy account and will be expired at 2020/11/20.
>>>>
>>>> For the server that provides service of editor.weex.io, If we CAN NOT
>>>> continue using it, we could apply for a new server that has no branding
>>>> issue with ASF to migrate it.
>>>>
>>>>
>>>> Best Regards,
>>>> Hanks Zhang
>>>>
>>>>
>>>> 申远 <shenyua...@gmail.com> 于2019年11月26日周二 上午11:55写道:
>>>>
>>>>> Well, it seems like the brand management,VP doesn't like the idea [1]
>>>>> that we hold the domain name of http://editor.weex.io/, we have to
>>>>> take down the domain name for better or worse. As some of you may not see
>>>>> discussion in private mailing list, I will move it back to this mailing
>>>>> list. Here is the options we have.
>>>>>
>>>>>    - Take down weex.io, which saves us the money and satisfies the
>>>>>    rule of apache brand management. Of course, this will have bad 
>>>>> influence on
>>>>>    Weex users.
>>>>>    - Transfer weex.io to ASF, and use it as always. This approach
>>>>>    doese seems better, but ASF refused to pay for the domain, which means 
>>>>> the
>>>>>    domain maintainer has to pay for it even it's not in his/her control. I
>>>>>    don't know wheter the domain maintainer would agree with this. @Dan
>>>>>    <faterr...@gmail.com> @Hanks Zhang <zhanghan...@gmail.com> Any
>>>>>    words you want to say on this proposal ? I remembered the domain is 
>>>>> under
>>>>>    one of you control.
>>>>>    - Request a VM from INFRA ASF and host the dynamic content of
>>>>>    editor.weex.io to the new VM. I don't know whether this is
>>>>>    possible in the aspect of engineering, still need replies from @Dan
>>>>>    <faterr...@gmail.com> @Hanks Zhang <zhanghan...@gmail.com>
>>>>>
>>>>> If there are other opinions, please let me know. I am trying to do my
>>>>> best to solve the problem, but none of the above solutions make me happy.
>>>>>
>>>>> [1]
>>>>> https://lists.apache.org/thread.html/78122338690c154ce1637bb0509edb948724fe98b61c7632e91cfc53@%3Cprivate.weex.apache.org%3E
>>>>>
>>>>> Best Regards,
>>>>> YorkShen
>>>>>
>>>>> 申远
>>>>>
>>>>>
>>>>> 申远 <shenyua...@gmail.com> 于2019年11月6日周三 下午8:45写道:
>>>>>
>>>>>> After some digging, I found that domain maintainer must request an
>>>>>> explicit permit [1] from VP, Brand management if they use Apache 
>>>>>> Trademark
>>>>>> in their domain. There is more work we need to do here.
>>>>>>
>>>>>> [1] http://www.apache.org/foundation/marks/domains.html#permission
>>>>>>
>>>>>> Best Regards,
>>>>>> YorkShen
>>>>>>
>>>>>> 申远
>>>>>>
>>>>>>
>>>>>> 申远 <shenyua...@gmail.com> 于2019年11月6日周三 上午11:14写道:
>>>>>>
>>>>>>> First of all, thanks all for participating.
>>>>>>>
>>>>>>> it would be great if someone could find a way to pay for it and keep
>>>>>>>> the redirects alive so no external links break.
>>>>>>>>
>>>>>>>
>>>>>>> I will see what I can do, maybe my company could pay the bill, as
>>>>>>> the company relies on Weex deeply.
>>>>>>>
>>>>>>> I found a new domain name[2] in the page[1]. And the content in the
>>>>>>>> two domain names is highly similar. Is it possible to merge the 
>>>>>>>> contents of
>>>>>>>> domain [3] into domain [2] ?
>>>>>>>>
>>>>>>>
>>>>>>> Based on my communnication with the website maintainer,
>>>>>>> http://dotwe.org/vue is the V1 version, and http://editor.weex.io/
>>>>>>> is the V2 version, it's very unlikely to merge them into one, especially
>>>>>>> some features in V1 version doesn't get support in V2 version.
>>>>>>>
>>>>>>> Besides, both of the sites you mentioned may violate the brand of
>>>>>>> Apache Weex, they have to change their content or donate to ASF.
>>>>>>> Considering ASF website only has static content, mirgating those 
>>>>>>> websites
>>>>>>> containing dynamic content to ASF server will be a great deal of work, 
>>>>>>> or
>>>>>>> impractical, even if they're willing to donate to ASF.
>>>>>>>
>>>>>>> I am in favour of remaining the current situation, e.g. two websites
>>>>>>> separated from Apache Weex,  if they could fix the brand issue.
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> YorkShen
>>>>>>>
>>>>>>> 申远
>>>>>>>
>>>>>>>
>>>>>>> Jan Piotrowski <piotrow...@gmail.com> 于2019年11月6日周三 上午5:20写道:
>>>>>>>
>>>>>>>> I second the comments made before, as weex.io seems to be in use
>>>>>>>> for some
>>>>>>>> things and probably also linked all over the internet with earlier
>>>>>>>> mentions
>>>>>>>> of Weex, it would be great if someone could find a way to pay for
>>>>>>>> it and
>>>>>>>> keep the redirects alive so no external links break.
>>>>>>>>
>>>>>>>> (I'd be happy to sponsor the first year or three - just contact me
>>>>>>>> directly
>>>>>>>> so I can send the money to the person taking care of this.)
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Jan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Am Di., 5. Nov. 2019 um 16:32 Uhr schrieb 任 跃兵 <cn...@live.cn>:
>>>>>>>>
>>>>>>>> >
>>>>>>>> > I found a new domain name[2] in the page[1]. And the content in
>>>>>>>> the two
>>>>>>>> > domain names is highly similar.
>>>>>>>> > Is it possible to merge the contents of domain [3] into domain
>>>>>>>> [2] ?
>>>>>>>> >
>>>>>>>> > [1] https://weex.apache.org/zh/guide/introduction.html
>>>>>>>> > [2] http://dotwe.org/vue
>>>>>>>> > [3] http://editor.weex.io/
>>>>>>>> >
>>>>>>>> > ________________________________
>>>>>>>> > 发件人: 申远 <shenyua...@gmail.com>
>>>>>>>> > 发送时间: Tuesday, November 5, 2019 10:08:17 PM
>>>>>>>> > 收件人: dev <dev@weex.incubator.apache.org>
>>>>>>>> > 主题: Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of
>>>>>>>> this month
>>>>>>>> >
>>>>>>>> > Thanks
>>>>>>>> >
>>>>>>>> > According to the message from incubator [1], weex.io could still
>>>>>>>> exists if
>>>>>>>> > they meet some requirements.
>>>>>>>> >
>>>>>>>> > We could convince the owner of weex.io to do some change, or we
>>>>>>>> could
>>>>>>>> > rewrite links on our website. What do you think?
>>>>>>>> >
>>>>>>>> > [1]
>>>>>>>> >
>>>>>>>> >
>>>>>>>> https://mail-archives.apache.org/mod_mbox/incubator-general/201911.mbox/%3cCAEWfVJ=jns8oq6_ftg33eqzobqhf5mhjsuadbseee94uzop...@mail.gmail.com%3e
>>>>>>>> >
>>>>>>>> > Best Regards,
>>>>>>>> > YorkShen
>>>>>>>> >
>>>>>>>> > 申远
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > 任 跃兵 <cn...@live.cn> 于2019年11月5日周二 下午8:03写道:
>>>>>>>> >
>>>>>>>> > > The links in page [1] will be unable to open.
>>>>>>>> > > Please pay attention to these demos and links to this domain in
>>>>>>>> the
>>>>>>>> > > website [2].
>>>>>>>> > >
>>>>>>>> > > [1] https://weex.apache.org/community/code-demos.html
>>>>>>>> > > [2] https://weex.apache.org<
>>>>>>>> > > https://weex.apache.org/community/code-demos.html>
>>>>>>>> > >
>>>>>>>> > > ________________________________
>>>>>>>> > > 发件人: 申远 <shenyua...@gmail.com>
>>>>>>>> > > 发送时间: 2019年11月5日 10:55
>>>>>>>> > > 收件人: dev <d...@weex.apache.org>
>>>>>>>> > > 主题: [ANNOUNCEMENT] Weex.io will be offliine in the end of this
>>>>>>>> month
>>>>>>>> > >
>>>>>>>> > > Hi, communtiy
>>>>>>>> > >
>>>>>>>> > > The website of weex used to host on a thirt party domain [1],
>>>>>>>> and we
>>>>>>>> > > configured a 302 redirect to our official website [2] years ago.
>>>>>>>> > >
>>>>>>>> > > We will not pay for the old domain server [1] in this month,
>>>>>>>> which means
>>>>>>>> > > you will not be able to visit the old domain [1]. Please always
>>>>>>>> visit
>>>>>>>> > Weex
>>>>>>>> > > through the new domain [2].
>>>>>>>> > >
>>>>>>>> > > [1] https://weex.io
>>>>>>>> > > [2] https://weex.apache.org
>>>>>>>> > >
>>>>>>>> > > Best Regards,
>>>>>>>> > > YorkShen
>>>>>>>> > >
>>>>>>>> > > 申远
>>>>>>>> > >
>>>>>>>> >
>>>>>>>>
>>>>>>>

Reply via email to