Re: [VOTE]: Release Apache Weex (Incubating) 0.19.0 [RC0]

[He Sai]

Hi, Adam, I noticed there are some Chinese characters in the release note.
should we change them to English ?

2018-06-20 10:26 GMT+08:00 Adam Feng :

> Hi Weex Community,
> I'm calling this vote to release Apache Weex (Incubating) version 0.19.0.
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.
> git;a=shortlog;h=refs/tags/0.19.0-rc0
>
> Hash for the release tag:
> 9ea6ac79ecf7cd855e1afe114a1897fe06621e81
>
> The source tarball can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC0/
>
> The artifacts have been signed with Key : 4FD8BC09C7E9DB81, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> Release note about this version:
> https://issues.apache.org/jira/projects/WEEX/issues/WEEX-464
> This vote will remain open for at least 72 hours.
> Please vote on releasing this RC.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks.
> Adam Feng
>



-- 

Best Wishes！
_danz

Re: [DISCUSS] Forward to our second Apache release (0.19)

[He Sai]

For the record, I've removed some irrelative dependencies in the
POSSIBLE-NOTICES-FOR-BIN-DIST,
which are 'autoprefixer', 'query-string' and 'weex-picker', since we
haven't used this packages
as dependencies for a while. I also fixed the repo url for weex-vue-render.
Adam, can you
checkout the pr here: https://github.com/apache/incubator-weex/pull/1204 ?

Thanks.


2018-05-23 10:56 GMT+08:00 Adam Feng :

> Thanks,  It looks much clearer to me.
>
> So can I ask if it is OK to only provide the source release in Apache？
>
> Weex, by its nature, has a complicated codebase, it includes
> iOS/Android/Web/JS code, and the environment required to build Weex
> includes NodeJS/JDK/Android SDK/Gradle/Xcode, it is far from a java project
> with a jar output.   I suppose it’s difficult for us to release Weex in a
> single binary.
>
> If it is OK,  can we provide the source release using the current version
> of POSSIBLE-NOTICES-FOR-BIN-DIST?
>
> In any case,  I will go through the POSSIBLE-NOTICES-FOR-BIN-DIST later
> and check every dependency to see if some additional notice is really
> required.
>
> Thanks.
> Adam Feng
>
> On 23 May 2018, 9:29 AM +0800, Willem Jiang ,
> wrote:
> > Hi,
> >
> > For the source release, the NOTICE file looks good.
> > I just checked the release you did last year, it looks like you only
> > provide the source release, so it's OK.
> > But for the POSSIBLE-NOTICES-FOR-BIN-DIST, it looks you put the all the
> > third party License information into the NOTICE file.
> > It's a common mistake. NOTICE is not supposed to hold the LICENSE
> > information, if you are planing to do the binary release, you need to
> > provide another version of License to hold the third party license
> > information there.
> >
> >
> >
> >
> > Willem Jiang
> >
> > Blog: http://willemjiang.blogspot.com (English)
> > http://jnn.iteye.com (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, May 22, 2018 at 11:06 PM, Adam Feng  wrote:
> >
> > > Thanks for the document, Willem. I have just read through it and have
> > > some confusions here：
> > >
> > > > NOTICE is reserved for a certain subset of legally required
> > > notifications which are not satisfied by either the text of LICENSE or
> the
> > > presence of licensing information embedded within the bundled
> dependency.
> > > Aside from Apache-licensed dependencies which supply NOTICE files of
> their
> > > own, it is uncommon for a dependency to require additions to NOTICE.
> > > > Copyright notifications which have been relocated from source files
> > > (rather than removed) must be preserved in NOTICE. However, elements
> such
> > > as the copyright notifications embedded within BSD and MIT licenses
> need
> > > not be duplicated in NOTICE -- it suffices to leave those notices in
> their
> > > original locations.
> > > > It is important to keep NOTICE as brief and simple as possible, as
> each
> > > addition places a burden on downstream consumers.
> > > > Do not add anything to NOTICE which is not legally required.
> > > 1. I can’t figure out any special cases that we need modify NOTICE for
> src
> > > release, so if the LICENSE file[1] is good for the src release， will a
> > > clean NOTICE[2] be OK for src release ?
> > > 2. I see why the POSSIBLE-NOTICES-FOR-BIN-DIST[3] file come in the
> > > mailing thread[4], it is supposed to be used in binary release, should
> we
> > > create another POSSIBLE-LICENSE-FOR-BIN-DIST file? For most of what's
> being
> > > called out in NOTICE should actually be in LICENSE, but the last Weex
> > > Release[5] which had passed voting was not including such file.
> > >
> > > Please give your comment, thanks!
> > >
> > >
> > > [1] https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > weex.git;a=blob_plain;f=LICENSE;hb=f44a8fd5d6e0d9fb2292f921ebbef8
> > > 424563f93d
> > > [2] https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > weex.git;a=blob_plain;f=NOTICE;hb=f44a8fd5d6e0d9fb2292f921ebbef8
> 424563f93d
> > > [3] https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > weex.git;a=blob_plain;f=POSSIBLE-NOTICES-FOR-BIN-DIST;hb=
> > > f44a8fd5d6e0d9fb2292f921ebbef8424563f93d
> > > [4] https://lists.apache.org/thread.html/
> 636530863af603203bb3320a93b3f2
> > > 4e38bbeaf8a2cacb420f6f6734@%3Cgeneral.incubator.apache.org%3E
> > > [5] http://apache.org/dist/incubator/weex/0.12.0-incubating/
> > >
> > >
> > >
> > > Thanks.
> > > Adam Feng
> > >
> > > On 22 May 2018, 7:48 PM +0800, Willem Jiang ,
> > > wrote:
> > > > The LICENSE file looks good for the src release, but for the NOTICE
> is
> > > not
> > > > right.
> > > > For the binary release, you need to provide another LICENSE file.
> Please
> > > go
> > > > through the document here[1].
> > > >
> > > > [1]http://www.apache.org/dev/licensing-howto.html
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Blog: http://willemjiang.blogspot.com (English)
> > > > 

Re: Separate the weex-vue-render from the incubator-weex repo

[He Sai]

Yes.. About that, I think we should have more discussion on not just
renders but all the js codes in 'html5' folder, because there may be other
legacy codes we might want to remove or archive.

Firstly, the codes in html5/render/ include three different web renderer.
They should be removed, but the render/native is just a entry file for
frameworks. Maybe the native render should be moved to the html5/frameworks
as well.

Secondly, should we remove it once for all, or should we just archive it
into the path of html5/render/legacy ? Since the way we dealing with the
old js-framework is like this.

At last, what we do here is to clear out the DSL layer code, making weex
more concentrative and foucs on the core SDK and js-runtime, so that our
main project structure could be much clearer and more lightweight.

I tend to remove all the codes in html5 including frameworks and renders,
move runtime codes into a 'runtime' path, and import whichever js-framework
into that runtime codes from npm packages.

The structure might be like this:

```
- android
- ios
- html5
- runtime (new) / all the js runtime code here...
- ...
```




2017-12-22 14:17 GMT+08:00 Hanks Zhang <zhanghan...@gmail.com>:

> I noticed that the weex-vue-render have already been moved to
> https://github.com/weexteam/weex-vue-render
>
> So, I think the source code of it should be removed from the
> [apache/incubator-weex] repo. I created an issue to track it:
> https://issues.apache.org/jira/browse/WEEX-181
>
>
>
> 2017-12-19 23:42 GMT+08:00 He Sai <tekk...@gmail.com>:
>
> > @Jonathan Dong, Great, Thanks ! I'll transfer it into weexteam group
> soon.
> >
> > 2017-12-19 19:04 GMT+08:00 Jonathan Dong <jondong.commun...@outlook.com
> >:
> >
> > > That is nice. I can help to create a repo in
> https://github.com/weexteam
> > > to host the codes here instead of using a personal github account.
> > >
> > > On 19 Dec 2017, 5:52 PM +0800, He Sai <tekk...@gmail.com>, wrote:
> > > I think it's better to separate it from this repo. It's more like a DSL
> > > layer stuff, a
> > > javascript framework to run the dot vue file on web platform, not a
> > feature
> > > of
> > > weex SDK it self. Since the rax DSL framework is not included in this
> > repo,
> > > it's
> > > more or less the same.
> > >
> > > I have already created a new repo for these codes, with building
> scripts
> > > and
> > > test cases:
> > >
> > > https://github.com/MrRaindrop/weex-vue-render
> > >
> > > The main project in this repo should be more focusing and cleaner,
> > > and the render codes in html5 folder could all be removed later.
> > >
> > > 2017-12-19 17:31 GMT+08:00 Hanks Zhang <zhanghan...@gmail.com>:
> > >
> > > The "weex-vue-render" is a component and module library for Vue.js. It
> > > enables pages written in Weex + Vue to run on the Web platform. It can
> be
> > > used to downgrade the weex native pages to web pages.
> > >
> > > However, I think this package should separate from the incubator-weex
> > repo.
> > >
> > > Because it doesn't rely on any code of WeexSDK, and WeexSDK doesn't
> rely
> > on
> > > any code of weex-vue-render neither. Even the vue framework itself is
> > > separated from the incubator-weex repo, weex require it as a
> dependency,
> > > not to mention that weex-vue-render is not a part of WeexSDK.
> > >
> > > Moreover, weex-vue-render also required many web dependencies which
> could
> > > not be used in WeexSDK. I think it's a better to keep the source code
> of
> > > incubator-weex more simple and move the weex-vue-render and its
> > > dependencies to a separate repo.
> > >
> > >
> > >
> > >
> > > --
> > > 
> > > Best Wishes！
> > > _danz
> > >
> >
> >
> >
> > --
> > 
> > Best Wishes！
> > _danz
> >
>



-- 

Best Wishes！
_danz

Re: Separate the weex-vue-render from the incubator-weex repo

[He Sai]

I think it's better to separate it from this repo. It's more like a DSL
layer stuff, a
javascript framework to run the dot vue file on web platform, not a feature
of
weex SDK it self. Since the rax DSL framework is not included in this repo,
it's
more or less the same.

I have already created a new repo for these codes, with building scripts and
test cases:

https://github.com/MrRaindrop/weex-vue-render

The main project in this repo should be more focusing and cleaner,
and the render codes in html5 folder could all be removed later.

2017-12-19 17:31 GMT+08:00 Hanks Zhang :

> The "weex-vue-render" is a component and module library for Vue.js. It
> enables pages written in Weex + Vue to run on the Web platform. It can be
> used to downgrade the weex native pages to web pages.
>
> However, I think this package should separate from the incubator-weex repo.
>
> Because it doesn't rely on any code of WeexSDK, and WeexSDK doesn't rely on
> any code of weex-vue-render neither. Even the vue framework itself is
> separated from the incubator-weex repo, weex require it as a dependency,
> not to mention that weex-vue-render is not a part of WeexSDK.
>
> Moreover, weex-vue-render also required many web dependencies which could
> not be used in WeexSDK. I think it's a better to keep the source code of
> incubator-weex more simple and move the weex-vue-render and its
> dependencies to a separate repo.
>



-- 

Best Wishes！
_danz

Re: Where's the rest?!?

[He Sai]

Dear Bircher,

You are right. Most of the discusses happens in the github repo issue, or
some places else. I think we need more communication in this mail list, and
embrace the Apache way. And Welcome all the proposal, suggestions and
questions on weex project from all you guys who have subscribed this mail
list.

2017-08-15 23:25 GMT+08:00 NetPuter :

> No more discussion in the mail list?
>
> 2017-06-09 17:56 GMT+08:00 jerry.s :
>
> > Hi, NetPuter:
> >
> > You're welcome. if you have any suggestion about weex, we can discuss
> here
> > :-)
> >
> > Best Regards
> > Jerry
> >
> > > 在 2017年6月9日，下午5:42，NetPuter  写道：
> > >
> > > As a external weex user, it is great to hear more about weex.
> > >
> > > 2017-06-09 17:33 GMT+08:00 xing zhang :
> > >
> > >> Yeah，you are right, I just ignore this, and will talk more later, do
> > more
> > >> on mailing list， thx for your support.
> > >>
> > >> 2017-06-09 16:16 GMT+08:00 Raphael Bircher  >:
> > >>
> > >>> Hi folks,
> > >>>
> > >>> We have the first release out. That's great. But as you all know, we
> > just
> > >>> started here. One thing who is really bad at this project, (sorry I
> > can't
> > >>> say it otherwise) you don't communicate in public. On the mailing
> list
> > >> it's
> > >>> more or less a dialog between sospartan end me. I know, there are
> much
> > >> more
> > >>> people behind this project. At the moment weex is a company project
> who
> > >>> stands under a Open Source License, but it's not an Open Source
> > project.
> > >>>
> > >>> At the moment, if you come from outside, you miss all the
> > communication.
> > >>> That's a big issue. Since I'm on this list, I didn't see a single
> > >> Proposal.
> > >>> Only as an example.
> > >>>
> > >>> So please come on this list, and talk. I know, it's not easy to learn
> > the
> > >>> Apache Way, but we will support you!
> > >>>
> > >>> Regards, Raphael
> > >>>
> > >>> --
> > >>> My introduction https://youtu.be/Ln4vly5sxYU
> > >>>
> > >>
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > NetPuter Lin *»* 
> >
> >
>
>
> --
> Best Regards,
> NetPuter Lin *»* 
>



-- 

Best Wishes！
_danz

Re: [VOTE]Apache Weex-incubating Release 0.12.0-RC3

[He Sai]

+1

2017-04-30 1:12 GMT+08:00 申远 :

> +1
> > 在 2017年4月28日，16:59，sospartan  写道：
> >
> > This should be 'RC2', since it's the third RC of 0.12.0, after RC0 and
> RC1.
> > But I make a mistake in last vote in IPMC, already used the name "RC2".
> So
> > 
> >
> > On Fri, Apr 28, 2017 at 4:51 PM, sospartan  wrote:
> >
> >> Hi Weex PPMC,
> >> I'll calling a vote for release Weex-incubating 0.12.0-RC3.
> >>
> >> The tag to be voted upon:
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> >> ;a=shortlog;h=refs/tags/0.12.0-rc3
> >>
> >> The commit hash:
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.
> git;a=commit;h=
> >> 702d04c4922105069f537afdb4688f808530994d
> >>
> >> The source tarball can be found at:
> >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0
> >> -incubating/RC3/
> >>
> >> The fingerprint of key to sign release artifacts:
> >> 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
> >>
> >> Release artifacts are signed with the following key:
> >> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> >>
> >> Release note about this version:
> >> https://issues.apache.org/jira/browse/WEEX-26
> >>
> >> This vote will remain open for at least 72 hours.
> >> Please vote on releasing this RC.
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >>
> >> --
> >> Best Regards!
> >> --
> >>
> >> sospartan
> >> https://weex-project.io
> >>
> >
> >
> >
> > --
> > Best Regards!
> > --
> >
> > sospartan
> > https://weex-project.io
>
>


-- 

Best Wishes！
_danz

[RESULT][VOTE] New Committer: Tancy

[He Sai]

Hi,

I've called a vote for inviting Tancy as new weex commiter. It's been more
than a week.
The result:

+1 votes: 3 binding

+0  votes: 0 binding

 -1 votes: 0 binding


This vote is ***SUCCESSFUL***.

Thanks to  sospartan, Adam Feng and shenyuan for this votes.

-- 

Best Wishes！
_danz

Re: [VOTE] Release of Apache Weex (incubating) 0.12.0-RC1

[He Sai]

+1

2017-04-18 10:15 GMT+08:00 shihan zheng :

> +1
>
> 2017-04-18 10:01 GMT+08:00 Adam Feng :
>
> > +1
> >
> > Thanks.
> > Adam Feng
> >
> > On 2017年4月18日 +0800 AM10:00, 宁栗 , wrote:
> > > +1
> > >
> > > 2017-04-17 15:30 GMT+08:00 sospartan :
> > >
> > > > Hi Weex PPMC,
> > > >
> > > > I'm calling this vote to release Apache Weex 0.12.0-RC1.
> > > >
> > > > The tag to be voted upon:
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.
> > > > git;a=shortlog;h=refs/tags/0.12.0-rc1
> > > >
> > > > The commit hash:
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.
> > > > git;a=commit;h=9ac0c82443e65b1c9d8a2714fea6b9a5b8af9907
> > > >
> > > > The source tarball can be found at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.
> > > > 0-incubating/RC1/
> > > >
> > > > The fingerprint of key to sign release artifacts:
> > > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> > > >
> > > > Release note about this version:
> > > > https://issues.apache.org/jira/browse/WEEX-26
> > > >
> > > > This vote will remain open for at least 72 hours.
> > > > Please vote on releasing this RC.
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > > > --
> > > > Best Regards!
> > > > --
> > > >
> > > > sospartan
> > > > https://weex-project.io
> > > >
> >
>
>
>
> --
>
> Best Regards!
> -
> Shihan Zheng (Weex project team member )
>



-- 

Best Wishes！
_danz