I opened issue https://github.com/apache/incubator-openwhisk/issues/4558
and corresponding PR https://github.com/apache/incubator-openwhisk/pull/4559
.
Additional feedback and critique welcomed.
-r
IMO, CLAs should be required for any non-trivial contributions (as
in-effect IP is being added and their contributions have to be done within
a legal framework that preserves the overall code license) and our wording
should better clarify (with examples, what qualifies).
The question, for the
On Sat, 13 Jul 2019 at 22:07, Matt Sicker wrote:
>
> I've looked around for some existing guidelines around CLA
> requirements, and so far I've found this:
>
> https://www.apache.org/licenses/contributor-agreements.html#clas
>
> So basically, the general idea I've seen is that small, trivial
>
I implemented both, the "convention" and the parameters designated as init
through the API. The latter wasn't much more over the former and is
backward compatible. This can be introduced incrementally into the main
repo/REST API, then the runtimes (I added it to Node but not the others),
and
Welcome, Michele and Rob~! : )
2019년 7월 16일 (화) 오전 1:55, Matt Rutkowski 님이 작성:
> Welcome Michele and Rob!
>
> - Forwarded by Matt Rutkowski/Austin/IBM on 07/15/2019 11:55 AM -
>
> From: Rodric Rabbah
> To: dev@openwhisk.apache.org
> Date: 07/15/2019 11:44 AM
> Subject:
2019-07-15 00:30:18 UTC - Marty Wallace: Hey guys, is there a preferred channel
for me to ask about some problems I've been having with OpenWhisk with IBM?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563150618433100
2019-07-15 01:03:06 UTC - Rodric Rabbah: Hi Marty. There are some
Michele,
Two thoughts:
1) For writing a controller in Knative I recommend to choose Go instead of
Rust (even when I like Rust more).
With Go you can leverage the fantastic Operator SDK from Redhat which makes
writing controllers fairly
simple (I had my first one up and running in under an
