Re: Question about the website of weex

Anyway, I think we should list all the problematic things first and then discuss how to solve. Using legal weapon should not be our first choice. Best Regards, YorkShen 申远 Willem Jiang 于2019年3月7日周四 上午6:31写道： > This kind of issue is exit for a while, for the health of the > community, we

Re: Question about the website of weex

This kind of issue is exit for a while, for the health of the community, we need to get touch with these developers and help them to donate the code into Apache. I think most of them will be happy to be a part of the big family. If the code has some kind of License issue (has the hard dependency

Re: Question about the website of weex

In my opinion there is no dilemma, just a bit of work ahead of us. We will start by collecting all the possibly problematic things, then find simple and effective solutions to each and every one. And _if_ we can't solve some of them, we might have to think about "legal" or other solutions. But I

Re: Question about the website of weex

I understand the brand issues and the general topics. But let me explain my concerns first: There are definitely some third party extensions violating the trademark of Apache Weex. But in my opinion, I think weex’s( difficult to pronounce 路‍♀️) priority is getting more developers into the

Re: Question about the website of weex

I assume Myrle's response was not focused on this one extension, but on the general topic we discussed over multiple emails. As soon as I have the necessary rights I will start to collect all the "problematic" things I can find in the GitHub project board and we can then start to discuss possible

Re: Question about the website of weex

This might also be useful: http://www.apache.org/foundation/marks/reporting.html Best Regards, Myrle On Wed, Mar 6, 2019 at 4:14 PM Myrle Krantz wrote: > Hey YorkShen, > > If someone is misusing your brand and ignoring your requests to stop > branding violations, the law is on your side.

Re: Question about the website of weex

Hey YorkShen, If someone is misusing your brand and ignoring your requests to stop branding violations, the law is on your side. This is a point on which the Apache Software Foundation can help: http://www.apache.org/foundation/marks/responsibility#responsible If you need help with this, you

Re: Question about the website of weex

I am totally aware of the situation, but what we met here is that someone published a VSCode extension named weex-plugin/tool/helper. I cannot contact all of the author of such extension to ask them rename their code or invite all of them into Weex repo under Apache. Either of these choices is

Re: Question about the website of weex

Apache Weex dev team: Using the Weex name to denote something that isn't weex is a problem. Calling a team a "weex team" if they aren't the Apache Weex committers and PMC is confusing to end users. Apache doesn't allow project brands to be diluted like this. Registering a website with the weex

Re: Question about the website of weex

Of course there can still be a "VS Code extension" entry under (e.g.) "Third party tools". And the extension actually has a perfectly fine website, so no need to rehost the documentation and images etc: Both https://marketplace.visualstudio.com/items?itemName=weex.vscode-weex and

Re: Question about the website of weex

Agreed. We should set the boundary clearly about what is Apache Weex and what is not and mention that on the webpage. But given current situation, it is hard to move them to a seperate domain totally. For example, vscode extension are just

Re: Question about the website of weex

Ok, then it's pretty simple: Those tools should have their own website on another domain (one that does not redirect to the .apache.org site by default - maybe subdomains for weex-community.io or something if someone wants to sponsor that?) and the official weex page just links out to them,

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

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

Re: Question about the website of weex

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

Re: Question about the website of weex

> > 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

Re: Question about the website of weex

At present, I have added a file to redirect the old documents to the new documents. These are the links of the first 20 pages about weex that I have searched through Google search and Baidu search. If there are other pages that cannot find the corresponding content, we can redirect user access by

Re: Question about the website of weex

Hm, what kind of code is the user missing at that link? (Google Translate unfortunately didn't help) If there was something on the old site that can now not be par of it any more, it should at least be moved somewhere else (subdomain of weex.io for example?) and the old URL redirected. Being

Re: Question about the website of weex

1. https://weex.io has been redirected to https://weex.apache.org 2. All the commercial should also be removed now. If there is still something inappropriate, please let me know, thanks. Best Regards, YorkShen 申远 申远 于2019年2月26日周二 上午11:54写道： > I will redirect weex.io, weex-project.io and all

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]

Re: Question about the website of weex

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

Re: Question about the website of weex

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:

Re: Question about the website of weex

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

Question about the website of weex

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