Re: I created a variant of the go runtime that is faster at init time

The go repo could hold the code to produce the 3 runtime images For example: action-loop-v1.0.1:tag action-go-v1.11:tag action-gccgo-v1.10:tag - Carlos Santana @csantanapr > On Dec 12, 2018, at 9:25 AM, Rodric Rabbah wrote: > > +1 “I think it would be better to organize around 1 git repo

Re: "nightly" releases of clis (was Graduation)

Hi Bertrand, I hope I addressed some of your most recent comments with my PRs today. Please view the updated page here: https://openwhisk.incubator.apache.org/downloads.html Thanks, Matt On 2018/12/12 08:02:48, Bertrand Delacretaz wrote: > Hi Matt, > > On Tue, Dec 11, 2018 at 7:32 PM Matt

Re: publishing developer-oriented binary artifacts

Thanks Dave for consolidating the various points of discussion. This is very helpful and the thoughtful recommendations. I agree on all parts with your assessment and direction, and will help out on driving the releases so we can get to a more cogent point. -r > On Dec 12, 2018, at 9:16 AM,

Re: I created a variant of the go runtime that is faster at init time

+1 “I think it would be better to organize around 1 git repo per language.” -r > On Dec 12, 2018, at 9:21 AM, David P Grove wrote: > > For the runtimes specifically, if it is technically feasible I think it would > be better to organize around 1 git repo per language. > > That repo could

Re: I created a variant of the go runtime that is faster at init time

For the runtimes specifically, if it is technically feasible I think it would be better to organize around 1 git repo per language. That repo could contain multiple runtime variants with different degrees of maturity. Several of the runtime repos already contain multiple variants (nodejs, php,

publishing developer-oriented binary artifacts

We have related conversations on mail threads [1] and [2]. I suggest we consolidate to a new thread to nail down a policy that we can document. I suspect it is pretty close to what we are operationally doing already, but we need to write it down. 1. Publishing on dockerhub. a. I suggest we

Re: I created a variant of the go runtime that is faster at init time

The book is name learning OpenWhisk, it’s ok to have a matching Github .org/repo I don’t see any problem you are not using “openwhisk” to miss represent I think to make it legit, send request to the PPMC at priv...@openwhisk.apache.org asking if it’s ok. This is similar as if someone that

Re: I created a variant of the go runtime that is faster at init time

> Accounts with "openwhisk" in their name should be owned by the >OpenWhisk (P)PMC as the name is a trademark of the Apache Software >Foundation - technically being donated as we speak IIUC but that >doesn't make a real difference. Uh oh... I created a github organizations named

Re: I created a variant of the go runtime that is faster at init time

Actually, the issue is where to publish in Docker Hub the contrib runtimes, like the `actionloop-gccgo-v1.11` I did that produces smaller executable but uses a different Go compiler, with all the consequences of being "different" (it is not the mainstream one). It won't go on the standard set

Re: I created a variant of the go runtime that is faster at init time

My 2 cents about the "contrib" repo for best effort support and experimental code we already have a repo It used be named incubator-openwhisk-experimental, but then we rename it to incubator-openwhisk-devtools [1] If any one has some cool experiments we have created a new folder in the repo and

Re: "nightly" releases of clis (was Graduation)

To help with the confusion I try to clean up the "releases" github pages for both CLIs wsk and wskdeploy https://github.com/apache/incubator-openwhisk-wskdeploy/releases https://github.com/apache/incubator-openwhisk-cli/releases The tag "latest" means nightly and is mark in red as "pre-release"

Re: Tagging the actionloop with a name matching the version

I think we should instea ddo a Apache Release cut across all runtime repos and including the recent new ones like Go, DotNet. I know this is something Dave Grove and Rodric want to drive soon We can do one single email to vote for all runtimes It should take about a week, depending how fast we

Tagging the actionloop with a name matching the version

Hello all, at the moment there are, using actionloop: - my upcoming runtime for Python - on the work a runtime for PHP - the newly announced Crystal runtime I am using now, to build the images, the FROM actionloop as builder but I am a bit afraid of getting the wrong version (it happened to

Re: I created a variant of the go runtime that is faster at init time

Hmm, I understand the concern but I wonder HOW the "convenience" binaries should be handled in practice. In OpenWhisk what it matters is the runtime you specify with --docker, so that "convenience" is not really just a convenience, it is a core requirement. We could setup an openwhisk contrib

Re: I created a variant of the go runtime that is faster at init time

Hi Michele This is shaky ground and we don’t want to be the next npm horror story. Technically speaking, at Apache we primarily release source packages, all binary is pure convenience. Granted the convience today is what most people use. So what we should primarily do, as Bertrand hinted, is

Re: I created a variant of the go runtime that is faster at init time

Hi Michele „Dynamic libraries included in the container" was the answer I was looking for. Thanks Regards Felix > Am 12.12.2018 um 10:49 schrieb Michele Sciabarra : > > To answer to the second part of your question: > > if you compile a Go program with the native go compiler, the final

Re: I created a variant of the go runtime that is faster at init time

Yes, a single contrib repository. I guess we still would want to lock it down but be more open to accept contributions, provided IP is properly transferred Regards Felix > Am 12.12.2018 um 10:45 schrieb Bertrand Delacretaz : > > Hi, > > On Wed, Dec 12, 2018 at 10:42 AM Michele Sciabarra >

Re: I created a variant of the go runtime that is faster at init time

To answer to the second part of your question: if you compile a Go program with the native go compiler, the final executable links statically everything including the garbage collector and other stuff. If you use gccgo, those things are dynamic libraries and are not included in the executable.

Re: I created a variant of the go runtime that is faster at init time

Hi, On Wed, Dec 12, 2018 at 10:42 AM Michele Sciabarra wrote: > > Indeed I was thinking to create a docker account "openwhisk-contrib" to > place those, let's say, unofficial images. > I am not sure who should own this account... Accounts with "openwhisk" in their name should be owned by the

Re: I created a variant of the go runtime that is faster at init time

Indeed I was thinking to create a docker account "openwhisk-contrib" to place those, let's say, unofficial images. I am not sure who should own this account, I think should be owned by the community(not me) but with a less strict policy to accept images. -- Michele Sciabarra

Re: I created a variant of the go runtime that is faster at init time

On Wed, Dec 12, 2018 at 10:10 AM Felix Meschberger wrote: > ...I wonder, whether such a thing would not have a space in some sort of an > „unsupported“ > contrib area ?... Big +1, with my incubation mentor hat on - having modules which are not guaranteed to be supported, nor part of the core

Re: I created a variant of the go runtime that is faster at init time

Hi From the sidelines… I understand that there is limited bandwidth to support all sorts of runtimes .. But I wonder, whether such a thing would not have a space in some sort of an „unsupported“ contrib area ? I myself like the idea of smaller binaries but wonder how you solve the dynmic

Re: "nightly" releases of clis (was Graduation)

Hi Matt, On Tue, Dec 11, 2018 at 7:32 PM Matt Rutkowski wrote: > ...https://github.com/apache/incubator-openwhisk-website/pull/353 ... Thank you very much for this. I like it, with a few minor comments. I'd prefer saying "Apache Releases" or "Apache OpenWhisk Releases" instead of "Official