Re: [DISCUSS] Weex Trademark issue

2019-05-13 Thread 申远
Except for marking things like weex-plugin as Un-Apache, I don't think
there is any more progress now.

Some of the projects under weexteam are no longer maintained, in which case
changing the repo's name to "xxx for apache weex" is enough.

But what should we do to handle weexteam[1] itself ? After all, the name
itself may violate trademark too.

[1] https://github.com/weexteam

Best Regards,
YorkShen

申远


Willem Jiang  于2019年5月14日周二 上午9:34写道:

> Hi York,
>
> Please take a look at the wiki page of the
> Apache-Dubbo-external-ecosystem-status, most of the repos were moved
> into Apache Dubbo umberaller.
> As Jan has said, we cannot see any improvements on Weex side yet. I
> think we should work together to try our best address this important
> issue in few month.
>
> BTW, I just have a quick look at the projects in the weex-plugin and
> weexteam. Lots of projects in weex-plugin have no update since 2017. I
> think we need to put more efforts to work with weexteam to make sure
> the projects are handled properly.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, May 13, 2019 at 3:39 PM 申远  wrote:
> >
> > Hi, community
> >
> > I know this discussion happened before, but I'd like to mention it again.
> >
> > After review the discussion of trademark issue in Apache dubbo[1], I
> think
> > Weex should pay more attention trademark, too. As both Weex and Dubbo
> have
> > external ecosystem, which means there are repos[2] on github related to
> > Weex but not under ASF.
> >
> > Owners of this repo can choose donate this repo to Weex, renaming repos
> to
> > xxx-for-apache-weex or deleting such repos. Apache Dubbo really shows us
> a
> > good example.
> >
> > [1]
> >
> https://lists.apache.org/thread.html/dd36fa6c4ae4c1962be6c6a1235507eaa8c5c3ae009281e7cfdb2522@%3Cgeneral.incubator.apache.org%3E
> > [2] https://github.com/weex-plugins
> > [3] https://github.com/weexteam
> > [4]
> >
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
>


Re: [DISCUSS] Weex Trademark issue

2019-05-13 Thread Willem Jiang
Hi York,

Please take a look at the wiki page of the
Apache-Dubbo-external-ecosystem-status, most of the repos were moved
into Apache Dubbo umberaller.
As Jan has said, we cannot see any improvements on Weex side yet. I
think we should work together to try our best address this important
issue in few month.

BTW, I just have a quick look at the projects in the weex-plugin and
weexteam. Lots of projects in weex-plugin have no update since 2017. I
think we need to put more efforts to work with weexteam to make sure
the projects are handled properly.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, May 13, 2019 at 3:39 PM 申远  wrote:
>
> Hi, community
>
> I know this discussion happened before, but I'd like to mention it again.
>
> After review the discussion of trademark issue in Apache dubbo[1], I think
> Weex should pay more attention trademark, too. As both Weex and Dubbo have
> external ecosystem, which means there are repos[2] on github related to
> Weex but not under ASF.
>
> Owners of this repo can choose donate this repo to Weex, renaming repos to
> xxx-for-apache-weex or deleting such repos. Apache Dubbo really shows us a
> good example.
>
> [1]
> https://lists.apache.org/thread.html/dd36fa6c4ae4c1962be6c6a1235507eaa8c5c3ae009281e7cfdb2522@%3Cgeneral.incubator.apache.org%3E
> [2] https://github.com/weex-plugins
> [3] https://github.com/weexteam
> [4]
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
>
> Best Regards,
> YorkShen
>
> 申远


Re: [DISCUSS] Weex Trademark issue

2019-05-13 Thread Jan Piotrowski
I was under the impression that nothing happened yet after we talked
about this the last time. Or was there some cleanup that I missed?
Because then I would re-review the situation and point out the
remaining problems again.

-J

Am Mo., 13. Mai 2019 um 09:39 Uhr schrieb 申远 :
>
> Hi, community
>
> I know this discussion happened before, but I'd like to mention it again.
>
> After review the discussion of trademark issue in Apache dubbo[1], I think
> Weex should pay more attention trademark, too. As both Weex and Dubbo have
> external ecosystem, which means there are repos[2] on github related to
> Weex but not under ASF.
>
> Owners of this repo can choose donate this repo to Weex, renaming repos to
> xxx-for-apache-weex or deleting such repos. Apache Dubbo really shows us a
> good example.
>
> [1]
> https://lists.apache.org/thread.html/dd36fa6c4ae4c1962be6c6a1235507eaa8c5c3ae009281e7cfdb2522@%3Cgeneral.incubator.apache.org%3E
> [2] https://github.com/weex-plugins
> [3] https://github.com/weexteam
> [4]
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
>
> Best Regards,
> YorkShen
>
> 申远


[DISCUSS] Weex Trademark issue

2019-05-13 Thread 申远
Hi, community

I know this discussion happened before, but I'd like to mention it again.

After review the discussion of trademark issue in Apache dubbo[1], I think
Weex should pay more attention trademark, too. As both Weex and Dubbo have
external ecosystem, which means there are repos[2] on github related to
Weex but not under ASF.

Owners of this repo can choose donate this repo to Weex, renaming repos to
xxx-for-apache-weex or deleting such repos. Apache Dubbo really shows us a
good example.

[1]
https://lists.apache.org/thread.html/dd36fa6c4ae4c1962be6c6a1235507eaa8c5c3ae009281e7cfdb2522@%3Cgeneral.incubator.apache.org%3E
[2] https://github.com/weex-plugins
[3] https://github.com/weexteam
[4]
https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status

Best Regards,
YorkShen

申远