ApacheCon is Coming 9-12 Sept. 2019 - Las Vegas The Apache Software Foundation
Apache 20th Anniversary Logo

Community-led development "The Apache Way"

Apache Support Logo

This was extracted (@ 2020-09-29 22:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).

OpenWhisk

20 May 2020 [Dave Grove / Bertrand]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (10 months ago)
There are currently 49 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Rob Allen on 2019-07-16.
- Alexander Klimetschek was added as committer on 2020-03-12

## Project Activity:

A major code contribution from Adobe Inc. of an OpenWhisk debugger was
formally completed in February.  The first Apache release of this new module
(openwsk-debug-1.2.0) was made several weeks later.

The project continues to make some progress towards a long-awaited next
release of the core OpenWhisk system (the last release of the core system was
0.9.0-incubating in 2018-10-31). This will be the first release of our new
standalone configuration which enables a very simple single machine deployment
of OpenWhisk. It will also be the first time the project has released a
coherent set of all its releasable software components (currently 23 separate
packages). The last lingering todo item is completing a release of the
remaining two packages that have not made releases since the project
exited incubation.

Recent releases:
- openwhisk-package-alarms-2.1.0 was released on 2020-05-11.
- openwhisk-client-js-3.21.2 was released on 2020-05-08.
- openwhisk-apigateway-1.0.0 was released on 2020-04-13.
- openwhisk-wskdebug-1.2.0 was released on 2020-03-10.
- openwhisk-runtime-nodejs-1.15.0 was released on 2020-02-17.
- openwhisk-runtime-python-1.14.0 was released on 2020-02-17.
- openwhisk-runtime-rust-1.0.0 was released on 2020-02-14.

## Community Health:
Community health is good with plenty of activity on dev list and slack.

Although metrics such as PRs and commits have declined since the previous
quarter, the project is continuing to make progress and is still averaging
more than one commit per day. It seems plausible that at least some of the
statistical decline may be attributable to short-term disruptions due to
COVID-19.

After a couple of months of intermittent discussion, the community adopted a
light-weight process for Proposing Openwhisk EnhanceMents (POEM) to facilitate
discussion of proposed architectural changes to the core system.  Since POEM
was adopted at the end of March, it has yet to be utilized. It remains to be
seen whether this indicates a lack of need for the POEM process, or whether
the six or so weeks since adoption have not been sufficient time for new POEMs
to be proposed by the community.

19 Feb 2020 [Dave Grove / Shane]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (7 months ago)
There are currently 48 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Rob Allen on 2019-07-16.
- Shawn Black was added as committer on 2019-11-26
- Cosmin Stanciu was added as committer on 2019-12-06
- PengCheng Jiang was added as committer on 2019-12-02
- Dan McWeeney was added as committer on 2020-01-15
- Duy Nguyen was added as committer on 2020-01-15
- Neeraj Mangal was added as committer on 2020-02-03

## Project Activity:

We are actively working towards a long-awaited next release of the core
OpenWhisk system (the last release of the core system was 0.9.0-incubating in
2018-10-31). This will be the first release of our new "standalone"
configuration which enables a very simple single machine deployment of
OpenWhisk. It will also be the first time the project has released a coherent
set of all its releasable software components (currently 22 separate
packages). This effort is driving a wave of component releases detailed below.

Recent releases:
- openwhisk-runtime-docker-1.14.0: 2020-02-11
- openwhisk-runtime-java-1.14.0: 2020-02-11
- openwhisk-runtime-php-1.14.0: 2020-02-11
- openwhisk-runtime-ruby-1.14.0: 2020-02-11
- openwhisk-runtime-swift-1.14.0: 2020-02-11
- openwhisk-client-js-3.21.1: 2020-02-08
- openwhisk-client-js-3.21.0: 2020-02-06
- openwhisk-composer-0.12.0: 2020-01-22
- openwhisk-runtime-go-1.15.0: 2020-01-17
- openwhisk-catalog-0.11.0: 2020-01-07
- openwhisk-runtime-dotnet-1.14.0: 2020-01-07

## Community Health:
Community health is good with plenty of activity on dev list and slack.

Statistical metrics (PRs, commits, list traffic, etc.) are stable.

The community is working on developing a light-weight process for Proposing
Openwhisk EnhanceMents (POEM) to facilitate discussion of proposed
architectural changes to the core system. There is a sense that by having a
documented series of steps for managing such changes we could increase community
involvement and project velocity.

20 Nov 2019 [Dave Grove / Shane]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions

## Issues:
There are no issues requiring board attention.

In feedback from last month's board report, DF asked us to verify that "the
Redis included in Composer is still an acceptable Open Source Software
license." OpenWhisk Composer depends/uses only Redis Core which continues to
be made available under a BSD 3-Clause license.  The apigateway component of
OpenWhisk also uses the same Redis Core functionality.

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (4 months ago)
There are currently 42 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Rob Allen on 2019-07-16.
- Justin Halsall was added as committer on 2019-08-22

## Project Activity:
Recent releases: openwhisk-runtime-go-1.14.0 was released on 2019-10-10.

With the merging of the last of the "playground ui" PRs on November 1, we
should finally be feature-complete for the standalone configuration of
OpenWhisk. We are now working towards making a source release containing this
feature. We hope to get this release out before the end of 2019.

## Community Health:

Community health is good with plenty of activity on dev list and slack.

Statistically, the decline in all metrics vs. the previous quarter is mainly
due to the compare against the one-time surge of activity associated with
graduating from the incubator.

16 Oct 2019 [Dave Grove / Dave]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (3 months ago)
There are currently 42 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- Justin Halsall was added as committer on 2019-08-22

## Project Activity:

Work continues on the "standalone" OpenWhisk configuration mentioned in our
previous board report that will enable a very simple basic install of
OpenWhisk.  Since the last report, a few additional enhancements were
identified as being desirable to include in the first release and are being
implemented. This work appears to be on track to be completed by the end of
October.

We made a major release of the OpenWhisk command line tools.

Releases since the last report:
- openwhisk-cli-1.0.0 was released on 2019-09-23.
- openwhisk-client-go-1.0.0 was released on 2019-09-23.
- openwhisk-wskdeploy-1.0.0 was released on 2019-09-23.

## Community Health:

Community health remains good with active dev list design discussions on
several topics including enhancements to the OpenWhisk scheduler, standalone
OpenWhisk, the intersection of OpenWhisk and Knative, and better support for
user events, monitoring, and operational metrics.

18 Sep 2019 [Dave Grove / Rich]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions

## Issues:
There are no issues requiring board attention

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (2 months ago)
There are currently 42 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- Justin Halsall was added as committer on 2019-08-22

## Project Activity:
- The project has completed updating its website, development tooling, and its
 52 github repos and associated CI/CD jobs  to reflect its graduation to a
 top-level project. In the process, 17 github repos were identified as being
 inactive and were archived (made read-only).

- We made our first two non-incubating releases of OpenWhisk sub-components:
 - openwhisk-apigateway-0.11.0 was released on 2019-08-30.
 - openwhisk-client-js-3.20.0 was released on 2019-08-28.

- Development work was completed on a new "standalone" configuration of
 OpenWhisk  that will enable significantly easier installation and
 experimentation with the OpenWhisk programming model by end users. A major
 focus for the next month will be to make a new release of the core system
 component so we can then make the standalone OpenWhisk jar easily available
 to end users via Maven.

## Community Health:
Overall community health is good.

There are active technical discussions on the dev list around several new
features that are being designed.

Overall, significant code contributions are holding steady. Statistically,
there was a large spike in GitHub PR activity (64% increase in opened PRs, 99%
increase in closed PRs) in this period, but at least half of the spike can be
attributed to fairly mechanical changes to "de-incubate" the repos, website,
and release tooling.

21 Aug 2019 [Dave Grove / Shane]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (21 days ago)
There are currently 41 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.

## Project Activity:

In the first few weeks post-graduation, there has been a focus on executing
the transfer of the project's resources out of the Incubator.  At graduation,
the project owned 52 github repos; an initial wave of 28 have been renamed and
we are in the midst of updating associated build tasks, cross-links, etc. to
reflect the renaming. A community discussion to identify inactive github repos
that should be archived has been started (most likely about a dozen will be
archived). We anticipate completing the transfer of resources before the
September board report is due.

A "standalone" OpenWhisk jar that enables easy local execution of the
OpenWhisk programming model is nearing completion and has generated community
excitement. We anticipate making a release within the next month to make this
capability widely available.  It will greatly simplify the "kick the tires"
experience of trying OpenWhisk by potentially interested users.

## Community Health:

Overall community health is good.  There is active technical discussion and
development activity across the various levels of the OpenWhisk stack.

17 Jul 2019

Establish the Apache OpenWhisk Project

 WHEREAS, the Board of Directors deems it to be in the best interests
 of the Foundation and consistent with the Foundation's purpose to
 establish a Project Management Committee charged with the creation and
 maintenance of open-source software, for distribution at no charge to
 the public, related to a platform for building serverless applications
 with functions.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
 (PMC), to be known as the "Apache OpenWhisk Project", be and hereby is
 established pursuant to Bylaws of the Foundation; and be it further

 RESOLVED, that the Apache OpenWhisk Project be and hereby is
 responsible for the creation and maintenance of software related to a
 platform for building serverless applications with functions; and be
 it further

 RESOLVED, that the office of "Vice President, Apache OpenWhisk" be and
 hereby is created, the person holding such office to serve at the
 direction of the Board of Directors as the chair of the Apache
 OpenWhisk Project, and to have primary responsibility for management
 of the projects within the scope of responsibility of the Apache
 OpenWhisk Project; and be it further

 RESOLVED, that the persons listed immediately below be and hereby are
 appointed to serve as the initial members of the Apache OpenWhisk
 Project:

 * Bertrand Delacretaz <bdelacretaz@apache.org>
 * Carlos Santana <csantanapr@apache.org>
 * Chetan Mehrotra <chetanm@apache.org>
 * Dave Grove <dgrove@apache.org>
 * Dominic Kim <style95@apache.org>
 * Dragos Dascalita Haut <dragos@apache.org>
 * James Dubee <dubeejw@apache.org>
 * James Thomas <jamesthomas@apache.org>
 * Jeremias Werner <jeremiaswerner@apache.org>
 * Krzysztof Sobkowiak <ksobkowiak@apache.org>
 * Markus Thömmes <markusthoemmes@apache.org>
 * Matt Rutkowski <mrutkowski@apache.org>
 * Matt Sicker <mattsicker@apache.org>
 * Michele Sciabarra <msciabarra@apache.org>
 * Olivier Tardieu <tardieu@apache.org>
 * Rob Allen <akrabat@apache.org>
 * Rodric Rabbah <rabbah@apache.org>
 * Sven Lange-Last <slange@apache.org>
 * Tyson Norris <tysonnorris@apache.org>
 * Vincent Hou <houshengbo@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Grove be appointed
 to the office of Vice President, Apache OpenWhisk, to serve in
 accordance with and subject to the direction of the Board of Directors
 and the Bylaws of the Foundation until death, resignation, retirement,
 removal or disqualification, or until a successor is appointed; and be
 it further

 RESOLVED, that the Apache OpenWhisk Project be and hereby is tasked
 with the migration and rationalization of the Apache Incubator
 OpenWhisk podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache Incubator
 OpenWhisk podling encumbered upon the Apache Incubator Project are
 hereafter discharged.

 Special Order 7C, Establish the Apache OpenWhisk Project, was
 approved by Unanimous Vote of the directors present.

19 Jun 2019

Distributed Serverless computing platform.

OpenWhisk has been incubating since 2016-11-23.

### Three most important unfinished issues to address before graduating:

 1. None.  The PPMC has engaged the community in initiating the
    graduation process.

### Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 No.

### How has the community developed since the last report?

 1. Strong dev-list activity with good mix of technical discussion,
    project direction, highlighting of significant PRs, and release
    coordination. For last 3 months, we are averaging over >150 messages
    per month sent by >28 individuals.
 2. incubator-openwhisk Github stars: 4,032 (+207 since last report)
 3. incubator-openwhisk GitHub forks: 779 (+41 since last report)
 4. Slack community 1,243 members (+84 from last report) and >12,000
    messages since the last report. Actively used by users for support.
 5. Received 6 new ICLAs since the last report.

### How has the project developed since the last report?

 1. Have now released multiple versions of virtually all OpenWhisk
    software components.  Nearing completion of project's
    first "unified release" wave.
 2. Active experimentation with KNative and OpenWhisk combinations
    to understand how best to leverage both technologies to support
    Serverless computing for our user community.
 3. Formal legal transfer of the OpenWhisk trademark from
    IBM to ASF has been completed.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

 - [ ] Initial setup
 - [ ] Working towards first release
 - [ ] Community building
 - [X] Nearing graduation
 - [ ] Other:

### Date of last release:

 2019-05-13 (released second versions of 9 OpenWhisk runtime components)

### When were the last committers or PPMC members elected?

 Dominic Kim was elected as committer and PPMC member on 4/12/2019

### Have your mentors been helpful?

 Yes.  Mentors have been helpful.

### Signed-off-by:

 - [X] (openwhisk) Bertrand Delacretaz
    Comments: Expecting graduation soon indeed!
 - [X] (openwhisk) Matt Sicker
    Comments:
 - [ ] (openwhisk) Krzysztof Sobkowiak
    Comments:

### IPMC/Shepherd notes:
 Justin Mclean: Just a minor thing. I see a number of conversations
 happening on the private list that probably should be occurring on the
 public list.

20 Mar 2019

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.  The OpenWhisk platform components are packaged
as Docker containers and can be deployed directly to Docker or
deployed using Container Frameworks such as Mesos, Kubernetes,
Compose, and YARN.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:
 1. Close legal transfer of trademark on "OpenWhisk" name and
    logo to ASF from IBM.
 2. Complete project maturity model assessment and formal
    graduation process.
 3. Improve release automation. A comprehensive OpenWhisk
    release includes over 20 sub-components, each drawn from its
    own github repo and each packaged as a separately
    downloadable source release.
   a. Release process/automation/documentation are here
      https://github.com/apache/incubator-openwhisk-release.
   b. During incubation, we have made over a dozen conforming
      Apache releases of sub-components.  We have developed
      reasonable automation for releasing a group of
      sub-components, but there is a need to further define and
      automate the process of making a unified release of a
      coherent set of released sub-components.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
 1. Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
    executed; hopefully this will happen at the March ASF Board meeting.
 2. The podling was down to one active mentor for several months,
    which has made getting the required minimum of 3 positive IPMC
    votes for each released component a significant challenge.  This
    had a negative effect on project velocity and PPMC morale.  At
    the time of this report, the IPMC is taking action by soliciting
    additional mentors to help the project finish out its incubation.

How has the community developed since the last report?
 + dev mailing list activity:
     + We have implemented an automated process to post a daily
       archive of the OpenWhisk Team Slack to our dev mailing list.
     + Increased use of the dev list for technical discussion,
       especially around releasing sub-components and ensuring
       awareness of significant PRs before merging.
 + incubator-openwhisk Github stars: 3,825 (+168 since last report)
 + incubator-openwhisk GitHub forks: 738 (+46 since last report)
 + Slack community:
   + 1,159 members (+87 from last report).  Very active in most
     channels from both end users or the project and contributors
   + To-date: 141,783 messages sent across all channels (+15,501
     since last report)
   + Analytics: https://openwhisk-team.slack.com/admin/stats
 + The  bi-weekly Zoom "Technical Interchange" continues to be well
 received and attended.
   Complete videos posted to OW YouTube channel and detailed notes to our
   CWIKI.
 + New Contributors
   + 13 new ICLAs received (including some that were missed in the
   previous two status reports):
     1. Sam Baxter 6/11/18
     2. Emanuel Russo 8/6/18
     3. Prabhash Rathnayake 10/2/18
     4. Shawn Black 10/2/18
     5. Moritz Raho 10/4/18
     6. Duy Nguyen 10/4/18
     7. Sam Hjelmfelt 11/21/18
     8. Marc Schwind 1/28/19
     9. Avi Weit 2/5/19
     10. Lars Andersson 2/8/19
     11. Maciej Małecki 2/26/19
     12. Somaya Jamil 2/27/19
     13. Erez Hadad 3/1/19
  + 5 new people Joined Community Technical Interchange calls and
  introduced themselves:
    1. Thomas Peikert: grad. student using OW, looking to make
    contributions in future
    2. Erez Hadad (IBM Research),  working on Serverless, incl. OW and
    knative, etc.
    3. Rahul (Adobe) - working on some depl. strat.  starting a CWIKI
    post...
    4. Lavanya (Adobe)
    5. Manoj (Adobe) - SW quality engineer

How has the project developed since the last report?
 1. There has been a focus on clearing the backlog of PRs and issues
    across all our github repos, motivated by a desire to make a
    unified release of all the OpenWhisk system sub-components.
    There is still significant work needed to clear out stale issues
    in the core repository, but the PR backlog mentioned in multiple
    previous reports has been rectified.
 2. Project technical highlights include (a) the addition of a .NET
    runtime component, (b) merged support for concurrent activation
    processing, (c) merged support for a "lean" system configuration
    suited for resource-limited hosts, (d) added the capability of
    deploying OpenWhisk on Apache YARN, (e) the unification of the
    `wskdeploy` and `wsk` CLIs into a single `wsk` cli.

How would you assess the podling's maturity?  Please feel free to add your
own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:
   Apache OpenWhisk Composer v0.10.0-incubating (2/27/19)
   Links to latest releases of all components can be found here:
https://openwhisk.apache.org/downloads.html

When were the last committers or PPMC members elected?
   New Committers+PPMC:
     1. Olivier Tardieu (2/27/19)

   New Committers:
     1. Michele Sciabarra (1/8/19)
     2. Rob Allen (1/8/19)

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

 Our sole remaining mentor has been helpful and responsive, but
 release voting has been challenging.  The recent efforts of the IPMC
 to identify projects needing additional mentors and should allow us
 to regain our desired release velocity.

Signed-off-by:

 [ ] (openwhisk) Bertrand Delacretaz

Comments:

IPMC/Shepherd notes:

19 Sep 2018

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.  Additionally, it now provides options to host the platform
components as Docker containers on various Container Frameworks such as Mesos,
Kubernetes, and Compose.

OpenWhisk has been incubating since 2016-11-23.
  Three most important issues to address in the move towards graduation:
  1. Finish the remaining component source code release under Incubator
     a. Release process/automation/documtantion are here
     https://github.com/apache/incubator-openwhisk-release).
  2. Increase additional company and individual Contributors to maintain all
  project repos. and address Issue / PR backlog.
  3. Close legal transferred of Trademark handoff for "OpenWhisk" name and
  logo to ASF

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?


   * Issue backlog building on incubator-openwhisk is still a major issue
 (partly due to #2 above). As of this report, the "open" issue backlog is 384
 (up from 365 as of last report), but open PR is at 35 (down from 55 as of last
 report). Please note this is just on the "main" platform repo. and likely is
 paralleled in other release component repos.
       * Need to prioritize and work to reduce while advancing major proposals
 around restructuring around abstractions to accommodate running on Knative
 while enhancing support for better logging/scheduling and performance testing
 enhancements.
       * Trying to add more active Committers to augment those who have
 dropped off in their activity; however, we have reached an impasse where
 potential new Contributor pull requests are not getting timely reviews/merges
 to provide a resume' for adding to the Committer roles.
   * It seems that Apache Infra. will not provide us servers to host a staging
 environment that would help us perform needed staging testing on Pull Requests.
 This means that independent testing needs to be done by members (companies).
 We have explored a corporate donation as suggested (ala Spark and SystemML),
 but this does not seem possible at this time.
       * No change in status since last quarterly report.
   * Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
 executed; need to identify process for this. See #3 above.
       * Discussion started w/ Apache legal via "legal-discuss" mailing list
 with subject "Trademark handoff for "OpenWhisk" name and logo".
       * IBM intends to hand-off ownership of trademarks at time of graduation.

How has the community developed since the last report?

   * dev mailing list activity increased since Q2 driven by release-related
 activity and an increase in technical discussion on the mailing list.
   * incubator-openwhisk Github stars: 3472 (+254 since last report)
   * incubator-openwhisk GitHub forks: 652 (+36 since last report). Note lots
 of more competing projects entering the Serverless space.
   * Slack community:
       * 969 members (+151 from last report).  Very active in most channels
 from both end users or the project and contributors
       * To-date: 112,326 messages sent across all channels
       * Analytics: https://openwhisk-team.slack.com/admin/stats
   * The  bi-weekly Zoom "Technical Interchange" continues to be well received
 and attended.
       * Complete videos posted to OW YouTube channel and detailed notes to
 our CWIKI.
       * YouTube Channel: Apache Meetings Playlist
       * CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting Notes
         * 2018-08-29:
         https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-29+OW+Tech+Interch
ange+-+Meeting+Notes
         * 2018-08-15:
         https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-15+OW+Tech+Interch
ange+-+Meeting+Notes
         * 2018-08-01:
         https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-01+OW+Tech+Interch
ange+-+Meeting+Notes
         * 2018-07-18:
         https://cwiki.apache.org/confluence/display/OPENWHISK/2018-07-18+OW+Tech+Interch
ange+-+Meeting+Notes
         * 2018-06-20:
         https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-20+OW+Tech+Interch
ange+-+Meeting+Notes
         * 2018-06-06:
         https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-06+OW+Tech+Interch
ange+-+Meeting+Notes

   * New Contributors
       * ICLAs received:
           * Qian Gao (gaoqian126@126.com), No intentions submitted (is this
           Albert Gau from Cloud Academy?)
           * Manoj Mishra (manojmishra404@gmail.com)
           (https://github.com/manojkmishra), Looking at integrating the "Karate" test
           framework into OpenWhisk working with Rahul.
           * Rahul Tripathi (er.rahultr@yahoo.com)
           (https://github.com/rahulqelfo), Leading the "Karate" test framework
           integration (proposed). See https://github.com/rahulqelfo/ow-karate
           * Justin Halsall, IBM Developer Advocate based in NYC, Submitted
           the Ruby runtime, helped update/correct website content, added CLI and
           wskdeploy to Homebrew to provide convenient installs on Linux, Mac, and
           Windows.  Seeks to improve end-user experience and documentation.
           * Kei Sawada (k@swd.cc)(https://github.com/remore) (@remore), Red
           Hat, DevOps consultant, No intentions submitted.
       * Joined Community Interchange calls and introduced themselves:
           * Mparuthickal (Matthew) - NYC, last 4-5 months been exploring OW,
           delivering all data fabric via OW api
           * Viay - also trying to inc. OW in our environment, doing PoC using
           OW last 2 months
           * Sam Baxter - 2nd call, phd student at UMass an IBM intern,
           looking at long-running computations using javascript
           * Spencer Krum, Similar job as Justin, works at IBM as an advocate;
           wishes to become active in community.
           How has the project developed since the last report?
    Emphasis on these areas have been featured since last report:
       * Google Knative announce
           * The announcement of Knative has elicited LOTS of discussion on
           dev list and during interchange calls, as well as proposals on the Wiki, as to
           how OpenWhisk can better align/position itself relative to this Kubernetes
           (family) technology.  See some of the proposal discussions:
               * Knative, Kubernetes, and Apache OpenWhisk
               * Prototyping for a future architecture
               * Proposal on a future architecture of OpenWhisk
               * Kafka and Proposal on a future architecture of OpenWhisk
               * Simplifying configuring OpenWhisk Components (#3984)
       * Naver has asked to be listed as both a project Supporter and an
       acknowledged OpenWhisk provider
           * Logo added: http://openwhisk.apache.org/community.html#supporters
       * Release process
           * Please see incubator-openwhisk-release (code, tools,
           documentation), see demo (as of 2/28):
           https://www.youtube.com/watch?v=qkqenC5b1kE
           * So far we have release the following components
               * [RESULT][VOTE]: Release Apache OpenWhisk (Incubating): main
               module 0.9.0 [RC2]
                   * https://lists.apache.org/thread.html/44d91b570ba51e7c88eff59aaca04a83fcad706bdabf4614baadac3f@%3Cdev.openwhisk.apache.org%3E
               * [RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1:
               OpenWhisk catalog and apigateway
                   * https://lists.apache.org/thread.html/8df308901539b825466505e7e51df32ba511fa2a39de8335a694bd05@%3Cdev.openwhisk.apache.org%3E
               * [RESULT][VOTE] Release Apache OpenWhisk (Incubating): Client
Go and CLI 0.9.0 [RC1]
                   * https://lists.apache.org/thread.html/7985c7ad9528fada0efa4093d67ae47d78ba0dcf2f1f7f5916570f69@%3Cdev.openwhisk.apache.org%3E
               * [RESULT][VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1:
OpenWhisk wskdeploy
                   * https://lists.apache.org/thread.html/caea29e3b3c8ea56f5bb3e40ee4b57153787ef193dc64ff63024230b@%3Cdev.openwhisk.apache.org%3E
           * with these components being prepared for the voting process:
               * Runtimes (i.e., NodeJS, Python, Java, Go, Ruby, Swift, etc.)
                   * The comm. is currently discussing how to align versions
                   (i.e., rebase to same version level) for all runtime components
                   (e.g., Java, JS, Python, Ruby, etc.) now:
                   * Re: [DISCUSSION]: Proposing to use 1.12.0 as the version
                   for all runtimes for the first-time
                       * https://lists.apache.org/thread.html/7df7764fc6a0f33580ab5666645b61d857c5492ca6e1d2438c2518e8@%3Cdev.openwhisk.apache.org%3E
               * Providers (i.e., Alarms, Kafka/MessageHub, Cloudant/Couch)
            * The community anticipates producing a combined 1.x release (of
            all components at once) in the near future under a single tar.gz.
       * Website revamp
           * See proposal here (with proof that no information was lost in
           transitioning):
               * OpenWhisk Website Redesign:
https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Website+Redesign
           * Apache Compliant: Updated to be fully compliant with Apache
           standards: see https://whimsy.apache.org/pods/project/openwhisk
           * Canonical starting point for all things Apache OpenWhisk
               * Role-based
                   * The entire website was revamped and streamlined to
                   include only current info targeted to 2 roles: Developer and Operator
                   * See Documentation:
                   http://openwhisk.apache.org/documentation.html
                   * Indexed all content and added left-side navigation
               * Provided initial "getting started" examples for all language
               runtimes (using CLI and wskdeploy
               * Leveraged github repo content, and created proper linkage to
               further resources (no broken links)
               * Assured we had no redundant information
           * leverage CWiki
               * In addition, we cleaned up (and organized) the project
               Confluence Wiki: https://cwiki.apache.org/confluence/display/OPENWHISK
               * and the Cwiki content now has proper ANCHORS that we
               reference from our project website.
           * Media Adaptive Content: Verified website worked in all major
           browsers and on all device form-factors (mobile, tablet, and desktop)
       * Security enhancements
           * PureSec contacted PPMC about a runtime security vulnerability,
           Rodric Rabbah took the lead in addressing and followed the Apache process (as
           the project is mature for an Incubator project and we are aware that
           companies have OW in production)
               * [CVE] CVE-2018-11756 PHP Runtime for Apache OpenWhisk
               * [CVE] CVE-2018-11757 Docker Skeleton Runtime for Apache
               OpenWhisk
            * Here is the Apache OpenWhisk project blog (Medium) explaining
            the vulnerability and how it was closed by the team:
                 * https://medium.com/openwhisk/security-and-serverless-functions-b97618430db6
       * Scalability / Performance / Testing
            * Presentation/proposals to integrate the Karate Web Service Test
            Framework into OW. Intent is not to overlap or replace exiting Scala
            tests but to allow Java developers the ability to submit new test cases
            more easily. See
            https://github.com/intuit/karate.
               * Thread: OpenWhisk Karate Based BDD Functional and Performance
               Tests
           * BDD Test Cases Contribution to complement existing test cases and
           coverage
       * Runtime updates:
           * New runtime for the Ballerina language: Proposing Ballerina
           Runtime for OpenWhisk
           * Github repo.:
           https://github.com/apache/incubator-openwhisk-runtime-ballerina
       * Other Notable discussions/changes/issues/features:
           * [Discussion] Use TransactionID as ActivationID
               * Re: Proposal: Memory Aware Scheduling
           * logging baby step -- worth pursuing?
           * Pluggable API Gateways
                * Re: AI Actions as a first-class citizen in OpenWhisk
           * MiniWhisk: what you think?
           * Proposing Lean OpenWhisk
           * System overflow based on invoker status
           * Add support for microkernels instead of containers

How would you assess the podling's maturity?  Please feel free to add your own
commentary.

  [ ] Initial setup
  [X] Working towards first release  (nearly complete, see above)
  [X] Community building
  [X] Nearing graduation
  [ ] Other:

Comments:
   * Need greater variety of contributors and contributing companies

Date of last release:
   * Various, by component, see above for details

When were the last committers or PPMC members elected?
   * New Committers+PPMC:
       * Ben Browning, Red Hat
       * Brendan McAdams, Red Hat
       * Sven Lange-Last, IBM
       * Tyson Norris, Adobe, added to PPMC (already a Committer)
   * New Committers:
       * No new Committers

Signed-off-by:

 [x] (openwhisk) Bertrand Delacretaz
    Comments:
 [X] (openwhisk) Jim Jagielski
    Comments:
 [ ] (openwhisk) Isabel Drost-Fromm
    Comments:

20 Jun 2018

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.  Additionally, it now provides options to
host the platform components as Docker containers on various Container
Frameworks such as Mesos, Kubernetes, and Compose.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 * Produce our first source code release under Incubator (automation work
 is now complete here https://github.com/apache/incubator-openwhisk-release).
 We believe that the process to release will be initiated in the next 2
 weeks.
 * Increase contributions to ensure all project repos are maintained. and
 address Issue / PR backlog.
 * Close legal transferred of Trademark handoff for "OpenWhisk" name and
 logo to ASF

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 * Issue backlog building on incubator-openwhisk is still a major issue
 (partly due to #3 above). As of this report, the "open" issue backlog is
 365 and open PR is 55. Need to prioritize and work to reduce while
 advancing performance/security/deployment issues.

 * Trying to add more active Committers to augment those who have dropped
 off in their activity; however, we have reached an impasse where potential
 new Contributor pull requests are not getting timely reviews/merges to
 provide a resume' for adding to the Committer roles.

 * It seems that Apache Infra. will not provide us servers to host a
 staging
 environment that would help us perform needed staging testing on Pull
 Requests.  This means that independent testing needs to be done by members
 (companies). We have explored a corporate donation as suggested (ala Spark
 and SystemML), but this does not seem possible at this time.

 * Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
 executed; need to identify process for this.
 Discussion started w/ Apache legal via "legal-discuss" mailing list with
 subject "Trademark handoff for "OpenWhisk" name and logo".
 IBM intends to hand-off ownership of trademarks at time of graduation.

How has the community developed since the last report?

 * "dev" mailing list activity has been down with the exception of work
 around the new Go language runtime (mostly April).  It appears that 2Q
 conferences may be partly to blame with corporate Committers being
 preoccupied.

 * incubator-openwhisk Github stars: 3218 (+341 since last report)

 * incubator-openwhisk GitHub forks: 616 (+72 since last report)

 * Slack community We're ~800 members and it is really active, from both
 end users or the project and contributors

 * The  bi-weekly Zoom "Technical Interchange" continues to be well
 received and attended. Complete videos posted to OW YouTube channel and detailed
 notes to our CWIKI. YouTube Channel: Apache Meetings Playlist
 (https://www.youtube.com/channel/UCbzgShnQk8F43NKsvEYA1SA)

 * CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting Notes
   * 2018-05-23 OW Tech Interchange - Meeting Notes
   * 2018-05-09 OW Tech Interchange - Meeting Notes
   * 2018-04-25 OW Tech Interchange - Meeting Notes
   * 2018-04-11 OW Tech Interchange - Meeting Notes
   * 2018-03-28 OW Tech Interchange - Meeting Notes
   * 2018-03-14 OW Tech Interchange - Meeting Notes

New Contributors

 * Moritz Raho: (Adobe) intern, focus on user/dev experience
 * Nareej: (Adobe) started using OpenWhisk for internal notifications,
 looking to become a contrib.
 * Andy Steed (Adobe): starting to work on OW project, getting on-boarded
 * Dan Klco, comes from Apache Sling looking at OW and Java tooling…
 * Eric in RTP (IBM) plans to help with runtime work; newer to open source
 openwhisk
 * Justin Halsall (IBM) dev. looking at creating a Ruby runtime
 * Dominic Kim: (Naver) working for Naver in Korea on their platform using
 OW, interested in improving scheduling algorithms.
 * Sam Baxter - no intentions described yet
 * Tzu Chiao - no intentions described yet

How has the project developed since the last report?

Emphasis on these areas have been featured since last report:

 * Release process, See incubator-openwhisk-release (code, tools,
 documentation), see demo (as of 2/28) on YouTube
   * Automated and Manual release process complete and documented:
   * Instructions for Release Managers.
   * 100% of release candidate source code has Apache 2 license headers or
   a documented exception as allowed by ASF policy (e.g., simple data or
   config files):
   * See
 https://github.com/apache/incubator-openwhisk-release/blob/master/docs/licen
se_compliance.md
   * Currently, working to assure JDK is configurable for builds.
   * See PR: Update the document regarding Open JDK and Oracle JDK
   * Codecov added: codecov coverage badge displayed

 * Security enhancements
   * Limit cipher suites used for controller https
   * Assure nginx verifies upstream ssl certs
   * Add option to encrypt redis password
   * CLI "Go client": Changing default namespace from guest to _
   * Docker runtime/SDK: add openssh client for dockerskeleton

 * Scalability / Performance
   * Make REST communication with action containers more robust - Lowered
   the time between retries from 100 ms to 10 ms because this shorter time
   should be sufficient to have routing available / the target socket
   listening.
   * Add build matrix to execute performance tests
   * Add gatling as performance test suite
   * Add gatling-throughput test for cold invocations - added a
   "ColdBlockingInvokeSimulation"
   * Split test jobs in Travis - improve Travis build performance
   (parallelize tests)
   * Make limit overcommit relative to the actual cluster size
   * Augment RuntimeManifest with stem cell configuration per kind

 * Other Notable discussions/changes/issues/features:
   * MemoryArtifactStore for unit testing and ArtifactStore SPI Validation
   * bump reference for NodeJS images, updating NodeJS6 & NodeJS8
   * Bump nginx version to latest and disable server-side information
   * Emit activation metadata to Kafka
   * Update akka to 2.5.12 and akka-http to 10.1.1
   * Various Vagrant (user, ez-up) fixes, including: increase vagrant
   disksize using plugin vagrant-disksize,
   * Fix vagrant not use runc

 * Document updates:
     * Remove Consul from "The Internal flow of processing" section
     diagram in about.md
     * Create troubleshooting guide for dependency download failures
     * Fix outdated docs in about.md and actions.md

 * Runtime updates
   * NodeJS: update nodejs6 -> 6.14.2, nodejs8 -> 8.11.2
   * Java: Make AdoptOpenJDK Eclipse OpenJ9 the Java runtime for Java
   actions
   * Swift: Update swift41 to 03-26a - update swift41 snapshot build to
   `2018-03-26-a`

  How would you assess the podling's maturity?  Please feel free to add
your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Comments:

 * Need greater variety of contributors and contributing companies

Date of last release:

 * N/A

When were the last committers or PPMC members elected?

 * New Committers+PPMC: None
 * New Committers: Vadim Raskin (2018-04-20), Jason Peterson (2018-04-18)

Signed-off-by:

 [ ](openwhisk) Isabel Drost-Fromm
    Comments:
 [X](openwhisk) Bertrand Delacretaz
    Comments:
 [X](openwhisk) Jim Jagielski
    Comments:

IPMC/Shepherd notes:

--------------------
Pulsar
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for
subscribers, and cross-datacenter replication.

Pulsar has been incubating since 2017-06-01.

Most important issues to address in the move towards graduation:

 1. Complete the Podling name search tasks. The task is in progress right
now.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 None

How has the community developed since the last report?

 The community added 7 new contributors that submitted pull-requests which
 were merged into master.

 The number of users approaching the team on the Slack channel has kept
 steadily increasing since the last report. Many users have actively
 deployed. Pulsar for evaluation and production use cases.

 Project members from several companies have organized or participated in
 several meetups, presenting Pulsar's introductions, deep-dives and hands-on
 tutorial, including recorded podcasts. We have several scheduled talks on
 Pulsar at various conferences, 2 at ApacheCon in September, one at OSCon
 in July and 2 others at Strata New York in September. A Pulsar dedicated
 meetup is being organized for next July.

 Since the last report the number of weekly-active-users on the Slack
 channel has increased from 53 to 88.

 We have reached the 1 year mark since Pulsar entering the Apache
 Incubator.
 Here is a summary of the community developments over the past year:

 1. Pulsar community has done 5 Apache releases since entering
    incubator. The release process is well documented and we have
    had 4 different release managers from 3 different companies.

 2. We have added 3 committers and PPMC members since incubation and
    there are also other candidates who have already made significant
    contributions to the project.

 3. Community of users and people interested in Pulsar has expanded
    considerably. Thanks to the months long work in improving ease of
    use, documentation and blogs, many people became aware of Pulsar
    and started playing with it, then evaluating it and finally
    putting it in production for critical use cases.

 4. We have tried to help users getting started through any
    communication channel. Even though we keep trying to encourage
    people to use the mailing list, most of the first interactions
    have been happening through the Slack channel. We also did make
    sure that:

    a) No decisions are taken in Slack channel

    b) Developers technical discussion happen mostly in Github
       issue/Pull-Request or in developers mailing list

    c) Conversations in Slack are sent to dev/user mailing list in a
       daily digest form for archival and to be searchable

    In any case Slack has been working fairly well in engaging with
    users, by providing a tool to have very quick informal
    question/answer interactions that were very appreciated by users.

  5. Overall, there were a lot of healthy discussions, with feedback
     and collaborations from people from different companies and
     different perspectives that resulted in much stronger design
     decisions and ultimately a better system.

  6. We have taken several steps to increase awareness, like blog
     posts, meetups (both dedicated to Pulsar or dedicated to similar
     topics) and presentations to conferences, like Strata or
     ApacheCon (where we have 2 talks scheduled for next September).

How has the project developed since the last report?

 23 authors have pushed 469 commits to master in the last 3 months.

 The project has made the its fifth release since joining the
 Apache Incubator (2.0.0-rc1-incubating on May 29th). This was a
 major release that culminated several months of works and lays the
 foundation for the next stage in Pulsar development. New major
 features include:
  * Pulsar Functions (Lightweight compute framework)
  * Schema registry
  * Topic compaction

 Community is actively working on next milestone, 2.1 release that
 will include several new features including:
  * Pulsar IO connector framework
  * Tiered storage
  * Go client library

 Since March, 3 new PIPs (Pulsar Improvement Proposals) for major
 feature/changes, have been submitted to the wiki and discussed in the
 mailing list.

 To recap the project developments since entering Apache Incubator:

 1. Moved to Apache BookKeeper 4.7. Before Pulsar 2.0, we were using
    a fork of BookKeeper from Yahoo, based on 4.3.1 with 245
    additional commits. Thanks to a a big effort in the BookKeeper
    community (which has a large overlap with Pulsar community), all
    these changed were merged back into mainstream BookKeeper branch
    and released in BookKeeper 4.7.0, making possible for Pulsar to
    switch over from the Yahoo fork.

 2. We have received a lot of feedback from people approaching Pulsar
    and learned a lot on how to simplify tools, documentation and
    concepts to make it easier for people to get started.

 3. Based on the same feedback and inputs, we have been adding new
    features or extended existing features to match a new variety of
    use case, some of them outside the scope the initial Pulsar
    codebase from Yahoo.

    To summarize the "major" features added in the last year:

     - Pulsar stateless proxy
     - Non-persistent topics
     - End-to-End message encryption
     - Effectively-once semantics
     - Type-safe APIs
     - Schema Registry
     - Pulsar Functions
     - Topic compaction
     - Python client library

   With more scheduled for next upcoming release 2.1:

     - Pulsar IO connector framework
     - Tiered storage
     - Go client library

 4. In addition to features, we have been trying to smooth the
    deployment of a production ready Pulsar cluster, by improving the
    documentation and providing templates for more common environments,
    such as Kubernetes, DCOS or just plain VMs with Ansible.

 5. Having exposure to many users testing and using the sytem outside
    the original Yahoo use cases has proven very effecting in helping
    identifying and resolving corner cases that were not being
    stressed before. This resulted in a much resilient system that
    can adapt better to a large array of different requirements and
    environments.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [X] Nearing graduation
 [ ] Other:

Date of last release:
 2018-05-29, 2.0.0-rc1-incubating

When were the last committers or PPMC members elected?

 2018-05-28 - Jerry Peng
 2018-05-28 - Sanjeev Kulkarni

Signed-off-by:

 [X](pulsar) Dave Fisher
    Comments: PPMC needs to work on brand management issues. Mentors are
engaging the PPMC in the issue.
 [X](pulsar) Jim Jagielski
    Comments: Also community and corporate interaction issues are being worked.
 [X](pulsar) P. Taylor Goetz
    Comments:
 [ ](pulsar) Francis Liu
    Comments:

IPMC/Shepherd notes:

21 Mar 2018

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.  Additionally, it now provides options to host the platform
components as Docker containers on various Container Frameworks such as Mesos,
Kubernetes, and Compose.


OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 Establish process for source release (automation work ongoing here
 https://github.com/apache/incubator-openwhisk-release) Increase contributions
 to maintain all project repos. Kubernetes and Mesos deployments work and
 integrations need improvement; comm, aware of lots of work being done in
 (private and public) forks.

 Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
 of?

 - Issue backlog building on incubator-openwhisk has grown significantly;
   need to prioritize and work to reduce while advancing
   performance/security/deployment issues.
    - Trying to add more active Committers to augment those who have
     dropped off in their activity. A consistent hosted, staging
     environment would help repro. issues, as well as stage PRs to test
     fixes. It had been our intent to have Apache host our staging (and
     move it out of disparate private builds within various companies).
     However, INFRA indicates they only typically allocate 1 VM per
     project for use with demos and minor things.  They indicate that
     perhaps a corporate donation is in order (ala. Spark).
    - Goal: standup testing resources at Apache and utilize for public CI
     and performance testing of OpenWhisk on Kubernetes
    - See discussion here: OpenWhisk / Kubernetes proposed epics/action
     items/questions
    - No change in status since last quarterly report
 - Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
   executed; need to identify process for this.
    - Discussion started w/ Apache legal via "legal-discuss" mailing list
     with subject "Trademark handoff for "OpenWhisk" name and logo".
    - No change in status since last quarterly report

How has the community developed since the last report?

 Mentor changes:
    - Felix Meschberger and Sergio Fernández have stepped down from being
     mentors with regrets.
    - Bertrand Delacretaz volunteered to become mentor to fill Felix' spot.
    - Jim Jagielski volunteered to become mentor to fill Sergio's spot.
 - dev mailing list usage has been relatively active
 - incubator-openwhisk Github stars: 2877 (+696 since last report)
 - incubator-openwhisk GitHub forks: 544 (+75 since last report)

 The bi-weekly Zoom "Technical Interchange" continues to be well received
 and attended. Complete videos posted to OW YouTube channel and detailed
 notes to our CWIKI. YouTube Channel:
 https://www.youtube.com/channel/UCbzgShnQk8F43NKsvEYA1SA CWiki Meeting
 Notes: OpenWhisk Technical Interchange Meeting
Notes:https://cwiki.apache.org  /confluence/display/OPENWHISK/OpenWhisk+Technical+Interchange+Meeting+Notes


New Contributors

 - Michele Sciabarra: developing a GoLang runtime w/ perf. tests
 - Seonghyun Oh: working on a Bash runtime for functions
 - Nhat Nguyen: NodeJS interest
 - Sang Heon Lee: working on CouchDB implementation for ArtifactStore (WIP)
 - Allen Servedio: identified a bug in wskdeploy, extended code to allow
   support for GitHub private repos.
 - Vipul Kashyap: RedHat, no commits yet
 - Lorna Mitchell: IBM, data service integrations (e.g., CouchDB), NodeJS,
   PHP runtimes
 - Neeraj Mangal: discussing namespace enhancements
 - Jason Peterson: IBM, maintaining packages Alarms, Push Notifications,
   Cloudant and Deploy
 - Sudipta Biswas: support S390X deployment (i.e., power architectures)
 - Kiseok Jang: Java (JVM) enhancement interest, no commits yet
 - Junyoung Sung: interest in support Bash actions (runtime), no commits yet

How has the project developed since the last report?

 Emphasis on 3 areas have been featured since last report:
 - Release process
    - See incubator-openwhisk-release (code, tools, documentation), see
     demo (as of 2/28): YouTube
       - Lots of discussion and work on developing both a manual and
        automated (source code) release process for 12 openwhisk project
        repos. that constitute the project's platform and related tooling
        (i.e., version tied).
       - All steps in release process are described in repo's markdown
        that the comm. is working to complete
       - Checklists/Runbooks created for release managers to follow
       - Automation tested with signing/hashing as per Apache requirements
       - still working on assuring all Apache license/legal/notice/change
        files are present (perhaps automated as well) issues with RAT and
        TENTACLES tools documented, working to document our exception
        lists and policies and alternative tools to verify licenses when
        not supported by RAT
 - Security enhancements
    - Now encrypting "data-in-motion" by enabling SSL between Controllers,
     Kafka and Invokers.
 - Scalability / Performance
    - Controller now uses fully scalable impl. instead of active with "hot
     standby"; lots of testing/changes to validate as optional before
     moving to promote as default on dev. list.
    - Introduced new LoadBalancer plug-in that uses Horizontal sharding;
     evaluating making it the default as perf. tests indicate notable
     improvement in controller-invoker throughput under load.
    - Improved handling of Artifact Attachments as a separate artifact (for
     storage/update/deletion) and provide alternative implementations
     (other than CouchDB), primarily Object Storage services as targets.
    - Made ActivationId implementation leaner by adopting UUID (single
     string) versus an object that wraps a UUID.
 - Other Notable discussions/changes/issues/features:
    - Added support of Time-series DBs using Kamon Tag (e.g., OpenTSDB,
     Datadog)
    - Discussions on large (size) argument support in runtimes/impacts on
     performance/configurability.
    - Updated all tools/ubuntu-setup to support xenial and later Ubuntu
     releases.
    - Implementation of runtime for Go (GoLang) actions.  New contributor
     authored new Invoker runtime and tested with 3 possible impls. for
     performance before submitting for review.
    - Action Compositions now supported in Controller and demonstrated on
     Interchange call; more changes may be coming for Controller to enable
     parallel processing.
    - Added A Pull Request (PR) template (checklist) for all code
     submissions (incubator-openwhisk) to assure they are ready for review
     and get assigned correctly.
       - https://github.com/apache/incubator-openwhisk/pull/3386
    - Action time limits are now configurable.

 How would you assess the podling's maturity?  Please feel free to add your
 own commentary.

 [ ] Initial setup
 [X] Working towards first release
 [X] Community building
 [ ] Nearing graduation
 [ ] Other:

Comments:

 Need greater variety of contributors and contributing companies

Date of last release:

 N/A

When were the last committers or PPMC members elected?

 New Committers+PPMC: Dave Grove (2018-02-08), James Thomas (2018-02-08)
 Mark Deuser (2018-02-22) New Committers: Priti Desai (2018-02-19)

Signed-off-by:

[X](openwhisk) Bertrand Delacretaz
 Comments:
[ ] (openwhisk) Jim Jagielski
 Comments:
[ ](openwhisk) Isabel Drost-Fromm
 Comments:

20 Dec 2017


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.  Additionally, it now provides options to host the platform components as Docker containers on various Container Frameworks such as Mesos, Kunernetes, and Compose.


OpenWhisk has been incubating since 2016-11-23.

   Three most important issues to address in the move towards graduation:

    1. Est. release process for ZIP of source code
    2. Increase additional company and individual Contributors to maintain all project repos.

   Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be  aware of?

    - It had been our intent to have Apache infra. to host our staging (and move it out of disparate private builds within various companies). However, INFRA indicates they only typically allocate 1 VM per project for use with demos and minor things.  They indicate that perhaps a corporate donation is in order (ala. Spark).
        - Goal: standup testing resources at Apache and utilize for public CI and performance testing of OpenWhisk on Kubernetes
        - Needed resources:
            Minimum 5 worker node kubernetes cluster.  Each worker nodes can be fairly modest (2-4 virtual cores; 4-8GB of memory)
    - Formal hand-off of OpenWhisk trademark/logo from IBM needs to be executed; need to identify process for this.
        Discussion started w/ Apache legal via "legal-discuss" mailing list with subject "Trademark handoff for "OpenWhisk" name and logo".

How has the community developed since the last report?

    - incubator-openwhisk Github stars: 2181 (+253 since last report)
    - incubator-openwhisk GitHub forks: 469 (+52 since last report)
    - dev mailing list activity continues to be active
    - The  bi-weekly Zoom "Technical Interchange" continues to be well received and attended.
      - Complete videos posted to OW YouTube channel and detailed notes to our CWIKI.
      - YouTube Channel: Apache Meetings Playlist: https://www.youtube.com/watch?v=n4l9L8wyQlk&list=PLxVTI8yc_iX4qqr_45gduBFQxhSTfJ68g
      - CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting Notes: https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Technical+Interchange+Meeting+Notes

    New Contributors of note (not comprehensive):
    - Brendan McAddams: Red Hat: Akka expert working on creating separate Akka dispatchers for CouchDB and Kafka Clients
    - Kavitha Vallari Devara: Samsung FaaS team in "Open Service Lab of Convergence Team (SW R&D Center): incubator-openwhisk organizing project directory structure.
    - Gabriel Nicolas Avellaneda: independent. CLI contributions
    - Manjiri Tapaswi: N. Caroline State Univ. (NCSU): Fixed all "good first issues" for "incubator-wskdeploy"
    - Stig Bakken, Zedge (mobile phone customization), first review of PR in Kube repo.

How has the project developed since the last report?

 OpenWhisk general developments:
 - Reorg. of "core" openwhisk directories to better match architecture
   - Removal of openwhisk cli and cli related test cases
 - Community agreed to Scala formatting guidelines; re-enforced via github pre-commit hooks
 - Focus on improved per-invocation (of Actions) performance via logging and other improvements.
   - Changed default logging backend from log4j to Logback
   - Redis is now optional on deployment
   - Support for metrics streaming (via plug-in, default Kamon).
 - Continued focus in HA/Clustering enablement while continuing to reduce reliance on Ansible for configuration. Work included:
   - Enabling Controller HA support (defaults to active cluster of 2).
   - Enabling CouchDB clustering
   - Using ZooKeeper as persistent store for InvokerId assignment
   - Adaptive timeouts for controller and nginx
   - Programmatic lazy creation of completedN and invokerN topics
 - Certificate checking for secure mode
 - Now generating maven snapshot artifacts for some sub-projects
 - Kubernetes deployment improvements:
 - Moved Travis testing to using Minikube & more current Kubernetes version (1.7.4)
 - Significant progress on supporting deploy of complete OpenWhisk system on Kubernetes, eliminating custom containers, and streamlining deploy process
 - Separation of Language runtimes into their own top-level repos. including: docker (SDK) runtime, pythin, nodejs, java, php, swift
    - Updates to Akka and focus on improving messaging
    - Updates to improve API Gateway resiliency
    - Nginx performance improved
    - NodeJS 6 upgraded to 6.11.4
    - NodeJS 8 support
    - Swift 3.1.1 now default, deprecated Swift 3

 openwhisk-package-deploy:
 - New repo created with proper license, docs, tests, and Travis CI
 - New action wskdeploy allows to deploy wskdeploy git repos
 - New "managed" sync support

 openwhisk-packages-cloudant/couchdb:
 - Update to feed action to update trigger config (dbName)
 - Update to feed action to return config and status

 openwhisk-packages-kafka:
 - New ability for feed action to return config and status
 - Update to feed action to update trigger config (topic)

 openwhisk-packages-alarms:
 - New ability for feed action to return config and status
 - New alarm trigger type interval
 - New alarm trigger type fire once
 - New StartDate and stopDate parameters for cron

 openwhisk-cli:
 - New canonical source after duplication removal from main repo
 - New open issues moved from main repo to CLI repo
 - New trigger feed lifecycles on `trigger get` and `trigger update`

Significant. discussions (dev list):
 - Warm containers
 - Are Java actions first class citizens?
 - Git commit (accreditation)
 - Moving out runtime images and tests
 - Enablement of controller clustering
 - Invoker activation queueing proposal
 - proposal to remove trigger activations when no rules are matched
 - [Scala] code style guideline
 - NodeJS 8 support
 - Use an explicit property to define type of Whisk entity

How would you assess the podling's maturity?  Please feel free to add your own commentary.

   [ ] Initial setup
   [X] Working towards first release
   [X] Community building
   [ ] Nearing graduation
   [ ] Other:

Comments:

 Need greater variety of contributors and contributing companies

Date of last release:

    N/A

When were the last committers or PPMC members elected?

    None during this period

Signed-off-by:

  [ ](openwhisk) Felix Meschberger
     Comments:
  [ ](openwhisk) Isabel Drost-Fromm
     Comments:
  [X](openwhisk) Sergio Fernández
     Comments:

20 Sep 2017

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.  Additionslly, it now provides options to host the platform components as Docker containers on various Container Frameworks such as Mesos, Kunernetes, and Compose.
OpenWhisk has been incubating since 2016-11-23.

   Three most important issues to address in the move towards graduation:

    1. Est. release process for ZIP of source code
    2. Est. release process for Docker and other platform binaries
    3. Increase additional company and individual Contributors to maintain all project repos.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be  aware of?

    - It had been our intent to have Apache host our staging (and move it out of disparate private builds within various companies). However, INFRA indicates they only typically allocate 1 VM per project for use with demos and minor things. They indicated that typically a donation is in order (ala. Spark).
      -- Note: the desire for this staging capability was expressed in the Incubator submission where we anticipated needing ~12 VMs to host each platform component and be able to load balance/schedule Functional code as part of the OpenWhisk Serverless (across multiple supported language runtimes). This would also be needed to effectively test auto-scaling/load balancing and container pools and to get accurate performance test measures.
    - Formal hand-off of OpenWhisk trademark/logo from IBM needs to be executed; need to identify process for this.

How has the community developed since the last report?

    - First substantive design changes allowing for Service Provider Interfaces (SPIs) developed within Apache community (dev list, WIki, etc.).
    - Established bi-weekly Zoom "Technical Interchange" calls that have been well received.
        Complete videos posted to OW YouTube channel and detailed notes to our CWIKI.
    - Kubernetes on OpenWhisk work hosted a few ad-hoc to continue design discussions (CWIKI has designs and comments)
      for how best to move away from Ansible deployments to self-configuring, autoscalable containers (for use in Kube, Mesos, Compose, etc.).
    - Increased interest/list/Slack traffic in general due to experiment Kube work, as it is applicable to Mesos, etc.
    - Increased community discussions (design topics, features) of substance moved to dev list.

How has the project developed since the last report?

    - incubator-openwhisk Github stars: 1928
    - incubator-openwhisk GitHub forks: 417
    - Movement to become more "pluggable" via Service Provider Interfaces (SPI), several PRs that are ongoing.
        - So far there are now interfaces for MessagingProvider.scala, ArtifactStoreProvider.scala
          and proposals for others such as LogStore, ContainerFactory, LoadBalancer,

  Sig. PRs:

    - initial work on no root ansible #2669
        This allows to deploy with no sudo/root access. Significant to enable Kube/Mesos deployments.
    - Simplify Spi implementations. #2663
        Service Provider Interfaces (SPI) become more mature as patterns emerge.
        Healthy discussion/growth area for project to allow most components to become (eventually) pluggable
        (e.g., Log, Trace, Container build, Load    Balancing, Scheduler, Routing, Message Queue, etc.)
    - Apply standard scala formatting #2650
        Coding/linting standards debated/agreed to by community (and CI automated enforcement encoded)
    - Allow multiple controllers and invokers in local environments #2633
        implement a ContainerPool which is completely independent of the underlying container driver to facilitate testing and extensibility.
        More improvements to allow different pooling of invoker containers based upon different application use case
        (new ideas generated in community) including requirements for diff. scheduling/co-tenanting,/user responsiveness (http), etc. needs.

  Sig. discussions (dev list):

    - Release for OpenWhisk
    - Releases and SPI plans
    - OpenWhisk shell tool
    - authentication models for openwhisk
    - Performance tests for OpenWhisk
    - Adaption of hosts-files
    - Default handling for HTTP web actions

How would you assess the podling's maturity?  Please feel free to add your own commentary.

   [ ] Initial setup
   [X] Working towards first release
   [X] Community building
   [ ] Nearing graduation
   [ ] Other:


Comments:

    Need greater variety of contributors and contributing companies

 Date of last release:

    N/A

When were the last committers or PPMC members elected?

    - Tyson Norris, Committer, 08/31/2017
    - James Dubee, PPMC, Committer, 09/05/2017

Signed-off-by:

  [ ](openwhisk) Felix Meschberger
      Comments:
  [ ](openwhisk) Isabel Drost-Fromm
      Comments:
  [X](openwhisk) Sergio Fernández
      Comments:

21 Jun 2017

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.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 1. Moving last remaining (project website) github repo. :
         i.e., https://github.com/openwhisk/openwhisk.github.io
     under the Apache Github org.
         i.e. http://openwhisk.incubator.apache.org/
     and automatic Jenkins build to compile the static website
     (using current Jekyll) build and automate publishing
     to our incubator site. looking at using the “GitPubSub” tool:
     https://blogs.apache.org/infra/entry/git_based_websites_available
 2. Complete updating all source files with approved ASF header (incl. JS)
 3. Credentials sharing process for social media sites (e.g., Twitter,
     YouTube, Medium, etc.) to provide access to PPMC members.

     Continue working through project incubation checklists on CWIKI
     Compliance Checklist for OpenWhisk.org website.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 - Travis is still taking much longer under the Apache org. within GitHub then
   it did under the previous openwhisk.org and experiencing build time-outs.
   Developers are looking to reduce build dependencies to shorten build times
   by using pre-built Docker images, as well as optimizing CI tests.

How has the community developed since the last report?

 - Successful sessions / Shark Tank / BoF at ApacheCon NA 2017.
   - OpenWhisk booth presence very active with great interest in architecture.
 - GitHub project “Stars” = 1511 (up from 1395 last month) with 310 forks.
    - a couple new contributors in devtools/kube repos.
    - new ICLA from Vadim Raskin
 - “dev", “private” email list traffic continues to be healthy; positive
   discussion of a few new code feature/change topics.
 - requested/created new “issues” list to provide separate destination
   for GitHub issues emails / separate from “commits” and allow better
     “searchability"
 - Increased traffic on Slack “general” channel.  Install/deployment questions
   - setup/config/local build questions/errors being addressed.
 - Under our public Slack Team (openwhisk-team.slack.com).
       - Added a new channel named “kubernetes” for discussion of our new
         Kubernetes deployment (project/repo.)
 - Moving all GitHub issue emails to new “issues” list
 - Exploring forwarding “dev” Slack threads to “dev” email list

How has the project developed since the last report?
 - 29/30 Repositories moved from “openwhisk” to “apache” org. under
   GitHub successfully.
   - Addressing Travis (URL) changes repo-by-repo, fixing GitHub event/emails
     being sent to “dev” lists incorrectly,
   - Repo. topic/description changes/updates being done as encountered with
     INFRA.
 - Created the incubator-openwhisk-deploy-kube repo. to host a brand new
   deployment (still experimental) to Kubernetes.
 - Created the incubator-openwhisk-utilities repo. to host cross-project
   utilities;
   moved code scanning tool there and working through repos. to reference the
   tool in Travis.
 - Confluence WIKI
   (https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wi
     ki)
   adds/udaptes pages for:
   - Improved new Committer process / instructions
 - Incubator status site: http://incubator.apache.org/projects/openwhisk.html
   - updated all sections to be up-to-date as of 2017-05-15.
 - Active “dev” discussions on:
   - DockerContainer implementation with a MesosTask
  - Performance testing (new repo.?)
  - Potential use of PassportJS as a new “package” for OAuth integration
 - New features:
   - Progress on splitting out CLI from main project and making it “pluggable”
     (i.e., incubator-openwhisk-cli and incubator-openwhisk-client-go)
   - HA enabling of
  - improve monitoring (especially of containers) to elasticsearch.

Date of last release:

 - No release yet

When were the last committers or PPMC members elected?

 - Matt Hamann, new committer 2017-05-27

Signed-off-by:

 [X](openwhisk) Felix Meschberger
    Comments: Happy to see progress on infrastructure consolidation
 [ ](openwhisk) Isabel Drost-Fromm
    Comments:
 [ ](openwhisk) Sergio Fernández
    Comments:

15 Mar 2017

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.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 1. Moving github repos under the Apache Github Org (organization move,
    repository renames), first 2 repos. moved; issues identified and being
    worked.
 2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org,
    update openwhisk.org to be Apache compliant (pre-req is repo. move
    completion so that we can generate site via Jenkins/Apache tooling)
 3. Working through project incubation checklists on CWIKI
    Compliance Checklist for OpenWhisk.org website

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - Travis CI takes hours to process a PR on Apache Org; whereas it takes
   minutes under current OpenWhisk org.
   - The root cause is that Apache has 185 repos enable with Travis[1], but
     only an allocation of 30 concurrent builds. OpenWhisk typically needs 5
     concurrent build slots by itself continually.
 - Many of the OpenWhisk’s repos. have cross-build dependencies (primarily
   for Travis CI tests) this may will cause issues as repos. are brought
   over 1 at a time if forwarding links are not preserved by GitHub.
 - There may be issues with Committers in China being able
   to enable 2FA since it does not work with their cell phones and the
   alternative encryption tool seems to be blocked. Investigating with
   infra.

How has the community developed since the last report?

 - Committers have begun enable 2FA for GitHub and enable cross-
   authentication to their Apache accounts using GitBox.
 - “dev", “private” email list traffic continues to be healthy; positive
   discussion of a few new code feature/change topics
 - GitHub project “Stars” = 1144 (up from 1024 last month).
   - a few new contributors in package deployment tool repo.
   - more active discussions occurring on “dev” list.
 - Created new public Slack Team (openwhisk-team.slack.com). includes
   channels:
   - “general” for general project questions and help
   - “dev” channel where notifications of all OpenWhisk GitHub Issues are
     posted.
   - “dev-pr” channel where notifications of all OpenWhisk GitHub Pull
     Requests are posted.
   - Note: all development related discussions are directed to our “dev”
     mailing list.

How has the project developed since the last report?

 - Updating existing project code scan tools used in Travis CI to check for
   ASF license header in files.
 - Confluence WIKI
   (https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wiki)
   added pages for:
   - Accessing Apache GitHub as a Committer
   - GitHub How to Submit Pull Requests
   - Developer Best Practices
 - Active discussion on:
   - Configuration through environment vs. Consul KV
   - vanity urls for web actions
   - Exposing garbage collector for nodejs runtime
 - New features: webactions, official support for annotations
 - New repo.: https://github.com/openwhisk/openwhisk-GitHubSlackBot
    - This bot is designed to post updates to Slack when a GitHub pull
      request is ready to merge or a list of pull requests are under review
      for certain days and haven't merged.
 - Submissions to “dev” list for new articles, use cases (new contribs.)
 - New features: webactions, official support for annotations
 - Multiple sessions submitted for ApacheCon NA. In addition, submitted for
   panel talk and lightning talks.

Date of last release:

 - No release yet

When were the last committers or PPMC members elected?

 - Ioana Baldini, new committer 2017-02-09
 - Justin Berstler, new committer 2017-02-20

Signed-off-by:

 [X](openwhisk) Felix Meschberger
    Comments:
 [ ](openwhisk) Isabel Drost-Fromm
    Comments:
 [X](openwhisk) Sergio Fernández
    Comments:

      Podling still struggling with landing on ASF infrastructure, although
      slowly making progress.

27 Feb 2017

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.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 1. Moving github repos under the Apache Github Org (organization move,
    repository renames)
 2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org,
    update openwhisk.org to be Apache compliant
 3. Review and update project checklist
    http://incubator.apache.org/projects/openwhisk.html

 Some items should be mark done (around infra), CLA's have been confirmed
 for all Committers. URL/links need to be updated.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - No issues so far

How has the community developed since the last report?

 - All Initial Committers now have ICLA’s and have access to private email
   list
 - Nearly all pre-Incubator active contributors have signed ICLAs, a few
   new contributor ICLAs have been received
 - Project GitHub (all repos.) now govern access via 3 “Teams” Committer
   (write), Contributor-CLA (read), Contributor (read/default)
 - “dev", “private” email list traffic continues to be healthy; positive
   discussion of a few new code feature/change topics
 - GitHub project “Stars” = 1024 (a nice binary number), up a couple dozen
   from last month

How has the project developed since the last report?

 - Updated CONTRIBUTING.md to ref. Apache processes, Added CREDITS.txt to
   all repos., in process of changing all code headers to use Apache
   approved text. Need to update Travis CI checks to look for new header
   (per repo. basis)
 - Confluence WIKI established:
   https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wiki
   - added project overview and contributor/committer role/process
     descriptions
 - website updates continue, now include “Incubator” disclaimer, working
   issues opened by community to list “supporters” and provide a form to
   submit to request to be added.
 - deprecated “whisk” object for Nodejs6 runtime (javascript)
   actions/functions in favor of single dictionary and use of Nodejs
   built-in “promises”
 - Size limits discussed and being updated for per-request/response for
   actions (and sequences) to preserve performance/reliability
 - Discussing proposals for the proper use and optimization of KV stores
   for configurations information (along with Ansible for deployments)
 - API gateway moved to support LUA as plug-in model, added OAuth support.
   Client ID/secret validation, Dynamic upstream routing using Redis
 - An OpenWhisk plug-in contribution was accepted for the serverless.com
   framework
   https://serverless.com/blog/openwhisk-integration-with-serverless/

Date of last release:

 - No release yet

When were the last committers or PPMC members elected?

 - No activity

Signed-off-by:

 [ ](openwhisk) Felix Meschberger
 [ ](openwhisk) Isabel Drost-Fromm
 [X](openwhisk) Sergio Fernández

Shepherd/Mentor notes:

 John D. Ament:

   OpenWhisk is our GitHub as master guinea pig.  However, they still don't
   have source code in our organization.  Not sure what we can do to help, or
   why that isn't listed as a problem or issue.

18 Jan 2017

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.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 1. Moving github repos under the Apache Github Org
 2. Setup jenkins infra server to automate website deployment
 3. Review and update project
    [checklist](http://incubator.apache.org/projects/openwhisk.html).

 Some items should be mark done (around infra) and followup on committer
 that there is a ICLA submitted. Additionally, we add links to the project
 page to their respctive areas on our .org site and/or newly created
 COnfluence Wiki.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?

 - No issues so far

How has the community developed since the last report?

 - dev and private mailing list establish and initial activity healthy
 - New website deploy openwhisk.org with content from the Github repo

How has the project developed since the last report?

 - TBD: gather stats from Github repos commits, issues and pull requests
 - New in core: New API Auth Keys architecture, API Gateway experimental
 - New in packages: Kafka Feed
 - Added a "Dockerized" option for running the "wskdeploy" tool

Date of last release:

 - No release yet

When were the last committers or PMC members elected?

 - No one ha been elected or nominated yet.

Signed-off-by:

[X](openwhisk) Felix Meschberger
[ ](openwhisk) Isabel Drost-Fromm
[X](openwhisk) Sergio Fernández

21 Dec 2016

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.

OpenWhisk has been incubating since 2016-11-23.

Three most important issues to address in the move towards graduation:

 1. The project just entered the Incubator and infrastructure is in
    progress to be setup.
 2.
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 -

How has the community developed since the last report?

 -

How has the project developed since the last report?

 -

Date of last release:

 None yet.

When were the last committers or PMC members elected?

 -

Signed-off-by:

 [X](openwhisk) Felix Meschberger
 [X](openwhisk) Isabel Drost-Fromm
 [X](openwhisk) Sergio Fernández