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 don't expect that to be needed.
-J Am Mi., 6. März 2019 um 18:00 Uhr schrieb York Shen <shenyua...@gmail.com>: > > 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 community (mailing list instead > of github) and encourage them from users to contributor or committers. > Trademark issue is time consuming and may be not that urgent to Weex > community at this point (just personal opinion). > I’d like to treat thirty-party extensions as good sign because the Weex is > useful so that someone would develop tools for Weex. I want to show the kind > and friendly part of the Weex community, not threaten developers with law. > Maybe the boundary between kindness and weakness is not so clear, such > kindness may be treated as weakness. But I really don’t appreciate the idea > of threatening enthusiastic developers with law. > > Though, I understand that from ASF’s point, such violation may be > unacceptable and need corrected. So, I am really in a dilemma. > > > 在 2019年3月6日，23:11，Jan Piotrowski <piotrow...@gmail.com> 写道： > > > > 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 solutions or workarounds for those. > > > > The website is now fully on Git, so we should be able to iterate here > > quickly and efficiently. And I am sure we will find great solutions > > with all third parties as well. > > > > -J > > > > Am Mi., 6. März 2019 um 16:03 Uhr schrieb 申远 <shenyua...@gmail.com>: > >> > >> 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 impractical. > >> > >> But these tools are useful, I can't pretend that I don't know there is a > >> such tool and ignore all the things that happened in the world beyond > >> apache community. > >> > >> What I can think of is that listing the useful tools in weex website and > >> make it clear it is not part of apache weex. > >> > >> Best Regards, > >> YorkShen > >> > >> 申远 > >> > >> > >> Myrle Krantz <my...@apache.org> 于2019年3月6日周三 下午7:44写道： > >> > >>> 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 name which offers code that isn't from > >>> the weex project is a problem. If these tools are important to the > >>> project > >>> to the point that it is important that they share the weex brand, then > >>> they > >>> *do* belong on the Apache weex website. They also need to be licensed > >>> under ALv2, and released by the Weex PMC, and the source needs to be > >>> hosted > >>> on the apache github account. > >>> > >>> The Weex PMC needs to have control of all the weex code or else you won't > >>> be able to graduate. And generating more code in these off-list projects > >>> pushes your project *away* from graduation, not towards it. > >>> > >>> Best Regards, > >>> Myrle > >>> > >>> On Mon, Mar 4, 2019 at 1:51 PM Jan Piotrowski <piotrow...@gmail.com> > >>> wrote: > >>> > >>>> 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 https://github.com/weex-cli/vscode-weex (although the Github org > >>>> name is problematic) work just fine. > >>>> > >>>> Of course feel free to drop the PR link when it is up. Will be happy > >>>> to provide feedback. > >>>> > >>>> -J > >>>> > >>>> Am Mo., 4. März 2019 um 13:42 Uhr schrieb 申远 <shenyua...@gmail.com>: > >>>>> > >>>>> 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 > >>>>> <https://weex.apache.org/tools/extension.html#features> are just third > >>>>> party VSCode extension, which I found by searching on VScode. It is > >>>>> unlikely to ask them have their own website and remove them directly > >>>> from . > >>>>> apache.org is not also a good idea. > >>>>> > >>>>> What I can think of is marked them as third party plugin .apache.org > >>>>> clearly and remain them in the page as they are now. > >>>>> > >>>>> When I finished my work, maybe you could review my PR? > >>>>> > >>>>> > >>>>> Best Regards, > >>>>> YorkShen > >>>>> > >>>>> 申远 > >>>>> > >>>>> > >>>>> Jan Piotrowski <piotrow...@gmail.com> 于2019年3月1日周五 下午6:10写道： > >>>>> > >>>>>> 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, > >>>>>> mentioning that those are community supported and owned tools (e.g. > >>> by > >>>>>> having a "Community Tools" headline in the navigation or by combining > >>>>>> them all on a "Community Tools" page instead of having own navigation > >>>>>> item for each tool). > >>>>>> > >>>>>> To users it has to be absolutely clear and obvious what is official > >>>>>> Apache Weex, and what is not. > >>>>>> > >>>>>> Am Fr., 1. März 2019 um 03:22 Uhr schrieb 申远 <shenyua...@gmail.com>: > >>>>>>> > >>>>>>>> > >>>>>>>> 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 all of them to Apache repos, we > >>>> just > >>>>>>> list it in the page. > >>>>>>> > >>>>>>> [1] https://weex.apache.org/tools/playground.html > >>>>>>> > >>>>>>> Best Regards, > >>>>>>> YorkShen > >>>>>>> > >>>>>>> 申远 > >>>>>>> > >>>>>>> > >>>>>>> Jan Piotrowski <piotrow...@gmail.com> 于2019年2月28日周四 下午10:13写道： > >>>>>>> > >>>>>>>>> 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 > >>>>>>>> Gradle/Cocoapods/NPM to install the artifacts instead of source. > >>>> But I > >>>>>>>> could list the artifacts and Gradle/Cocoapods/NPM link together > >>> in > >>>> a > >>>>>>>> webpage later. > >>>>>>>> > >>>>>>>> This is of course no problem at all. But the original voting and > >>>>>>>> release process follows the required Apache way, when it is > >>>> finished > >>>>>>>> the binaries or releases can of course be distributed in any way > >>>>>>>> useful to the users. See here for an example of the Cordova > >>> release > >>>>>>>> process: > >>>>>>>> > >>>>>> > >>>> > >>> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#otherwise-publish-real-release-to-dist--npm > >>>>>>>> (pretty overcomplicated because of historical reasons, but you > >>> get > >>>> the > >>>>>>>> idea) > >>>>>>>> > >>>>>>>> Am Do., 28. Feb. 2019 um 04:58 Uhr schrieb Willem Jiang > >>>>>>>> <willem.ji...@gmail.com>: > >>>>>>>>> > >>>>>>>>> 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 > >>>>>>>>> > >>>>>>>>> Twitter: willemjiang > >>>>>>>>> Weibo: 姜宁willem > >>>>>>>>> > >>>>>>>>> On Thu, Feb 28, 2019 at 11:46 AM 申远 <shenyua...@gmail.com> > >>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> 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 than > >>>> https://weex.apache.org/ > >>>>>> for > >>>>>>>> such > >>>>>>>>>> tools, I can move them. > >>>>>>>>>> > >>>>>>>>>> I cannot find the download the weex artifacts but only the > >>>> weex IDE > >>>>>>>>>>> and playground. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> As weex users are Android/iOS/JavaScript developers, they > >>> often > >>>>>> choose > >>>>>>>>>> Gradle/Cocoapods/NPM to install the artifacts instead of > >>>> source. > >>>>>> But I > >>>>>>>>>> could list the artifacts and Gradle/Cocoapods/NPM link > >>>> together in > >>>>>> a > >>>>>>>>>> webpage later. > >>>>>>>>>> > >>>>>>>>>> BTW, once we vote the release, we need to distributed those > >>>> release > >>>>>>>>>>> kit to Apache mirrors for the downloads of user. > >>>>>>>>>>> I don't think we did this step of work after the vote of > >>> weex > >>>>>> 0.22.0 > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> I will move it later. I think I would propose the next > >>> release > >>>> of > >>>>>> weex, > >>>>>>>>>> which will give me a better understanding of the whole Apache > >>>>>> release > >>>>>>>>>> procedure. > >>>>>>>>>> > >>>>>>>>>> Best Regards, > >>>>>>>>>> YorkShen > >>>>>>>>>> > >>>>>>>>>> 申远 > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Willem Jiang <willem.ji...@gmail.com> 于2019年2月28日周四 > >>> 上午10:35写道： > >>>>>>>>>> > >>>>>>>>>>> Hi York, > >>>>>>>>>>> > >>>>>>>>>>> I know weex team put lot of effort to build the whole eco > >>>> system, > >>>>>>>> from > >>>>>>>>>>> the runtime to development tools and others. > >>>>>>>>>>> But we can only host the downloads of the weex project, not > >>>> the > >>>>>> other > >>>>>>>>>>> tools which are built on top it. > >>>>>>>>>>> I cannot find the download the weex artifacts but only the > >>>> weex > >>>>>> IDE > >>>>>>>>>>> and playground. > >>>>>>>>>>> > >>>>>>>>>>> Could you explain it? > >>>>>>>>>>> > >>>>>>>>>>> BTW, once we vote the release, we need to distributed those > >>>>>> release > >>>>>>>>>>> kit to Apache mirrors for the downloads of user. > >>>>>>>>>>> I don't think we did this step of work after the vote of > >>> weex > >>>>>>>> 0.22.0[1] > >>>>>>>>>>> > >>>>>>>>>>> [1] > >>>>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> https://lists.apache.org/thread.html/76f90754258431e48a6d86afedd3862b642320a43e3c96de4326a9cd@%3Cgeneral.incubator.apache.org%3E > >>>>>>>>>>> > >>>>>>>>>>> Willem Jiang > >>>>>>>>>>> > >>>>>>>>>>> Twitter: willemjiang > >>>>>>>>>>> Weibo: 姜宁willem > >>>>>>>>>>> > >>>>>>>>>>> On Tue, Feb 26, 2019 at 11:54 AM 申远 <shenyua...@gmail.com> > >>>>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> 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 <faterr...@gmail.com> 于2019年2月26日周二 上午11:35写道： > >>>>>>>>>>>> > >>>>>>>>>>>>> sure, that will be remove soon, that’s my mistake, > >>>>>>>>>>>>> > >>>>>>>>>>>>>> 在 2019年2月26日，上午11:33，Willem Jiang < > >>>> willem.ji...@gmail.com> > >>>>>> 写道： > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> 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 < > >>>> faterr...@gmail.com> > >>>>>>>> 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 <willem.ji...@gmail.com> 于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 > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> >
