Re: [VOTE] Apache Gearpump (incubating) 0.8.2-RC2

[Kam Kasravi]

The vote from the IPMC member community has passed with 3 +1 votes.
Thank you IPMC members for voting!! I'll announce the
gearpump-0.8.2-incubating shortly.


Thanks
Kam

On Mon, Nov 21, 2016 at 8:13 PM, Kam Kasravi  wrote:

> Hi IPMC Community
>
> The PPMC vote to release Apache Gearpump (incubating) 0.8.2-RC2 has passed.
> We would like to now submit this release candidate to the IPMC.
>
> The PPMC vote thread is here: 
> https://lists.apache.org/thread.html/2806964890bbcf4c8e5b0b871d5061e1e110b45435cd8135ebfa2964@%3Cdev.gearpump.apache.org%3E
>
> The source and binary tarballs including signatures, digests, etc. can be 
> found 
> at:https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.2-incubating/RC2/
>
> The release hash
> is: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=tree;h=4ab8cfae10e4f6a24a6f083352b2ca5bc9a186ab;hb=refs/tags/0.8.2-RC2
>
> Release artifacts are signed with the following
> key: https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
>
> The KEYS file is available
> here: https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
>
> For information about the contents of this release (including fixes
> for prior failed release candidates) 
> see:https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=blob;f=CHANGELOG.md;h=24df95951fa2f5aee49d3a5c973b92ce28214bf1;hb=refs/tags/0.8.2-RC2
>
> The vote will be open for 72 hours (Thurs, Nov 24, 2016 at 8:30PM PST)
>
> Please download the release candidate and evaluate the necessary items 
> including checking hashes, signatures, build from source, run the
> binary artifacts in the binary release and test.
> Please vote:
>
> [ ] +1 Release this package as gearpump-0.8.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> Thanks,
> Kam
>
>
>

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

[Justin Mclean]

Hi,

> but I wanted to specifically clarify [5] referenced below.  This license is 
> not considered Category X either — do you know what the status of 4-clause 
> BSD is?

My understanding it’s considered Category X.

Unless that is you can contact the author and ask if adding something to NOTICE 
is enough to satisfy the advertising clause. Like what done with OpenSSL.

See legal discuss on the topic here [1], the rest of the thread may help as 
well.

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/557a49d678809e2c543ef465dc36b2bd02eb02fda3c484f204468e39@%3Clegal-discuss.apache.org%3E
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[CANCEL][VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

[Christopher Collins]

Hello all,

Voting for the release of Apache Mynewt 1.0.0, beta 1, rc1 has been cancelled
due to some out of date LICENSE files.

Sorry for the confusion, and thank you to everyone who voted.  A second
release candidate will be put up for a vote on the dev list shortly.

Thanks,
Chris

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

[Christopher Collins]

Thanks, Justin.  Somehow I completely forgot to update the LICENSE
files this time around.  I'll cancel the vote.

Chris

On Tue, Nov 29, 2016 at 02:13:02PM +1100, Justin Mclean wrote:
> Hi,
> 
> -1 binding due to LICENSE issues (see below) and cryptography issues 
> (tinycrypt and polarssl) and there’s a license incompatible with Apache 
> license 2.0 in the release. [5] (4 clause BSD)
> 
> It looks like tinycrypt and polarssl has been added  since last release but 
> not listed here(?) [2]
> 
> I checked:
> - artefacts include incubating
> - signatures and hashes good
> - NOTICE is good
> - LICENSE is missing quite a few items (see below)
> - DISCLAIMER exists
> - All source files have headers
> - No unexpected binary files in release
> 
> The LICENSE files for core and newt are identical to last release but several 
> 3rd party items have been added
> 
> For core:
> - BSD licensed  tiny crypt  copyright (c) 2015, Intel Corporation [3]
> - BSD license PPP copyright (c) 1994-2002 Paul Mackerras [4]+
> - BSD license CHAP/MD5 copyright (c) 1994-2002 Paul Mackerras [4]+
> - BSD license CHAP copyright (c) 1995 Eric Rosenquist. [4]
> - PD license EAP for PP  2001 by Sun Microsystems, Inc. [4]
> - BSD license PPP Encryption copyright (c) 2002 Google, Inc.[4]
> - BSD license EUI64 copyright (c) 1999 Tommi Komulainen[4]+
> - BSD license assorted files copyright (c) 1984-2000 Carnegie Mellon 
> University. [4]+
> - MIT licensed PPP copyright (c) 2003 by Marc Boucher and Copyright (c) 1997 
> Global Election Systems Inc. [4]+
> - BSD licensed files copyright 2016 STMicroelectronics [6]
> - BSD licensed code based on XySSL copyright (C) 2006-2008  Christophe Devine 
> [7]
> - BSD licensed polarssl  copyright (C) 2009  Paul Bakker [7]
> - BSD license SNMP copyright (c) 2001, 2002 Leon Woestenberg and copyright 
> (c) 2001, 2002 Axon Digital Design B.V. [8] (and other files)
> - BSD licensed lwIP TCP/IP stack copyright (c) 2001, 2002 Swedish Institute 
> of Computer Science. [9]
> - BSD licensed IGMP copyright (c) 2002 CITEL Technologies Ltd. [10]
> - BSD license AutoIP copyright (c) 2007 Dominik Spies [11]
> - BSD license files copyright (c) 2013 - 2015, Freescale Semiconductor, Inc. 
> [12]
> - BSD licensed coap copyright 2016 Intel Corporation and 2013, Institute for 
> Pervasive Computing, ETH Zurich [13] 
> - and about a dozen others (including ARM and Nordic Semiconductor) as I gave 
> up at this point
> 
> Note the lines marked + have an additional clause (required notice) that 
> effects the NOTICE file (I think).
> 
> For newt:
> - PD licensed code copyright (c) 2012 Miki Tebeka [14]
> - 20 or so MIT(?) licensed files [15] copyright Ugorji Nwoke [15]
> - MIT licensed go coap copyright (c) 2013 Dustin Sallings [16]
> - BSD licensed gatt  copyright (c) 2014 PayPal Inc [17]
> - MIT licensed xpc [18]
> - MIT licensed gioctl copyright (c) 2014 Mark Wolfe [19]
> 
> This file [5] is licensed under a 4 clause BSD license which is not on the 
> list of approved licenses. 
> 
> Also looks like you download page need updating to provide links to download 
> the voted on artefacts for the last release. [1]
> 
> Thanks,
> Justin
> 
> 1. https://mynewt.apache.org/download/
> 2. https://www.apache.org/licenses/exports/
> 3. ./apache-mynewt-core-1.0.0-b1-incubating/crypto/tinycrypt/*
> 4. ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/*
> 5. 
> ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/pppoe.c
> 6. 
> ./apache-mynewt-core-1.0.0-b1-incubating/hw/mcu/stm/stm32f4xx/src/ext/Drivers/CMSIS/Device/ST/STM32F4xx/*
> 7. 
> ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/polarssl/*
> 8. 
> ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/include/lwip/apps/snmp.h
> 9. ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/
> 10. 
> ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/core/ipv4/igmp.c
> 11. 
> ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/core/ipv4/autoip.c
> 12. 
> ./apache-mynewt-core-1.0.0-b1-incubating/hw/mcu/nxp/src/ext/sdk-2.0-frdm-k64f_b160321/devices/MK64F12/*
> 13. ./apache-mynewt-core-1.0.0-b1-incubating/net/oic/src/messaging/coap/*
> 14. 
> ./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/Sirupsen/logrus/alt_exit.go
> 15  
> ./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/ugorji/go/codec/*.go
> 16 
> ./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/dustin/go-coap/LICENSE
> 17 
> ./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/*
> 18 
> ./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/xpc/*
> 19. 
> ./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/linux/gioctl/*
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

[Sterling Hughes]

Thanks Justin.

I’ll let Chris chime in on the rest of the notices (or just fix them), 
but I wanted to specifically clarify [5] referenced below.  This license 
is not considered Category X either — do you know what the status of 
4-clause BSD is?


Its low risk to remove that file, and we can eventually replace it.  I 
just wanted to clarify license status.


Sterling

On 28 Nov 2016, at 19:13, Justin Mclean wrote:


Hi,

-1 binding due to LICENSE issues (see below) and cryptography issues 
(tinycrypt and polarssl) and there’s a license incompatible with 
Apache license 2.0 in the release. [5] (4 clause BSD)


It looks like tinycrypt and polarssl has been added  since last 
release but not listed here(?) [2]


I checked:
- artefacts include incubating
- signatures and hashes good
- NOTICE is good
- LICENSE is missing quite a few items (see below)
- DISCLAIMER exists
- All source files have headers
- No unexpected binary files in release

The LICENSE files for core and newt are identical to last release but 
several 3rd party items have been added


For core:
- BSD licensed  tiny crypt  copyright (c) 2015, Intel Corporation [3]
- BSD license PPP copyright (c) 1994-2002 Paul Mackerras [4]+
- BSD license CHAP/MD5 copyright (c) 1994-2002 Paul Mackerras [4]+
- BSD license CHAP copyright (c) 1995 Eric Rosenquist. [4]
- PD license EAP for PP  2001 by Sun Microsystems, Inc. [4]
- BSD license PPP Encryption copyright (c) 2002 Google, Inc.[4]
- BSD license EUI64 copyright (c) 1999 Tommi Komulainen[4]+
- BSD license assorted files copyright (c) 1984-2000 Carnegie Mellon 
University. [4]+
- MIT licensed PPP copyright (c) 2003 by Marc Boucher and Copyright 
(c) 1997 Global Election Systems Inc. [4]+

- BSD licensed files copyright 2016 STMicroelectronics [6]
- BSD licensed code based on XySSL copyright (C) 2006-2008  Christophe 
Devine [7]

- BSD licensed polarssl  copyright (C) 2009  Paul Bakker [7]
- BSD license SNMP copyright (c) 2001, 2002 Leon Woestenberg and 
copyright (c) 2001, 2002 Axon Digital Design B.V. [8] (and other 
files)
- BSD licensed lwIP TCP/IP stack copyright (c) 2001, 2002 Swedish 
Institute of Computer Science. [9]

- BSD licensed IGMP copyright (c) 2002 CITEL Technologies Ltd. [10]
- BSD license AutoIP copyright (c) 2007 Dominik Spies [11]
- BSD license files copyright (c) 2013 - 2015, Freescale 
Semiconductor, Inc. [12]
- BSD licensed coap copyright 2016 Intel Corporation and 2013, 
Institute for Pervasive Computing, ETH Zurich [13]
- and about a dozen others (including ARM and Nordic Semiconductor) as 
I gave up at this point


Note the lines marked + have an additional clause (required notice) 
that effects the NOTICE file (I think).


For newt:
- PD licensed code copyright (c) 2012 Miki Tebeka [14]
- 20 or so MIT(?) licensed files [15] copyright Ugorji Nwoke [15]
- MIT licensed go coap copyright (c) 2013 Dustin Sallings [16]
- BSD licensed gatt  copyright (c) 2014 PayPal Inc [17]
- MIT licensed xpc [18]
- MIT licensed gioctl copyright (c) 2014 Mark Wolfe [19]

This file [5] is licensed under a 4 clause BSD license which is not on 
the list of approved licenses.


Also looks like you download page need updating to provide links to 
download the voted on artefacts for the last release. [1]


Thanks,
Justin

1. https://mynewt.apache.org/download/
2. https://www.apache.org/licenses/exports/
3. ./apache-mynewt-core-1.0.0-b1-incubating/crypto/tinycrypt/*
4. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/*
5. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/pppoe.c
6. 
./apache-mynewt-core-1.0.0-b1-incubating/hw/mcu/stm/stm32f4xx/src/ext/Drivers/CMSIS/Device/ST/STM32F4xx/*
7. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/polarssl/*
8. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/include/lwip/apps/snmp.h

9. ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/
10. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/core/ipv4/igmp.c
11. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/core/ipv4/autoip.c
12. 
./apache-mynewt-core-1.0.0-b1-incubating/hw/mcu/nxp/src/ext/sdk-2.0-frdm-k64f_b160321/devices/MK64F12/*
13. 
./apache-mynewt-core-1.0.0-b1-incubating/net/oic/src/messaging/coap/*
14. 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/Sirupsen/logrus/alt_exit.go
15  
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/ugorji/go/codec/*.go
16 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/dustin/go-coap/LICENSE
17 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/*
18 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/xpc/*
19. 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/linux/gioctl/*



-
To unsubscribe, e-mail: 

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

[Justin Mclean]

Hi,

-1 binding due to LICENSE issues (see below) and cryptography issues (tinycrypt 
and polarssl) and there’s a license incompatible with Apache license 2.0 in the 
release. [5] (4 clause BSD)

It looks like tinycrypt and polarssl has been added  since last release but not 
listed here(?) [2]

I checked:
- artefacts include incubating
- signatures and hashes good
- NOTICE is good
- LICENSE is missing quite a few items (see below)
- DISCLAIMER exists
- All source files have headers
- No unexpected binary files in release

The LICENSE files for core and newt are identical to last release but several 
3rd party items have been added

For core:
- BSD licensed  tiny crypt  copyright (c) 2015, Intel Corporation [3]
- BSD license PPP copyright (c) 1994-2002 Paul Mackerras [4]+
- BSD license CHAP/MD5 copyright (c) 1994-2002 Paul Mackerras [4]+
- BSD license CHAP copyright (c) 1995 Eric Rosenquist. [4]
- PD license EAP for PP  2001 by Sun Microsystems, Inc. [4]
- BSD license PPP Encryption copyright (c) 2002 Google, Inc.[4]
- BSD license EUI64 copyright (c) 1999 Tommi Komulainen[4]+
- BSD license assorted files copyright (c) 1984-2000 Carnegie Mellon 
University. [4]+
- MIT licensed PPP copyright (c) 2003 by Marc Boucher and Copyright (c) 1997 
Global Election Systems Inc. [4]+
- BSD licensed files copyright 2016 STMicroelectronics [6]
- BSD licensed code based on XySSL copyright (C) 2006-2008  Christophe Devine 
[7]
- BSD licensed polarssl  copyright (C) 2009  Paul Bakker [7]
- BSD license SNMP copyright (c) 2001, 2002 Leon Woestenberg and copyright (c) 
2001, 2002 Axon Digital Design B.V. [8] (and other files)
- BSD licensed lwIP TCP/IP stack copyright (c) 2001, 2002 Swedish Institute of 
Computer Science. [9]
- BSD licensed IGMP copyright (c) 2002 CITEL Technologies Ltd. [10]
- BSD license AutoIP copyright (c) 2007 Dominik Spies [11]
- BSD license files copyright (c) 2013 - 2015, Freescale Semiconductor, Inc. 
[12]
- BSD licensed coap copyright 2016 Intel Corporation and 2013, Institute for 
Pervasive Computing, ETH Zurich [13] 
- and about a dozen others (including ARM and Nordic Semiconductor) as I gave 
up at this point

Note the lines marked + have an additional clause (required notice) that 
effects the NOTICE file (I think).

For newt:
- PD licensed code copyright (c) 2012 Miki Tebeka [14]
- 20 or so MIT(?) licensed files [15] copyright Ugorji Nwoke [15]
- MIT licensed go coap copyright (c) 2013 Dustin Sallings [16]
- BSD licensed gatt  copyright (c) 2014 PayPal Inc [17]
- MIT licensed xpc [18]
- MIT licensed gioctl copyright (c) 2014 Mark Wolfe [19]

This file [5] is licensed under a 4 clause BSD license which is not on the list 
of approved licenses. 

Also looks like you download page need updating to provide links to download 
the voted on artefacts for the last release. [1]

Thanks,
Justin

1. https://mynewt.apache.org/download/
2. https://www.apache.org/licenses/exports/
3. ./apache-mynewt-core-1.0.0-b1-incubating/crypto/tinycrypt/*
4. ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/*
5. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/pppoe.c
6. 
./apache-mynewt-core-1.0.0-b1-incubating/hw/mcu/stm/stm32f4xx/src/ext/Drivers/CMSIS/Device/ST/STM32F4xx/*
7. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/netif/ppp/polarssl/*
8. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/include/lwip/apps/snmp.h
9. ./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/
10. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/core/ipv4/igmp.c
11. 
./apache-mynewt-core-1.0.0-b1-incubating/net/ip/lwip_base/src/core/ipv4/autoip.c
12. 
./apache-mynewt-core-1.0.0-b1-incubating/hw/mcu/nxp/src/ext/sdk-2.0-frdm-k64f_b160321/devices/MK64F12/*
13. ./apache-mynewt-core-1.0.0-b1-incubating/net/oic/src/messaging/coap/*
14. 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/Sirupsen/logrus/alt_exit.go
15  
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/ugorji/go/codec/*.go
16 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/dustin/go-coap/LICENSE
17 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/*
18 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/xpc/*
19. 
./apache-mynewt-newt-1.0.0-b1-incubating/newtmgr/vendor/github.com/runtimeinc/gatt/linux/gioctl/*


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Joshua 6.1 RC#2

[Justin Mclean]

Hi,

Sorry but it’s -1 (binding) as:
- Your missing incubating in the release artefacts name. [1]
- There are a number of binary files in the source release that look to be 
compiled source code.

I checked:
- name doesn’t include incubating
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE is missing a few things (see below)
- a source file is missing an Apache header [7]
- Several unexpected binary files are contained in the source release 
[8][9][10][11]
- Can compile from source

License is missing:
- MIT licensed normalize.css v3.0.3 bundled in [5]
- glyph icon fonts [6]

Not an issue but it's a little odd to have LICENSE and NOTICE.txt - usually 
both are bare or both have .txt extension.

Also while looking at your site I noticed that the download links of you 
incubating site [2] points to github, please change to point to the offical 
release area.
Also the 6.1 release has already been tagged and it available for public 
download on github [4]  before this vote is finished. This is IMO against 
Apache release policy [3] please remove.

I also notice you recently released the language packs (18th Nov) but there 
doesn’t seem to have been a vote for that? Any reason for this?

Thanks,
Justin

1. http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
2. 
https://cwiki.apache.org/confluence/display/JOSHUA/Apache+Joshua+%28Incubating%29+Home
3. http://www.apache.org/dev/release.html#what
4. https://github.com/apache/incubator-joshua/releases
5. ./demo/bootstrap/css/bootstrap.min.css
6. apache-joshua-6.1/demo/bootstrap/fonts/*
7. ./src/test/java/org/apache/joshua/decoder/ff/tm/OwnerMapTest.java
8. ./bin/GIZA++
9. ./bin/mkcls
10. ./bin/snt2cooc.out
11. ,/src/test/resources/berkeley_lm/lm.berkeleylm.gz


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Joshua 6.1 RC#2

[lewis john mcgibbney]

Hello general@,
Please VOTE on the Apache Joshua 6.1 Release Candidate #2.
This RC#2 has already successfully passed a VOTE over on user@ and
dev@joshua and RESULTS were as follows

[10] +1, let's get it released!!!
Lewis John McGibbney*
Matt Post
Tommaso Teofili*
John Hewitt
Kellen Sunderland
Tom Barber*
Chris A. Mattmann*
Henry Saptura*
Michael A. Hedderich
Felix Hieber

[0] +/-0, fine, but consider to fix few issues before...
[0] -1, nope, because... (and please explain why)

*IPMC-binding

We solved ~50 issues: https://s.apache.org/joshua6.1

Git source tag (29c8be650d53216f779a340d33f8f61af4d45629):
https://s.apache.org/pk2t 

Staging repo: https://repository.apache.org/content/repositories/
orgapachejoshua-1001/


Source Release Artifacts: https://dist.apache.org/repos/
dist/dev/incubator/joshua/

PGP release keys (signed using 48BAEBF6): https://dist.apache.org/repos/
dist/release/incubator/joshua/KEYS

Vote will be open for 72 hours.
Thank you to everyone that is able to VOTE as well as everyone that
contributed to Apache Joshua 6.1.

[ ] +1, let's get it released!!!
[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

P.S. here is my +1

-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re：[VOTE] Weex to enter the Apache Incubator

[BryantWu]

+1(non-binding)

Thanks for Edward j. Yoon 's  nice suggestion。

Regards

BryantWu--发件人：Edward
 J. Yoon 发送时间：2016年11月29日(星期二) 
04:53收件人：general@incubator.apache.org ; 吴志华(天施) 
主　题：Re: 回复：[VOTE] Weex to enter the Apache Incubator
吴志华(天施),

Of course, you can cast your vote. But your vote is non-binding.

And this list's subscribers are from various countries. Always use
text as your email format and create the email signature as english
nickname.

Thanks.


On Tue, Nov 29, 2016 at 12:49 AM, 吴志华(天施)  wrote:
>BryantWuhuaz...@gmail.com (Alibaba Inc)。Weex Init 
>developer
> Can I vote for Weex Project? I love Weex so 
>much。--发件人：Daniel
> Gruno 发送时间：2016年11月28日(星期一) 23:17收件人：general 
>主 题：Re: 回复：[VOTE] Weex to enter the Apache 
>Incubator
>
> On 11/28/2016 04:06 PM, 吴志华(天施) wrote:
>>
>>  +1 (binding)
>
> For binding +1s, we generally require a name we can compare with our
> Apache Phonebook to make sure you are on the IPMC. I was unable to find
> you as a committer, could you please tell me your apache ID?
>
> With regards,
> Daniel.
>
>> 
>>--发件人：Stephan 
>>Ewen 发送时间：2016年11月28日(星期一) 18:02收件人：general 
>>主 题：Re: [VOTE] Weex to enter the Apache 
>>Incubator
>> +1 (binding)
>>
>>
>> On Sun, Nov 27, 2016 at 1:44 AM, Luke Han  wrote:
>>
>>>  +1 binding
>>>
>>>  Get Outlook for iOS
>>>
>>>
>>>
>>>
>>>  On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" <
>>>  willem.ji...@gmail.com> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  +1 （binding）
>>>
>>>
>>>  Willem Jiang
>>>
>>>  Blog: http://willemjiang.blogspot.com (English)
>>>http://jnn.iteye.com  (Chinese)
>>>  Twitter: willemjiang
>>>  Weibo: 姜宁willem
>>>
>>>  On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon
>>>  wrote:
>>>
>>>  > Greetings!
>>>  >
>>>  > I would like to call a vote for accepting "Weex" for incubation in the
>>>  > Apache Incubator. The full proposal is available below.  We ask the
>>>  > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion,
>>>  and
>>>  > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to
>>>  be
>>>  > Mentors.
>>>  >
>>>  > Please cast your vote:
>>>  >
>>>  > [ ] +1, bring Weex into Incubator
>>>  > [ ] +0, I don't care either way,
>>>  > [ ] -1, do not bring Weex into Incubator, because...
>>>  >
>>>  > This vote will be open at least for 72 hours and only votes from the
>>>  > Incubator PMC are binding.
>>>  >
>>>  > --
>>>  > https://wiki.apache.org/incubator/WeexProposal
>>>  >
>>>  > = Weex Proposal =
>>>  >
>>>  > == Abstract ==
>>>  > Weex is a framework for building Mobile cross-platform high performance
>>>  UI.
>>>  > Weex enables developers to use Web-like syntax to build iOS, Android and
>>>  > Web
>>>  > UI with a single codebase.
>>>  >
>>>  > == Proposal ==
>>>  > Weex provide an uniform Web-like syntax for develop native Mobile App UI.
>>>  > By
>>>  > leverage the Javascript engine that enable dynamic update, the process of
>>>  > App interfce and content update can be simple and controllable just like
>>>  > Web.Compared with WebView based UI framework which performance are
>>>  limited,
>>>  > Weex use build-in native components instead.
>>>  >
>>>  > Because of tag based syntax that maintain a consistent style with Web
>>>  > standards Weex using. Developers write in this language just like
>>>  writting
>>>  > in HTML. After transforming to JSBundle by Weex tools, these tags will be
>>>  > rendered by build-in platform-specific components. The logic part of Weex
>>>  > syntax write in Javascript which don't need be compiled control these
>>>  > components.
>>>  >
>>>  > The vision of Weex is to complement gap between platform-specific Native
>>>  UI
>>>  > and Web technical based UI in Mobile age. The team behind Weex believe
>>>  that
>>>  > dynamicly interface update and high performance should be achieved at the
>>>  > same time when people develop a Mobile App. Meanwhile duplicate work
>>>  > between
>>>  > the different platforms should be avoided.
>>>  >
>>>  > == Background ==
>>>  > Prior to Weex, in order to develop high performance mobile application we
>>>  > need write at least three different codebase(iOS, Android, Mobile Web) or
>>>  > adopt WebView based UI technique(Apache Cordova for example) which can't
>>>  > satisfy the demand for performance.
>>>  >
>>>  > A special task force at Alibaba Inc try to provide a solution for this
>>>  > problem has been setup since 2013.  At first the team release a
>>>  > cross-platform rendering engine which render a special format JSON to
>>>  

Re: [VOTE][RESULT] Accept OpenWhisk into the Apache Incubator

[John D. Ament]

I just added it, to unblock secretary actions.

On Mon, Nov 28, 2016 at 6:28 PM Craig Russell 
wrote:

> I’m unable to find the proposal at
> https://wiki.apache.org/incubator/ProjectProposals
>
> Is it me or is the proposal not included on that page?
>
> Thanks,
>
> Craig
>
> > On Nov 23, 2016, at 12:20 PM, Sam Ruby  wrote:
> >
> > This vote passes with 10 binding +1's, 3 non-binding +1, and no -1's
> >
> > Binding:
> >  John D. Ament
> >  Bertrand Delacretaz
> >  Ted Dunning
> >  Niclas Hedhman
> >  Sergio Fernández
> >  Felix Meschberger
> >  Jean-Baptiste Onofré
> >  Karl Pauls
> >  Edward J. Yoon
> >  Reynold Xin
> >
> > Non-binding:
> >  Liang Chen
> >  Debo Dutta
> >  Charith Elvitigala
> >
> > Note that John Ament indicated his intention to vote -1 on any
> > OpenWhisk release until the "GitHub as master" issue is resolved by
> > the Apache Infrastructure team.
> >
> > - Sam Ruby
> >
> > On Thu, Nov 17, 2016 at 10:22 AM, Sam Ruby 
> wrote:
> >> Now that the discussion thread on the OpenWhisk Proposal has died
> >> down, please take a moment to vote on accepting OpenWhisk into the
> >> Apache Incubator.
> >>
> >> The ASF voting rules are described at:
> >>   http://www.apache.org/foundation/voting.html
> >>
> >> A vote for accepting a new Apache Incubator podling is a majority vote
> >> for which only Incubator PMC member votes are binding.
> >>
> >> Votes from other people are also welcome as an indication of peoples
> >> enthusiasm (or lack thereof).
> >>
> >> Please do not use this VOTE thread for discussions.
> >> If needed, start a new thread instead.
> >>
> >> This vote will run for at least 72 hours. Please VOTE as follows
> >> [] +1 Accept OpenWhisk into the Apache Incubator
> >> [] +0 Abstain.
> >> [] -1 Do not accept OpenWhisk into the Apache Incubator because ...
> >>
> >> The proposal is listed below, but you can also access it on the wiki:
> >>   https://wiki.apache.org/incubator/OpenWhiskProposal
> >>
> >> - Sam Ruby
> >>
> >> = OpenWhisk Proposal =
> >>
> >> OpenWhisk is an open source, distributed Serverless computing platform
> >> able to execute application logic (Actions) in response to events
> >> (Triggers) from external sources (Feeds) or HTTP requests governed by
> >> conditional logic (Rules). It provides a programming environment
> >> supported by a REST API-based Command Line Interface (CLI) along with
> >> tooling to support packaging and catalog services.
> >>
> >> Champion: Sam Ruby, IBM
> >>
> >> Mentors:
> >> * Felix Meschberger, Adobe
> >> * Isabel Drost-Fromm, Elasticsearch GmbH
> >> * Sergio Fernández, Redlink GmbH
> >>
> >> == Background ==
> >>
> >> Serverless computing is the evolutionary next stage in Cloud computing
> >> carrying further the abstraction offered to software developers using
> >> Container-based operating system virtualization. The Serverless
> >> paradigm enables programmers to just “write” functional code and not
> >> worry about having to configure any aspect of a server needed for
> >> execution. Such Serverless functions are single purpose and stateless
> >> that respond to event-driven data sources and can be scaled on-demand.
> >>
> >> The OpenWhisk project offers a truly open, highly scalable, performant
> >> distributed Serverless platform leveraging other open technologies
> >> along with a robust programming model, catalog of service and event
> >> provider integrations and developer tooling.
> >> Specifically, every architectural component service of the OpenWhisk
> >> platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API
> >> Gateway, etc.) all is designed to be run and scaled as a Docker
> >> container. In addition, OpenWhisk uniquely leverages aspects of Docker
> >> engine to manage, load balance and scale supported OpenWhisk runtime
> >> environments (e.g., JavaScript, Python, Swift, Java, etc.), that run
> >> Serverless functional code within Invoker compute instances, using
> >> Docker containers.
> >>
> >> OpenWhisk's containerized design tenants not only allows it to be
> >> hosted in various IaaS, PaaS Clouds platforms that support Docker
> >> containers, but also achieves the high expectation of the Serverless
> >> computing experience by masking all aspects of traditional resource
> >> specification and configuration from the end user simplifying and
> >> accelerating Cloud application development.
> >> In order to enable HTTP requests as a source of events, and thus the
> >> creation of Serverless microservices that expose REST APIs, OpenWhisk
> >> includes an API Gateway that performs tasks like security, request
> >> routing, throttling, and logging.
> >>
> >> == Rationale ==
> >>
> >> Serverless computing is in the very early stages of the technology
> >> adoption curve and has great promise in enabling new paradigms in
> >> event-driven application development, but current implementation
> >> efforts are fractured as most are 

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

[Sterling Hughes]

+1 Binding.

Compiled and ran regression test suites, tested in on both Nordic and 
Atmel hardware.


Sterling

On 26 Nov 2016, at 17:18, Christopher Collins wrote:


Hello all,

I am pleased to be calling this vote for the source release of Apache
Mynewt 1.0.0, beta 1.

Apache Mynewt is a community-driven, permissively licensed open source
initiative for constrained, embedded applications. Mynewt provides a
real-time operating system, flash file system, network stacks, and
support utilities for real-world embedded systems.

For full release notes, please visit the Apache Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

[VOTE] thread:
https://lists.apache.org/thread.html/81f0abec5177734af735ad251c0a63a397656032b646f89aa8d8c9d2@%3Cdev.mynewt.apache.org%3E

[RESULT][VOTE] thread:
https://lists.apache.org/thread.html/998ab676cfa8624237e71c38d2e6b53773a180322f25a957ba7a35c2@%3Cdev.mynewt.apache.org%3E

[DISCUSS] thread:
https://lists.apache.org/thread.html/f419185576b86206daf4b7eeb379ec48a294a2722ab7028d408e5584@%3Cdev.mynewt.apache.org%3E

This release candidate was tested as follows:
1. Manual execution of the Mynewt test plan:
   
https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan
   The test results can be found at:
   https://cwiki.apache.org/confluence/display/MYNEWT/1.0.0-b1+Test+Results

2. The full unit test suite for this release was executed via 
"newt

   test all" with no failures.  This testing was performed on the
   following platforms:
 * OS X 10.10.5
 * Linux 4.4.6 (Gentoo)

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-b1-incubating/rc1/

The commits under consideration are as follows:

blinky:
repos: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky

commit: b6918edc174b764f1e0b4ef4f4652aca8fedf8dd

core:
repos: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core

commit: c6a8f88f6b8dc7c8eee6dc75a34c9b6ea295b05d

newt:
repos: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt

commit: 59ec3af372952382390cfd988e503d8cf3d5b34b

In addition, the following newt convenience binaries are available:
linux: 
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-b1-incubating/rc1/apache-mynewt-newt-bin-linux-1.0.0-b1-incubating.tgz
osx: 
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-b1-incubating/rc1/apache-mynewt-newt-bin-osx-1.0.0-b1-incubating.tgz


The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS

The vote is open for at least 72 hours and passes if a majority of at
least three +1 PPMC votes are cast.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

The vote is open for at least 72 hours and passes if a majority of at
least three +1 PPMC votes are cast.

Thanks,
Chris

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE][RESULT] Accept OpenWhisk into the Apache Incubator

[Craig Russell]

I’m unable to find the proposal at 
https://wiki.apache.org/incubator/ProjectProposals

Is it me or is the proposal not included on that page?

Thanks,

Craig

> On Nov 23, 2016, at 12:20 PM, Sam Ruby  wrote:
> 
> This vote passes with 10 binding +1's, 3 non-binding +1, and no -1's
> 
> Binding:
>  John D. Ament
>  Bertrand Delacretaz
>  Ted Dunning
>  Niclas Hedhman
>  Sergio Fernández
>  Felix Meschberger
>  Jean-Baptiste Onofré
>  Karl Pauls
>  Edward J. Yoon
>  Reynold Xin
> 
> Non-binding:
>  Liang Chen
>  Debo Dutta
>  Charith Elvitigala
> 
> Note that John Ament indicated his intention to vote -1 on any
> OpenWhisk release until the "GitHub as master" issue is resolved by
> the Apache Infrastructure team.
> 
> - Sam Ruby
> 
> On Thu, Nov 17, 2016 at 10:22 AM, Sam Ruby  wrote:
>> Now that the discussion thread on the OpenWhisk Proposal has died
>> down, please take a moment to vote on accepting OpenWhisk into the
>> Apache Incubator.
>> 
>> The ASF voting rules are described at:
>>   http://www.apache.org/foundation/voting.html
>> 
>> A vote for accepting a new Apache Incubator podling is a majority vote
>> for which only Incubator PMC member votes are binding.
>> 
>> Votes from other people are also welcome as an indication of peoples
>> enthusiasm (or lack thereof).
>> 
>> Please do not use this VOTE thread for discussions.
>> If needed, start a new thread instead.
>> 
>> This vote will run for at least 72 hours. Please VOTE as follows
>> [] +1 Accept OpenWhisk into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept OpenWhisk into the Apache Incubator because ...
>> 
>> The proposal is listed below, but you can also access it on the wiki:
>>   https://wiki.apache.org/incubator/OpenWhiskProposal
>> 
>> - Sam Ruby
>> 
>> = OpenWhisk Proposal =
>> 
>> OpenWhisk is an open source, distributed Serverless computing platform
>> able to execute application logic (Actions) in response to events
>> (Triggers) from external sources (Feeds) or HTTP requests governed by
>> conditional logic (Rules). It provides a programming environment
>> supported by a REST API-based Command Line Interface (CLI) along with
>> tooling to support packaging and catalog services.
>> 
>> Champion: Sam Ruby, IBM
>> 
>> Mentors:
>> * Felix Meschberger, Adobe
>> * Isabel Drost-Fromm, Elasticsearch GmbH
>> * Sergio Fernández, Redlink GmbH
>> 
>> == Background ==
>> 
>> Serverless computing is the evolutionary next stage in Cloud computing
>> carrying further the abstraction offered to software developers using
>> Container-based operating system virtualization. The Serverless
>> paradigm enables programmers to just “write” functional code and not
>> worry about having to configure any aspect of a server needed for
>> execution. Such Serverless functions are single purpose and stateless
>> that respond to event-driven data sources and can be scaled on-demand.
>> 
>> The OpenWhisk project offers a truly open, highly scalable, performant
>> distributed Serverless platform leveraging other open technologies
>> along with a robust programming model, catalog of service and event
>> provider integrations and developer tooling.
>> Specifically, every architectural component service of the OpenWhisk
>> platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API
>> Gateway, etc.) all is designed to be run and scaled as a Docker
>> container. In addition, OpenWhisk uniquely leverages aspects of Docker
>> engine to manage, load balance and scale supported OpenWhisk runtime
>> environments (e.g., JavaScript, Python, Swift, Java, etc.), that run
>> Serverless functional code within Invoker compute instances, using
>> Docker containers.
>> 
>> OpenWhisk's containerized design tenants not only allows it to be
>> hosted in various IaaS, PaaS Clouds platforms that support Docker
>> containers, but also achieves the high expectation of the Serverless
>> computing experience by masking all aspects of traditional resource
>> specification and configuration from the end user simplifying and
>> accelerating Cloud application development.
>> In order to enable HTTP requests as a source of events, and thus the
>> creation of Serverless microservices that expose REST APIs, OpenWhisk
>> includes an API Gateway that performs tasks like security, request
>> routing, throttling, and logging.
>> 
>> == Rationale ==
>> 
>> Serverless computing is in the very early stages of the technology
>> adoption curve and has great promise in enabling new paradigms in
>> event-driven application development, but current implementation
>> efforts are fractured as most are tied to specific Cloud platforms and
>> services. Having an open implementation of a Serverless platform, such
>> as OpenWhisk, available and governed by an open community like Apache
>> could accelerate growth of this technology, as well as encourage
>> dialog and interoperability.
>> 
>> Having the ASF accept and incubate OpenWhisk would 

Re: Most successful projects in Apache in the past 2 years

[Roman Shaposhnik]

On Sun, Nov 27, 2016 at 8:22 AM, Genoveffa Pagano
 wrote:
> Thanks Daniel,
> even generic data would be interesting for me.
> Is there a web page that collects this type on info? Can you advise me on
> where to find the data?

If you don't need a [semi-]complete list, but rather you're looking
for representative
example projects I'd say that the following will give you a great start:
   Apache Beam (incubating)
   Apache Spark
   Apache Flink
   Apache Hadoop

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Weex to enter the Apache Incubator

[Henry Saputra]

+1 (binding)

Best of luck, guys!

On Thu, Nov 24, 2016 at 2:47 PM, Edward J. Yoon  wrote:
> Greetings!
>
> I would like to call a vote for accepting "Weex" for incubation in the
> Apache Incubator. The full proposal is available below.  We ask the
> Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion, and
> Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to be
> Mentors.
>
> Please cast your vote:
>
> [ ] +1, bring Weex into Incubator
> [ ] +0, I don't care either way,
> [ ] -1, do not bring Weex into Incubator, because...
>
> This vote will be open at least for 72 hours and only votes from the
> Incubator PMC are binding.
>
> --
> https://wiki.apache.org/incubator/WeexProposal
>
> = Weex Proposal =
>
> == Abstract ==
> Weex is a framework for building Mobile cross-platform high performance UI.
> Weex enables developers to use Web-like syntax to build iOS, Android and Web
> UI with a single codebase.
>
> == Proposal ==
> Weex provide an uniform Web-like syntax for develop native Mobile App UI. By
> leverage the Javascript engine that enable dynamic update, the process of
> App interfce and content update can be simple and controllable just like
> Web.Compared with WebView based UI framework which performance are limited,
> Weex use build-in native components instead.
>
> Because of tag based syntax that maintain a consistent style with Web
> standards Weex using. Developers write in this language just like writting
> in HTML. After transforming to JSBundle by Weex tools, these tags will be
> rendered by build-in platform-specific components. The logic part of Weex
> syntax write in Javascript which don't need be compiled control these
> components.
>
> The vision of Weex is to complement gap between platform-specific Native UI
> and Web technical based UI in Mobile age. The team behind Weex believe that
> dynamicly interface update and high performance should be achieved at the
> same time when people develop a Mobile App. Meanwhile duplicate work between
> the different platforms should be avoided.
>
> == Background ==
> Prior to Weex, in order to develop high performance mobile application we
> need write at least three different codebase(iOS, Android, Mobile Web) or
> adopt WebView based UI technique(Apache Cordova for example) which can't
> satisfy the demand for performance.
>
> A special task force at Alibaba Inc try to provide a solution for this
> problem has been setup since 2013.  At first the team release a
> cross-platform rendering engine which render a special format JSON to native
> components on different platform. To output this JSON file the team had
> build a website which other developer can use to simply design final
> interface.
>
> Although This solution had worked for a while, we found it not able to meet
> our UI developer's habits. Most of our UI developer have Web background
> which make them used to use tag based language to design App interface.
> Meanwhile we found the JSON file lacks of enough flexibility. The following
> discussion inspire we start to develop Weex.
>
> Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest user
> volume eCommerce App in China has adapted Weex in a lot of UI. In the latest
> November 11th promotions(Alibaba's annual Singles' Day online shopping
> event), UI developers from Alibaba Inc have build more then 1,500 pages
> using Weex, 99.6% of all the promotional pages. The ratio of less than one
> second page open time is more than 90%, the frame rate is 53.0~58.5(depend
> on device) due to the high performance of Weex. In addition to user
> experience improvement, the productivity of page development and the
> efficiency of content delivery both have been improved.
>
> After open-source and have got a lot of followers in chinese mobile App
> development community, several of popular Apps listed on chinese top charts
> have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning etc...)
>
> == Current Status ==
> Weex has become an open source project since June 2016.  It has been used at
> a lot of Alibaba producted mobile softwares which running on the mobile
> phone of millions of users.
>
> Weex code repository located at GitHub. All development activities have
> already happened on GitHub as open source manner.
>
> == Community ==
> The community surrounding Weex is a variety of developer which have
> different technique background.iOS, Android, Web developer must collaborate
> closely to implement most Weex feature.
>
> Currently total 61 contributors involved in the GitHub development process.
> Weex repository has received 791 pull requests until Nov 2016.
>
> Beyond committer from Alibaba Inc, Weex community welcome anybody join us.
> Nowaday Evan You from Vue Technology LLC, Wang Run Xiang from Aipai Inc and
> lots of GitHub users have contributed source code or document to Weex.
>
> Weex syntax is inspired a lot from Web framework Vue.js. For 

Re: 回复：[VOTE] Weex to enter the Apache Incubator

[Edward J. Yoon]

吴志华(天施),

Of course, you can cast your vote. But your vote is non-binding.

And this list's subscribers are from various countries. Always use
text as your email format and create the email signature as english
nickname.

Thanks.


On Tue, Nov 29, 2016 at 12:49 AM, 吴志华(天施)  wrote:
>BryantWuhuaz...@gmail.com (Alibaba Inc)。Weex Init 
> developer
> Can I vote for Weex Project? I love Weex so 
> much。--发件人：Daniel
>  Gruno 发送时间：2016年11月28日(星期一) 23:17收件人：general 
> 主　题：Re: 回复：[VOTE] Weex to enter the Apache 
> Incubator
>
> On 11/28/2016 04:06 PM, 吴志华(天施) wrote:
>>
>>  +1 (binding)
>
> For binding +1s, we generally require a name we can compare with our
> Apache Phonebook to make sure you are on the IPMC. I was unable to find
> you as a committer, could you please tell me your apache ID?
>
> With regards,
> Daniel.
>
>> --发件人：Stephan
>>  Ewen 发送时间：2016年11月28日(星期一) 18:02收件人：general 
>> 主 题：Re: [VOTE] Weex to enter the Apache 
>> Incubator
>> +1 (binding)
>>
>>
>> On Sun, Nov 27, 2016 at 1:44 AM, Luke Han  wrote:
>>
>>>  +1 binding
>>>
>>>  Get Outlook for iOS
>>>
>>>
>>>
>>>
>>>  On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" <
>>>  willem.ji...@gmail.com> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  +1 （binding）
>>>
>>>
>>>  Willem Jiang
>>>
>>>  Blog: http://willemjiang.blogspot.com (English)
>>>http://jnn.iteye.com  (Chinese)
>>>  Twitter: willemjiang
>>>  Weibo: 姜宁willem
>>>
>>>  On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon
>>>  wrote:
>>>
>>>  > Greetings!
>>>  >
>>>  > I would like to call a vote for accepting "Weex" for incubation in the
>>>  > Apache Incubator. The full proposal is available below.  We ask the
>>>  > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion,
>>>  and
>>>  > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to
>>>  be
>>>  > Mentors.
>>>  >
>>>  > Please cast your vote:
>>>  >
>>>  > [ ] +1, bring Weex into Incubator
>>>  > [ ] +0, I don't care either way,
>>>  > [ ] -1, do not bring Weex into Incubator, because...
>>>  >
>>>  > This vote will be open at least for 72 hours and only votes from the
>>>  > Incubator PMC are binding.
>>>  >
>>>  > --
>>>  > https://wiki.apache.org/incubator/WeexProposal
>>>  >
>>>  > = Weex Proposal =
>>>  >
>>>  > == Abstract ==
>>>  > Weex is a framework for building Mobile cross-platform high performance
>>>  UI.
>>>  > Weex enables developers to use Web-like syntax to build iOS, Android and
>>>  > Web
>>>  > UI with a single codebase.
>>>  >
>>>  > == Proposal ==
>>>  > Weex provide an uniform Web-like syntax for develop native Mobile App UI.
>>>  > By
>>>  > leverage the Javascript engine that enable dynamic update, the process of
>>>  > App interfce and content update can be simple and controllable just like
>>>  > Web.Compared with WebView based UI framework which performance are
>>>  limited,
>>>  > Weex use build-in native components instead.
>>>  >
>>>  > Because of tag based syntax that maintain a consistent style with Web
>>>  > standards Weex using. Developers write in this language just like
>>>  writting
>>>  > in HTML. After transforming to JSBundle by Weex tools, these tags will be
>>>  > rendered by build-in platform-specific components. The logic part of Weex
>>>  > syntax write in Javascript which don't need be compiled control these
>>>  > components.
>>>  >
>>>  > The vision of Weex is to complement gap between platform-specific Native
>>>  UI
>>>  > and Web technical based UI in Mobile age. The team behind Weex believe
>>>  that
>>>  > dynamicly interface update and high performance should be achieved at the
>>>  > same time when people develop a Mobile App. Meanwhile duplicate work
>>>  > between
>>>  > the different platforms should be avoided.
>>>  >
>>>  > == Background ==
>>>  > Prior to Weex, in order to develop high performance mobile application we
>>>  > need write at least three different codebase(iOS, Android, Mobile Web) or
>>>  > adopt WebView based UI technique(Apache Cordova for example) which can't
>>>  > satisfy the demand for performance.
>>>  >
>>>  > A special task force at Alibaba Inc try to provide a solution for this
>>>  > problem has been setup since 2013.  At first the team release a
>>>  > cross-platform rendering engine which render a special format JSON to
>>>  > native
>>>  > components on different platform. To output this JSON file the team had
>>>  > build a website which other developer can use to simply design final
>>>  > interface.
>>>  >
>>>  > Although This solution had worked for a while, we found it not able to
>>>  meet
>>>  > our UI developer's habits. Most of our UI developer have Web background
>>>  > which 

[NOTICE] Paul McNamee for Apache Joshua (Incubating) PPMC + Committership

[Matt Post]

Hello,

The Apache Joshua (Incubating) PPMC has voted to extend Paul McNamee 
(mcna...@jhu.edu) a PPMC and Committership invitation, based on his 
contributions, including assembling a large number of language packs. We will 
extend the invitation three business days from now, assuming we hear no 
objections.

For details please see the following mail threads: [VOTE 
] [RESULT ]
 
Sincerely,
Matt Post
On behalf of the Apache Joshua (Incubating) PPMC

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

[Casey Stella]

This vote passed with +1s (all binding)

Billie Rinaldi
Stian Soiland-Reyes
Julian Hyde
Justin Mclean
John D. Ament

Thanks,
Casey

On Mon, Nov 28, 2016 at 1:57 PM, Casey Stella  wrote:

> Hi Stian,
>
> We can clarify the licensing around Stix in the next release, no problem.
> It is my understanding that it is 3-clause BSD.
>
> Casey
>
> On Wed, Nov 23, 2016 at 12:48 PM, Stian Soiland-Reyes 
> wrote:
>
>> My vote: +1 (binding)
>>
>> +1 git tag matches src (commit
>> 7aea4ba35d1a931d72898bffd9725be3075fe8ca) (except site/ and .git*)
>> +1 .asc signatures match, key in KEYS
>> +0  .sha/.md5 hashes correct - could these have more conventional
>> format and filenames?
>> -0 Vote email didn't reference hash values or dist.apache.org SVN
>> revision number (I assume r16997)
>> +0 No need for DISCLAIMER or LICENSE within dist folder
>> +1 apache- and -incubator in file/folder-name
>> +1 DISCLAIMER present in archive
>> +1 NOTICE present in archive with attributions (you don't need the
>> indentation)
>> +1 LICENSE present. (first newline missing, indentation wrong on first
>> line. Very long line in extension)
>> -0 STIX BSD license not included, URL is wrong.
>> +1 mvn apache-rat:check
>> -1 mvn install crashes my X server (!)  (See below)
>> +1 No unexpected binaries (except test data, serialized from Hadoop?)
>>
>>
>> For the next release vote, could you include either the git commit ID
>> (not just tag) or the hash of the source archive? for archival
>> purposes?
>>
>> For the next release's LICENSE, download
>> http://www.apache.org/licenses/LICENSE-2.0.txt and add at the end your
>> extensions about the Stix project as you have already, except perhaps
>> wrap the long lines.
>>
>> For the next release, could you include the STIX license as it was at
>> the point of importing? A link like
>> > available under a BSD license.  For details, see
>> http://stix.mitre.org/about/termsofuse.html
>>
>> This is not enough long term as the license is not versioned and can
>> change later - in fact the URL already redirects to
>> http://stixproject.github.io/about/ which points to
>> http://stixproject.github.io/legal/ which points back to /about/ - and
>> so I can't find the actual STIX license to verify this.
>>
>> Add it as a file like licenses/STIX.LICENSE.txt and refer to that from
>> the top level LICENSE and the file headers.  (don't remove the old
>> file headers, just augment)
>>
>>
>> My +1 vote assumes this STIX license is a BSD-3-clause or 2-Clause, if
>> it is a BSD-4 clause it is NOT open source or compatible and my vote
>> would be -1.
>>
>>
>> For the hashes  I would have preferred the style:
>>
>> apache-metron-0.3.0-rc1-incubating.tar.gz.sha1 containing:
>> 080a54dd02cfe9fa91cd92305726443302ef250e
>> apache-metron-0.3.0-rc1-incubating.tar.gz
>>
>> apache-metron-0.3.0-rc1-incubating.tar.gz.md5 containing:
>> 1cc8ecfac074d5667845b835e28f6403  apache-metron-0.3.0-rc1-incuba
>> ting.tar.gz
>>
>> ..or Maven-compatible without the spaces, filename or newline (no
>> spacing within the hash value)
>>
>>
>> (You may fix the hashes for this RC before you svn mv on dist)
>>
>>
>>
>> Below details about test failures only:
>>
>>
>>
>> The unit tests of metron-analytics/metron-maas-service crashes my X
>> server on Ubuntu 16.04 with Nvidia drivers..! Not sure why it would
>> touch X?
>>
>> It happens right after it says once "Found endpoint 
>> biggieubuntu:someport"  (my hostname). -- sorry it crashed a bit too
>> fast to check the port number!
>>
>> mvn clean install -DskipTests works though, so I won't fail this
>> particular vote.
>>
>>
>> I had a similar problem with mvn clean install within
>>
>> docker run -it maven:3-jdk-8 bash
>>
>> (which take a while in metron-maas-service) - that does a lot of
>> echo-endpoint things, but then fails with
>>
>> Found endpoints: dummy:1.0 @ http://c6ced9e36c5e:1500 serving:
>> apply=echo
>> Cleaning up...
>> Killing 1413 from  1413 ?00:00:00 dummy_rest.sh
>> 2016-11-23 17:33:23,070 ERROR [Thread[Thread-615,5,main]]
>> delegation.AbstractDelegationTokenSecretManager
>> (AbstractDelegationTokenSecretManager.java:run(659)) -
>> ExpiredTokenRemover received java.lang.InterruptedException: sleep
>> interrupted
>> 2016-11-23 17:33:23,183 ERROR [Thread[Thread-595,5,main]]
>> delegation.AbstractDelegationTokenSecretManager
>> (AbstractDelegationTokenSecretManager.java:run(659)) -
>> ExpiredTokenRemover received java.lang.InterruptedException: sleep
>> interrupted
>> 2016-11-23 17:33:23,193 ERROR [Thread[Thread-591,5,main]]
>> delegation.AbstractDelegationTokenSecretManager
>> (AbstractDelegationTokenSecretManager.java:run(659)) -
>> ExpiredTokenRemover received java.lang.InterruptedException: sleep
>> interrupted
>> 2016-11-23 17:33:38,159 ERROR [Curator-TreeCache-1]
>> curator.ConnectionState (ConnectionState.java:checkTimeouts(200)) -
>> Connection timed out for connection string (127.0.0.1:46611) and
>> timeout (15000) / 

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

[Casey Stella]

Hi Stian,

We can clarify the licensing around Stix in the next release, no problem.
It is my understanding that it is 3-clause BSD.

Casey

On Wed, Nov 23, 2016 at 12:48 PM, Stian Soiland-Reyes 
wrote:

> My vote: +1 (binding)
>
> +1 git tag matches src (commit
> 7aea4ba35d1a931d72898bffd9725be3075fe8ca) (except site/ and .git*)
> +1 .asc signatures match, key in KEYS
> +0  .sha/.md5 hashes correct - could these have more conventional
> format and filenames?
> -0 Vote email didn't reference hash values or dist.apache.org SVN
> revision number (I assume r16997)
> +0 No need for DISCLAIMER or LICENSE within dist folder
> +1 apache- and -incubator in file/folder-name
> +1 DISCLAIMER present in archive
> +1 NOTICE present in archive with attributions (you don't need the
> indentation)
> +1 LICENSE present. (first newline missing, indentation wrong on first
> line. Very long line in extension)
> -0 STIX BSD license not included, URL is wrong.
> +1 mvn apache-rat:check
> -1 mvn install crashes my X server (!)  (See below)
> +1 No unexpected binaries (except test data, serialized from Hadoop?)
>
>
> For the next release vote, could you include either the git commit ID
> (not just tag) or the hash of the source archive? for archival
> purposes?
>
> For the next release's LICENSE, download
> http://www.apache.org/licenses/LICENSE-2.0.txt and add at the end your
> extensions about the Stix project as you have already, except perhaps
> wrap the long lines.
>
> For the next release, could you include the STIX license as it was at
> the point of importing? A link like
> > available under a BSD license.  For details, see
> http://stix.mitre.org/about/termsofuse.html
>
> This is not enough long term as the license is not versioned and can
> change later - in fact the URL already redirects to
> http://stixproject.github.io/about/ which points to
> http://stixproject.github.io/legal/ which points back to /about/ - and
> so I can't find the actual STIX license to verify this.
>
> Add it as a file like licenses/STIX.LICENSE.txt and refer to that from
> the top level LICENSE and the file headers.  (don't remove the old
> file headers, just augment)
>
>
> My +1 vote assumes this STIX license is a BSD-3-clause or 2-Clause, if
> it is a BSD-4 clause it is NOT open source or compatible and my vote
> would be -1.
>
>
> For the hashes  I would have preferred the style:
>
> apache-metron-0.3.0-rc1-incubating.tar.gz.sha1 containing:
> 080a54dd02cfe9fa91cd92305726443302ef250e
> apache-metron-0.3.0-rc1-incubating.tar.gz
>
> apache-metron-0.3.0-rc1-incubating.tar.gz.md5 containing:
> 1cc8ecfac074d5667845b835e28f6403  apache-metron-0.3.0-rc1-
> incubating.tar.gz
>
> ..or Maven-compatible without the spaces, filename or newline (no
> spacing within the hash value)
>
>
> (You may fix the hashes for this RC before you svn mv on dist)
>
>
>
> Below details about test failures only:
>
>
>
> The unit tests of metron-analytics/metron-maas-service crashes my X
> server on Ubuntu 16.04 with Nvidia drivers..! Not sure why it would
> touch X?
>
> It happens right after it says once "Found endpoint 
> biggieubuntu:someport"  (my hostname). -- sorry it crashed a bit too
> fast to check the port number!
>
> mvn clean install -DskipTests works though, so I won't fail this
> particular vote.
>
>
> I had a similar problem with mvn clean install within
>
> docker run -it maven:3-jdk-8 bash
>
> (which take a while in metron-maas-service) - that does a lot of
> echo-endpoint things, but then fails with
>
> Found endpoints: dummy:1.0 @ http://c6ced9e36c5e:1500 serving:
> apply=echo
> Cleaning up...
> Killing 1413 from  1413 ?00:00:00 dummy_rest.sh
> 2016-11-23 17:33:23,070 ERROR [Thread[Thread-615,5,main]]
> delegation.AbstractDelegationTokenSecretManager
> (AbstractDelegationTokenSecretManager.java:run(659)) -
> ExpiredTokenRemover received java.lang.InterruptedException: sleep
> interrupted
> 2016-11-23 17:33:23,183 ERROR [Thread[Thread-595,5,main]]
> delegation.AbstractDelegationTokenSecretManager
> (AbstractDelegationTokenSecretManager.java:run(659)) -
> ExpiredTokenRemover received java.lang.InterruptedException: sleep
> interrupted
> 2016-11-23 17:33:23,193 ERROR [Thread[Thread-591,5,main]]
> delegation.AbstractDelegationTokenSecretManager
> (AbstractDelegationTokenSecretManager.java:run(659)) -
> ExpiredTokenRemover received java.lang.InterruptedException: sleep
> interrupted
> 2016-11-23 17:33:38,159 ERROR [Curator-TreeCache-1]
> curator.ConnectionState (ConnectionState.java:checkTimeouts(200)) -
> Connection timed out for connection string (127.0.0.1:46611) and
> timeout (15000) / elapsed (15003)
> org.apache.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at org.apache.curator.ConnectionState.checkTimeouts(
> ConnectionState.java:197)
> at org.apache.curator.ConnectionState.getZooKeeper(
> ConnectionState.java:87)
>
> and fails tests like
>
> at 

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

[Casey Stella]

Hi all,

Thanks for pointing out the branding issues.  The website is updated to
refer to the apache release page.  There is also a JIRA
 (with accompanying PR
 on github) to correct
the branding issue on the website.  I will see to it that the twitter page
gets the appropriate parenthetical as well.

Best,

Casey

On Thu, Nov 24, 2016 at 2:47 PM, John D. Ament 
wrote:

> That's an issue.  Want to let them know directly that their website needs
> fixing?
>
> On Nov 24, 2016 1:00 PM, "Justin Mclean"  wrote:
>
> > Hi,
> >
> > > RE Justin - that's a potential issue, but is also how github works.
> >
> > It may be how GitHub works but it is IMO against release policy
> especially
> > as on their site they link to GitHub and not the Apache release area.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: RocketMQ link on https://wiki.apache.org/incubator/ProjectProposals

[Bertrand Delacretaz]

On Mon, Nov 28, 2016 at 5:58 PM, Craig Russell  wrote:
> Is it me or is this link broken?

It was broken indeed, fixed now.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RocketMQ link on https://wiki.apache.org/incubator/ProjectProposals

[Craig Russell]

Is it me or is this link broken?

Thanks,

Craig

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

回复：回复：[VOTE] Weex to enter the Apache Incubator

[吴志华(天施)]

           BryantWu        huaz...@gmail.com (Alibaba Inc)。        Weex Init 
developer
        Can I vote for Weex Project? I love Weex so 
much。--发件人：Daniel
 Gruno 发送时间：2016年11月28日(星期一) 23:17收件人：general 
主　题：Re: 回复：[VOTE] Weex to enter the Apache 
Incubator

On 11/28/2016 04:06 PM, 吴志华(天施) wrote:
> 
>  +1 (binding)

For binding +1s, we generally require a name we can compare with our
Apache Phonebook to make sure you are on the IPMC. I was unable to find
you as a committer, could you please tell me your apache ID?

With regards,
Daniel.

> --发件人：Stephan 
>Ewen 发送时间：2016年11月28日(星期一) 18:02收件人：general 
>主 题：Re: [VOTE] Weex to enter the Apache Incubator
> +1 (binding)
> 
> 
> On Sun, Nov 27, 2016 at 1:44 AM, Luke Han  wrote:
> 
>>  +1 binding
>>
>>  Get Outlook for iOS
>>
>>
>>
>>
>>  On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" <
>>  willem.ji...@gmail.com> wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>  +1 （binding）
>>
>>
>>  Willem Jiang
>>
>>  Blog: http://willemjiang.blogspot.com (English)
>>http://jnn.iteye.com  (Chinese)
>>  Twitter: willemjiang
>>  Weibo: 姜宁willem
>>
>>  On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon
>>  wrote:
>>
>>  > Greetings!
>>  >
>>  > I would like to call a vote for accepting "Weex" for incubation in the
>>  > Apache Incubator. The full proposal is available below.  We ask the
>>  > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion,
>>  and
>>  > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to
>>  be
>>  > Mentors.
>>  >
>>  > Please cast your vote:
>>  >
>>  > [ ] +1, bring Weex into Incubator
>>  > [ ] +0, I don't care either way,
>>  > [ ] -1, do not bring Weex into Incubator, because...
>>  >
>>  > This vote will be open at least for 72 hours and only votes from the
>>  > Incubator PMC are binding.
>>  >
>>  > --
>>  > https://wiki.apache.org/incubator/WeexProposal
>>  >
>>  > = Weex Proposal =
>>  >
>>  > == Abstract ==
>>  > Weex is a framework for building Mobile cross-platform high performance
>>  UI.
>>  > Weex enables developers to use Web-like syntax to build iOS, Android and
>>  > Web
>>  > UI with a single codebase.
>>  >
>>  > == Proposal ==
>>  > Weex provide an uniform Web-like syntax for develop native Mobile App UI.
>>  > By
>>  > leverage the Javascript engine that enable dynamic update, the process of
>>  > App interfce and content update can be simple and controllable just like
>>  > Web.Compared with WebView based UI framework which performance are
>>  limited,
>>  > Weex use build-in native components instead.
>>  >
>>  > Because of tag based syntax that maintain a consistent style with Web
>>  > standards Weex using. Developers write in this language just like
>>  writting
>>  > in HTML. After transforming to JSBundle by Weex tools, these tags will be
>>  > rendered by build-in platform-specific components. The logic part of Weex
>>  > syntax write in Javascript which don't need be compiled control these
>>  > components.
>>  >
>>  > The vision of Weex is to complement gap between platform-specific Native
>>  UI
>>  > and Web technical based UI in Mobile age. The team behind Weex believe
>>  that
>>  > dynamicly interface update and high performance should be achieved at the
>>  > same time when people develop a Mobile App. Meanwhile duplicate work
>>  > between
>>  > the different platforms should be avoided.
>>  >
>>  > == Background ==
>>  > Prior to Weex, in order to develop high performance mobile application we
>>  > need write at least three different codebase(iOS, Android, Mobile Web) or
>>  > adopt WebView based UI technique(Apache Cordova for example) which can't
>>  > satisfy the demand for performance.
>>  >
>>  > A special task force at Alibaba Inc try to provide a solution for this
>>  > problem has been setup since 2013.  At first the team release a
>>  > cross-platform rendering engine which render a special format JSON to
>>  > native
>>  > components on different platform. To output this JSON file the team had
>>  > build a website which other developer can use to simply design final
>>  > interface.
>>  >
>>  > Although This solution had worked for a while, we found it not able to
>>  meet
>>  > our UI developer's habits. Most of our UI developer have Web background
>>  > which make them used to use tag based language to design App interface.
>>  > Meanwhile we found the JSON file lacks of enough flexibility. The
>>  following
>>  > discussion inspire we start to develop Weex.
>>  >
>>  > Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest
>>  user
>>  > volume eCommerce App in China has adapted Weex in a lot of UI. In the
>>  > latest
>>  > November 11th promotions(Alibaba's annual Singles' Day online 

Re: 回复：[VOTE] Weex to enter the Apache Incubator

[Daniel Gruno]

On 11/28/2016 04:06 PM, 吴志华(天施) wrote:
> 
>  +1 (binding)

For binding +1s, we generally require a name we can compare with our
Apache Phonebook to make sure you are on the IPMC. I was unable to find
you as a committer, could you please tell me your apache ID?

With regards,
Daniel.

> --发件人：Stephan 
> Ewen 发送时间：2016年11月28日(星期一) 18:02收件人：general 
> 主　题：Re: [VOTE] Weex to enter the Apache 
> Incubator
> +1 (binding)
> 
> 
> On Sun, Nov 27, 2016 at 1:44 AM, Luke Han  wrote:
> 
>>  +1 binding
>>
>>  Get Outlook for iOS
>>
>>
>>
>>
>>  On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" <
>>  willem.ji...@gmail.com> wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>  +1 （binding）
>>
>>
>>  Willem Jiang
>>
>>  Blog: http://willemjiang.blogspot.com (English)
>>http://jnn.iteye.com  (Chinese)
>>  Twitter: willemjiang
>>  Weibo: 姜宁willem
>>
>>  On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon
>>  wrote:
>>
>>  > Greetings!
>>  >
>>  > I would like to call a vote for accepting "Weex" for incubation in the
>>  > Apache Incubator. The full proposal is available below.  We ask the
>>  > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion,
>>  and
>>  > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to
>>  be
>>  > Mentors.
>>  >
>>  > Please cast your vote:
>>  >
>>  > [ ] +1, bring Weex into Incubator
>>  > [ ] +0, I don't care either way,
>>  > [ ] -1, do not bring Weex into Incubator, because...
>>  >
>>  > This vote will be open at least for 72 hours and only votes from the
>>  > Incubator PMC are binding.
>>  >
>>  > --
>>  > https://wiki.apache.org/incubator/WeexProposal
>>  >
>>  > = Weex Proposal =
>>  >
>>  > == Abstract ==
>>  > Weex is a framework for building Mobile cross-platform high performance
>>  UI.
>>  > Weex enables developers to use Web-like syntax to build iOS, Android and
>>  > Web
>>  > UI with a single codebase.
>>  >
>>  > == Proposal ==
>>  > Weex provide an uniform Web-like syntax for develop native Mobile App UI.
>>  > By
>>  > leverage the Javascript engine that enable dynamic update, the process of
>>  > App interfce and content update can be simple and controllable just like
>>  > Web.Compared with WebView based UI framework which performance are
>>  limited,
>>  > Weex use build-in native components instead.
>>  >
>>  > Because of tag based syntax that maintain a consistent style with Web
>>  > standards Weex using. Developers write in this language just like
>>  writting
>>  > in HTML. After transforming to JSBundle by Weex tools, these tags will be
>>  > rendered by build-in platform-specific components. The logic part of Weex
>>  > syntax write in Javascript which don't need be compiled control these
>>  > components.
>>  >
>>  > The vision of Weex is to complement gap between platform-specific Native
>>  UI
>>  > and Web technical based UI in Mobile age. The team behind Weex believe
>>  that
>>  > dynamicly interface update and high performance should be achieved at the
>>  > same time when people develop a Mobile App. Meanwhile duplicate work
>>  > between
>>  > the different platforms should be avoided.
>>  >
>>  > == Background ==
>>  > Prior to Weex, in order to develop high performance mobile application we
>>  > need write at least three different codebase(iOS, Android, Mobile Web) or
>>  > adopt WebView based UI technique(Apache Cordova for example) which can't
>>  > satisfy the demand for performance.
>>  >
>>  > A special task force at Alibaba Inc try to provide a solution for this
>>  > problem has been setup since 2013.  At first the team release a
>>  > cross-platform rendering engine which render a special format JSON to
>>  > native
>>  > components on different platform. To output this JSON file the team had
>>  > build a website which other developer can use to simply design final
>>  > interface.
>>  >
>>  > Although This solution had worked for a while, we found it not able to
>>  meet
>>  > our UI developer's habits. Most of our UI developer have Web background
>>  > which make them used to use tag based language to design App interface.
>>  > Meanwhile we found the JSON file lacks of enough flexibility. The
>>  following
>>  > discussion inspire we start to develop Weex.
>>  >
>>  > Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest
>>  user
>>  > volume eCommerce App in China has adapted Weex in a lot of UI. In the
>>  > latest
>>  > November 11th promotions(Alibaba's annual Singles' Day online shopping
>>  > event), UI developers from Alibaba Inc have build more then 1,500 pages
>>  > using Weex, 99.6% of all the promotional pages. The ratio of less than
>>  one
>>  > second page open time is more than 90%, the frame rate is
>>  53.0~58.5(depend
>>  > on device) due to the high performance of Weex. In addition to user
>>  > experience improvement, the productivity 

回复：[VOTE] Weex to enter the Apache Incubator

[吴志华(天施)]

     +1 (binding)
--发件人：Stephan 
Ewen 发送时间：2016年11月28日(星期一) 18:02收件人：general 
主　题：Re: [VOTE] Weex to enter the Apache Incubator
+1 (binding)


On Sun, Nov 27, 2016 at 1:44 AM, Luke Han  wrote:

> +1 binding
>
> Get Outlook for iOS
>
>
>
>
> On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" <
> willem.ji...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> +1 （binding）
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon
> wrote:
>
> > Greetings!
> >
> > I would like to call a vote for accepting "Weex" for incubation in the
> > Apache Incubator. The full proposal is available below.  We ask the
> > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion,
> and
> > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to
> be
> > Mentors.
> >
> > Please cast your vote:
> >
> > [ ] +1, bring Weex into Incubator
> > [ ] +0, I don't care either way,
> > [ ] -1, do not bring Weex into Incubator, because...
> >
> > This vote will be open at least for 72 hours and only votes from the
> > Incubator PMC are binding.
> >
> > --
> > https://wiki.apache.org/incubator/WeexProposal
> >
> > = Weex Proposal =
> >
> > == Abstract ==
> > Weex is a framework for building Mobile cross-platform high performance
> UI.
> > Weex enables developers to use Web-like syntax to build iOS, Android and
> > Web
> > UI with a single codebase.
> >
> > == Proposal ==
> > Weex provide an uniform Web-like syntax for develop native Mobile App UI.
> > By
> > leverage the Javascript engine that enable dynamic update, the process of
> > App interfce and content update can be simple and controllable just like
> > Web.Compared with WebView based UI framework which performance are
> limited,
> > Weex use build-in native components instead.
> >
> > Because of tag based syntax that maintain a consistent style with Web
> > standards Weex using. Developers write in this language just like
> writting
> > in HTML. After transforming to JSBundle by Weex tools, these tags will be
> > rendered by build-in platform-specific components. The logic part of Weex
> > syntax write in Javascript which don't need be compiled control these
> > components.
> >
> > The vision of Weex is to complement gap between platform-specific Native
> UI
> > and Web technical based UI in Mobile age. The team behind Weex believe
> that
> > dynamicly interface update and high performance should be achieved at the
> > same time when people develop a Mobile App. Meanwhile duplicate work
> > between
> > the different platforms should be avoided.
> >
> > == Background ==
> > Prior to Weex, in order to develop high performance mobile application we
> > need write at least three different codebase(iOS, Android, Mobile Web) or
> > adopt WebView based UI technique(Apache Cordova for example) which can't
> > satisfy the demand for performance.
> >
> > A special task force at Alibaba Inc try to provide a solution for this
> > problem has been setup since 2013.  At first the team release a
> > cross-platform rendering engine which render a special format JSON to
> > native
> > components on different platform. To output this JSON file the team had
> > build a website which other developer can use to simply design final
> > interface.
> >
> > Although This solution had worked for a while, we found it not able to
> meet
> > our UI developer's habits. Most of our UI developer have Web background
> > which make them used to use tag based language to design App interface.
> > Meanwhile we found the JSON file lacks of enough flexibility. The
> following
> > discussion inspire we start to develop Weex.
> >
> > Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest
> user
> > volume eCommerce App in China has adapted Weex in a lot of UI. In the
> > latest
> > November 11th promotions(Alibaba's annual Singles' Day online shopping
> > event), UI developers from Alibaba Inc have build more then 1,500 pages
> > using Weex, 99.6% of all the promotional pages. The ratio of less than
> one
> > second page open time is more than 90%, the frame rate is
> 53.0~58.5(depend
> > on device) due to the high performance of Weex. In addition to user
> > experience improvement, the productivity of page development and the
> > efficiency of content delivery both have been improved.
> >
> > After open-source and have got a lot of followers in chinese mobile App
> > development community, several of popular Apps listed on chinese top
> charts
> > have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning
> > etc...)
> >
> > == Current Status ==
> > Weex has become an open source project since June 2016.  It has been used
> > at
> > a lot of Alibaba producted mobile softwares which running on 

Re: [RESULT] [VOTE] Graduate Commons RDF from incubator

[John D. Ament]

On Mon, Nov 28, 2016 at 6:11 AM Stian Soiland-Reyes 
wrote:

> On 23 November 2016 at 13:46, Stian Soiland-Reyes 
> wrote:
> > [Note: this is the IPMC vote on general@incubator - there's a
> > concurrent VOTE thread on dev@commons]
>
> > Please VOTE on graduating Commons RDF to Commons:
>
> Thanks to everyone who voted!
>
> The results are:
>
> +1 Andy Seaborne (Incubator PMC binding)
> +1 Sergio Fernandez (Incubator PMC binding)
> +1 Stian Soiland-Reyes (Incubator PMC binding)
> +1 Lewis John McGibbney (Incubator PMC binding)
> +1 Jochen Wiedman (Incubator PMC binding)
> +1 John D. Ament (Incubator PMC binding)
> +1 Ted Dunning (Incubator PMC binding)
>
> +7 positive binding votes, no negative votes.
>
> The vote has PASSED at Incubator PMC (and at Commons PMC). I will
> proceed with the relevant community and infrastructure request for
> moving mailing list/repository/dist to Commons. (Any hints on this
> welcome!)
>

No, but there do appear to be some hints in ivy's graduation that may be
relevant.  Don't forget to update the various incubator website contents to
mark the graduation as well.  Those aren't dependent on the infra steps
required.


>
> As Commons RDF is graduating to become a subproject of Commons there
> won't be a legal TLP resolution needed by the board.
>
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT] [VOTE] Graduate Commons RDF from incubator

[Stian Soiland-Reyes]

On 23 November 2016 at 13:46, Stian Soiland-Reyes  wrote:
> [Note: this is the IPMC vote on general@incubator - there's a
> concurrent VOTE thread on dev@commons]

> Please VOTE on graduating Commons RDF to Commons:

Thanks to everyone who voted!

The results are:

+1 Andy Seaborne (Incubator PMC binding)
+1 Sergio Fernandez (Incubator PMC binding)
+1 Stian Soiland-Reyes (Incubator PMC binding)
+1 Lewis John McGibbney (Incubator PMC binding)
+1 Jochen Wiedman (Incubator PMC binding)
+1 John D. Ament (Incubator PMC binding)
+1 Ted Dunning (Incubator PMC binding)

+7 positive binding votes, no negative votes.

The vote has PASSED at Incubator PMC (and at Commons PMC). I will
proceed with the relevant community and infrastructure request for
moving mailing list/repository/dist to Commons. (Any hints on this
welcome!)

As Commons RDF is graduating to become a subproject of Commons there
won't be a legal TLP resolution needed by the board.

-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Weex to enter the Apache Incubator

[Stephan Ewen]

+1 (binding)


On Sun, Nov 27, 2016 at 1:44 AM, Luke Han  wrote:

> +1 binding
>
> Get Outlook for iOS
>
>
>
>
> On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" <
> willem.ji...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> +1 （binding）
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon
> wrote:
>
> > Greetings!
> >
> > I would like to call a vote for accepting "Weex" for incubation in the
> > Apache Incubator. The full proposal is available below.  We ask the
> > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion,
> and
> > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to
> be
> > Mentors.
> >
> > Please cast your vote:
> >
> > [ ] +1, bring Weex into Incubator
> > [ ] +0, I don't care either way,
> > [ ] -1, do not bring Weex into Incubator, because...
> >
> > This vote will be open at least for 72 hours and only votes from the
> > Incubator PMC are binding.
> >
> > --
> > https://wiki.apache.org/incubator/WeexProposal
> >
> > = Weex Proposal =
> >
> > == Abstract ==
> > Weex is a framework for building Mobile cross-platform high performance
> UI.
> > Weex enables developers to use Web-like syntax to build iOS, Android and
> > Web
> > UI with a single codebase.
> >
> > == Proposal ==
> > Weex provide an uniform Web-like syntax for develop native Mobile App UI.
> > By
> > leverage the Javascript engine that enable dynamic update, the process of
> > App interfce and content update can be simple and controllable just like
> > Web.Compared with WebView based UI framework which performance are
> limited,
> > Weex use build-in native components instead.
> >
> > Because of tag based syntax that maintain a consistent style with Web
> > standards Weex using. Developers write in this language just like
> writting
> > in HTML. After transforming to JSBundle by Weex tools, these tags will be
> > rendered by build-in platform-specific components. The logic part of Weex
> > syntax write in Javascript which don't need be compiled control these
> > components.
> >
> > The vision of Weex is to complement gap between platform-specific Native
> UI
> > and Web technical based UI in Mobile age. The team behind Weex believe
> that
> > dynamicly interface update and high performance should be achieved at the
> > same time when people develop a Mobile App. Meanwhile duplicate work
> > between
> > the different platforms should be avoided.
> >
> > == Background ==
> > Prior to Weex, in order to develop high performance mobile application we
> > need write at least three different codebase(iOS, Android, Mobile Web) or
> > adopt WebView based UI technique(Apache Cordova for example) which can't
> > satisfy the demand for performance.
> >
> > A special task force at Alibaba Inc try to provide a solution for this
> > problem has been setup since 2013.  At first the team release a
> > cross-platform rendering engine which render a special format JSON to
> > native
> > components on different platform. To output this JSON file the team had
> > build a website which other developer can use to simply design final
> > interface.
> >
> > Although This solution had worked for a while, we found it not able to
> meet
> > our UI developer's habits. Most of our UI developer have Web background
> > which make them used to use tag based language to design App interface.
> > Meanwhile we found the JSON file lacks of enough flexibility. The
> following
> > discussion inspire we start to develop Weex.
> >
> > Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest
> user
> > volume eCommerce App in China has adapted Weex in a lot of UI. In the
> > latest
> > November 11th promotions(Alibaba's annual Singles' Day online shopping
> > event), UI developers from Alibaba Inc have build more then 1,500 pages
> > using Weex, 99.6% of all the promotional pages. The ratio of less than
> one
> > second page open time is more than 90%, the frame rate is
> 53.0~58.5(depend
> > on device) due to the high performance of Weex. In addition to user
> > experience improvement, the productivity of page development and the
> > efficiency of content delivery both have been improved.
> >
> > After open-source and have got a lot of followers in chinese mobile App
> > development community, several of popular Apps listed on chinese top
> charts
> > have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning
> > etc...)
> >
> > == Current Status ==
> > Weex has become an open source project since June 2016.  It has been used
> > at
> > a lot of Alibaba producted mobile softwares which running on the mobile
> > phone of millions of users.
> >
> > Weex code repository located at GitHub. All development activities have
> > already happened on GitHub as open source manner.
> >
> > == Community ==
> > The community surrounding Weex is a