Re: Please review our project's draft Apache Incubator June board report

2018-06-06 Thread Bertrand Delacretaz
Hi, On Tue, Jun 5, 2018 at 10:28 PM, Matt Rutkowski wrote: > ...We recently had a public (and private threads) around "models" for > donation at Apache which went no where... IIUC you mean donating resources for automated testing? The ASF now has a Targeted Sponsors [1] program meant

Re: Please review our project's draft Apache Incubator June board report

2018-06-06 Thread James Thomas
LGTM - nice work Matt. On the "Community" section? Would it be worth adding the growth of the Slack community? We're ~800 members and it is really active. On 5 June 2018 at 18:51, Matt Rutkowski wrote: > Whiskers, > > I have drafted our project board report for this quarter (June); I plan to >

Re: Please review our project's draft Apache Incubator June board report

2018-06-06 Thread Carlos Santana
Matt, Thanks for spending time doing the report, I can't express more gratitude about this. On one of the board meetings, someone mentioned that "OpenWhisk" report is one of the best incubator reports they have seen in years. Kudos !! I don't know how you come up with so excellent detail report

Re: About Ruby2.5 runtime support proposal(in relation to #3725)

2018-06-06 Thread James Thomas
This looks excellent - I've seen lots of people asking about Ruby support before! If you had time to write up generic instructions for creating a new runtime, based on your experiences, it would help others add more. It has been something we've been meaning to do since the PHP runtime. Also, if

Re: Please review our project's draft Apache Incubator June board report

2018-06-06 Thread Bertrand Delacretaz
On Tue, Jun 5, 2018 at 7:51 PM, Matt Rutkowski wrote: ... > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85475755 ... Thanks for this! Great report as usual. Could "Increase additional company and individual Contributors to maintain all project repos" be changed to just

About Ruby2.5 runtime support proposal(in relation to #3725)

2018-06-06 Thread Kei Sawada
Hi, This email is follow-up from #3725 which proposes Ruby2.5 runtime addition. https://github.com/apache/incubator-openwhisk/pull/3725 > (perhaps including a small example on how to try it) Here is a quick introduction on how to use and test this runtime. Excuse me in advance for a little bit

Re: Tech Interchange meeting tomorrow

2018-06-06 Thread Dominic Kim
Dear Tyson. Sorry for the late response, I thought I am already supposed to share it at this meeting. I am in. Let me continue to share my scheduling proposal. Thanks Regards Dominic. 2018-06-06 17:41 GMT+09:00 Rodric Rabbah : > Thanks Sandeep - id like to see; we need a plan for resolving

Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Bertrand Delacretaz
Someone wrote: > ...Would it be worth adding the growth of the > Slack community? We're ~800 members and it is really active With my incubation mentor hat on: enthusiasm for the the project is fantastic news, but Apache projects should do their business on asynchronous channels, and I don't

Re: Tech Interchange meeting tomorrow

2018-06-06 Thread sandy801
Hi Tyson, If time permits I can demo OpenWhisk tracing support based on my PR. thanks, Sandeep On 2018/06/05 16:08:23, Tyson Norris wrote: > Hi All - > Reminder: the biweekly call is tomorrow 10 am GMT-5:00 (US Central Time), > please send any agenda items to the list or myself. > Google cal

Re: Tech Interchange meeting tomorrow

2018-06-06 Thread Rodric Rabbah
Thanks Sandeep - id like to see; we need a plan for resolving the long outstanding pr so getting to see the status, features, and your thoughts will be essential. Tyson, I hope we can put this toward the top of the agenda, along with the release discussion. -r > On Jun 6, 2018, at 4:37 AM,

Re: About Ruby2.5 runtime support proposal(in relation to #3725)

2018-06-06 Thread Kei Sawada
> > If you had time to write up generic instructions for creating a new > > runtime, based on your experiences, it would help others add more. It has > > been something we've been meaning to do since the PHP runtime. > > > > Also, if you get time, adding a simple OpenWhisk Ruby client library to >

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Rob Allen
> On 6 Jun 2018, at 15:30, Rodric Rabbah wrote: > > Re slack... good discipline on our part does make it easier to catch up > even after hundreds of messages are posted. We do try to organize > discussions using slack threads so that it is easier to follow a particular > topic. This doesn't

Re: Please review our project's draft Apache Incubator June board report

2018-06-06 Thread Carlos Santana
I think the company is referring to that to my understanding is that the project to graduate should have at least 3 companies sponsoring the project, which typically in practice sponsoring means that they are behind the project in case 1 company drops, there are at least 2 to continue the project.

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Bertrand Delacretaz
On Wed, Jun 6, 2018 at 4:42 PM, David P Grove wrote: > ...As Rodric said, properly organized channels and the use of threads help > quite a bit... Do you have a few Slack URLs of good examples of that? I'll look at them quickly, before they disappear ;-) -Bertrand

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Bertrand Delacretaz
Hi, On Wed, Jun 6, 2018 at 4:05 PM, David P Grove wrote: > ...Professionally, I'm on several Slack teams that are paid (unlimited > history) and I personally find it _much_ easier to catch up with and > understand multiple weeks of technical conversation in a properly focused > Slack channel

Re: Tech Interchange meeting tomorrow

2018-06-06 Thread David P Grove
Apologies for missing the interchange today; unavoidable personal conflict. A quick update on the openwhisk-deploy-kube sub-project. 1. Main focus in the last two weeks has been the Helm-based deployment. This is looking really solid. I'm working on a PR now to reorganize the

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Rodric Rabbah
Chetan suggested looking into Slack workspace export - It looks like we can export all the messages this way (since 1/20/2017 for public channels). A simple UI to polish the JSON and make it easier to read and search would be helpful. Here's an example of a recent thread of discussion:

Re: Please review our project's draft Apache Incubator June board report

2018-06-06 Thread Bertrand Delacretaz
On Wed, Jun 6, 2018 at 4:04 PM, Carlos Santana wrote: > ...I think the company is referring to that to my understanding is that the > project to graduate should have at least 3 companies sponsoring the > project... It's not exactly that. To graduate, a project must have "sufficient diversity" so

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Rodric Rabbah
Re slack... good discipline on our part does make it easier to catch up even after hundreds of messages are posted. We do try to organize discussions using slack threads so that it is easier to follow a particular topic. This doesn't always happen and as I noted, requires good habits. We have

Re: New scheduling algorithm proposal.

2018-06-06 Thread Dominic Kim
Sorry for the late response Tyson. Let me first answer your second question. Vuser is just the number of threads to send the requests. Each Vusers randomly picked the namespace and send the request using REST API. So they are independent of the number of namespaces. And regarding performance

Re: New scheduling algorithm proposal.

2018-06-06 Thread Dominic Kim
Sorry. Let me share Kafka benchmark results again. | # of topics | Kafka TPS | |50 | 34,488 | | 100 | 34,502 | | 200 | 31,781 | | 500 | 30,324 | | 1000 | 30,855 | Best regards Dominic 2018-06-07 2:04 GMT+09:00 Dominic Kim : > Sorry for the late response Tyson. > > Let

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread David P Grove
Bertrand Delacretaz wrote on 06/06/2018 11:06:01 AM: > > On Wed, Jun 6, 2018 at 4:42 PM, David P Grove wrote: > > ...As Rodric said, properly organized channels and the use of threads help > > quite a bit... > > Do you have a few Slack URLs of good examples of that? > > I'll look at them

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread David P Grove
Bertrand Delacretaz wrote on 06/06/2018 09:32:09 AM: > > ...Would it be worth adding the growth of the > > Slack community? We're ~800 members and it is really active > > With my incubation mentor hat on: enthusiasm for the the project is > fantastic news, but Apache projects should do