Hi, there
It took me a few hours to evaluate the maturity for Weex according to The
Apache Project Maturity Model (
http://community.apache.org/apache-way/apache-project-maturity-model.html),
it seems like there is still a big improvement space for Weex. The detail
is listed below:
Document
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
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
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
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
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
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.
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
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
Congratulations He Ling!!
Greets,
Myrle
On Wed, Mar 6, 2019 at 11:46 AM Jan Piotrowski wrote:
> Welcome He Ling!
>
> Am Mi., 6. März 2019 um 03:41 Uhr schrieb 申远 :
> >
> > The Podling Project Management Committee (PPMC) for Apache Weex has
> invited
> > He Ling to become a committer and we are
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
Welcome He Ling!
Am Mi., 6. März 2019 um 03:41 Uhr schrieb 申远 :
>
> The Podling Project Management Committee (PPMC) for Apache Weex has invited
> He Ling to become a committer and we are pleased to announce that he has
> accepted.
>
> He Ling is a great iOS Developer and works with weex project
12 matches
Mail list logo
