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

[Rodric Rabbah]

I'm +1 for all the three.
I used the rc verification script to verify all three.
I found some minor nits with the wskdeploy artifact for which I opened
https://github.com/apache/incubator-openwhisk-wskdeploy/issues/1044.

> rcverify.sh openwhisk-wskdeploy 'OpenWhisk Wskdeploy' 0.10.0
computing sha512 and validating... passed
verifying asc... passed
verifying disclaimer... failed (cat
'/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.XIYIn1nQ/incubator-openwhisk-wskdeploy-0.10.0-incubating/DISCLAIMER.txt')
verifing notice... passed
verifying license... passed
verifying sources have proper headers... passed
scanning for binaries... failed
(/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.XIYIn1nQ/incubator-openwhisk-wskdeploy-0.10.0-incubating/cmd/version.go
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.XIYIn1nQ/incubator-openwhisk-wskdeploy-0.10.0-incubating/tools/travis/docker/Dockerfile
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.XIYIn1nQ/incubator-openwhisk-wskdeploy-0.10.0-incubating/ansible/environments/local/group_vars/all)
scanning for archives... passed
scanning for packages... passed

> rcverify.sh openwhisk-client-go 'OpenWhisk Client Go' 0.10.0
computing sha512 and validating... passed
verifying asc... passed
verifying disclaimer... passed
verifing notice... passed
verifying license... failed (diff
'/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.BpNJ5TOg/incubator-openwhisk-client-go-0.10.0-incubating/LICENSE.txt'
'/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.BpNJ5TOg/LICENSE-2.0')
verifying sources have proper headers... passed
scanning for binaries... passed
scanning for archives... passed
scanning for packages... passed

the license failure is a false positive, attributed to a leading empty line
missing in the rc.

> rcverify.sh openwhisk-cli 'OpenWhisk Command Line Interface(CLI)' 0.10.0
computing sha512 and validating... passed
verifying asc... passed
verifying disclaimer... passed
verifing notice... failed (cat
'/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.ve1ltMpW/incubator-openwhisk-cli-0.10.0-incubating/NOTICE.txt')
verifying license... passed
verifying sources have proper headers... passed
scanning for binaries... passed
scanning for archives... passed
scanning for packages... passed

the notice file used a different description than the disclaimer.

-r




On Sat, Mar 16, 2019 at 2:57 PM David P Grove  wrote:

>
>
> This is a call to vote on releasing version 0.10.0-incubating of the Apache
> OpenWhisk CLI.
>
> The Apache OpenWhisk CLI provides the command line tooling for interacting
> with Apache OpenWhisk.
>
> This release comprises of source code distribution only. There are three
> modules (git repos) included in this CLI release. All artifacts were built
> by PR#249 in the openwhisk-release repo from the following Git commit IDs:
> * openwhisk-cli: eaf64ae
> * openwhisk-client-go: 4286a82
> * openwhisk-wskdeploy: 7d79fd7
>
> openwhisk-cli (55BEEB6D CDF621AB 7AA6098A 5DBCA55E 6D7E3B0C A3DAA7DF
> B44103F8 CE30ACC9 13411ECC BFF18519 3E142EC3 D27AA081 E1D47F63 14E9E708
> 90646EC7 C13756D6)
> src.tar.gz:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz
> sha512 checksum:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.sha512
> signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.asc
>
> openwhisk-client-go (068DBC87 533905DB D0089CAE 74FD0B91 109992D8 D843CAA4
> 01EA87B6 9CDC9550 6D555655 4679FF36 7A52414E DCC59126 E558085D 3E960DEB
> 18804581 6B2FA019)
> src.tar.gz:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz
> sha512 checksum:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.sha512
> signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.asc
>
> openwhisk-wskdeploy (412B1E09 129F2884 A1D4E9DE 0A979B47 55A54FC5 61E1D328
> 325E8A12 AE504779 A2350B9F 4185582F 7782EEA5 AE9018CD 52E4AA4C 484B5211
> AA449B4B 9F9E2432)
> src.tar.gz:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz
> sha512 checksum:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.sha512
> signature:
>
> 

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

[Rodric Rabbah]

Another minor point, the NOTICE refers to "Apache OpenWhisk" not the
'OpenWhisk JavaScript Client Library'.

-r

On Tue, Mar 19, 2019 at 4:50 PM Rodric Rabbah  wrote:

> +1
>
> I wrote a script to verify this release. The gist is here
> https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041
> You'll see sample output at the bottom. It detected the same issue raised
> by Matt wrt the license, otherwise everything checked out.
>
> computing sha512 and validating... valid
> verifying asc... valid
> verifying disclaimer... valid
> verifing notice... valid
> verifying license... not valid (diff 
> '/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.6t9xcMV8/incubator-openwhisk-client-js-3.19.0-incubating/LICENSE.txt'
>  '/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.6t9xcMV8/LICENSE-2.0')
> verifying sources have proper headers... valid
> scanning for binaries... valid
>
>
> -r
>
>
> On Tue, Mar 19, 2019 at 2:49 PM Matt Sicker  wrote:
>
>> +1
>>
>> Notes:
>>
>> * LICENSE has incorrect boilerplate example at bottom. It seems to
>> have been replaced with a concrete example of IBM. This should
>> probably be reverted to the original text of the ASLv2.
>> * NPM says there are a few vulnerable dependencies. Neat feature,
>> though unclear if they're real vulnerabilities (I'm not a JS expert
>> like I am with Java).
>> * Tests passing.
>> * Standard checklist all passes.
>>
>> On Mon, 18 Mar 2019 at 22:29, Dominic Kim  wrote:
>> >
>> > +1
>> >
>> > I could verify the artifacts with the key.
>> >
>> > [x] Download links are valid.
>> > [x] 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 repository.
>> > [x] All files have license headers if necessary.
>> > [x] No compiled archives bundled in source archive.
>> >
>> > 2019년 3월 19일 (화) 오전 11:36, 甯尤刚 님이 작성:
>> >
>> > > +1
>> > >
>> > > I was able to verify the release artifacts for client-js 3.19 rc1
>> > >
>> > > [x] Download links are valid.
>> > > [x] 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
>> repository.
>> > > [x] All files have license headers if necessary.
>> > > [x] No compiled archives bundled in source archive.
>> > >
>> > > -Original Message-
>> > > From: "Carlos Santana"
>> > > To: ;
>> > > Cc:
>> > > Sent: 2019-03-19 (星期二) 10:18:28 (GMT+08:00)
>> > > Subject: Re: [VOTE] Release Apache OpenWhisk Client JS (incubating)
>> 3.19.0
>> > >
>> > > +1
>> > >
>> > > I was able to verify the release artifacts for client-js 3.19 rc1
>> > >
>> > > [x] Download links are valid.
>> > > [x] 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
>> repository.
>> > > [x] All files have license headers if necessary.
>> > > [x] No compiled archives bundled in source archive.
>> > >
>> > >
>> > > On Mon, Mar 18, 2019 at 5:50 PM Dave Grove  wrote:
>> > >
>> > > > I vote +1 Release as Apache OpenWhisk 3.19.0-incubating: OpenWhisk
>> Client
>> > > > JS
>> > > >
>> > > > I verified:
>> > > > [ X ] Download links are valid.
>> > > > [ X ] 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.
>> > > >
>> > > > --dave
>> > > >
>> > > > On 2019/03/18 18:14:39, James Thomas  wrote:
>> > > > > This is to call for a vote for the release of Apache OpenWhisk
>> Client
>> > > JS
>> > > > > (incubating) 3.19.0
>> > > > >
>> > > > > List of JIRA ticket(s) resolved for this release can be found at
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/INCUBATOR-232.
>> > > > >
>> > > > > This release comprises of source code distribution only. There is
>> only
>> > > > one
>> > > > > module within this release number 3.19.0. The artifact were built
>> from
>> > > > the
>> > > > > following Git commit IDs:
>> > > > >
>> > > > >-
>> > > > >
>> > > > >openwhisk-client-js: 726b982,
>> > > > >
>> > > > > The source code artifact of openwhisk client js can be found at:
>> > > > >
>> > > >
>> > >
>> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-3.19.0-incubating-rc1/openwhisk-client-js-3.19.0-incubating-sources.tar.gz
>> > > > >
>> > > > > The SHA-512 checksum for the artifact of openwhisk client js is
>> > > > > openwhisk-client-js-3.19.0-incubating-sources.tar.gz: 8D8FE6C5
>> 48F5FE72
>> > > > 

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

[Rodric Rabbah]

+1

I wrote a script to verify this release. The gist is here
https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041
You'll see sample output at the bottom. It detected the same issue raised
by Matt wrt the license, otherwise everything checked out.

computing sha512 and validating... valid
verifying asc... valid
verifying disclaimer... valid
verifing notice... valid
verifying license... not valid (diff
'/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.6t9xcMV8/incubator-openwhisk-client-js-3.19.0-incubating/LICENSE.txt'
'/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.6t9xcMV8/LICENSE-2.0')
verifying sources have proper headers... valid
scanning for binaries... valid


-r


On Tue, Mar 19, 2019 at 2:49 PM Matt Sicker  wrote:

> +1
>
> Notes:
>
> * LICENSE has incorrect boilerplate example at bottom. It seems to
> have been replaced with a concrete example of IBM. This should
> probably be reverted to the original text of the ASLv2.
> * NPM says there are a few vulnerable dependencies. Neat feature,
> though unclear if they're real vulnerabilities (I'm not a JS expert
> like I am with Java).
> * Tests passing.
> * Standard checklist all passes.
>
> On Mon, 18 Mar 2019 at 22:29, Dominic Kim  wrote:
> >
> > +1
> >
> > I could verify the artifacts with the key.
> >
> > [x] Download links are valid.
> > [x] 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 repository.
> > [x] All files have license headers if necessary.
> > [x] No compiled archives bundled in source archive.
> >
> > 2019년 3월 19일 (화) 오전 11:36, 甯尤刚 님이 작성:
> >
> > > +1
> > >
> > > I was able to verify the release artifacts for client-js 3.19 rc1
> > >
> > > [x] Download links are valid.
> > > [x] 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 repository.
> > > [x] All files have license headers if necessary.
> > > [x] No compiled archives bundled in source archive.
> > >
> > > -Original Message-
> > > From: "Carlos Santana"
> > > To: ;
> > > Cc:
> > > Sent: 2019-03-19 (星期二) 10:18:28 (GMT+08:00)
> > > Subject: Re: [VOTE] Release Apache OpenWhisk Client JS (incubating)
> 3.19.0
> > >
> > > +1
> > >
> > > I was able to verify the release artifacts for client-js 3.19 rc1
> > >
> > > [x] Download links are valid.
> > > [x] 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 repository.
> > > [x] All files have license headers if necessary.
> > > [x] No compiled archives bundled in source archive.
> > >
> > >
> > > On Mon, Mar 18, 2019 at 5:50 PM Dave Grove  wrote:
> > >
> > > > I vote +1 Release as Apache OpenWhisk 3.19.0-incubating: OpenWhisk
> Client
> > > > JS
> > > >
> > > > I verified:
> > > > [ X ] Download links are valid.
> > > > [ X ] 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.
> > > >
> > > > --dave
> > > >
> > > > On 2019/03/18 18:14:39, James Thomas  wrote:
> > > > > This is to call for a vote for the release of Apache OpenWhisk
> Client
> > > JS
> > > > > (incubating) 3.19.0
> > > > >
> > > > > List of JIRA ticket(s) resolved for this release can be found at
> > > > >
> > > > > https://issues.apache.org/jira/browse/INCUBATOR-232.
> > > > >
> > > > > This release comprises of source code distribution only. There is
> only
> > > > one
> > > > > module within this release number 3.19.0. The artifact were built
> from
> > > > the
> > > > > following Git commit IDs:
> > > > >
> > > > >-
> > > > >
> > > > >openwhisk-client-js: 726b982,
> > > > >
> > > > > The source code artifact of openwhisk client js can be found at:
> > > > >
> > > >
> > >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-3.19.0-incubating-rc1/openwhisk-client-js-3.19.0-incubating-sources.tar.gz
> > > > >
> > > > > The SHA-512 checksum for the artifact of openwhisk client js is
> > > > > openwhisk-client-js-3.19.0-incubating-sources.tar.gz: 8D8FE6C5
> 48F5FE72
> > > > > F5C5CC2E 1539416F 84B18BB7 D6A0075B 50CAFC22 55BFA27E C8E60B9D
> 6660E203
> > > > > 72CEB667 EAE91474 DAB16D8B 764B5141 8B7595DE 78CBA217
> > > > >
> > > > > which can can be found via:
> > > > >
> > > >
> > >
> 

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

[Matt Sicker]

+1

Notes:

* LICENSE has incorrect boilerplate example at bottom. It seems to
have been replaced with a concrete example of IBM. This should
probably be reverted to the original text of the ASLv2.
* NPM says there are a few vulnerable dependencies. Neat feature,
though unclear if they're real vulnerabilities (I'm not a JS expert
like I am with Java).
* Tests passing.
* Standard checklist all passes.

On Mon, 18 Mar 2019 at 22:29, Dominic Kim  wrote:
>
> +1
>
> I could verify the artifacts with the key.
>
> [x] Download links are valid.
> [x] 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 repository.
> [x] All files have license headers if necessary.
> [x] No compiled archives bundled in source archive.
>
> 2019년 3월 19일 (화) 오전 11:36, 甯尤刚 님이 작성:
>
> > +1
> >
> > I was able to verify the release artifacts for client-js 3.19 rc1
> >
> > [x] Download links are valid.
> > [x] 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 repository.
> > [x] All files have license headers if necessary.
> > [x] No compiled archives bundled in source archive.
> >
> > -Original Message-
> > From: "Carlos Santana"
> > To: ;
> > Cc:
> > Sent: 2019-03-19 (星期二) 10:18:28 (GMT+08:00)
> > Subject: Re: [VOTE] Release Apache OpenWhisk Client JS (incubating) 3.19.0
> >
> > +1
> >
> > I was able to verify the release artifacts for client-js 3.19 rc1
> >
> > [x] Download links are valid.
> > [x] 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 repository.
> > [x] All files have license headers if necessary.
> > [x] No compiled archives bundled in source archive.
> >
> >
> > On Mon, Mar 18, 2019 at 5:50 PM Dave Grove  wrote:
> >
> > > I vote +1 Release as Apache OpenWhisk 3.19.0-incubating: OpenWhisk Client
> > > JS
> > >
> > > I verified:
> > > [ X ] Download links are valid.
> > > [ X ] 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.
> > >
> > > --dave
> > >
> > > On 2019/03/18 18:14:39, James Thomas  wrote:
> > > > This is to call for a vote for the release of Apache OpenWhisk Client
> > JS
> > > > (incubating) 3.19.0
> > > >
> > > > List of JIRA ticket(s) resolved for this release can be found at
> > > >
> > > > https://issues.apache.org/jira/browse/INCUBATOR-232.
> > > >
> > > > This release comprises of source code distribution only. There is only
> > > one
> > > > module within this release number 3.19.0. The artifact were built from
> > > the
> > > > following Git commit IDs:
> > > >
> > > >-
> > > >
> > > >openwhisk-client-js: 726b982,
> > > >
> > > > The source code artifact of openwhisk client js can be found at:
> > > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-3.19.0-incubating-rc1/openwhisk-client-js-3.19.0-incubating-sources.tar.gz
> > > >
> > > > The SHA-512 checksum for the artifact of openwhisk client js is
> > > > openwhisk-client-js-3.19.0-incubating-sources.tar.gz: 8D8FE6C5 48F5FE72
> > > > F5C5CC2E 1539416F 84B18BB7 D6A0075B 50CAFC22 55BFA27E C8E60B9D 6660E203
> > > > 72CEB667 EAE91474 DAB16D8B 764B5141 8B7595DE 78CBA217
> > > >
> > > > which can can be found via:
> > > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-3.19.0-incubating-rc1/openwhisk-client-js-3.19.0-incubating-sources.tar.gz.sha512
> > > >
> > > > The signature of the artifact of openwhisk client js can be found via:
> > > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-3.19.0-incubating-rc1/openwhisk-client-js-3.19.0-incubating-sources.tar.gz.asc
> > > >
> > > > KEYS file is available here:
> > > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
> > > >
> > > > Please vote on releasing this package as Apache OpenWhisk
> > > > 3.19.0-incubating: OpenWhisk Client JS
> > > >
> > > > The vote will be open for at least 72 hours.
> > > >
> > > > [ ] +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:
> > > >
> > > > [ ] Download links are valid.
> > > >
> > > > [ ] Checksums and PGP signatures are valid.
> > > >
> > > > [ ] DISCLAIMER is included.
> > > >
> > > > [ ] 

Re: [DISCUSS] graduation from the incubator

[Matt Sicker]

Oh, and if you all figure out a way to easily digest the notification
info for dev@, that would be really cool, though I wouldn't consider
it necessary for graduation. Other ASF projects I've either worked
with or observed will all have their own spammy notification email for
archiving all the commits, issues, and comments. Finding a way to make
that more usable for contributors would be awesome, but I believe that
is an orthogonal concern to synchronous chat in general. Then again,
if you can digest a digest like that, maybe it will help more than I'd
expect?

On Tue, 19 Mar 2019 at 13:27, Matt Sicker  wrote:
>
> So I have some agreements with Bertrand here. I obviously don't work
> on this project full time (my full time work is involved in developing
> Jenkins), and the Slack digests, while useful, are nearly impossible
> to read whenever a large amount of discussion happens during a day,
> particularly because synchronous communication is mixed in with the
> typical development talk that would benefit most from being
> asynchronous. Another limitation I find there is that I can't exactly
> reply to digests, so having a longer term conversation that way
> doesn't exactly work.
>
> Suppose, for example, I'm a contributor from a timezone not typically
> aligned with the times most of the full time engineers work on this
> project. Then having a back and forth conversation on Slack can easily
> get lost in the history, particularly because I haven't exactly seen
> judicious use of threads, either (which are themselves limited to a
> single level of threading unlike email). The large amounts of
> unnecessary messages that come in with a digest make it much harder to
> follow the technical discussions compared to, say, the threads I've
> seen on dev@ and GitHub issues. This also makes it harder for anyone
> who didn't see the initial Slack thread to contribute to the
> discussion.
>
> In all, I'm very impressed by the maturity of this project so far.
> It's certainly a production-ready project from what I can tell, but
> I'm still concerned about the chat. This would still be a concern even
> if the ASF hosted Slack itself (which isn't currently possible
> anyways) or some other chat service. Basically, in a distributed OSS
> project like with ASF projects, I'd expect to be able to contribute
> outside work hours (e.g., nights and weekends) as a hobby, and having
> communications be focused in media such as mailing lists, forums, and
> issue trackers makes it much easier to keep up to date with things,
> filter out topics I don't care about, and maintain conversations over
> a period longer than a few hours or days. For a work comparison, do
> you bother reading all your missed Slack messages when you come back
> from a week or two of vacation? If so, you're much faster than I am at
> communication, and I'm already reading way too many mailing lists as
> it is. :D
>
> My suggestion as to how to improve this wouldn't be the daily digest.
> My suggestion would be to ensure any development conversations that
> take place on Slack should be recreated on the mailing lists. This can
> be based on or start from the digest or chat log, but coming up with a
> summary of what was discussed along with providing an easier to use
> anchor point for further discussion would go a long way toward helping
> address this disconnect. As we typically say over in Commons or the
> other more volunteer-driven projects at ASF: if it didn't happen on
> the mailing list, it didn't happen!
>
> On Tue, 19 Mar 2019 at 12:25, Michael Marth  wrote:
> >
> > Matt, all,
> >
> > Strongly agree.
> > My understanding is that moving from ASF incubator to TLP is not (at all) a 
> > statement about the technology but a statement about the community, its 
> > diversity (in terms of stakeholders) and ability to carry forward the 
> > project. I agree with everyone on this thread that OpenWhisk has proven to 
> > have achieved that mile stone
> >
> > (but it does not hurt the cause to say that the technology runs in 
> > production and is solid)
> >
> > Cheers
> > Michael
> >
> >
> >
> > On 19.03.19, 16:56, "Matt Rutkowski"  wrote:
> >
> > Thanks Dave for raising graduation as a topic.
> >
> > To be clear... +1 (with stars) from me on moving to graduate...
> >
> > It is my belief that this project has reached a maturity level, with 
> > credits to its devoted community, over the last 2 plus years to graduate.  
> > It has been no small task to bring under Apache compliance the numerous 
> > repos. this project manages and to deal with the ever-changing landscape of 
> > Serverless and remain relevant as new technologies and projects continue to 
> > enter this space.
> >
> > IMO, no other Serverless project offers a complete open source FaaS 
> > platform solution that supports such a wide array of deployment choices, 
> > runtimes, tooling (and I could go on and on) while striving to enable 
> > choice for via documented 

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

[David P Grove]

Matt Sicker  wrote on 03/19/2019 02:09:36 PM:
>
> * I haven't really combed through literally every file to ensure
> license headers and notice are correct, though I'm assuming this has
> been kept up to date so far. If that's not the case, then I'll have to
> dig through these releases in more depth next time.
>

Thanks Matt!

We automate this by running a scancode program (
https://github.com/apache/incubator-openwhisk-utilities/tree/master/scancode
) as part of every TravisCI build (both PRs and on master).  It can also be
run manually to verify a releases.  This doesn't help if scancode is buggy
or the configuration is incomplete, but it does provide some level of
automatic enforcement.

--dave

Re: [DISCUSS] graduation from the incubator

[Matt Sicker]

So I have some agreements with Bertrand here. I obviously don't work
on this project full time (my full time work is involved in developing
Jenkins), and the Slack digests, while useful, are nearly impossible
to read whenever a large amount of discussion happens during a day,
particularly because synchronous communication is mixed in with the
typical development talk that would benefit most from being
asynchronous. Another limitation I find there is that I can't exactly
reply to digests, so having a longer term conversation that way
doesn't exactly work.

Suppose, for example, I'm a contributor from a timezone not typically
aligned with the times most of the full time engineers work on this
project. Then having a back and forth conversation on Slack can easily
get lost in the history, particularly because I haven't exactly seen
judicious use of threads, either (which are themselves limited to a
single level of threading unlike email). The large amounts of
unnecessary messages that come in with a digest make it much harder to
follow the technical discussions compared to, say, the threads I've
seen on dev@ and GitHub issues. This also makes it harder for anyone
who didn't see the initial Slack thread to contribute to the
discussion.

In all, I'm very impressed by the maturity of this project so far.
It's certainly a production-ready project from what I can tell, but
I'm still concerned about the chat. This would still be a concern even
if the ASF hosted Slack itself (which isn't currently possible
anyways) or some other chat service. Basically, in a distributed OSS
project like with ASF projects, I'd expect to be able to contribute
outside work hours (e.g., nights and weekends) as a hobby, and having
communications be focused in media such as mailing lists, forums, and
issue trackers makes it much easier to keep up to date with things,
filter out topics I don't care about, and maintain conversations over
a period longer than a few hours or days. For a work comparison, do
you bother reading all your missed Slack messages when you come back
from a week or two of vacation? If so, you're much faster than I am at
communication, and I'm already reading way too many mailing lists as
it is. :D

My suggestion as to how to improve this wouldn't be the daily digest.
My suggestion would be to ensure any development conversations that
take place on Slack should be recreated on the mailing lists. This can
be based on or start from the digest or chat log, but coming up with a
summary of what was discussed along with providing an easier to use
anchor point for further discussion would go a long way toward helping
address this disconnect. As we typically say over in Commons or the
other more volunteer-driven projects at ASF: if it didn't happen on
the mailing list, it didn't happen!

On Tue, 19 Mar 2019 at 12:25, Michael Marth  wrote:
>
> Matt, all,
>
> Strongly agree.
> My understanding is that moving from ASF incubator to TLP is not (at all) a 
> statement about the technology but a statement about the community, its 
> diversity (in terms of stakeholders) and ability to carry forward the 
> project. I agree with everyone on this thread that OpenWhisk has proven to 
> have achieved that mile stone
>
> (but it does not hurt the cause to say that the technology runs in production 
> and is solid)
>
> Cheers
> Michael
>
>
>
> On 19.03.19, 16:56, "Matt Rutkowski"  wrote:
>
> Thanks Dave for raising graduation as a topic.
>
> To be clear... +1 (with stars) from me on moving to graduate...
>
> It is my belief that this project has reached a maturity level, with 
> credits to its devoted community, over the last 2 plus years to graduate.  It 
> has been no small task to bring under Apache compliance the numerous repos. 
> this project manages and to deal with the ever-changing landscape of 
> Serverless and remain relevant as new technologies and projects continue to 
> enter this space.
>
> IMO, no other Serverless project offers a complete open source FaaS 
> platform solution that supports such a wide array of deployment choices, 
> runtimes, tooling (and I could go on and on) while striving to enable choice 
> for via documented plug-in points for common platform integrations such as 
> logging, metrics and test tooling, but also, for very complex topics such as 
> load balancing, scheduling and container pooling.
>
> This project is has matured to a point, where it should be noted, that we 
> are aware it is used in several public production offerings as a Serverless 
> platform directly or as the backing for FaaS integrations (such as for API 
> management or web hosting).
>
> If you cannot tell, I am all for moving towards graduation and (prompted 
> seeing this thread appear yesterday) have cleared my day to complete filling 
> out the maturity model matrix on our CWIKI (see 
> https://cwiki.apache.org/confluence/display/OPENWHISK/Project+Maturity+Model) 
> to the best of my abilities and 

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

[Matt Sicker]

+1

[x] Download links are valid.
[x] 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 repository.
[x] All files have license headers if necessary.
[x] No compiled archives bundled in source archive.

Some notes from testing releases:

* Disclaimer file would be nice to have reflowed as a normal text file
with ~80 character width limits, or at least written like a typical
text source file where each sentence is on its own line. Sort of a
personal preference, though when you compare the disclaimer with the
other usual files (LICENSE and NOTICE), it's not consistent.
* client-go doesn't seem to have any tests? I ran `make test` and got
an error of no tests being available, though `make integration_test`
passed ok.
* Tested with Gradle 5.2.1 and Go 1.12.1. See next point for why.
* I know this debate has been had ad nauseum, but including gradle
wrapper scripts without the bootstrap binary (which isn't allowed, I
know) makes it kind of pointless to include. This is more of an issue
for people like myself who don't use Gradle that often but rely on
scripts like gdub  to help manage
Gradle usage. I've seen some efforts on the Maven wrapper side of
things to try and make a self-booting Java source file or similar to
download the wrapper binary at runtime, and such a thing might be
doable as a Groovy script or a Java "script" (Java 11 style). This is
a usability concern to me because typical users who install Gradle on
their machine will only have the latest version of Gradle available,
so if your build isn't compatible with, say, 4.10.x or 5.2.x (e.g.,
some people still use Gradle 2.x, and 4.x is the first release of
Gradle that removed deprecated APIs from 2.x), then I have the fun job
of figuring out which version of Gradle I need. :(
  - For comparison, I didn't need to install some specific version of
Make or Maven to test anything else.
  - I also just filed a ticket with gdub
 to help support this use
case. We'll see if this becomes a non-problem. :)
* I haven't really combed through literally every file to ensure
license headers and notice are correct, though I'm assuming this has
been kept up to date so far. If that's not the case, then I'll have to
dig through these releases in more depth next time.


--
Matt Sicker 

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

[James Thomas]

I'd like to show my new web action http proxy - it'll only take 5 - 10 mins.

On Tue, 19 Mar 2019 at 17:26, Priti Desai  wrote:

> Hi Dragos,
>
> Please reserve 10 to 15 minutes for Knative buiid.
>
> Cheers
> Priti
>
>
>
> From:   Dascalita Dragos 
> To: dev@openwhisk.apache.org
> Date:   03/19/2019 09:08 AM
> Subject:[Bi-Weekly Tech Interchange] Call for agenda topics
>
>
>
> Hi,
> I'm starting this thread to start capturing topics to discuss for our call
> tomorrow.
> Please reply to this email to reserve your spot !
>
> Bi-weekly Tech Interchange call details:
> - Zoom:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=6V3FXFwHvE0SFE3N4Rk7-rlMhS2xkaqR1AlgZ0xtvKY=27x2jBqNcasvt0sohR9IvAJ_JZoi4YvKvgdtpOjxtRE=AXU7OQ9kktdXLKRBmyqhY63F-s7B-U3h2nElV5sk_WI=
>
> - Wednesday March 20th
> 11AM EST(Eastern US)
> 5PM CET (Central Europe),
> 4PM UTC, 12AM CST (Beijing)
>
> Thanks,
> dragos
>
>
>
>
>

-- 
Regards,
James Thomas

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

[Vincent S Hou]

I would like to present the Jenkins CI for OpenWhisk.

 
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

-Dascalita Dragos  wrote: -
To: dev@openwhisk.apache.org
From: Dascalita Dragos 
Date: 03/19/2019 12:08PM
Subject: [Bi-Weekly Tech Interchange] Call for agenda topics

Hi,
I'm starting this thread to start capturing topics to discuss for our call
tomorrow.
Please reply to this email to reserve your spot !

Bi-weekly Tech Interchange call details:
- Zoom: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=4k5b6m3eq3AWF5UnQ_O8wXYfS0gQ-Q4bL0-nuqxWNis=tbRToEdvZdx_tpFXKR-W1dxIg94EOIN4JxWze8kVvKs=
- Wednesday March 20th
11AM EST(Eastern US)
5PM CET (Central Europe),
4PM UTC, 12AM CST (Beijing)

Thanks,
dragos

[Bi-Weekly Tech Interchange] Call for agenda topics

[Dascalita Dragos]

Hi,
I'm starting this thread to start capturing topics to discuss for our call
tomorrow.
Please reply to this email to reserve your spot !

Bi-weekly Tech Interchange call details:
- Zoom: https://zoom.us/my/asfopenwhisk
- Wednesday March 20th
11AM EST(Eastern US)
5PM CET (Central Europe),
4PM UTC, 12AM CST (Beijing)

Thanks,
dragos

Re: [DISCUSS] graduation from the incubator

[Matt Rutkowski]

Thanks Dave for raising graduation as a topic.  

To be clear... +1 (with stars) from me on moving to graduate...

It is my belief that this project has reached a maturity level, with credits to 
its devoted community, over the last 2 plus years to graduate.  It has been no 
small task to bring under Apache compliance the numerous repos. this project 
manages and to deal with the ever-changing landscape of Serverless and remain 
relevant as new technologies and projects continue to enter this space. 

IMO, no other Serverless project offers a complete open source FaaS platform 
solution that supports such a wide array of deployment choices, runtimes, 
tooling (and I could go on and on) while striving to enable choice for via 
documented plug-in points for common platform integrations such as logging, 
metrics and test tooling, but also, for very complex topics such as load 
balancing, scheduling and container pooling.

This project is has matured to a point, where it should be noted, that we are 
aware it is used in several public production offerings as a Serverless 
platform directly or as the backing for FaaS integrations (such as for API 
management or web hosting). 

If you cannot tell, I am all for moving towards graduation and (prompted seeing 
this thread appear yesterday) have cleared my day to complete filling out the 
maturity model matrix on our CWIKI (see 
https://cwiki.apache.org/confluence/display/OPENWHISK/Project+Maturity+Model) 
to the best of my abilities and will be asking for comment/review/edits on a 
separate thread once I complete my draft pass.

In truth, over the course of the last 2 years, I have have truly witnessed the 
community itself become a welcoming family that cares first and foremost about 
the code and improving and enabling it for its user base while establishing 
friendships that transcend other affiliations.

Cheers,
Matt


On 2019/03/15 22:06:38, "David P Grove"  wrote: 
> 
> 
> 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://lists.apache.org/thread.html/b2217c61caad5c7a0369699d06d44e5cf688d3cba982e354a45b8c78@%3Cdev.openwhisk.apache.org%3E
> [2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103091999
> 

Re: [DISCUSS] graduation from the incubator

[Rob Allen]

> On 19 Mar 2019, at 15:21, David P Grove  wrote:
> 
> Bertrand Delacretaz  wrote on 03/19/2019 11:01:30
> AM:
> 
>> 
>> Send a summary here, as a single message, with links, of which tickets
>> and pull requests are being actively worked on, aggregating all
>> OpenWhisk repositories. Based on activity stats (assuming the GitHub
>> API provides them) as well as optional labels that people can set on
>> tickets and PRs to surface them in that report.
>> 
>> I think that would be a great and quick way of answering "what's going
>> on these days" as well as help steer conversations towards these
>> places.
>> 
> 
> Does pony mail support digest subscriptions?  If so, the most robust way to
> accomplish this would be to subscribe @dev to a weekly digest of @issues.


The problem with @issues is that it's every comment. Ideally, @dev just needs 
the newly opened PRs. 


Regards,

Rob

Re: [DISCUSS] graduation from the incubator

[David P Grove]

Bertrand Delacretaz  wrote on 03/19/2019 11:01:30
AM:

> From: Bertrand Delacretaz 
> To: OpenWhisk Dev 
> Date: 03/19/2019 11:04 AM
> Subject: Re: [DISCUSS] graduation from the incubator
>
> Hi,
>
> On Tue, Mar 19, 2019 at 3:57 PM Rodric Rabbah  wrote:
> > On Tue, Mar 19, 2019 at 10:41 AM Bertrand Delacretaz
> 
> > wrote:
> > > Maybe running a query on all repositories for items with recent
> > > activity or with a specific label and sending the results here would
> > > help expose that?
> > >
> > Do you mean as a one off?...
>
> No, I mean regularly, weekly maybe?
>
> Send a summary here, as a single message, with links, of which tickets
> and pull requests are being actively worked on, aggregating all
> OpenWhisk repositories. Based on activity stats (assuming the GitHub
> API provides them) as well as optional labels that people can set on
> tickets and PRs to surface them in that report.
>
> I think that would be a great and quick way of answering "what's going
> on these days" as well as help steer conversations towards these
> places.
>

Does pony mail support digest subscriptions?  If so, the most robust way to
accomplish this would be to subscribe @dev to a weekly digest of @issues.

Seems like it would be common ask for apache projects given the culture of
wanting everything on the dev list...

--dave

Re: [DISCUSS] graduation from the incubator

[Rodric Rabbah]

On Tue, Mar 19, 2019 at 11:01 AM Bertrand Delacretaz 
wrote:

> Send a summary here, as a single message, with links, of which tickets
> and pull requests are being actively worked on, aggregating all
> OpenWhisk repositories. Based on activity stats (assuming the GitHub
> API provides them) as well as optional labels that people can set on
> tickets and PRs to surface them in that report.
>

Do you know of other Apache projects that might already be doing this with
Github that we can borrow from?

-r

Re: [DISCUSS] graduation from the incubator

[Rob Allen]

> On 19 Mar 2019, at 14:50, David P Grove  wrote:
> 
> Bertrand Delacretaz  wrote on 03/19/2019 10:40:51
> AM:
> 
>> From: Bertrand Delacretaz 
>> 
>> On Tue, Mar 19, 2019 at 3:34 PM Rob Allen  wrote:
>>> ...The activity on the GitHub PRs and issues is, I suspect,
>> overlooked as one of the key places
>>> where technical discussions are happening...
>> 
>> Yes, probably - exposing that here would be fantastic.
>> 
> 
> One can subscribe/search iss...@openwhisk.apache.org that's where all of
> the github emails go.  Simply document that?
> 
> Arguably in an ideal world issue/PR creation would trigger an email to dev
> and all the rest of the emails could stay on issues, but I suspect that
> isn't a supported out-of-the-box configuration

A weekly or daily email with a set of links to all the newly opened PR this 
week/day would be nice. As you say, I'm pretty sure this isn't available out of 
the box.

Regards,

Rob

Re: [DISCUSS] graduation from the incubator

[Rodric Rabbah]

On Tue, Mar 19, 2019 at 10:41 AM Bertrand Delacretaz 
wrote:

> Maybe running a query on all repositories for items with recent
> activity or with a specific label and sending the results here would
> help expose that?
>

Do you mean as a one off?

The stats per repository are available on github as project "insights"
For example, in the last month, from
https://github.com/apache/incubator-openwhisk/pulse/monthly

   Excluding merges, *13 authors* have pushed *31 commits* to master and *31
commits* to all branches. On master, *78 files* have changed and there have
been *2,762* *additions* and *434* *deletions*
.


There were 31 merged pull requests, 10 new pull requests, 15 closed issues
and 19 new issues.

Additionally -- All our issues and prs activity is sent to our issues@
mailing list. You can search for comments, new issues, new pull requests,
comments on both of these etc. there as well. That should span all our
repositories.

-r

Re: [DISCUSS] graduation from the incubator

[David P Grove]

Bertrand Delacretaz  wrote on 03/19/2019 10:40:51
AM:

> From: Bertrand Delacretaz 
> To: OpenWhisk Dev 
> Date: 03/19/2019 10:41 AM
> Subject: Re: [DISCUSS] graduation from the incubator
>
> On Tue, Mar 19, 2019 at 3:34 PM Rob Allen  wrote:
> > ...The activity on the GitHub PRs and issues is, I suspect,
> overlooked as one of the key places
> > where technical discussions are happening...
>
> Yes, probably - exposing that here would be fantastic.
>

One can subscribe/search iss...@openwhisk.apache.org that's where all of
the github emails go.  Simply document that?

Arguably in an ideal world issue/PR creation would trigger an email to dev
and all the rest of the emails could stay on issues, but I suspect that
isn't a supported out-of-the-box configuration

--dave

Re: [DISCUSS] graduation from the incubator

[Rodric Rabbah]

Thank you Bertrand for the input.

With respect to Slack and how this project uses it, I think I can make the
case that it fits the criteria you quoted from Mark Thomas.

> ...The criteria that the ASF looks for in communication channels used by
projects are (in no particular order):

> - open to all

Our self-signup is fully automated and open to all. Unlike other projects
which send requests to moderators, anyone with an email id can register to
join our Slack and is admitted automatically. Our #general channel ---
which is where the majority of public discussion happens --- links to the
project's code of conduct as well.

> - asynchronous

Slack does the give the impression of synchronicity which is why I think
it's probably preferred --- As in, if one has a question and wants an
answer quickly, it's more likely they will try slack (or gasp, twitter).
But there is often asynchronous communication also happening on Slack and i
think it's detrimental to people's well-being to treat Slack as a fully
synchronous medium. Anyway, I'm tending toward different topics now but I
just wanted to point out that there are plenty of cases in our Slack where
questions aren't always answered "immediately" and might take a few hours
or even a day.

> - available off-line

This is perhaps too nuanced -- the Slack client will generally allow you to
read messages when disconnected, and if you receive Slack notifications by
email, and your email is also available offline, then it also works. Is
that satisfactory? The daily digests we've automated also provide another
way to consume the messages off-line.

> - full history

We only recently started sending our daily slack digests to our Apache dev
list. But I can replay the digests from the very first day we started using
the current Slack for the project. If there's value in that, I'm happy to
do it, but perhaps consolidate the historical digest into a single large
email to avoid a thousand emails being sent (or use a different target list
to reduce the noise).

> - searchable
> - archived on ASF controlled systems

The Slack daily digests are searchable and archived in the way our dev list
is searchable.

> - low bandwidth / minimal system requirements ...

Heh - I guess there are some stories about Slack being a CPU hog sometimes.

To your comment that:
Slack is central to the project and one cannot really get involved
without being active there "all the time".

I think it will serve us well to avoid this misconception --- certainly
that is NOT the case in my opinion and no one should be expected to be
active in Slack all the time. Thank you for the advice for establishing
better guidelines on the communication channels, I very much like the
suggestions and support us addressing these concerns.

-r

Re: [DISCUSS] graduation from the incubator

[Michele Sciabarra]

>With my incubation mentor hat on, I think the role of the project's
>communications channels needs to be clarified before graduating. It is
>easy to get the impression that the vast majority of the project's
>business happens on Slack - maybe it's not really the case but I think
>having guidelines for how to use the various communications channels
>will help convince the Incubator that the project is following the
>Apache principles of inclusive communication.

I have seen other projects (I would say almost all) that use an online chat for 
communication.
What I have seen here though, and I have not seen in other projects, is the 
wonderful thing that Rodric did forwarding the slack digest to the mailing 
list.  My feeling is that this thing makes very easy to follow what is going on 
in the project without having to hook in slack frequently.

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

[Vincent S Hou]

+1 from me.

[x] Download links are valid.
[x] 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 repository.
[x] All files have license headers if necessary.
[x] 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

-James Thomas  wrote: -
To: dev@openwhisk.apache.org
From: James Thomas 
Date: 03/19/2019 08:15AM
Subject: Re: [VOTE] release Apache OpenWhisk CLI 0.10.0-incubating

+1

[x] Download links are valid.
[x] 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 repository.
[x] All files have license headers if necessary.
[x] No compiled archives bundled in source archive.

On Sat, 16 Mar 2019 at 18:57, David P Grove  wrote:

>
>
> This is a call to vote on releasing version 0.10.0-incubating of the Apache
> OpenWhisk CLI.
>
> The Apache OpenWhisk CLI provides the command line tooling for interacting
> with Apache OpenWhisk.
>
> This release comprises of source code distribution only. There are three
> modules (git repos) included in this CLI release. All artifacts were built
> by PR#249 in the openwhisk-release repo from the following Git commit IDs:
> * openwhisk-cli: eaf64ae
> * openwhisk-client-go: 4286a82
> * openwhisk-wskdeploy: 7d79fd7
>
> openwhisk-cli (55BEEB6D CDF621AB 7AA6098A 5DBCA55E 6D7E3B0C A3DAA7DF
> B44103F8 CE30ACC9 13411ECC BFF18519 3E142EC3 D27AA081 E1D47F63 14E9E708
> 90646EC7 C13756D6)
> src.tar.gz:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dcli-2D0.10.0-2Dincubating-2Dsources.tar.gz=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=Q3ePIMcrSrMTk5YRau4KJ3yonzOcphdte_KN8n07UJI=
> sha512 checksum:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dcli-2D0.10.0-2Dincubating-2Dsources.tar.gz.sha512=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=qir7ISkaEsAa9nDbXvqWREoSLrYkMFZsaKm--SJDlp4=
> signature:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dcli-2D0.10.0-2Dincubating-2Dsources.tar.gz.asc=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=fJrR3-25kgXmNsWMp7f_QAxzDLJXs94V8TU5qhk9lV8=
>
> openwhisk-client-go (068DBC87 533905DB D0089CAE 74FD0B91 109992D8 D843CAA4
> 01EA87B6 9CDC9550 6D555655 4679FF36 7A52414E DCC59126 E558085D 3E960DEB
> 18804581 6B2FA019)
> src.tar.gz:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dclient-2Dgo-2D0.10.0-2Dincubating-2Dsources.tar.gz=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=OOYCfesKrrDIXS0QA3AUk4Ulby14hUKXtmKnjYP-Ae4=
> sha512 checksum:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dclient-2Dgo-2D0.10.0-2Dincubating-2Dsources.tar.gz.sha512=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=lLtWohXlKMdewdg6uTQjhl_CMeEH8StqWKDEvJisYds=
> signature:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dclient-2Dgo-2D0.10.0-2Dincubating-2Dsources.tar.gz.asc=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=TLbJxHCxkVIQIPwJNybBPqjZ-hbxTMyURiu8crWl3jg=
>
> openwhisk-wskdeploy (412B1E09 129F2884 A1D4E9DE 0A979B47 55A54FC5 61E1D328
> 325E8A12 AE504779 A2350B9F 4185582F 7782EEA5 AE9018CD 52E4AA4C 484B5211
> AA449B4B 9F9E2432)
> src.tar.gz:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dwskdeploy-2D0.10.0-2Dincubating-2Dsources.tar.gz=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=8hq1GIGSe8S96oUUN0jP9PeLs-tNgpwxuAJLrs698ZM=
> sha512 checksum:
>
> 

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

[James Thomas]

+1

[x] Download links are valid.
[x] 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 repository.
[x] All files have license headers if necessary.
[x] No compiled archives bundled in source archive.

On Sat, 16 Mar 2019 at 18:57, David P Grove  wrote:

>
>
> This is a call to vote on releasing version 0.10.0-incubating of the Apache
> OpenWhisk CLI.
>
> The Apache OpenWhisk CLI provides the command line tooling for interacting
> with Apache OpenWhisk.
>
> This release comprises of source code distribution only. There are three
> modules (git repos) included in this CLI release. All artifacts were built
> by PR#249 in the openwhisk-release repo from the following Git commit IDs:
> * openwhisk-cli: eaf64ae
> * openwhisk-client-go: 4286a82
> * openwhisk-wskdeploy: 7d79fd7
>
> openwhisk-cli (55BEEB6D CDF621AB 7AA6098A 5DBCA55E 6D7E3B0C A3DAA7DF
> B44103F8 CE30ACC9 13411ECC BFF18519 3E142EC3 D27AA081 E1D47F63 14E9E708
> 90646EC7 C13756D6)
> src.tar.gz:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz
> sha512 checksum:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.sha512
> signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.asc
>
> openwhisk-client-go (068DBC87 533905DB D0089CAE 74FD0B91 109992D8 D843CAA4
> 01EA87B6 9CDC9550 6D555655 4679FF36 7A52414E DCC59126 E558085D 3E960DEB
> 18804581 6B2FA019)
> src.tar.gz:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz
> sha512 checksum:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.sha512
> signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.asc
>
> openwhisk-wskdeploy (412B1E09 129F2884 A1D4E9DE 0A979B47 55A54FC5 61E1D328
> 325E8A12 AE504779 A2350B9F 4185582F 7782EEA5 AE9018CD 52E4AA4C 484B5211
> AA449B4B 9F9E2432)
> src.tar.gz:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz
> sha512 checksum:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.sha512
> signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.asc
>
> All release artifacts were signed with key 72AF0CC22C4CF320.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>
> How to verify the artifacts can be found at:
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the
> +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
>
> Please vote on releasing the three components of Apache OpenWhisk CLI
> 0.10.0-incubating as described above.
>
> The vote will be open for at least 72 hours.
> [ ] +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:
> [ ] 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 repository.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> regards,
>
> --dave
>


-- 
Regards,
James Thomas

Re: [DISCUSS] graduation from the incubator

[Markus Thömmes]

+1.

Make it happen!

Am Di., 19. März 2019 um 07:02 Uhr schrieb Michele Sciabarra <
mich...@sciabarra.com>:

> Actually it looks to me pretty unusual that a project of this size has not
> yet graduated.
>
> --
>  Michele Sciabarra
>  mich...@sciabarra.com
>
>
>
> - Original message -
> From: David P Grove 
> To: OpenWhisk Dev 
> Subject: [DISCUSS] graduation from the incubator
> Date: Friday, March 15, 2019 11:06 PM
>
>
>
> 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://lists.apache.org/thread.html/b2217c61caad5c7a0369699d06d44e5cf688d3cba982e354a45b8c78@%3Cdev.openwhisk.apache.org%3E
> [2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103091999
>
>

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

[OpenWhisk Team Slack]

2019-03-18 14:05:50 UTC - Michele Sciabarra: I do not see the image 
openwhisk/actionloop-v2 but the change has been merged and it is in the 
official repo
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552917950313300

2019-03-18 14:06:00 UTC - Michele Sciabarra: any reason because it is not 
automatically pushed?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552917960313600

2019-03-18 15:51:12 UTC - Carlos Santana: @Michele Sciabarra check travis
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552924272313900

2019-03-18 15:51:23 UTC - Carlos Santana: 

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552924283314100

2019-03-18 16:04:39 UTC - Carlos Santana: @Michele Sciabarra 

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552925079314300

2019-03-18 16:06:23 UTC - Michele Sciabarra: yeah! I need it for the actionloop 
tutorial I am writing
+1 : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552925183314700

2019-03-18 18:15:36 UTC - James Thomas: 

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552932936315000

2019-03-18 18:15:58 UTC - James Thomas: committers - please vote on this 
release of the openwhisk client js
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552932958315600

2019-03-18 18:16:11 UTC - James Thomas: :pray:
+1 : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552932971315800

Re: [DISCUSS] graduation from the incubator

[Michele Sciabarra]

Actually it looks to me pretty unusual that a project of this size has not yet 
graduated.

-- 
 Michele Sciabarra
 mich...@sciabarra.com



- Original message -
From: David P Grove 
To: OpenWhisk Dev 
Subject: [DISCUSS] graduation from the incubator
Date: Friday, March 15, 2019 11:06 PM



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://lists.apache.org/thread.html/b2217c61caad5c7a0369699d06d44e5cf688d3cba982e354a45b8c78@%3Cdev.openwhisk.apache.org%3E
[2]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103091999