Re: [VOTE] Release DataSketches-java 1.1.0-incubating-RC1
Hi, > Please inspect it at > https://github.com/apache/incubator-datasketches-java/blob/master/NOTICE to > see if there are any other changes that you would like to make. That looks good. Thanks. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release DataSketches-java 1.1.0-incubating-RC1
Justin, Thank you for your vote and comments. Your suggestions for the NOTICE file have already been incorporated in master going forward. Please inspect it at https://github.com/apache/incubator-datasketches-java/blob/master/NOTICE to see if there are any other changes that you would like to make. Lee. On Tue, Oct 1, 2019 at 6:07 PM Justin Mclean wrote: > Hi, > > +1 binding > > I checked: > - incubating in name > - signature and hashes correct > - LICENSE is OK > - NOTICE has minor issues > - no unexpected binary files > - all source file have ASF headers > - can compile from source > > One minor thing with the NOTICE it’s not correct to say "2019 - Present”, > copyright applies when a work is published and doesn’t last forever. I’d > also (as suggested before on the last release) put the ASF copyright first. > > Also these two statement seem to possibly contradict each other: > Copyright 2018 - Present, Verizon > Copyright 2019 - Present, The Apache Software Foundation > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Milagro (incubating) Decentralized Trust Authority v0.1.0 (alpha release)
On 19/09/2019 10:06, Brian Spector wrote: Bumping this up. IPMC folks, could you please help us and review. +1 from me, anyway it is a alpha ;-) -- Cheers Jean-Frederic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Donation of subproject for PLC4X
Thanks Bertrand, I will start editing the IP Clearance Form then! Julian Am 02.10.19, 14:36 schrieb "Bertrand Delacretaz" : Hi, On Wed, Oct 2, 2019 at 1:59 PM Julian Feinauer wrote: > my company decided to donate our project CRUNCH [1] that has been developed internally to the ASF > ...We need to find a name and go through namesearch, or?... No, that's only for Apache PMCs which need to have a suitable name. IOW if your module is called "Apache PLC4X Foo" you don't need to do a name search on "Foo". > And also we need to do IP Clearance, or? Yes, see https://incubator.apache.org/ip-clearance/ -Bertrand
Re: Donation of subproject for PLC4X
Hi, On Wed, Oct 2, 2019 at 1:59 PM Julian Feinauer wrote: > my company decided to donate our project CRUNCH [1] that has been developed > internally to the ASF > ...We need to find a name and go through namesearch, or?... No, that's only for Apache PMCs which need to have a suitable name. IOW if your module is called "Apache PLC4X Foo" you don't need to do a name search on "Foo". > And also we need to do IP Clearance, or? Yes, see https://incubator.apache.org/ip-clearance/ -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Donation of subproject for PLC4X
Hi all, my company decided to donate our project CRUNCH [1] that has been developed internally to the ASF. The idea is to integrate it as subproject into the PLC4X Project [2]. The PMC has already performed a VOTE on that task [3,4] and we also filed a Software Grant as well as CCLA and ICLAs for all committers of the project. What are the next steps to take? We need to find a name and go through namesearch, or? And also we need to do IP Clearance, or? I’m happy for all pointers in the right direction : ) Julian [1] https://github.com/pragmaticminds/crunch [2] plc4x.apache.org [3] https://lists.apache.org/thread.html/9a8078209e005215232f6c02c2433ce0ef67473fe01414a1ac717c23@%3Cdev.plc4x.apache.org%3E [4] https://lists.apache.org/thread.html/3ef7b144ae60a3bd3bf2f592b6ecb6ed540967a45be252a072d3eead@%3Cdev.plc4x.apache.org%3E
RE: [VOTE] Release Apache Milagro (incubating) Decentralized Trust Authority v0.1.0 (alpha release)
Hi Julian, Many thanks for your updated vote. In the next release, we'll make the following changes: - Add missing licence headers to all source code files - Ensure that all build scripts, docker files and documentation build from official signed source archives (as per Dave Fisher's observations) Regards, John -Original Message- From: Julian Feinauer Sent: 02 October 2019 11:54 To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Milagro (incubating) Decentralized Trust Authority v0.1.0 (alpha release) Hi all, I change my vote to +1 (binding) It seems like I had some issues on my machine and on another PC the builds work. So my "major" concerns are no longer true and I change my vote. So, from below my checks: - Keys present in KEYS file - Signatures and Hash match for all 3 artifacts - DISCLAIMER is present, see findings below - LICENSE and NOTICE - Building of sources - works for crypto C (`make`) - works for crypt js (`npm install` and `npm test`) - works for dta The other "minor" findings should be corrected for the next release (see below). Thanks to John for his support and work helping me with the release. Best Julian Am 19.09.19, 23:01 schrieb "Julian Feinauer" : Hi, let me initially say, that the release locks pretty good and well prepared. But, unfortunately I found two issues I would consider major, thus I vote -1 (binding) Remember, this is no VETO so this does not necessarily stop the release. But from my experience its easier to fix things while you still are in release mode than after one. The two major issues I see are the Headers and the failing build of dta. I checked: - Keys present in KEYS file - Signatures and Hash match for all 3 artifacts - DISCLAIMER is present, see findings below - LICENSE and NOTICE - Building of sources - works for crypto C (`make`) - works for crypt js (`npm install`) but `npm test` fails, see below - fails for dta, see below (Minor) Findings: - Why is the DISCLAIMER different(ly formatted) for dta than for crypto c/js ? (Less Minor) Findings: - Several Files do not have apache headers. But at least "code" files like Dockerfile's and bash scripts should for sure have some (also CMake). In dta these are, e.g. /.dockerignore 25 ./.gitignore 26 ./.travis.yml 27 ./Dockerfile 28 ./Dockerfile-alpine 29 ./build-static.sh 30 ./build.sh 31 ./go.mod 32 ./go.sum 33 ./lint.sh 34 ./report 35 ./test.sh 36 ./cmd/servicetester/e2e_test.sh 37 ./cmd/servicetester/fulltest.sh 38 ./cmd/servicetester/id_test.sh 39 ./libs/crypto/libpqnist/CMakeLists.txt 40 ./libs/crypto/libpqnist/CPackConfig.cmake 41 ./libs/crypto/libpqnist/VERSION 42 ./libs/crypto/libpqnist/cmake_uninstall.cmake.in 43 ./libs/crypto/libpqnist/examples/CMakeLists.txt 44 ./libs/crypto/libpqnist/include/CMakeLists.txt 45 ./libs/crypto/libpqnist/src/CMakeLists.txt 46 ./libs/crypto/libpqnist/test/smoke/CMakeLists.txt 47 ./libs/crypto/libpqnist/testVectors/aes/CBCMMT256.rsp 48 ./libs/documents/docs.pb.go 49 ./libs/documents/docs.proto 50 ./libs/documents/docs.validator.pb.go 51 ./pkg/safeguardsecret/README.md 52 ./pkg/safeguardsecret/open-api.yaml - When trying to build dta on MacOs via Docker I Get Digest: sha256:b88f8848e9a1a4e4558ba7cfc4acc5879e1d0e7ac06401409062ad2627e6fb58 Status: Downloaded newer image for ubuntu:latest ---> 2ca708c1c9cc Step 2/29 : RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates cmake g++ gcc git make libtool automake libssl-dev ---> Running in f8a17dc7ab42 Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease 403 Forbidden [IP: 91.189.88.31 80] Err:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease 403 Forbidden [IP: 91.189.88.31 80] Err:3 http://security.ubuntu.com/ubuntu bionic-security InRelease 403 Forbidden [IP: 91.189.88.31 80] Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease 403 Forbidden [IP: 91.189.88.31 80] Reading package lists... E: The repository 'http://archive.ubuntu.com/ubuntu bionic InRelease' is not signed. E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: The repository 'http://archive.ubuntu.com/ubuntu bionic-updates InRelease' is not signed. E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: The repository
Re: [VOTE] Release Apache Milagro (incubating) Decentralized Trust Authority v0.1.0 (alpha release)
Hi all, I change my vote to +1 (binding) It seems like I had some issues on my machine and on another PC the builds work. So my "major" concerns are no longer true and I change my vote. So, from below my checks: - Keys present in KEYS file - Signatures and Hash match for all 3 artifacts - DISCLAIMER is present, see findings below - LICENSE and NOTICE - Building of sources - works for crypto C (`make`) - works for crypt js (`npm install` and `npm test`) - works for dta The other "minor" findings should be corrected for the next release (see below). Thanks to John for his support and work helping me with the release. Best Julian Am 19.09.19, 23:01 schrieb "Julian Feinauer" : Hi, let me initially say, that the release locks pretty good and well prepared. But, unfortunately I found two issues I would consider major, thus I vote -1 (binding) Remember, this is no VETO so this does not necessarily stop the release. But from my experience its easier to fix things while you still are in release mode than after one. The two major issues I see are the Headers and the failing build of dta. I checked: - Keys present in KEYS file - Signatures and Hash match for all 3 artifacts - DISCLAIMER is present, see findings below - LICENSE and NOTICE - Building of sources - works for crypto C (`make`) - works for crypt js (`npm install`) but `npm test` fails, see below - fails for dta, see below (Minor) Findings: - Why is the DISCLAIMER different(ly formatted) for dta than for crypto c/js ? (Less Minor) Findings: - Several Files do not have apache headers. But at least "code" files like Dockerfile's and bash scripts should for sure have some (also CMake). In dta these are, e.g. /.dockerignore 25 ./.gitignore 26 ./.travis.yml 27 ./Dockerfile 28 ./Dockerfile-alpine 29 ./build-static.sh 30 ./build.sh 31 ./go.mod 32 ./go.sum 33 ./lint.sh 34 ./report 35 ./test.sh 36 ./cmd/servicetester/e2e_test.sh 37 ./cmd/servicetester/fulltest.sh 38 ./cmd/servicetester/id_test.sh 39 ./libs/crypto/libpqnist/CMakeLists.txt 40 ./libs/crypto/libpqnist/CPackConfig.cmake 41 ./libs/crypto/libpqnist/VERSION 42 ./libs/crypto/libpqnist/cmake_uninstall.cmake.in 43 ./libs/crypto/libpqnist/examples/CMakeLists.txt 44 ./libs/crypto/libpqnist/include/CMakeLists.txt 45 ./libs/crypto/libpqnist/src/CMakeLists.txt 46 ./libs/crypto/libpqnist/test/smoke/CMakeLists.txt 47 ./libs/crypto/libpqnist/testVectors/aes/CBCMMT256.rsp 48 ./libs/documents/docs.pb.go 49 ./libs/documents/docs.proto 50 ./libs/documents/docs.validator.pb.go 51 ./pkg/safeguardsecret/README.md 52 ./pkg/safeguardsecret/open-api.yaml - When trying to build dta on MacOs via Docker I Get Digest: sha256:b88f8848e9a1a4e4558ba7cfc4acc5879e1d0e7ac06401409062ad2627e6fb58 Status: Downloaded newer image for ubuntu:latest ---> 2ca708c1c9cc Step 2/29 : RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates cmake g++ gcc git make libtool automake libssl-dev ---> Running in f8a17dc7ab42 Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease 403 Forbidden [IP: 91.189.88.31 80] Err:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease 403 Forbidden [IP: 91.189.88.31 80] Err:3 http://security.ubuntu.com/ubuntu bionic-security InRelease 403 Forbidden [IP: 91.189.88.31 80] Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease 403 Forbidden [IP: 91.189.88.31 80] Reading package lists... E: The repository 'http://archive.ubuntu.com/ubuntu bionic InRelease' is not signed. E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: The repository 'http://archive.ubuntu.com/ubuntu bionic-updates InRelease' is not signed. E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: The repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' is not signed. E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease 403 Forbidden [IP: 91.189.88.31 80] E: The repository 'http://archive.ubuntu.com/ubuntu bionic-backports InRelease' is not signed. The command '/bin/sh -c apt-get update && apt-get install -y --no-install-recommends ca-certificates cmake g++ gcc git make libtool automake libssl-dev'
