incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "September2018" by Justin Mclean
Date Tue, 11 Sep 2018 20:46:21 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "September2018" page has been changed by Justin Mclean:
https://wiki.apache.org/incubator/September2018?action=diff&rev1=109&rev2=110

Comment:
Move OpenWhisk to correct place and fixed formatting

  = Incubator PMC report for September 2018 =
+ 
+ ** FINAL - DO NOT EDIT **
  
  === Timeline ===
  ||Wed September 05 ||Podling reports due by end of day ||
@@ -46, +48 @@

  
  === Report content ===
  {{{
- IIncubator PMC report for September 2018
+ Incubator PMC report for September 2018
  
  The Apache Incubator is the entry path into the ASF for projects and
  codebases wishing to become part of the Foundation's efforts.
@@ -161, +163 @@

  Myriad
  Nemo
  Omid
+ OpenWhisk
  Pony Mail
  Pulsar
  Quickstep
@@ -1111, +1114 @@

  IPMC/Shepherd notes:
  
  --------------------
- Pony Mail
- 
- Pony Mail is a mail-archiving, archive viewing, and interaction service, 
- that
- can be integrated with many email platforms.
- 
- Pony Mail has been incubating since 2016-05-27.
- 
- Three most important issues to address in the move towards graduation:
- 
-   1. Growing community and interest around the project
-   2. Step up pace of branch development
-   3. Fine-tune release process
- 
- Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
- aware of?
- 
-   Pony Mail is in a bit of a slumber at the moment, with the principal
-   people being busy elsewhere. This is not to say that oversight isn't
-   happening, but that the development pace has slowed significantly.
-   We hope this picks up in the foreseeable future.
- 
- How has the community developed since the last report?
- 
-   Sharan Foga has joined as a new mentor. We are assessing whether there
-   is need for more people to help out.
- 
- How has the project developed since the last report?
- 
-   Not much to report here, a few bug fixes and issues filed.
- 
- 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:
- 
- Date of last release:
- 
-   2018-02-19
- 
- When were the last committers or PPMC members elected?
- 
-   Sebastian Bazley was elected committer in Oct, 2016.
- 
- Signed-off-by:
- 
-   [ ](ponymail) Andrew Bayer
-      Comments:
-   [X](ponymail) John D. Ament
-      Comments:
-   [x](ponymail) Sharan Foga
-      Comments:Good to see community building being highlighted as something 
- to work on.
- 
- IPMC/Shepherd notes:
- wave (Dave Fisher): I would ask what this project that has become core to 
- ASF infra with lists.apache.org needs to do before graduating?
- 
- 
- --------------------
  
  OpenWhisk  
  
- 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 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).

+       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.
+    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
+    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?    
+ 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. 
+     * 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".
+     * 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.
+     * 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.
+     * 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
+         * 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.
+     * 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.
+         * 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: 
-           * 2018-08-29: https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-29+OW+Tech+Interchange+-+Meeting+Notes
+           https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-29+OW+Tech+Interch
+ ange+-+Meeting+Notes
+           * 2018-08-15: 
-           * 2018-08-15: https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-15+OW+Tech+Interchange+-+Meeting+Notes
+           https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-15+OW+Tech+Interch
+ ange+-+Meeting+Notes
+           * 2018-08-01: 
-           * 2018-08-01: https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-01+OW+Tech+Interchange+-+Meeting+Notes
+           https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-01+OW+Tech+Interch
+ ange+-+Meeting+Notes
+           * 2018-07-18: 
-           * 2018-07-18: https://cwiki.apache.org/confluence/display/OPENWHISK/2018-07-18+OW+Tech+Interchange+-+Meeting+Notes
+           https://cwiki.apache.org/confluence/display/OPENWHISK/2018-07-18+OW+Tech+Interch
+ ange+-+Meeting+Notes
+           * 2018-06-20: 
-           * 2018-06-20: https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-20+OW+Tech+Interchange+-+Meeting+Notes
+           https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-20+OW+Tech+Interch
+ ange+-+Meeting+Notes
+           * 2018-06-06: 
-           * 2018-06-06: https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-06+OW+Tech+Interchange+-+Meeting+Notes
+           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?)
+             * Qian Gao (gaoqian126@126.com), No intentions submitted (is this 
-             * 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.
+             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.
+             * 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
+             * 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
+             * Viay - also trying to inc. OW in our environment, doing PoC using 
-             * Sam Baxter - 2nd call, phd student at UMass an IBM intern, looking at long-running
computations using javascript
+             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.
+             * 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?
+             How has the project developed since the last report?
- Emphasis on these areas have been featured since 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:
+             * 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
+         * 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
+             * 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]
+                 * [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
+                 * [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]
+                 * [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
+                 * [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:
+                     * 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
+                     * 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.
+              * 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):
+             * See proposal here (with proof that no information was lost in 
+             transitioning):
+                 * OpenWhisk Website Redesign: 
-                 * OpenWhisk Website Redesign: https://cwiki.apache.org/confluence/display/OPENWHISK/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
+             * 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 
-                     * The entire website was revamped and streamlined to include only current
info targeted to 2 roles: Developer and Operator
+                     include only current info targeted to 2 roles: Developer and Operator
+                     * See Documentation: 
-                     * See Documentation: http://openwhisk.apache.org/documentation.html
+                     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
+                 * 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)
+                 * 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 
-                 * In addition, we cleaned up (and organized) the project Confluence Wiki:
https://cwiki.apache.org/confluence/display/OPENWHISK
+                 Confluence Wiki: https://cwiki.apache.org/confluence/display/OPENWHISK
-                 * and the Cwiki content now has proper ANCHORS that we reference from our
project website.
+                 * and the Cwiki content now has proper ANCHORS that we 
-             * Media Adaptive Content: Verified website worked in all major browsers and
on all device form-factors (mobile, tablet, and desktop)
+                 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)
+             * 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
+                 * [CVE] CVE-2018-11757 Docker Skeleton Runtime for Apache 
-              * Here is the Apache OpenWhisk project blog (Medium) explaining the vulnerability
and how it was closed by the team:
+                 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.
+              * 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
+                 * Thread: OpenWhisk Karate Based BDD Functional and Performance 
+                 Tests
-             * BDD Test Cases Contribution to complement existing test cases and coverage
+             * BDD Test Cases Contribution to complement existing test cases and 
+             coverage
          * Runtime updates:
-             * New runtime for the Ballerina language: Proposing Ballerina Runtime for OpenWhisk
+             * New runtime for the Ballerina language: Proposing Ballerina 
+             Runtime for OpenWhisk
+             * Github repo.: 
-             * Github repo.: https://github.com/apache/incubator-openwhisk-runtime-ballerina
+             https://github.com/apache/incubator-openwhisk-runtime-ballerina
          * Other Notable discussions/changes/issues/features:
              * [Discussion] Use TransactionID as ActivationID
                  * Re: Proposal: Memory Aware Scheduling
@@ -1299, +1332 @@

              * 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.
   
+ 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)
@@ -1327, +1361 @@

    [ ] (openwhisk) Bertrand Delacretaz  Comments:
    [ ] (openwhisk) Jim Jagielski  Comments:  
    [ ] (openwhisk) Isabel Drost-Fromm   Comments:
+ 
+ --------------------
+ Pony Mail
+ 
+ Pony Mail is a mail-archiving, archive viewing, and interaction service, 
+ that
+ can be integrated with many email platforms.
+ 
+ Pony Mail has been incubating since 2016-05-27.
+ 
+ Three most important issues to address in the move towards graduation:
+ 
+   1. Growing community and interest around the project
+   2. Step up pace of branch development
+   3. Fine-tune release process
+ 
+ Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
+ aware of?
+ 
+   Pony Mail is in a bit of a slumber at the moment, with the principal
+   people being busy elsewhere. This is not to say that oversight isn't
+   happening, but that the development pace has slowed significantly.
+   We hope this picks up in the foreseeable future.
+ 
+ How has the community developed since the last report?
+ 
+   Sharan Foga has joined as a new mentor. We are assessing whether there
+   is need for more people to help out.
+ 
+ How has the project developed since the last report?
+ 
+   Not much to report here, a few bug fixes and issues filed.
+ 
+ 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:
+ 
+ Date of last release:
+ 
+   2018-02-19
+ 
+ When were the last committers or PPMC members elected?
+ 
+   Sebastian Bazley was elected committer in Oct, 2016.
+ 
+ Signed-off-by:
+ 
+   [ ](ponymail) Andrew Bayer
+      Comments:
+   [X](ponymail) John D. Ament
+      Comments:
+   [x](ponymail) Sharan Foga
+      Comments:Good to see community building being highlighted as something 
+ to work on.
+ 
+ IPMC/Shepherd notes:
+ wave (Dave Fisher): I would ask what this project that has become core to 
+ ASF infra with lists.apache.org needs to do before graduating?
  
  --------------------
  Pulsar

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message