Fw: Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose?
Dear OpenWhiskers, I will bring this question and the current solution to the dev list. Our Travis build of openwhisk-release, it will import the public key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_pub.gpg ) and the private key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_sec.gpg.enc ), available in openwhisk-release repo. Private key is encrypted. The public key has already uploaded to the SVN repo as well: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS, so it can be used to verify the signature of each artifact. The name of this pair of keys is OpenWhisk Release Bot, and the email I used is openwhisk-release-...@apache.org. They are used to indicate that the Travis build is the guy which pushes the release artifacts. 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 - Forwarded by Vincent S Hou/Raleigh/IBM on 03/13/2018 05:17 PM - From: "Vincent S Hou"To: priv...@openwhisk.apache.org Date: 03/08/2018 11:13 AM Subject:Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose? Dear OpenWhisk mentors, So far we have been automating the release process of OpenWhisk, and already created a repository dedicated to it: https://github.com/apache/incubator-openwhisk-release We are now able to release the source code artifacts in manual mode and automated mode, and Travis build is used in the automated mode to sign the artifacts and push them to the SVN. We try to avoid using some private accounts to generate the PGP keys and update the SVN repository. I am wondering what can be the proper credentials I can use to generate the PGP keys and access the apache SVN. Do we have a general account for the build purpose? Thank you. 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
Fw: Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose?
Dear OpenWhiskers, I will bring this question and the current solution to the dev list. Our Travis build of openwhisk-release, it will import the public key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_pub.gpg ) and the private key( https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_sec.gpg.enc ), available in openwhisk-release repo. Private key is encrypted. The public key has already uploaded to the SVN repo as well: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS, so it can be used to verify the signature of each artifact. The name of this pair of keys is OpenWhisk Release Bot, and the email I used is openwhisk-release-...@apache.org. They are used to indicate that the Travis build is the guy which pushes the release artifacts. 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 - Forwarded by Vincent S Hou/Raleigh/IBM on 03/13/2018 05:17 PM - From: "Vincent S Hou"To: priv...@openwhisk.apache.org Date: 03/08/2018 11:13 AM Subject:Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose? Dear OpenWhisk mentors, So far we have been automating the release process of OpenWhisk, and already created a repository dedicated to it: https://github.com/apache/incubator-openwhisk-release We are now able to release the source code artifacts in manual mode and automated mode, and Travis build is used in the automated mode to sign the artifacts and push them to the SVN. We try to avoid using some private accounts to generate the PGP keys and update the SVN repository. I am wondering what can be the proper credentials I can use to generate the PGP keys and access the apache SVN. Do we have a general account for the build purpose? Thank you. 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: any updates to include in OW quarterly board report draft?
Thanks again for taking on this Matt! On 5 March 2018 at 22:02, Carlos Santanawrote: > Thanks Matt for handling this +1 > > - Carlos Santana > @csantanapr > > > On Mar 5, 2018, at 12:20 PM, Matt Rutkowski wrote: > > > > working in earnest to draft our project's quarterly board report on our > > CWIKI: > > https://cwiki.apache.org/confluence/display/OPENWHISK/2018-03+March > > > > Please feel free to send me of notable items/features/contribs. you do > not > > want me to miss (as I will use primarily the "dev" list discussions, as > > well as scan the merged PRs over last 3 months across most repos. > > > > Any help appreciated. > > > > Kind regards, > > Matt > > > > > -- Regards, James Thomas
Signed off the Incubator PMC report draft, with one change
Hi, I have signed off the OpenWhisk report at https://wiki.apache.org/incubator/March2018, with one somewhat significant change: Replace "Increase additional company and individual Contributors to maintain all project repos" by "Increase contributions to maintain all project repos" There are no company contributions of code in Apache projects, except for code donations - from the ASF's point of view it's only individuals who contribute. They might be funded by their employers to do that, and that's fantastic, but the distinction is important in terms of Apache's (fierce) independence from companies and organizations. The ASF's 2018 vision statement [1] helps explain these things. Apart from that the report is great, quite extensive! It would be fine to have just a summary of the technical progress, as the Incubator is mostly interested in community and release topics. But it's great to have those summaries for the OpenWhisk community, so thanks! -Bertrand [1] https://blogs.apache.org/foundation/entry/the-apache-software-foundation-2018
Any Topics for next community Tech Interchange 14.03 @4pm GMT / 11am EST / 8am PST
Besides the normal agenda: - Introduction/New faces on the call? - Asking around for notable changes/updates? - Find and confirm moderator for next meeting Feb 14th Does anyone have any updates they’d like to talk about? Thanks! -d