Re: [VOTE][RESULT] Accept OpenWhisk into the Apache Incubator

[John D. Ament]

I just added it, to unblock secretary actions.

On Mon, Nov 28, 2016 at 6:28 PM Craig Russell 
wrote:

> I’m unable to find the proposal at
> https://wiki.apache.org/incubator/ProjectProposals
>
> Is it me or is the proposal not included on that page?
>
> Thanks,
>
> Craig
>
> > On Nov 23, 2016, at 12:20 PM, Sam Ruby  wrote:
> >
> > This vote passes with 10 binding +1's, 3 non-binding +1, and no -1's
> >
> > Binding:
> >  John D. Ament
> >  Bertrand Delacretaz
> >  Ted Dunning
> >  Niclas Hedhman
> >  Sergio Fernández
> >  Felix Meschberger
> >  Jean-Baptiste Onofré
> >  Karl Pauls
> >  Edward J. Yoon
> >  Reynold Xin
> >
> > Non-binding:
> >  Liang Chen
> >  Debo Dutta
> >  Charith Elvitigala
> >
> > Note that John Ament indicated his intention to vote -1 on any
> > OpenWhisk release until the "GitHub as master" issue is resolved by
> > the Apache Infrastructure team.
> >
> > - Sam Ruby
> >
> > On Thu, Nov 17, 2016 at 10:22 AM, Sam Ruby 
> wrote:
> >> Now that the discussion thread on the OpenWhisk Proposal has died
> >> down, please take a moment to vote on accepting OpenWhisk into the
> >> Apache Incubator.
> >>
> >> The ASF voting rules are described at:
> >>   http://www.apache.org/foundation/voting.html
> >>
> >> A vote for accepting a new Apache Incubator podling is a majority vote
> >> for which only Incubator PMC member votes are binding.
> >>
> >> Votes from other people are also welcome as an indication of peoples
> >> enthusiasm (or lack thereof).
> >>
> >> Please do not use this VOTE thread for discussions.
> >> If needed, start a new thread instead.
> >>
> >> This vote will run for at least 72 hours. Please VOTE as follows
> >> [] +1 Accept OpenWhisk into the Apache Incubator
> >> [] +0 Abstain.
> >> [] -1 Do not accept OpenWhisk into the Apache Incubator because ...
> >>
> >> The proposal is listed below, but you can also access it on the wiki:
> >>   https://wiki.apache.org/incubator/OpenWhiskProposal
> >>
> >> - Sam Ruby
> >>
> >> = OpenWhisk Proposal =
> >>
> >> OpenWhisk is an open source, distributed Serverless computing platform
> >> able to execute application logic (Actions) in response to events
> >> (Triggers) from external sources (Feeds) or HTTP requests governed by
> >> conditional logic (Rules). It provides a programming environment
> >> supported by a REST API-based Command Line Interface (CLI) along with
> >> tooling to support packaging and catalog services.
> >>
> >> Champion: Sam Ruby, IBM
> >>
> >> Mentors:
> >> * Felix Meschberger, Adobe
> >> * Isabel Drost-Fromm, Elasticsearch GmbH
> >> * Sergio Fernández, Redlink GmbH
> >>
> >> == Background ==
> >>
> >> Serverless computing is the evolutionary next stage in Cloud computing
> >> carrying further the abstraction offered to software developers using
> >> Container-based operating system virtualization. The Serverless
> >> paradigm enables programmers to just “write” functional code and not
> >> worry about having to configure any aspect of a server needed for
> >> execution. Such Serverless functions are single purpose and stateless
> >> that respond to event-driven data sources and can be scaled on-demand.
> >>
> >> The OpenWhisk project offers a truly open, highly scalable, performant
> >> distributed Serverless platform leveraging other open technologies
> >> along with a robust programming model, catalog of service and event
> >> provider integrations and developer tooling.
> >> Specifically, every architectural component service of the OpenWhisk
> >> platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API
> >> Gateway, etc.) all is designed to be run and scaled as a Docker
> >> container. In addition, OpenWhisk uniquely leverages aspects of Docker
> >> engine to manage, load balance and scale supported OpenWhisk runtime
> >> environments (e.g., JavaScript, Python, Swift, Java, etc.), that run
> >> Serverless functional code within Invoker compute instances, using
> >> Docker containers.
> >>
> >> OpenWhisk's containerized design tenants not only allows it to be
> >> hosted in various IaaS, PaaS Clouds platforms that support Docker
> >> containers, but also achieves the high expectation of the Serverless
> >> computing experience by masking all aspects of traditional resource
> >> specification and configuration from the end user simplifying and
> >> accelerating Cloud application development.
> >> In order to enable HTTP requests as a source of events, and thus the
> >> creation of Serverless microservices that expose REST APIs, OpenWhisk
> >> includes an API Gateway that performs tasks like security, request
> >> routing, throttling, and logging.
> >>
> >> == Rationale ==
> >>
> >> Serverless computing is in the very early stages of the technology
> >> adoption curve and has great promise in enabling new paradigms in
> >> event-driven application development, but current implementation
> >> efforts are fractured as most are 

Re: [VOTE][RESULT] Accept OpenWhisk into the Apache Incubator

[Craig Russell]

I’m unable to find the proposal at 
https://wiki.apache.org/incubator/ProjectProposals

Is it me or is the proposal not included on that page?

Thanks,

Craig

> On Nov 23, 2016, at 12:20 PM, Sam Ruby  wrote:
> 
> This vote passes with 10 binding +1's, 3 non-binding +1, and no -1's
> 
> Binding:
>  John D. Ament
>  Bertrand Delacretaz
>  Ted Dunning
>  Niclas Hedhman
>  Sergio Fernández
>  Felix Meschberger
>  Jean-Baptiste Onofré
>  Karl Pauls
>  Edward J. Yoon
>  Reynold Xin
> 
> Non-binding:
>  Liang Chen
>  Debo Dutta
>  Charith Elvitigala
> 
> Note that John Ament indicated his intention to vote -1 on any
> OpenWhisk release until the "GitHub as master" issue is resolved by
> the Apache Infrastructure team.
> 
> - Sam Ruby
> 
> On Thu, Nov 17, 2016 at 10:22 AM, Sam Ruby  wrote:
>> Now that the discussion thread on the OpenWhisk Proposal has died
>> down, please take a moment to vote on accepting OpenWhisk into the
>> Apache Incubator.
>> 
>> The ASF voting rules are described at:
>>   http://www.apache.org/foundation/voting.html
>> 
>> A vote for accepting a new Apache Incubator podling is a majority vote
>> for which only Incubator PMC member votes are binding.
>> 
>> Votes from other people are also welcome as an indication of peoples
>> enthusiasm (or lack thereof).
>> 
>> Please do not use this VOTE thread for discussions.
>> If needed, start a new thread instead.
>> 
>> This vote will run for at least 72 hours. Please VOTE as follows
>> [] +1 Accept OpenWhisk into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept OpenWhisk into the Apache Incubator because ...
>> 
>> The proposal is listed below, but you can also access it on the wiki:
>>   https://wiki.apache.org/incubator/OpenWhiskProposal
>> 
>> - Sam Ruby
>> 
>> = OpenWhisk Proposal =
>> 
>> OpenWhisk is an open source, distributed Serverless computing platform
>> able to execute application logic (Actions) in response to events
>> (Triggers) from external sources (Feeds) or HTTP requests governed by
>> conditional logic (Rules). It provides a programming environment
>> supported by a REST API-based Command Line Interface (CLI) along with
>> tooling to support packaging and catalog services.
>> 
>> Champion: Sam Ruby, IBM
>> 
>> Mentors:
>> * Felix Meschberger, Adobe
>> * Isabel Drost-Fromm, Elasticsearch GmbH
>> * Sergio Fernández, Redlink GmbH
>> 
>> == Background ==
>> 
>> Serverless computing is the evolutionary next stage in Cloud computing
>> carrying further the abstraction offered to software developers using
>> Container-based operating system virtualization. The Serverless
>> paradigm enables programmers to just “write” functional code and not
>> worry about having to configure any aspect of a server needed for
>> execution. Such Serverless functions are single purpose and stateless
>> that respond to event-driven data sources and can be scaled on-demand.
>> 
>> The OpenWhisk project offers a truly open, highly scalable, performant
>> distributed Serverless platform leveraging other open technologies
>> along with a robust programming model, catalog of service and event
>> provider integrations and developer tooling.
>> Specifically, every architectural component service of the OpenWhisk
>> platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API
>> Gateway, etc.) all is designed to be run and scaled as a Docker
>> container. In addition, OpenWhisk uniquely leverages aspects of Docker
>> engine to manage, load balance and scale supported OpenWhisk runtime
>> environments (e.g., JavaScript, Python, Swift, Java, etc.), that run
>> Serverless functional code within Invoker compute instances, using
>> Docker containers.
>> 
>> OpenWhisk's containerized design tenants not only allows it to be
>> hosted in various IaaS, PaaS Clouds platforms that support Docker
>> containers, but also achieves the high expectation of the Serverless
>> computing experience by masking all aspects of traditional resource
>> specification and configuration from the end user simplifying and
>> accelerating Cloud application development.
>> In order to enable HTTP requests as a source of events, and thus the
>> creation of Serverless microservices that expose REST APIs, OpenWhisk
>> includes an API Gateway that performs tasks like security, request
>> routing, throttling, and logging.
>> 
>> == Rationale ==
>> 
>> Serverless computing is in the very early stages of the technology
>> adoption curve and has great promise in enabling new paradigms in
>> event-driven application development, but current implementation
>> efforts are fractured as most are tied to specific Cloud platforms and
>> services. Having an open implementation of a Serverless platform, such
>> as OpenWhisk, available and governed by an open community like Apache
>> could accelerate growth of this technology, as well as encourage
>> dialog and interoperability.
>> 
>> Having the ASF accept and incubate OpenWhisk would