Re: [DISCUSS] graduation from the incubator
+1. I totally agree. I think the community is mature enough and ready to graduate. Thank you for bringing this for discussion. Best regards Ying Chun Guo (Daisy) -"David P Grove" wrote: - To: "OpenWhisk Dev" From: "David P Grove" Date: 03/16/2019 06:06AM Subject: [DISCUSS] graduation from the incubator I'd like to kick off a discussion to assess the project's readiness for graduation from the incubator. Per Rodric's recent stats [1], the community has developed nicely in terms of code contribution. We've released a number of software components following the Apache release process. We are in the midst of making our first "uber-release" across all of our sub-components (expect at least 2 voting threads next week). Overall I think the community is active. Communication on the project slack is frequent (avg of >160 messages a day) and is now digested daily to the dev list. (See [2] for stats). There are a couple procedural tasks we still need to complete, foremost being the formal transfer of the OpenWhisk trademarks from IBM to the ASF. But I think we can assume that these tasks will be completed and start considering graduation in parallel. Please share your thoughts, --dave [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apache.org_thread.html_b2217c61caad5c7a0369699d06d44e5cf688d3cba982e354a45b8c78-40-253Cdev.openwhisk.apache.org-253E=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=GRIRMIoZuK8tbK6TZq8368Lj7uKxlj6ZkR-yP7hl7RM=S0KcLa9uT60OMjsq821jZOOVIEEzd13okF2v1_od4-w= [2] https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_pages_viewpage.action-3FpageId-3D103091999=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=GRIRMIoZuK8tbK6TZq8368Lj7uKxlj6ZkR-yP7hl7RM=gGuNq0zh4G0CUDQbnWUCjhTMEF_6Q2m0hkweVxzQO6k=
Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client go and CLI
I vote +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI. Thanks to Vincent for taking this effort. Checklist for reference: [X] Download links are valid. [ ] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts have correct names matching the current release. [X] LICENSE and NOTICE files are correct for each OpenWhisk repo. [X] All files have license headers if necessary. [X] No compiled archives bundled in source archive. Best regards Ying Chun Guo (Daisy) -"Vincent S Hou" wrote: - To: dev@openwhisk.apache.org From: "Vincent S Hou" Date: 08/01/2018 06:36AM Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client go and CLI Hi everyone, This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating: OpenWhisk client go and CLI. List of JIRA ticket(s) resolved for this release can be found at https://issues.apache.org/jira/browse/INCUBATOR-215. To learn more about Apache OpenWhisk, please visit https://openwhisk.apache.org/. This release comprises of source code distribution only. There are two modules within this release. The artifact were built from the following Git commit IDs: * openwhisk-client-go: 90976ef, Update the doc of client go to make it clear for 0.9.0 * openwhisk-cli: 4a5a372, Bump gradle and scoverage version The source code artifact of openwhisk client go can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz The SHA-512 checksum for the artifact of openwhisk client go can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512 The signature of the artifact of openwhisk client go can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc The source code artifact of openwhisk cli can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz The SHA-512 checksum for the artifact of openwhisk cli can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512 The signature of the artifact of openwhisk cli can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc KEYS file is available here: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS The documentation can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating. The vote will be open for at least 72 hours. [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI [ ] +0 no opinion [ ] -1 Do not release and the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Thank you very much. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module
I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating Checklist for reference: [X] Download links are valid. [O] Checksums and PGP signatures are valid. [X] Source code artifacts have correct names matching the current release. [X] LICENSE and NOTICE files are correct for each OpenWhisk repo. [X] All files have license headers if necessary. [X] No compiled archives bundled in source archive. Best regards Ying Chun Guo (Daisy) -"Vincent S Hou" wrote: - To: dev@openwhisk.apache.org From: "Vincent S Hou" Date: 07/04/2018 02:55AM Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module Hi everyone, This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module. We have resolved all the issues regarding the dependency's license, gradle wrapper, some documentation issues, etc, based on we discussed during last voting mail thread for rc1. This release comprises of source code distribution only. There is one module within this release. The artifact was built from the following Git commit ID: * openwhisk: b1476b9, add until for all ansible retries (#3806) The source code artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz The MD5 checksum for each artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.md5 The SHA-512 checksum for each artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512 The signature of this artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc KEYS file is available here: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS The documentation can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating rc2. The vote will be open for at least 72 hours. [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating [ ] +0 no opinion [ ] -1 Do not release and the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Thank you very much. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
Re: removal of non-Helm deployment from incubator-openwhisk-deploy-kube
Agree. It's easy for maintainess. Best regards Ying Chun Guo (Daisy) -"David P Grove" wrote: - To: dev@openwhisk.apache.org From: "David P Grove" Date: 06/29/2018 06:07AM Subject: removal of non-Helm deployment from incubator-openwhisk-deploy-kube I've just submitted a PR [1] to remove the "old style" non-Helm deployment from the deploy-kube project. The Helm-based deployment is (a) much simpler for users to deploy and (b) supports strictly more configuration options than the code being removed. We've been heading this direction for a couple of months, but since this is a significant change I wanted to raise it on the dev list and wait for a couple of days before actually proceeding with the removal of the old code. thanks, --dave [1] https://github.com/apache/incubator-openwhisk-deploy-kube/pull/239
Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module
I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating. Checklist: [X] Download links are valid. [X] Source code artifacts have correct names matching the current release. [X] LICENSE and NOTICE files are correct for each OpenWhisk repo. [X] All files have license headers if necessary. [X] No compiled archives bundled in source archive. Best regards Ying Chun Guo (Daisy) -"Vincent S Hou" wrote: - To: dev@openwhisk.apache.org From: "Vincent S Hou" Date: 06/26/2018 05:27AM Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module Hi everyone, This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module. List of JIRA ticket(s) resolved for this release can be found at https://issues.apache.org/jira/browse/INCUBATOR-213. To learn more about Apache OpenWhisk, please visit https://openwhisk.apache.org/. This release comprises of source code distribution only. There is one module within this release. The artifact was built from the following Git commit ID: * openwhisk: 76dadd2, Bump gradle and scoverage version The source code artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz The MD5 checksum for each artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.md5 The SHA-512 checksum for each artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.sha512 The signature of this artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.asc KEYS file is available here: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS The documentation can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating. The vote will be open for at least 72 hours. [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating [ ] +0 no opinion [ ] -1 Do not release and the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Thank you very much. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating
I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating. I went through the check list. I think it's good for the first release. I'm looking forward to it. Thanks Vincent for the work. Best regards Ying Chun Guo (Daisy) -"Vincent S Hou" wrote: - To: dev@openwhisk.apache.org From: "Vincent S Hou" Date: 06/21/2018 05:16AM Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating Hi everyone, This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating. List of JIRA ticket(s) resolved for this release can be found at https://issues.apache.org/jira/browse/INCUBATOR-213. To learn more about Apache OpenWhisk, please visit https://openwhisk.apache.org/. This release comprises of source code distribution only. There are totally 13 OpenWhisk projects within this release. The artifacts were built from the following Git commit IDs: * openwhisk: 071d841, Make test-instances of Exec depend on the loaded manifest. * openwhisk-client-go: 1e50522, Add the DISCLAIMER file for Apache incubator project * openwhisk-cli: 461f94f, add OS and CPU architecture to user agent header * openwhisk-catalog: 517341d, Add the DISCLAIMER file for Apache incubator project * openwhisk-wskdeploy: 7620ef7, disabling export integration * openwhisk-apigateway: 2b87366, Fix awk command in init.sh generating resolvers.conf file * openwhisk-deploy-kube: cb9c3f5, Update runtimes for upstream changes. * openwhisk-runtime-nodejs: 557c4bd, update nodejs 6 & 8 to latest security patch * openwhisk-runtime-java: b20f90e, Add skip_pull_runtimes for Travis CI * openwhisk-runtime-swift: 06c4972, update travis to push "master" tag to Docker on "master" branch merges * openwhisk-runtime-python: a2098d9, update travis to push "master" tag to Docker on "master" branch merges * openwhisk-runtime-php: b0834a5, Fix travis publish 72 * openwhisk-runtime-docker: 650842a, Add ActionProxyContainer tests All the source code artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/ Each source code artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/[project name]-0.9.0-incubating-sources.tar.gz The MD5 checksum for each artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/[project name]-0.9.0-incubating-sources.tar.gz.md5 The SHA-512 checksum for each artifact can be found via: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/[project name]-0.9.0-incubating-sources.tar.gz.sha512 KEYS file is available here: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating. The vote will be open for at least 72 hours. [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating [ ] +0 no opinion [ ] -1 Do not release and the reason Thank you very much. Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
PRs to update NOTICE file
Hi, whiskers Today I have a list of PRs to OpenWhisk repo to update NOTICE file. I made follow updates: - change the extension of NOTICE from md to txt - add declarations of build and compile dependencies which are NOT Apache license. I got the dependencies information from compile and build configure files, e.g. build.gradle, DEPENDENCIES.md, package.json, and etc. - append NOTICE files for those dependencies which are Apache License if NOTICE file exists. Below are links to my PRs: https://github.com/apache/incubator-openwhisk/pull/3522 https://github.com/apache/incubator-openwhisk-cli/pull/265 https://github.com/apache/incubator-openwhisk-client-go/pull/74 https://github.com/apache/incubator-openwhisk-apigateway/pull/286 https://github.com/apache/incubator-openwhisk-catalog/pull/266 https://github.com/apache/incubator-openwhisk-runtime-docker/pull/25 https://github.com/apache/incubator-openwhisk-runtime-java/pull/29 https://github.com/apache/incubator-openwhisk-runtime-nodejs/pull/34 https://github.com/apache/incubator-openwhisk-runtime-php/pull/12 https://github.com/apache/incubator-openwhisk-runtime-python/pull/14 https://github.com/apache/incubator-openwhisk-runtime-swift/pull/43 https://github.com/apache/incubator-openwhisk-wskdeploy/pull/842 Please review them. Thanks. Best regards Ying Chun Guo (Daisy)
Re: Who has the experiences to assemble NOTICE file?
Thank you for the detail guidance, Justin I don't quite understand the differences between "3rd party code contained / bundleded inside the release" and "Software dependencies". Do you think the NOTICE file from Spark project is a good example? I think it declares dependencies which are not Apache license. It also append NOTICE files of dependencies which are Apache License. Also, Spark NOTICE also includes Copyrights information for those dependencies with Apache License, copied from NOTICE files. Is that conflict with what you said: Copyrights from licenses generally do not go in NOTICE. Best regards Ying Chun Guo (Daisy) [1] https://github.com/apache/spark/blob/master/NOTICE -Justin Mclean <jus...@classsoftware.com> wrote: - To: OpenWhisk Dev <dev@openwhisk.apache.org> From: Justin Mclean <jus...@classsoftware.com> Date: 03/31/2018 08:08AM Subject: Re: Who has the experiences to assemble NOTICE file? Hi, (sorry forgot to copy the dev list - so resending) I guess you have read [1]? But basically you should do this: - Take the boilerplate NOTICE [2] - Update the year to the current year - Did your code come in via a software grant, then add that (relocated copyrights).[3] - Is there any 3rd party code contained / bundleded inside the release? If so: - Is any of the code Apache licensed and do they have a NOTICE files? If so: - Pplace relevant parts of those NOTICE to your NOTICE file. [4] (There's also required notices but they are very rare [5] and you probably don’t need to worry about them). Things to watch out for: - License information should not be mentioned in NOTICE (that information goes in license) - Software dependencies should not be mentioned in NOTICE - Copyrights from licenses generally do not go in NOTICE. Take care if you copy one of the more “popular" TLP projects and use that, as some are poor examples or are confusing as they have had issues with upstream project NOTICE files. This worked example may also help [6][7] as may this talk [8] I gave the last ApacheCon. Thanks, Justin 1. https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_dev_licensing-2Dhowto.html=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=zqnvtIGA5h-10VHgNcAosG8SMrvSBz47Ar2rGiOGIZ8= 2. https://urldefense.proofpoint.com/v2/url?u=https-3A__www.apache.org_licenses_NOTICE-2D2.0.txt=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=Yyws7S_pGLGCR-VEleMx_BhECQtv1zNlKiLDgHa7SQM= 3. https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_legal_src-2Dheaders.html-23headers=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=3cweg-kgAb_yx0gSZkqL7XxeC6eWzewUHxBFedbz0pw= 4. https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_dev_licensing-2Dhowto.html-23alv2-2Ddep=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=0m8FbuGPyOmuxSZbVxic92HRh6LqlpmLpjJ7yxXXMGg= 5. https://urldefense.proofpoint.com/v2/url?u=https-3A__www.apache.org_legal_resolved.html-23required-2Dthird-2Dparty-2Dnotices=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=8TeWIsT_iU8M1m7LyG2kCg2Op4WnhJ7LxFroREHMe5Q= 6. https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_justinmclean_ApacheWombat=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=2lV6_4aFQSu0k_XHxUqOal8L5GS1VnyYUyZ1lzvItUU= 7. https://urldefense.proofpoint.com/v2/url?u=https-3A__vimeo.com_171210141=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=y0L7rJWPhsyeYtPNMM11ckG5iwxI0kCQzGo8BkydRlQ= 8. https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_watch-3Fv-3DI0-2Dlp1t9ee0=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=6SABlaLAYkaOvZYVgXkEN3r9D7US0VqcW_oXdWsVwUo=XmDvbxyMhE8xCrcRs0-FtaD9Xk_-K2iqgGgiDSx4buE= - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Who has the experiences to assemble NOTICE file?
Hi, friends I'd like to learn from people who has the experience to assemble the legal NOTICE file before. I need to do this for Apache OpenWhisk repos. I find manually assembling NOTICE is a complex and error-prone task especially for a non-legal person like me. Is there a tool to help on that ? Does anyone share any experiences on that? Best regards Ying Chun Guo (Daisy)
Re: Release policy compliance: Adding license headers and the excluded files
Hi, Matt I tested. The answer is NO. Apache Rat cannot recognize short header format. That will cause a problem because the large size of action files will slow down the tests running. We can ignore these files till Rat supports short header format. Best regards Ying Chun Guo (Daisy) -"Matt Rutkowski" <mrutk...@us.ibm.com> wrote: - >To: dev@openwhisk.apache.org >From: "Matt Rutkowski" <mrutk...@us.ibm.com> >Date: 02/12/2018 11:53PM >Subject: Re: Release policy compliance: Adding license headers and >the excluded files > >Is there any way for the RAT tool to acknowledge the "minified" ASF >header >that is approved for use in .js (and other files)? > >See "short form" approved here: >https://urldefense.proofpoint.com/v2/url?u=https-3A__www.apache.org_l >egal_src-2Dheaders.html=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEs >ahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=V06q35OiWjYJAWe2jq-3fSk7CreRb6Ah >wORWCs2KSJw=iNii7yGWwSTIBwziwicIhtKB91LCc5XgQpmAu_bTb9k= > >Kind regards, >Matt > > > > >From: "Ying Chun Guo" <guoyi...@cn.ibm.com> >To: dev@openwhisk.apache.org >Date: 02/12/2018 08:18 AM >Subject: Re: Release policy compliance: Adding license headers >and >the excluded files > > > >Hi, Bertrand > >Thank you for the inputs. > >My original thought was to maintain different Rat exclusions for >different >repo because they may have different files. If we want to maintain a >unique version, we may need to collect all exclusions in all the repo > >together and maintain a set. Sometimes it's difficult to tell whether >a >file shall be excluded or not. Hope you can help review after the >collection is ready. > >OpenWhisk has a repo in github to track release documents and >scripts. >Here it is: >https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apach >e_incubator-2Dopenwhisk-2Drelease_blob_master_README.md=DwIFaQ=jf >_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw= >tuRJI4eVUHlqHACnIGwvLgDqy1D9dIaSeLjOME3KJJg=RqfPKNiDPwlE1yljo6i5Rct >CRB6jXLLbQ5gickneycE= >. I think these information can be documented here: >https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apach >e_incubator-2Dopenwhisk-2Drelease_blob_master_docs_work-5Fitems.md-23 >2-2Dverify-2Dthe-2Dcompliance-2Dof-2Dthe-2Dsource-2Dcode-2Dopen-2Diss >ue=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS4 >78q2gZlAJj4Zw=tuRJI4eVUHlqHACnIGwvLgDqy1D9dIaSeLjOME3KJJg=t34yGdw >cAE-qLfsKcS0ueeVqUAffslBtsP_kxQmK2fk= >. > >Best regards >Ying Chun Guo (Daisy) > > >-Bertrand Delacretaz <bdelacre...@apache.org> wrote: - >To: dev@openwhisk.apache.org >From: Bertrand Delacretaz <bdelacre...@apache.org> >Date: 02/09/2018 06:41PM >Subject: Re: Release policy compliance: Adding license headers and >the >excluded files > >Hi Daisy, > >On Thu, Feb 8, 2018 at 1:24 PM, Ying Chun Guo <guoyi...@cn.ibm.com> >wrote: >> ...I use Apache Rat to audit license headers. I use wskdeploy repo >as >the trial repo. >> I reported an issue ( >https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apach >e_incubator-2Dopenwhisk-2Dwskdeploy_issues_716=DwIBaQ=jf_iaSHvJOb >Tbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=m3ygIAacP >w2tdx9MhWLfpLzsW1V32RO3z5g6A2YFWCo=zY3fWnnLVXjHDVQvYS73Db0ljWoQg4Oa >YlqNm1mbjWE= >) >> to wskdeploy including a report generated by Apache Rat. In the >report, >all the files >> with unapproved licenses will be listed... > >This sounds great. > >What you want basically is that for any build that's meant to create >a >release: > >-Rat should run >-The build should fail if Rat reports any anomalies >-The Rat exclusions should ideally be defined in the same way for all >modules, for consistency >-The Rat exclusions should be commented to indicate why each >exclusion >(or family of exclusions) is here > >I think this should be documented in a "coding standards" or "release >management" page, does OpenWhisk have this already? > >-Bertrand (with my incubation mentor hat on) > > > > > > >
Re: Tech Interchange Meeting February 14th
Hi, Martin Thank you for organizing this. I would like to take 5-10 minutes to talk about license header auditing in the release process and we need to get an agreement on the list of excluded files during header auditing. Here are some examples of issues I reported: https://github.com/apache/incubator-openwhisk/issues/3264 https://github.com/apache/incubator-openwhisk-catalog/issues/256 https://github.com/apache/incubator-openwhisk-wskdeploy/issues/716 Here is the discussion in mailing list: http://mail-archives.apache.org/mod_mbox/incubator-openwhisk-dev/201802.mbox/%3cof33eb10e9.d0ed99eb-on0025822e.00432d2b-0025822e.00442...@notes.na.collabserv.com%3e Is it able to arrange this topic this week? Thank you in advance. Best regards Ying Chun Guo (Daisy) -Martin Henke <martin.he...@web.de> wrote: - To: dev@openwhisk.apache.org From: Martin Henke <martin.he...@web.de> Date: 02/13/2018 05:15PM Subject: Tech Interchange Meeting February 14th Hello, this is a kind reminder for our bi-weekly Tech Interchange Meeting tomorrow. The proposed agenda up to now is: - Introduction of new attendees - Asking around for notable changes/updates - Updates on the graduation / release mgmt. process for OpenWhisk by Vincent S Hou [20 min] - Sharding Loadbalancer changes by Markus Thömmes [10 min] - Find and confirm moderator for next meeting Feb 28th @all: Please contact me if you have another topic that should show up on the agenda. @Matt: Can you please the agenda to the CWiki. Details: What: Apache OpenWhisk "Tech. Interchange" (bi-weekly) Zoom Meeting When: @ 11:00am EDT, 8am PDT, 3pm GMT, 5pm CEST , 3pm UTC Where: https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=9FnXQbMCgmxXL2yMESD0WjhcmAqHl7_85eJj1IBzQLg=DwPgj_ictYPTQbP1lIU_G_76udk0a05NJ-H-HDPyVPQ= Regards, Martin
Re: Release policy compliance: Adding license headers and the excluded files
Hi, Bertrand Can you help to answer a specific question to Apache Rat? For some short JavaScript files, we want to use short form of Apache license header. But I found Apache Rat cannot recognize short form headers. Do you know how to handler this situation? Besides Rat, are there any other tools that can help audit headers in a release? Best regards Ying Chun Guo (Daisy) -Bertrand Delacretaz <bdelacre...@apache.org> wrote: - To: dev@openwhisk.apache.org From: Bertrand Delacretaz <bdelacre...@apache.org> Date: 02/09/2018 06:41PM Subject: Re: Release policy compliance: Adding license headers and the excluded files Hi Daisy, On Thu, Feb 8, 2018 at 1:24 PM, Ying Chun Guo <guoyi...@cn.ibm.com> wrote: > ...I use Apache Rat to audit license headers. I use wskdeploy repo as the > trial repo. > I reported an issue > (https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Dwskdeploy_issues_716=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=m3ygIAacPw2tdx9MhWLfpLzsW1V32RO3z5g6A2YFWCo=zY3fWnnLVXjHDVQvYS73Db0ljWoQg4OaYlqNm1mbjWE=) > to wskdeploy including a report generated by Apache Rat. In the report, all > the files > with unapproved licenses will be listed... This sounds great. What you want basically is that for any build that's meant to create a release: -Rat should run -The build should fail if Rat reports any anomalies -The Rat exclusions should ideally be defined in the same way for all modules, for consistency -The Rat exclusions should be commented to indicate why each exclusion (or family of exclusions) is here I think this should be documented in a "coding standards" or "release management" page, does OpenWhisk have this already? -Bertrand (with my incubation mentor hat on)
Release policy compliance: Adding license headers and the excluded files
Hello, whiskers In order to get Apache release policy compliance, we need to add license headers to every source file in the distributions with few exceptions. I'd like to share what I have done and what I'm going to do with you. "With few exceptions, all human-readable Apache-developed files that are included within a distribution must include the header text." Quoted from http://www.apache.org/legal/src-headers.html I use Apache Rat to audit license headers. I use wskdeploy repo as the trial repo. I reported an issue (https://github.com/apache/incubator-openwhisk-wskdeploy/issues/716) to wskdeploy including a report generated by Apache Rat. In the report, all the files with unapproved licenses will be listed. Then I submit a PR (https://github.com/apache/incubator-openwhisk-wskdeploy/pull/709) to add Apache license headers. I'm going to do same to all the other projects in OpenWhisk community. Matt Rutkowski offers help to this work too. As to the exceptions, I followed the document in http://www.apache.org/legal/src-headers.html#faq-exceptions to decide which files can be excluded. In wskdeploy project, they are: # files copied from third parties or created by tools gradlew gradlew.bat Godeps i18n_resources.go # JSON data file doesn't support annotation .*json # Test data # others .gitignore .rat-excludes Different repo may have a different exception list. The exception list can be tracked by .rat-excludes in the root folder ( refer to https://github.com/daisy-ycguo/incubator-openwhisk-wskdeploy/blob/add_lice/.rat-excludes ) If you have comments or suggestions to my work or to the exception list, feel free to discuss here. I'm open for any inputs. Thank you. Best regards Ying Chun Guo (Daisy)
Using Apache Creadur to audit in the release process
Hi, all As we are setting up the release process, I'm investigating how Apache Creadur[1] - the auditing tools - can help us in the release process. This email describes what I found and what I propose. We can discuss together. First of all, we need to understand audit is very important in a Apache release process. "every ASF release MUST comply with ASF licensing policy. This requirement is of utmost importance and an audit SHOULD be performed before any full release is created.", described by Apache Release Policy[2]. Apache Creadur is such audit tooling to help us. Apache Creadur includes three projects: - Apache Rat audits license headers. It will check if files have Apache License or not, and generate a report. - Apache Tentacles helps to audit in bulk components uploaded to a staging repository. It will check if there is a LICENSE and NOTICE files under each archived source package and compiled package. A HTML report will be generated. - Apache Whisker will generate a correct legal documentation if a package bundles code under several licenses. I propose to use: - Apache Rat to check license headers during the release of the source package. We can develop a program to auto 'read' the report generated by Rat. If the report doesn't find any issues, the release can be continued. Or else, it will be stopped and errors will be returned. - Apache Tentacles to check if every archived package has a LICENSE and a NOTICE file. The check need to be done both in the release of the source package and the release of the compiled package after the artifacts are uploading to a staging repository. Similar as Rat report, we will develop program to auto "read" the report and decide whether there are issues. Apache Whisker is not relevant to us up to now, because we don't have codes under none Apache licenses. ( Correct me if I'm wrong ). In the future, we may need it. Let me know if you have any comments and suggestions to the audit process and tooling. Best regards Daisy Guo [1] http://creadur.apache.org [2] http://www.apache.org/legal/release-policy.html#licensing
Re: Propose BI-WEEKLY "Technical Exchange" Zoom meeting for OpenWhisk staring next Wed. 19th
I have a PR[1] to add links of English videos with Chinese subtitles from mini academy to incubator-openwhisk-external-resources. There is no special Chinese page with only OpenWhisk contents, but I can create a wiki page to do that, listing all links to technical exchange, in the same website with mini academy. Best regards Ying Chun Guo (Daisy) [1] https://github.com/apache/incubator-openwhisk-external-resources/pull/25 -"Matt Rutkowski" <mrutk...@us.ibm.com> wrote: - To: dev@openwhisk.apache.org From: "Matt Rutkowski" <mrutk...@us.ibm.com> Date: 07/13/2017 09:36PM Subject: Re: Propose BI-WEEKLY "Technical Exchange" Zoom meeting for OpenWhisk staring next Wed. 19th Hi David, Yes we should cross post the video to allow China access. Have we linked the China site for the Academy on our OW website? Also, do we have an OW "area" on this site to allow people to search and follow just OW videos? Kind regards, Matt From: "David ZL Liu" <david@cn.ibm.com> To: dev@openwhisk.apache.org Date: 07/12/2017 09:08 PM Subject:Re: Propose BI-WEEKLY "Technical Exchange" Zoom meeting for OpenWhisk staring next Wed. 19th Hi Matt, That's great, the topics are quite extensive. Is that possible we could put the video and materials to some chinese video web sites, such as Youku, it will improve the OpenWhisk impact here in china market. Currently we have a mini academy site host by @Daisy. Unfortunately most of time Youtube is not available in china due to some reasons. Kind Regards, dliu From: "Matt Rutkowski" <mrutk...@us.ibm.com> To: d...@openwhisk.incubator.apache.org Date: 2017-07-13 上午 05:49 Subject:Re: Propose BI-WEEKLY "Technical Exchange" Zoom meeting for OpenWhisk staring next Wed. 19th After delays for various reasons, I would very much like to propose we "kick off" the "Tech. Interchange" calls starting next Wednesday at 11am US EDT (am open to 10am US EDT if the PDT people have no problem) next week July 19th. Using Zoom as the meeting app. which allows us to see each other, share materials and of course record for playbacks from our YouTube channel. See all the proposed details from earlier post below... The call I propose would be Bi-Weekly (not weekly) to begin with (see if we need more/less over time and add other times for other geos. as we are able to add volunteer moderators). For the first agenda it would be nice to have introductions and propose the following general agenda format/template with attendees offering updates/topic discussion in the following areas: - main/core OpenWhisk - Kube/Mesos/Compose (Deployment) - API Gateway - Catalog/Packages/Samples - Tooling/Utils - prepared agenda topics (solicited and encouraged from the "dev" list primarily) * including education topics we would like to propose. e.g., Request trace through system, debugging/logs, etc. - "at large" / open topics submitted on "dev" list or observe on Slack, etc. My plan would be to post the bi-weekly agenda by EOD Monday of the same week on the "dev" list and use Slack as secondary posting mechanism and provide reminders on Slack as well before meeting starts. Everyone would be invited to speak up if they are working on an interesting topic in any area. I am also hoping to encourage education/discussion agenda topics (e.g., on debugging, logging, testing, feature change demos, etc.). Of course, I will record, post video to OW YouTube channel and upload notes (attendance topics) to our OW CWIKI. The Zoom info would be as follows: Topic: Apache OpenWhisk "Tech. Interchange" (bi-weekly) Zoom Meeting Time: this is a recurring meeting Meet anytime Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/asfopenwhisk Or iPhone one-tap (US Toll): +16465588656,,5043933185# or +14086380968,,5043933185# Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll) Meeting ID: 504 393 3185 International numbers available: https://zoom.us/zoomconference?m=T4Ycc4hVdhvPkjU0ZjPjwtzOUOtbAH5W I would moderate the first call and ask Jeremias/Carlos/Rodric/Dragos/etc. or any other PPMC member to share in moderating future bi-weekly calls. Kind regards, Matt From: Matt Rutkowski/Austin/IBM To: d...@openwhisk.incubator.apache.org Date: 06/07/2017 10:08 AM Subject:Propose weekly "Technical Exchange" video meeting for OpenWhisk Hi Whiskers! Having attended all the amazing and inspiring sessions at ApacheCon a few weeks ago and wanting to enable our growing community with better ways to foster technical interchange, I would like to propose we work towards having weekly Here are my thoughts on such a meeting… - 1 hour meeting, with agenda to be solicited from community in advance - po
Re: Development documents
Hi, Rodric Do you think if using scaladoc to generate dev document is a good idea ? Best regards Ying Chun Guo (Daisy) -Rodric Rabbah <rod...@gmail.com> wrote: - To: dev@openwhisk.apache.org From: Rodric Rabbah <rod...@gmail.com> Date: 06/05/2017 02:44PM Subject: Re: Development documents What in particular are you looking for - can you elaborate on the information that you think would be helpful to you? -r
Re: GitHub <-> Apache setup using GitBox stuck "MFA Status" remains "empty" after 6 hours
Aha. I found it. I think I need extra step to enable 2FA. The blog gives more detail guidance: https://github.com/blog/1614-two-factor-authentication. Now I'm struggling with setting up using an App or using SMS, and will let you know any updates. Best regards Ying Chun Guo (Daisy) -Ying Chun Guo/China/IBM@IBMCN wrote: - To: dev@openwhisk.apache.org From: Ying Chun Guo/China/IBM@IBMCN Date: 02/21/2017 10:24PM Subject: Re: GitHub <-> Apache setup using GitBox stuck "MFA Status" remains "empty" after 6 hours Well, I might be a little ahead. I got an invitation in Github to join ASF organization. I accepted the invitation. Now my MFA status changed from empty to a red cross. " Write access suspended. Please make sure you are a part of the ASF Organisation on GitHub and have 2FA enabled. Visit id.apache.org and set your GitHub ID to be invited to the org. " I have joined ASF organization. I have my GitHub ID set via id.apache.org. Do I need to enable 2FA by myself? Or do I just wait ? Best regards Ying Chun Guo (Daisy) -"Matt Rutkowski" <mrutk...@us.ibm.com> wrote: - To: dev@openwhisk.apache.org From: "Matt Rutkowski" <mrutk...@us.ibm.com> Date: 02/21/2017 10:12PM Subject: Re: GitHub <-> Apache setup using GitBox stuck "MFA Status" remains "empty" after 6 hours My INFRA ticket was returned (tennis match now perhaps) that reiterates the instructions I already followed, but also says that I need "an invitation from the Apache GitHub org.) whic I thought was part of the 3rd box's step... he implied I should have gotten an email with the invitation, but have not as of 21 hours later. https://issues.apache.org/jira/browse/INFRA-13547 We will see what the response is. Kind regards, Matt From: Jeremias Werner <jeremias.wer...@gmail.com> To: dev@openwhisk.apache.org Date: 02/21/2017 02:40 AM Subject:Re: GitHub <-> Apache setup using GitBox stuck "MFA Status" remains "empty" after 6 hours For me it behaves the same, two green check's but MFA Status remains empty. I also still don't seem to have write access to the repo. Kind regards, Jeremias On Tue, Feb 21, 2017 at 12:14 AM, Matt Rutkowski <mrutk...@us.ibm.com> wrote: > Followed Carlos' instructions to allow cross authentication between My > GitHub account and my Apache Account. Both the Apache Account box and > GitHub box indicate all is OK with a big green checkmark; yet the last > box "MFA Status" remains empty/blank. > > How do I fix? I see Carlos has "write access granted" and below these 3 > checkbox areas it lists the repos. (for openwhisk) that he has been > granted write access to. > > What do I do to correct? > > Kind regards, > Matt > > >
