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 "December2018" by DaveGrove
Date Thu, 06 Dec 2018 14:54:28 GMT
Dear Wiki user,

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

The "December2018" page has been changed by DaveGrove:
https://wiki.apache.org/incubator/December2018?action=diff&rev1=73&rev2=74

Comment:
formatting of OpenWhisk podling report

  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:    
+ Three most important issues to address in the move towards graduation:    
- 
-     Improve release automation to decrease manual steps in creating release artifacts.
+    1. Improve release automation to decrease manual steps in creating release artifacts.
- 
-         Release process/automation/documentation are here https://github.com/apache/incubator-openwhisk-release).
+       a. Release process/automation/documentation are here https://github.com/apache/incubator-openwhisk-release).
- 
-         We have made the initial releases of 12 core software components.  In the process
we have developed some release automation, but there is a need to further automate the process
and formalize the mechanisms for make a coordinated release of all components.
+       b. We have made the initial releases of 12 core software components.  In the process
we have developed some release automation, but there is a need to further automate the process
and formalize the mechanisms for make a coordinated release of all components.
- 
-     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.
- 
-     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?    
- 
-     Issue backlog building on incubator-openwhisk is still a major issue (partly due to
#2 above). As of this report, the "open" issue backlog on the "main" platform repo is 397
(up from 384 as of last report). The open PR count on the main repo has held steady at around
30 (down from 50+ 6 months ago), but still 1/3 of the ready-to-merge PRs are more than 1 month
old.  The PR and Issue backlog on other project repositories is generally much lower and of
less concern than the Issue backlog on the main repo.
+    1. Issue backlog building on incubator-openwhisk is still a major issue (partly due to
#2 above). As of this report, the "open" issue backlog on the "main" platform repo is 397
(up from 384 as of last report). The open PR count on the main repo has held steady at around
30 (down from 50+ 6 months ago), but still 1/3 of the ready-to-merge PRs are more than 1 month
old.  The PR and Issue backlog on other project repositories is generally much lower and of
less concern than the Issue backlog on the main repo.
- 
-         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.
+    2. 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.  We have potential new Contribs. to front-end Runtimes
we will look to nominate ASAP, but we still lack back-end Contribs.
+    3. 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.  We have potential new Contribs. to front-end Runtimes
we will look to nominate ASAP, but we still lack back-end Contribs.
+    4. 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). Six months after a corporate donation was
made, Apache Infra. finally provided the VMs and we have started to setup for PR testing.

- 
-     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.
- 
-         If indeed we now have the infra VMs (donation?), then we need Community to “step
up” to help us setup and automate.
- 
-     Formal hand-off of OpenWhisk trademark/logo from IBM needs to be executed; need to identify
process for this. See #3 above.
+    5. 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".
+       * 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.
+       * IBM intends to hand-off ownership of trademarks at time of graduation.
- 
-     Announcements from Google (Knative) in late July and AWS (Firecracker) just last week
apply pressure on our community in order to both explain to developers/operators how OW is
differentiated from, as well as compatible with, both popular providers’ frameworks.
+    6. Announcements from Google (Knative) in late July and AWS (Firecracker) just last week
apply pressure on our community in order to both explain to developers/operators how OW is
differentiated from, as well as compatible with, both popular providers’ frameworks.
  
  
  How has the community developed since the last report?    
- 
-     dev mailing list activity – was relatively light with the main discussion topics/activity
being (reflected in comments below as well):
+     * dev mailing list activity – was relatively light with the main discussion topics/activity
being (reflected in comments below as well):
          Golang runtime and new ActionLoop (runtime)
              Interpretation of "main" for GoLang and ActionLoop docker images
              Promises (or equivalent) in Python and GoLang
@@ -1218, +1203 @@

          Other:
              Autonomous Container Scheduler v2 proposal
  
-     incubator-openwhisk Github stars: 3657 (+185 since last report)
+     * incubator-openwhisk Github stars: 3657 (+185 since last report)
  
-     incubator-openwhisk GitHub forks: 692 (+40 since last report). Note lots of more competing
projects entering the Serverless space.
+     * incubator-openwhisk GitHub forks: 692 (+40 since last report). Note lots of more competing
projects entering the Serverless space.
  
-     Slack community:
+     * Slack community:
- 
-         1,072 members (+103 from last report).  Very active in most channels from both end
users or the project and contributors
+         * 1,072 members (+103 from last report).  Very active in most channels from both
end users or the project and contributors
- 
-         To-date: 126,282 messages sent across all channels (+13956 since last report)
+         * To-date: 126,282 messages sent across all channels (+13956 since last report)
- 
-         Analytics: https://openwhisk-team.slack.com/admin/stats
+         * 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.
  
@@ -1248, +1230 @@

  
              https://cwiki.apache.org/confluence/display/OPENWHISK/2018-11-07+OW+Tech+Interchange+Meeting+Notes
  
-     New Contributors
+     * New Contributors
- 
-         ICLAs received:
+         * ICLAs received:
- 
              Manjiri Tapaswi <mptapasw@ncsu.edu>
- 
              Andreas Tsagkaropoulos <atsagkaropoulos@mail.ntua.gr>
              Neeraj Laad <neeraj.laad@uk.ibm.com>
  
-         Joined Community Interchange calls and introduced themselves:
+         * Joined Community Interchange calls and introduced themselves:
- 
              Shawn Black: Architect at a reinsurance company in St. Louis.
- 
              Stanciu - at Adobe, joined runtime team a few weeks ago
- 
              Victor: Grad. student at USC. Working on a thesis on real-time computing in
the Cloud.  Goal is looking into how to apply real-time components into OpenWhisk.
- 
              Markus: now with Red Hat
              Prabhash Rathnayake, intern at WSO2, proposed JIRA package to catalog
  

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


Mime
View raw message