[slack-digest] [2019-03-19] #general

2019-03-20 Thread OpenWhisk Team Slack
2019-03-19 01:38:17 UTC - Dominic Kim: Can contributors also vote on it? 100 : Rodric Rabbah, Carlos Santana https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552959497316300 2019-03-19 04:24:41 UTC - Shazron Abdullah: Yes, but only committer votes are binding https://openwhisk-team.slac

[slack-digest] [2019-03-19] #apigateway

2019-03-20 Thread OpenWhisk Team Slack
2019-03-19 03:13:30 UTC - mhamann: Hi @Perry Dykes. Any chance you could DM me your API doc? Just choose “export api definition” from the UI https://openwhisk-team.slack.com/archives/C3TP33Y2U/p1552965210009600 2019-03-19 03:14:48 UTC - mhamann: Also, in your Cloud Functions logs, do you see

Re: [Bi-Weekly Tech Interchange] Call for agenda topics

2019-03-20 Thread Dascalita Dragos
Thanks. So far we have: - Vincent - Jenkins CI for OpenWhisk - Priti - Knative build - James - Web Action Http Proxy If you have more topics, it's not too late to send them. Thanks, dragos On Tue, Mar 19, 2019 at 11:06 AM James Thomas wrote: > I'd like to show my new web action http proxy - i

Uploaded Knative Build for Apache OW Runtimes slides

2019-03-20 Thread Matt Rutkowski
Just wanted to let everyone know that I uploaded the latest updated slide deck describing our work to enable our OW runtimes be run using Knative build (build templates) within the subdir. under "devtools" repo. where the experimental code lives... https://github.com/apache/incubator-openwhisk-

OW Tech. Int. Meeting Notes + Video posted as-per-usual

2019-03-20 Thread Matt Rutkowski
Thanks Dragos for hosting! Topics today featured: - New Jenkins staging (Vincent), - Knative runtimes (Priti) and - Web Action Http Proxy (James). Notes (please review/comment): https://cwiki.apache.org/confluence/display/OPENWHISK/2019-03-20+OW+Tech+Interchange+Meeting+Notes TouTube: https:

Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Matt Rutkowski
While filling out the Maturity Model, I noted that several questions were asked around our community's seriousness in addressing user security issues/reporting. However, our website (footer) had a "security" link that simply sent you to a general Apache site which has you contact the "Apache s

Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Rodric Rabbah
Looks good to me - thanks Matt. -r

Re: [VOTE] Release Apache OpenWhisk Client JS (incubating) 3.19.0

2019-03-20 Thread Matt Rutkowski
[X] +1 Release as Apache OpenWhisk 3.19.0-incubating: OpenWhisk Client JS [ ] +0 no opinion [ ] -1 Do not release and the reason Checklist for reference: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts have correct n

Re: [VOTE] release Apache OpenWhisk CLI 0.10.0-incubating

2019-03-20 Thread Matt Rutkowski
[X] +1 Release as Apache OpenWhisk 0.10.0-incubating: openwhisk-cli, openwhisk-client-go, openwhisk-wskdeploy [ ] +0 no opinion [ ] -1 Do not release and the reason Checklist for reference: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] So

Re: [DISCUSS] Release event providers

2019-03-20 Thread Matt Rutkowski
+1 Agree with your approach to use a version "2.0.0" release of all providers. - Matt On 2019/03/16 19:54:09, "David P Grove" wrote: > > > As part of the unified release, we will be doing the first Apache release > of the OpenWhisk event providers (openwhisk-package-alarms, > openwhisk-packag

Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Matt Sicker
I'm not exactly sure on the process, but I think it's important to use a security-specific mailing list for tracking purposes. If the reports don't filter through secur...@apache.org, it makes sense to make a dedicated security@ mailing list for the project. On Wed, 20 Mar 2019 at 11:57, Rodric Ra

Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Rodric Rabbah
We went through a case last year where a company reported a vulnerability to us through security@a.o and we cc'ed them on all the communications. I think that worked well. Are you suggesting we have our own project security mailing list that goes to both our private list and security@a.o? -r On W

Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Matt Rutkowski
As indicated, they are directed to use our private (PMC) email list as they should do by Apache process... having the new page makes this very clear... ASF encourages the use of a PMCs private list, but also provides a security email list for full projects... as we are an Incubator we do not g

Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Matt Sicker
On Wed, 20 Mar 2019 at 12:52, Rodric Rabbah wrote: > > We went through a case last year where a company reported a vulnerability > to us through security@a.o and we cc'ed them on all the communications. I > think that worked well. Are you suggesting we have our own project security > mailing list

Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting

2019-03-20 Thread Carlos Santana
For security reports, ASF already have a process let's not improvise Reported should send email to secur...@apache.org The process explains how to handle artifacts to reproduce the vulnerability Security will inform the PMC private list and forward the email --cs On Wed, Mar 20, 2019 at 3:09 P