Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2018-10-06 21: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.

2018 | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

OpenWhisk

19 Sep 2018

Report was filed, but display is awaiting the approval of the Board minutes.

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