Re: [DISCUSS] Package name in Java code

[York Shen]

Nope.

The class name in source code(.java) will be ‘org.apache.weex’, as this is the 
right thing to do, IMO. The apache source code release will be under 
‘org.apache.weex’ as well.
The weex_sdk will be built without the plugin therefore its package name shall 
also be 'org.apache.weex'.
The weex_sdk_legacy will be built with the plugin therefore its package name 
shall be ‘com.taobao.weex'.
Users can choose whichever the above connivence library they’d like.


> 在 2019年9月18日，02:56，Jan Piotrowski  写道：
> 
> Sounds good.
> 
>> weex_sdk will be compiled using the gradle-plugin mentioned above, while 
>> weex_sdk_legacy will not.
> 
> Don't you mean the other one around? The legacy one should be built
> using the plugin, leading to the class names being replaced with the
> old ones.
> 
> -J
> 
> Am Di., 17. Sept. 2019 um 13:56 Uhr schrieb York Shen  >:
>> 
>> Hi, community
>> 
>> Due to the restriction of Java language in method overriding [1], the 
>> solution I proposed months ago will not provide backwards-compatibility as 
>> expected but produce compiling error for users.
>> 
>> Therefore, I’d like to proposal a new solution to fix the problem.
>> 
>> Package name will be renamed from 'com.taobao.weex' to 'org.apache.weex' in 
>> source code and Apache Source Release as the previous plan.
>> Create a custom gradle-plugin which could rename package back to 
>> ‘com.taobao.weex’ at compiling time.
>> Publish two build variants (weex_sdk and weex_sdk_legacy) each time building 
>> connivence library. weex_sdk will be compiled using the gradle-plugin 
>> mentioned above, while weex_sdk_legacy will not.
>> Therefore, classes in weex_sdk will be under ‘org.apache.weex' package, and 
>> classes in weex_sdk_legacy will be under ‘com.taobao.weex’.
>> New users of weex should choose weex_sdk and new API, while current users 
>> could continue using weex_sdk_legacy which provide the same API behavior as 
>> now.
>> Finally, we would stop publishing weex_sdk_legacy sometime later.
>> 
>> The community could benefit from the above solution in following aspects:
>> For me, there is much less work to do in current plan than the old one. Less 
>> bug to write, less time to use. One or two weeks will be enough.
>> For users, There is a guarantee that the API behavior of weex_sdk_legacy is 
>> the same as before because the source code after processing of gradle-plugin 
>> is the same as before. The old plan won’t give this guarantee.
>> We make our position very clear by naming the connivence binary to 
>> weex_sdk_legacy .
>> 
>> [1] "When overriding a method, the signatures (name and argument types) have 
>> to be the same after type erasure." Ref 
>> https://docs.oracle.com/javase/specs/jls/se7/html/jls-8.html#jls-8.4.2 
>>  
>> > > 
>> for detail.
>> 
>> Best Regards,
>> York Shen
>> 
>> 申远
>> 
>>> 在 2019年7月1日，16:26，Jan Piotrowski >> > 写道：
>>> 
>>> Sounds pretty neat and was pretty much what I was thinking of.
>>> 
>>> Th

Re: [DISCUSS] Package name in Java code

[Jan Piotrowski]

Sounds good.

> weex_sdk will be compiled using the gradle-plugin mentioned above, while 
> weex_sdk_legacy will not.

Don't you mean the other one around? The legacy one should be built
using the plugin, leading to the class names being replaced with the
old ones.

-J

Am Di., 17. Sept. 2019 um 13:56 Uhr schrieb York Shen :
>
> Hi, community
>
> Due to the restriction of Java language in method overriding [1], the 
> solution I proposed months ago will not provide backwards-compatibility as 
> expected but produce compiling error for users.
>
> Therefore, I’d like to proposal a new solution to fix the problem.
>
> Package name will be renamed from 'com.taobao.weex' to 'org.apache.weex' in 
> source code and Apache Source Release as the previous plan.
> Create a custom gradle-plugin which could rename package back to 
> ‘com.taobao.weex’ at compiling time.
> Publish two build variants (weex_sdk and weex_sdk_legacy) each time building 
> connivence library. weex_sdk will be compiled using the gradle-plugin 
> mentioned above, while weex_sdk_legacy will not.
> Therefore, classes in weex_sdk will be under ‘org.apache.weex' package, and 
> classes in weex_sdk_legacy will be under ‘com.taobao.weex’.
> New users of weex should choose weex_sdk and new API, while current users 
> could continue using weex_sdk_legacy which provide the same API behavior as 
> now.
> Finally, we would stop publishing weex_sdk_legacy sometime later.
>
> The community could benefit from the above solution in following aspects:
> For me, there is much less work to do in current plan than the old one. Less 
> bug to write, less time to use. One or two weeks will be enough.
> For users, There is a guarantee that the API behavior of weex_sdk_legacy is 
> the same as before because the source code after processing of gradle-plugin 
> is the same as before. The old plan won’t give this guarantee.
> We make our position very clear by naming the connivence binary to 
> weex_sdk_legacy .
>
> [1] "When overriding a method, the signatures (name and argument types) have 
> to be the same after type erasure." Ref 
> https://docs.oracle.com/javase/specs/jls/se7/html/jls-8.html#jls-8.4.2 
>  for 
> detail.
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年7月1日，16:26，Jan Piotrowski  写道：
> >
> > Sounds pretty neat and was pretty much what I was thinking of.
> >
> > Th
>

回复：Re: Apache project meetup in ShangHai Sep 21st

[Liu Ted]

OK, I originally plan to go but need to change my travel plan now. Wish you 
have a good meeting then.

Best regards,

Ted Liu, 
ASF Member, Sponsor Ambassador, Incubator PMC Member 
 
  2019 年 9 月 17 日周二 16:16，Willem Jiang 写道：   The time 
is around 1:30 PM to 4:00 PM, now it's about 20 people will join us.
We are just trying to find some place to hold this event.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Sep 17, 2019 at 6:14 AM Liu Ted  wrote:
>
> Hi Willem, What's the current status if the captioned meeting in Shanghai on 
> Seot. 21st? Has the venue and time been decided yet?
>
> Best regards,
>
> Ted Liu,
> ASF Member, Sponsor Ambassador, Incubator PMC Member
>
>
>  2019 年 8 月 21 日周三 10:55，Willem Jiang 写道：  Hi,
>
> We would like to hold a meetup in ShangHai Sep 21st by inviting some
> Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some
> apache projects committers in China like we did last year.
>
> We hold this meetup can help Apache projects to know each other in
> China. As there are lot of Apache project committers are based in east
> China,  we can leverage this opportunity to let Apache know better
> about the committers in China and give us some advice to build up
> health community.
>
> The discussion topic of meetup could be:
> How to be the TLP of ASF?
> How can we help ASF know better about China?
> How can we help more Chinese know better about ASF?
>
> If you are interested about this meetup, please drop an email to
> ningjiang AT apache.org with the information of your name, phone
> number and the project name before Sep 18th 12 PM. We will send you
> detail information of the meetup later.
>
> Please forward the mail to your friend who may be interested about this event.
>
> Willem
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
>  

Re: [DISCUSS] Package name in Java code

[York Shen]

Hi, community

Due to the restriction of Java language in method overriding [1], the solution 
I proposed months ago will not provide backwards-compatibility as expected but 
produce compiling error for users. 

Therefore, I’d like to proposal a new solution to fix the problem.

Package name will be renamed from 'com.taobao.weex' to 'org.apache.weex' in 
source code and Apache Source Release as the previous plan.
Create a custom gradle-plugin which could rename package back to 
‘com.taobao.weex’ at compiling time.
Publish two build variants (weex_sdk and weex_sdk_legacy) each time building 
connivence library. weex_sdk will be compiled using the gradle-plugin mentioned 
above, while weex_sdk_legacy will not.
Therefore, classes in weex_sdk will be under ‘org.apache.weex' package, and 
classes in weex_sdk_legacy will be under ‘com.taobao.weex’.
New users of weex should choose weex_sdk and new API, while current users could 
continue using weex_sdk_legacy which provide the same API behavior as now.
Finally, we would stop publishing weex_sdk_legacy sometime later.

The community could benefit from the above solution in following aspects:
For me, there is much less work to do in current plan than the old one. Less 
bug to write, less time to use. One or two weeks will be enough.
For users, There is a guarantee that the API behavior of weex_sdk_legacy is the 
same as before because the source code after processing of gradle-plugin is the 
same as before. The old plan won’t give this guarantee.
We make our position very clear by naming the connivence binary to 
weex_sdk_legacy .

[1] "When overriding a method, the signatures (name and argument types) have to 
be the same after type erasure." Ref 
https://docs.oracle.com/javase/specs/jls/se7/html/jls-8.html#jls-8.4.2 
 for 
detail.

Best Regards,
York Shen

申远

> 在 2019年7月1日，16:26，Jan Piotrowski  写道：
> 
> Sounds pretty neat and was pretty much what I was thinking of.
> 
> Th

Re: Apache project meetup in ShangHai Sep 21st

[Sheng Wu]

Enjoy the meetup. It will be a great chance to meet senior Apache
members/board, learning the Apache Way.
I wouldn't join as my schedule has been too crazy already.

If any of you will be Alibaba APSARA(云溪大会) next week, I will be there. :)

Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108


Willem Jiang  于2019年9月17日周二 下午4:16写道：

> The time is around 1:30 PM to 4:00 PM, now it's about 20 people will join
> us.
> We are just trying to find some place to hold this event.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Sep 17, 2019 at 6:14 AM Liu Ted  wrote:
> >
> > Hi Willem, What's the current status if the captioned meeting in
> Shanghai on Seot. 21st? Has the venue and time been decided yet?
> >
> > Best regards,
> >
> > Ted Liu,
> > ASF Member, Sponsor Ambassador, Incubator PMC Member
> >
> >
> >   2019 年 8 月 21 日周三 10:55，Willem Jiang 写道：   Hi,
> >
> > We would like to hold a meetup in ShangHai Sep 21st by inviting some
> > Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some
> > apache projects committers in China like we did last year.
> >
> > We hold this meetup can help Apache projects to know each other in
> > China. As there are lot of Apache project committers are based in east
> > China,  we can leverage this opportunity to let Apache know better
> > about the committers in China and give us some advice to build up
> > health community.
> >
> > The discussion topic of meetup could be:
> > How to be the TLP of ASF?
> > How can we help ASF know better about China?
> > How can we help more Chinese know better about ASF?
> >
> > If you are interested about this meetup, please drop an email to
> > ningjiang AT apache.org with the information of your name, phone
> > number and the project name before Sep 18th 12 PM. We will send you
> > detail information of the meetup later.
> >
> > Please forward the mail to your friend who may be interested about this
> event.
> >
> > Willem
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> > For additional commands, e-mail: dev-h...@echarts.apache.org
> >
>

Re: Apache project meetup in ShangHai Sep 21st

[Willem Jiang]

The time is around 1:30 PM to 4:00 PM, now it's about 20 people will join us.
We are just trying to find some place to hold this event.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Sep 17, 2019 at 6:14 AM Liu Ted  wrote:
>
> Hi Willem, What's the current status if the captioned meeting in Shanghai on 
> Seot. 21st? Has the venue and time been decided yet?
>
> Best regards,
>
> Ted Liu,
> ASF Member, Sponsor Ambassador, Incubator PMC Member
>
>
>   2019 年 8 月 21 日周三 10:55，Willem Jiang 写道：   Hi,
>
> We would like to hold a meetup in ShangHai Sep 21st by inviting some
> Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some
> apache projects committers in China like we did last year.
>
> We hold this meetup can help Apache projects to know each other in
> China. As there are lot of Apache project committers are based in east
> China,  we can leverage this opportunity to let Apache know better
> about the committers in China and give us some advice to build up
> health community.
>
> The discussion topic of meetup could be:
> How to be the TLP of ASF?
> How can we help ASF know better about China?
> How can we help more Chinese know better about ASF?
>
> If you are interested about this meetup, please drop an email to
> ningjiang AT apache.org with the information of your name, phone
> number and the project name before Sep 18th 12 PM. We will send you
> detail information of the meetup later.
>
> Please forward the mail to your friend who may be interested about this event.
>
> Willem
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
>

Re: Errored: apache/incubator-weex-playground#41 (master - 1f536fa)

[York Shen]

It seems like there is some network error in Travis server. Anyway, the build 
is good now.

> 在 2019年9月17日，11:38，Travis CI  写道：
> 
> Build Update for apache/incubator-weex-playground
> -
> 
> Build: #41
> Status: Errored
> 
> Duration: 6 mins and 52 secs
> Commit: 1f536fa (master)
> Author: chen
> Message: [Android]build fix (#18)
> 
> View the changeset: 
> https://github.com/apache/incubator-weex-playground/compare/84b82365466c...1f536fa83893
> 
> View the full build log and details: 
> https://travis-ci.org/apache/incubator-weex-playground/builds/585876851?utm_medium=notification&utm_source=email
> 
> --
> 
> You can unsubscribe from build emails from the 
> apache/incubator-weex-playground repository going to 
> https://travis-ci.org/account/preferences/unsubscribe?repository=25215058&utm_medium=notification&utm_source=email.
> Or unsubscribe from *all* email updating your settings at 
> https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
> Or configure specific recipients for build notifications in your .travis.yml 
> file. See https://docs.travis-ci.com/user/notifications.
> 

Re: Errored: apache/incubator-weex#6621 (feature/master_ab_new - e9680b9)

[York Shen]

The related feature branch and PR is deleted for good, no need to worry about 
it.

> 在 2019年9月16日，18:06，Travis CI  写道：
> 
> Build Update for apache/incubator-weex
> -
> 
> Build: #6621
> Status: Errored
> 
> Duration: 2 mins and 51 secs
> Commit: e9680b9 (feature/master_ab_new)
> Author: chen
> Message: [Android] tmp
> 
> View the changeset: 
> https://github.com/apache/incubator-weex/compare/24085a2139d0...e9680b9c7313
> 
> View the full build log and details: 
> https://travis-ci.org/apache/incubator-weex/builds/585500528?utm_medium=notification&utm_source=email
> 
> --
> 
> You can unsubscribe from build emails from the apache/incubator-weex 
> repository going to 
> https://travis-ci.org/account/preferences/unsubscribe?repository=11562877&utm_medium=notification&utm_source=email.
> Or unsubscribe from *all* email updating your settings at 
> https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
> Or configure specific recipients for build notifications in your .travis.yml 
> file. See https://docs.travis-ci.com/user/notifications.
> 

[Result][Vote] Accepting donation of weex-loader

[York Shen]

Hi, all

The vote for accepting donation of weex-loader has now closed. The results are 
listed below:

Vote Result:
1 (+1 binding) (From Jan Piotrowski)
0 (0 binding)
0 (-1 binding)

And no non-binding votes.

IP clearance is based on lazy-consensus, therefore the vote is successful.

Voting thread: 
https://mail-archives.apache.org/mod_mbox/weex-dev/201909.mbox/%3C310836C0-10DE-4A0E-8C7B-989055D8A603%40gmail.com%3E
 


Best Regards,
York Shen

申远

Re: [Vote] [IP Clearance] Accepting donation of Weex-loader

[York Shen]

The vote is closed now, I shall post the result in another thread.

FYI: I am currently trying to get SGA singed from corresponding cooperation, 
which may take several days. After that, weex-loader could be part of Apache 
Weex formally.

Best Regards,
York Shen

申远

> 在 2019年9月12日，03:43，Jan Piotrowski  写道：
> 
> +1
> 
> Am Mi., 11. Sept. 2019 um 10:37 Uhr schrieb York Shen  >:
>> 
>> Hi, community
>> 
>> The community of weex-loader [1], some of whose contributors are also 
>> committers of Apache Weex recently proposed to make their code donated to 
>> ASF with Incubator-Weex as receiving PPMC.
>> 
>> "weex-loader is a loader of webpack that can transform *.vue file into a 
>> plain javascript module for Android and iOS platform."
>> 
>> According to my knowledge, with “weex-loader” and "CLI-for-Apache-Weex” 
>> donated to Weex PPMC, we will resolve the branding/outside-code issues for 
>> good [3] . All the essential tools for compiling and running Weex will be 
>> under ASF and they will be able to call themself Apache-Weex-.
>> 
>> As the donation is exactly what Weex Community needs, I am calling this vote 
>> for IP Clearance purpose.Again, it’s not necessary to go through IP 
>> Clearance process for Incubating projects, there is no harm to do so.
>> 
>> Voting ends three days from today, i.e. Sep, 14th, 2019 at 9:0:0 AM (UTC 
>> time) [4].
>> 
>> +1 for Yes I agree
>> 0 for I have no strong opinion
>> -1 for I object on the a specific grounds
>> 
>> FYI: IP Clearance is based on lazy consensus, but everyone is welcomed to 
>> vote on this thread.
>> 
>> [1] https://github.com/weexteam/weex-loader 
>>  
>> > >
>> [2] https://github.com/weexteam/CLI-for-Apache-Weex 
>>  
>> > >
>> [3] 
>> https://mail-archives.apache.org/mod_mbox/weex-dev/201901.mbox/%3C91448AB4-A929-4BE1-9541-BD7A7DEA5A1A%40gmail.com%3E
>>  
>> 
>>  
>> >  
>> >
>> [4] 
>> https://www.timeanddate.com/countdown/generic?iso=20190914T09&p0=1440&msg=Countdown+&font=cursive
>>  
>> 
>>  
>> >  
>> >
>> 
>> Best Regards,
>> York Shen
>> 
>> 申远