Incubator PMC report for February 2018

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are presently 54 podlings incubating.  In the month of January, podlings executed five releases, we added four additional IPMC members; as well as one new podling and one retiring podling.

* Community

  New IPMC members:

  - David E. Jones
  - Kevin A. McGrail
  - Mark Thomas
  - Timothy Chen

  People who left the IPMC:

  - None

* New Podlings

  - ECharts

* Podlings that failed to report, expected next month

  - iota: no further reports expected, podling is retiring
  - Milagro: expecting podling to retire
  - Myriad: expecting podling to retire
  - Slider: A report was submitted, but missed mentor sign off.  The report indicates a move into Hadoop is going to happen soon.

* Graduations

  The board has motions for the following:

  - None

* Releases

  The following releases entered distribution during the month of
  January:

  - 2018-01-02 Apache Airflow 1.9.0
  - 2018-01-16 Apache Aria Tosca 0.2.0
  - 2018-01-17 Apache Taverna Server 3.1.0
  - 2018-01-22 Apache Traffic Control 2.1.0
  - 2018-01-27 Apache DataFu 1.3.3

* IP Clearance

  - Appreciations go out for ensuring that RocketMQ performs proper IP Clearance.  Similar reminders have gone out to DeltaSpike and TomEE.

* Legal / Trademarks

  - Multiple podlings have open tickets and emails in to legal to review open questions.  Assistance is requested to guide them, even if the answer is "work with your mentors to get an answer."

* Infrastructure

  - Work will need to begin to clean up remaining links into the retired Service Desk instance.

* Miscellaneous

  - Due to a typo by the VP Incubator, report reminders were sent out to podlings as of February 2017 instead of February 2018.  While most TLPs who incorrectly received the alerts questioned it via their dev lists, a couple of TLPs skipped on list communication and instead verified off list.

----------------------------------------------------------------------
                       Table of Contents
Airflow
Crail
ECharts
Edgent
Heron
Joshua
Livy
PageSpeed
PLC4X
Ratis
S2Graph
SDAP
ServiceComb
SkyWalking
Spot
Tamaya
Toree
Unomi

----------------------------------------------------------------------

--------------------
Airflow

Airflow is a workflow automation and scheduling system that can be used to
author and manage data pipelines.

Airflow has been incubating since 2016-03-31.

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

  1. We have had 4 releases and are working toward our 5th. We are getting better at releases.
  2.
  3.

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?
1. We had our forth official release 1.9.0 on Jan 2, 2018.
2. Since our last podling report 4 months ago (i.e. between Sept 25 & Feb 8,
   inclusive), we grew our contributors from 315 to 385
3. Since our last podling report 4 months ago (i.e. between Sept 25 & Feb 8, 
   inclusive), we resolved 331 pull requests (currently at 2128 closed PRs)
4. Since being accepted into the incubator, the number of companies officially 
   using Apache Airflow has risen from 30 to 132, 18 new from the last podling
   report.


How has the project developed since the last report?
  See above : 331 PR resolved, 70 new contributors, & 18 new companies 
  officially using it.

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-01-02

When were the last committers or PPMC members elected?

  2017-11-30 joygao a.k.a Joy Gao (committer/PMC)

Signed-off-by:

  [ ](airflow) Chris Nauroth
     Comments:
  [x](airflow) Hitesh Shah
     Comments:
  [x](airflow) Jakob Homan
     Comments: Ready for graduation

--------------------
Crail

Crail is a storage platform for sharing performance critical data in
distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.

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

  1. Community building
  2. Improve project visibility
  3. Create the first release

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

* No issues require attention at this time.

How has the community developed since the last report?

* We are trying to advertise Crail to attract more people
  to contribute and/or use it. In that respect, we got a
  presentation at this years SF Spark Summit accepted, where
  we will talk about Crail deployment in the Spark context.

How has the project developed since the last report?

 * Code transfer to apache.org complete
 * Project website up, working on improvements and compliance
 * Working on adapting Crail build process to new (Apache)
   environment.

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:

 * N/A

When were the last committers or PPMC members elected?

 * 2017-11-01 (entering incubation)

Signed-off-by:

  [x](crail) Julian Hyde
     Comments:
       Well done getting the web site up and the source code into
       ASF git. It feels like the project is really up and running.
       Next steps are a release and podling name search.
  [x](crail) Luciano Resende
     Comments:
  [ ](crail) Raphael Bircher
     Comments:


--------------------
ECharts

ECharts is a charting and data visualization library written in JavaScript.

ECharts has been incubating since 2018-01-18.

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

  1. Get all ICLA signed of initial committers.
  2. Move GitHub repository to apache/incubator-echarts, update license to apache v2.
  3. Working towards first ASF release.

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?

  N/A(This is the first report); most developers have signed ICLAs, SGA is in
  flight.

How has the project developed since the last report?

  N/A(This is the first report)

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

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

Date of last release:

  N/A(This is the first report)

When were the last committers or PPMC members elected?

  2018-01-18(entering incubation)

Signed-off-by:

  [X](echarts) John D. Ament
     Comments:
  [ ](echarts) Daniel Gruno
     Comments:
  [ ](echarts) Kevin A. McGrail
     Comments:
  [X](echarts) Dave Fisher
     Comments:

--------------------
Edgent

Apache Edgent is a programming SDK and micro-kernel style runtime
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry Pis or smart phones). Working in
conjunction with centralized analytic systems, Apache Edgent provides
efficient and timely analytics across the whole IoT ecosystem: from the
center to the edge.

Edgent has been incubating since 2016-02-29.

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

  1. Create and expand a diverse community of contributors and committers
     around the Edgent project.
  2. Attracting at least another independent committer/ppmc member.
  3. Finding further real world users of Edgent

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

  Community growth and participation continues to be an issue. One of the 
  two active committer/PPMC members is retiring at the end of February
  and the level of their continuing participation is unclear.
  But synergy with Apache PLC4X is encouraging.

How has the community developed since the last report?

  * Apache PLC4X is very interested in and promoting Apache Edgent as
    part of their overall story.  An initial Edgent connector was created
    and contributed to PLC4X.  Christofer Dutz demonstrated Edgent
    working together with PLC4X at the IoT Hessen Meetup at end of
    December and at Nortec Hamburg (Industrial fair).
  * subscribers to our mailing list are steady

How has the project developed since the last report?

  * Apache Edgent 1.2.0 was released.  The release is the culmination
    of the conversion to Maven and includes a number of enhancements and
    bug fixes. Binaries are now available from Nexus and Maven Central
    to make it easier to use Edgent.
  * Edgent Samples are now available via the new GitHub repository
    apache/incubator-edgent-samples.
  * JIRA and commits show continued activity on the project.
  
How would you assess the podling's maturity?

  Edgent is making slow but consistent progress towards graduation. While we
  don't yet meet the diversity requirements, we put emphasis on community
  growth through outreach which will ultimately pave the way for additional
  committers and contributors.

  Additionally, before we graduate it is important that we find users
  outside of IBM. As most Edgent committers are employed by IBM, external
  stakeholders help ensure long term contribution to the project.

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

Date of last release:

  2017-12-14  Apache Edgent 1.2.0

When were the last committers or PPMC members elected?

  In August 2017, we added Christofer Dutz as a new committer
  and PPMC member.


Signed-off-by:

  [ ](edgent) Daniel Debrunner
     Comments:
  [ ](edgent) Luciano Resende
     Comments:
  [X](edgent) Justin Mclean
     Comments:
  [X](edgent) John D. Ament
     Comments:

--------------------
Heron

A real-time, distributed, fault-tolerant stream processing engine.

Heron has been incubating since 2017-06-23.

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

  1. Finish bootstrapping project, IP clearance, initial website
  2. Expanding the community and adding new committers
  3. 1st ASF release

Migrating the code to Apache is still stalled, pending the SGA from Twitter. We've recently received word that there is progress on this front and that the SGA should be forthcoming.

The Heron team has a migration plan[1] forward into Apache. This plan is mostly on hold as Twitter is not moving forward with the code migration until after the SGA has been submitted.

1 - https://lists.apache.org/thread.html/a83095cd44e09fa179c4b5034e04acdb055a671406f1501a796700e0@%3Cdev.heron.apache.org%3E 

How has the community developed since the last report?

  * The number of contributors to the project has increased from 71 to 82 since the last report.


How has the project developed since the last report?


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

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

Date of last release:

  No Apache releases as of yet, but 6 non-Apache releases have been made in this reporting period. The first Apache release will happen after the code import.

When were the last committers or PPMC members elected?

  N/A, still bootstrapping the project.

Signed-off-by:

  [X](heron) Jake Farrell
     Comments:  Code import to ASF currently waiting on SGA from Twitter, despite this the community is continuing positive growth around the project and lists 
  [ ](heron) Jacques Nadeau
     Comments:
  [ ](heron) Julien Le Dem
     Comments:
  [ ](heron) P. Taylor Goetz
     Comments:

IPMC/Shepherd notes:
  Dave Fisher: For the IPMC - how long do we wait for Twitter to execute the SGA? The committers from Twitter aren't or can't say what the status is.


--------------------

Joshua

Joshua is a statistical machine translation toolkit

Joshua has been incubating since 2016-02-13.

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

  1. Draft Graduation Resolution
  2. Identifying specific use cases that Joshua might excel at.
  3. Attracting active developers and users.

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

Joshua PPMC are in the process of moving towards an initial 
graduation resolution draft.

How has the community developed since the last report?

The PPMC has decided not to use the 7.X branch as new master.
Current master branch has more features and we have decided to
use it as the basis for moving forward.

How has the project developed since the last report?

New work is going in to updating the Homebrew Formula. This
will make Joshua available with some 50 or so language packs.
Essentially, this will make Joshua the most comprehensively
packaged open source machine translation library available.

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
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-06-22

When were the last committers or PPMC members elected?

  - 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC +
    Committership.
  - 2016-11-16 Tobias Domhan (tdomhan) joins the Joshua PPMC + Committership.
  - 2016-11-02 Max Thomas (mthomas) joins the Joshua PPMC + Committership.

Signed-off-by:

  [ ](joshua) Paul Ramirez
     Comments:
  [X](joshua) Lewis John McGibbney
     Comments:
  [ ](joshua) Chris Mattmann
     Comments:
  [ ](joshua) Tom Barber
     Comments:

--------------------
Livy

Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.

Livy has been incubating since 2017-06-05.

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

  1. Grow the community and continue to involve more users and contributors
  2. Grow more committers to maintain the project
  3. Solidify our release cadence

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

N/A

How has the community developed since the last report?

Activity on the dev mailing list increased.

How has the project developed since the last report?

We released Livy 0.5.0-incubating with features including:
  - Code autocompletion
  - Spark SQL support
  - Sharing variables across jobs
  - Multi-line output for statements
  - Using multiple languages in a single session
  - Building with Scala 2.11

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

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

Date of last release:

  2018-02-05

When were the last committers or PPMC members elected?

  2017-09-18

Signed-off-by:

  [X](livy) Bikas Saha
     Comments:
  [ ](livy) Brock Noland
     Comments:
  [X](livy) Luciano Resende
     Comments:
  [X](livy) Jean-Baptiste Onofre
     Comments:

--------------------
PageSpeed

PageSpeed represents a series of open source technologies to help make the web
faster by rewriting web pages to reduce latency and bandwidth.

PageSpeed has been incubating since 2017-09-30.

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

  1. Community building 
  2. Wrap up ASF license policy compliance
  3. Create a first release

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 dev list is showing much more activity since the last board report:
- Gitbox notifications are now reflected to dev@
- Most discussions by devs have had dev@ looped in

One of the original team members from Google has been invited to join
as a PMC member/committer.

Limited contributions from outside of the initial committer group:
Documentation fixes, cpanel support.

How has the project developed since the last report?

- The initial code drop has been performed
- The project was voted to switch to Commit-to-Review while we work
  on license compliance and lots of small changes are anticipated.
- It looks like RAT compliance is close to being done.
- A first pass for assembling NOTICE and LICENSE for mod_pagespeed
  is under review.
- Dependencies have been updated, a reliability fix was merged
- There have been discussions on designs for new features

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:

Date of last release:

  N/A

When were the last committers or PPMC members elected?

  2017-09-30 (entering incubation, one new member is pending acceptation)

Signed-off-by:

  [ ](pagespeed) Jukka Zitting
     Comments:
  [X](pagespeed) Leif Hedstrom
     Comments:
  [x](pagespeed) Nick Kew
     Comments:
  [ ](pagespeed) Phil Sorber
     Comments:

IPMC/Shepherd notes:
  Dave Fisher: LGTM


--------------------
PLC4X

PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.

PLC4X has been incubating since 2017-12-18.

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

  1. Building the community: The PPMC and committer group has a large percentage of 
codecentric employees, we have been recruiting people from other companies, but 
will have to continue these efforts for establishing a healthy Apache community.
Onboarding of new committers: With PLC4X several people on the team are not 
very familiar with the Apache Way. We have started and will continue our 
efforts on this onboarding.
  2. Making our first release.

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

In order to get access to some of the specifications the ASF will eventually 
have to become Members of some external foundations: OPC, EtherCat, Modbus … 
these memberships usually have a free level, that allows us to use the 
specifications but doesn’t result in any regular costs. We will have to discuss 
these details with the ASF and the other foundations.

One of the external foundations (Profinet) doesn’t have a free membership. In 
general, the CEO of the European branch of the Profinet Foundation has signaled 
that it should be possible for the ASF to become a member and have an outside 
company pay the membership fees, but we have to discuss the details (With them 
as well as the ASF).


How has the community developed since the last report?

We have finished the process of getting setup at Apache.

The Podling Name Search has been resolved successfully 
(https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-136)

In of January a list of about 40 different companies, which have indicated 
interest in PLC4X in personal discussions have been directly contacted 
regarding our project, some have subscribed to our mailing lists.
A small number of new people have been popping up on our mailing lists.

On 23rd of January Christofer Dutz had a talk PLC4X at the Nortec 2018 
conference in Hamburg (Production industry conference) 
(https://www.nortec-hamburg.de/).

We have continuing our onboarding of new Apache committers (extended emails 
with a lot of explanations on why we are doing things the way we are)
Testing coverage has been improved over the initial code base.

With Beckhoff, we managed to get a first major PLC vendor to support us with 
software as well as technical support. We hope on this having a signal-effect 
on other vendors.

How has the project developed since the last report?

Test coverage and SonarQube reported issues have been addressed hereby greatly 
increasing the quality of the initial POC code.

A lot of code and architecture reviews have been done which lead to great 
improvements in the API itself.

We have started work on a RawSocket Netty transport which is a requirement to 
implement protocols that are IP based, but are not TCP or UDP.

We have started work on implementing a driver for the Beckhoff ADS protocol.
(Beckhoff has been very helpful with providing Specs and Support for setting
up a test environment.)

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:

  None yet

When were the last committers or PPMC members elected?

  None elected beyond initial committers.

Signed-off-by:

  [ ](plc4x) Greg Trasuk
     Comments:
  [X](plc4x) Justin Mclean
     Comments:
  [X](plc4x) Luciano Resende
     Comments:
  [ ](plc4x) Stefan Bodewig
     Comments:

--------------------
Ratis

Ratis is a java implementation for RAFT consensus protocol

Ratis has been incubating since 2017-01-03.

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

  1. Work towards a beta release.
  2. Stabilize nightly build process.
  3. More committers.

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?
    5 new contributors have been added. Total 41 contributors currently.
    2 new committers have been elected.


How has the project developed since the last report?
    Jenkins setup is completed. 
    Project website is available at http://ratis.apache.org/
    62 new commits to the project. Multiple snapshot releases.

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

  [ ] Initial setup - Jenkins setup completed. Website available http://ratis.apache.org/
  [ ] Work towards 0.2-alpha has started. Plans for a beta release shaping up. Need to establish a release cadence.
  [ ] Community building - 5 new contributors. 2 new committers.
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-05-17: 0.1-alpha release
  2018-01-23: Last snapshot release
  

When were the last committers or PPMC members elected?
  2018-01-10


Signed-off-by:

  [ ](ratis) Chris Nauroth
     Comments:
  [x](ratis) Jakob Homan
     Comments:
  [x](ratis) Uma Maheswara Rao G
     Comments:
  [x](ratis) Devaraj Das
     Comments:

--------------------
S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

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

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

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?

  * Suggestion from community on interactive graph visualization feature is under development(S2GRAPH-174)
  * Initial committer who has been dormant for a while become active on(S2GRAPH-172)
		 		
How has the project developed since the last report?

  * Support GraphQL as standard web interface. (S2GRAPH-172)
  * Support Elastic Search as global index provider. (S2GRAPH-175)
  * Add Embedded RocksDB as storage backend. (S2GRAPH-166)
  * Provide java client.
    - Define public interface and change code base to only use interface. (S2GRAPH-170)
    - Implementing java client is not yet started.
	  
How would you assess the podling's maturity?
Please feel free to add your own commentary.

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

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
     Comments: 
  [ ](s2graph) Seetharam Venkatesh
     Comments:
  [X](s2graph) Sergio Fernández
     Comments: To me remains a concern if the community is able to grow outside of Kakao.

--------------------
SDAP

SDAP is an integrated data analytic center for Big Science problems.

SDAP has been incubating since 2017-10-22.

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

  1. Grow community
  2. Make formal SDAP (Incubating) releases
  3. Evangelize SDAP as an integrated data analytic center for Big Science problems

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?

The community is demonstrating the ability to VOTE decisively. 
We acquired quorum to move canonical source code development
to Gitbox.

How has the project developed since the last report?

All infrastructure and codebase(s) have successfully been
transitioned over to the ASF. Three new repositories have been 
created and initial source code imports have taken place.
Development is working through JIRA nicely.

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:

  XXXX-XX-XX

When were the last committers or PPMC members elected?

No new committers or PPMC have been added other than the
original SDAP committers.

Signed-off-by:

  [ ](sdap) Jörn Rottmann
     Comments:
  [ ](sdap) Raphael Bircher
     Comments:
  [ ](sdap) Suneel Marthi
     Comments:
  [X](sdap) Lewis John McGibbney
     Comments: SDAP is doing very well. Branding,
     trademarks, source code compliance are the
     primary issues blocking a release right now.

--------------------
ServiceComb

ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.

ServiceComb has been incubating since 2017-11-22.

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

  1. IP clearance and License clean up
  2. Community building
  3. Create a first release

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 (December 2017)?
   * Git repositories and mailing lists were set
   * The community has been working hard to get the first release out, which will be service-center 1.0.0-m1, java-chassis 1.0.0-m1 and saga 0.1.0

How has the project developed since the last report(December 2017)?

   * Java Chassis resolved 73 issues with 430 commits by 38 contributors.
   * Service Center resolved 34 issues with 124 commits by 13 contributors.
   * Saga resolved resolved 44 issues with 183 commits by 10 contributors.
   * 70 mails sent by 14 people on the dev@ list

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

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

Date of last release:

  XXXX-XX-XX

When were the last committers or PPMC members elected?
   
  None.


Signed-off-by:

  [X](servicecomb) Roman Shaposhnik
     Comments:
  [X](servicecomb) Jean-Baptiste Onofre
     Comments:
  [X](servicecomb) Timothy Chen
     Comments:

IPMC/Shepherd notes:

  Drew Farris (shepherd): At least one mentor post on the mailing lists, may have missed other (GitBox makes this hard). A great deal of activity for a young project.

--------------------
SkyWalking

Skywalking is an APM (application performance monitor), especially for
microservice, Cloud Native and container-based architecture systems. Also
known as a distributed tracing system. It provides an automatic way to
instrument applications: no need to change any of the source code of the
target application; and an collector with an very high efficiency streaming
module.

SkyWalking has been incubating since 2017-12-08.

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

  1. IP clearance.
  3. First ASF release. (SkyWalking 5.0)
  3. Further ASF culture and processes.

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

 Some GPL compile-time library dependencies were removed from the default
maven reactor. Related plugin components to the project can still be built
if the GPL dependencies are manually downloaded.


How has the community developed since the last report?

 Added a number of established committers to the PPMC, 
as it the norm in the Incubator.

 Improved understanding of usage of the Apache trademark, it use with
the project, and avoiding ASF explicit announcements during incubation.

 Community reaches out to press@apache.org whenever uncertain.


How has the project developed since the last report?

The project website has been uploaded to its new location at
 http://skywalking.incubator.apache.org/

Code wise the project has good momentum.
There has been ~40 pull requests opened and accepted, and 191 commits, 
in the last month.


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

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

Date of last release:
 n/a

When were the last committers or PPMC members elected?

 Hongtao Gao (PPMC)
 Shinn Zhang (PPMC)
 Yongsheng Peng (PPMC)


Signed-off-by:

  [x](skywalking) Luke Han
     Comments:
  [x](skywalking) Willem Ning Jiang
     Comments:
  [x](skywalking) Mick Semb Wever
     Comments:

--------------------
Spot

Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.

Spot has been incubating since 2016-09-23.

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

 1. Develop a better release process

 2. Handle additional data types for ingestion and enrichment into ODM shema

 3. Fostering more activity in the user, dev and private mail lists

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

a. Issues providing podling reports during December, January.
This is being addressed moving forward.

How has the community developed since the last report?

a. Seeing more pull requests from new contributors

How has the project developed since the last report?

a. Development on the ODM branch has been moving forward and will continue to push towards adoption into the master branch.
b. Ingest redesign underway

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

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

Date of last release:

2017-09-08

When were the last committers or PPMC members elected?

2018-01-18

Signed-off-by:

  [ ](spot) Jarek Jarcec Cecho
     Comments:
  [X](spot) Brock Noland
     Comments:
  [ ](spot) Andrei Savu
     Comments:
  [ ](spot) Uma Maheswara Rao G
     Comments:

IPMC/Shepherd notes:
  Dave Fisher: It's not clear to me where this podling has development discussions. 
  It would be good for the mentors to guide Spot to at least reflect discussions 
  on the dev@ list from Slack, Github or wherever these are happening.


--------------------
Tamaya

Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.

Tamaya has been incubating since 2014-11-14.

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

  1.release new versions compliant with configJSR/enhanced OSGi support
  2.grow the community, get more active participants
  3.graduate as the project is functionally very mature

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

We'd like to graduate after 0.4 is out, maybe Q1-2018.

How has the community developed since the last report?

New external contributor William Lieurance

How has the project developed since the last report?

Continued development of v0.4, struggled with build problems after JDK
updates, introduced rewritten Tamaya-API compliant with
Eclipse-ConfigJSR proposal (on a separate branch yet).
Integrated with Travis to get rid of build failures, updated
documentation of project, blog articles

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

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

Date of last release:

  2018-05-27 v0.3-incubating

When were the last committers or PPMC members elected?

P. Ottlinger at 2016-04-24.

Signed-off-by:

  [X](tamaya) John D. Ament
     Comments:
  [ ](tamaya) David Blevins
     Comments:

--------------------
Toree

Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.

Toree has been incubating since 2015-12-02.

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

  1.More discussion and engagement on the mailing list as opposed to "gitter"
  2.Community growth
  3.Continue to make releases

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

* No issues require attention at this time.

How has the community developed since the last report?

* The community has been working on the 0.2.0 release,
and a new RC3 should be available soon.

How has the project developed since the last report?

* Other then the work on the 0.2.0 release we have
seen some active discussions around performance, particularly
around Toree startup and an enhancement PR has been just
submitted and needs to be evaluated/reviewed by the community


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

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

Date of last release:

* 2017-02-21

When were the last committers or PPMC members elected?

* Ryan Blue was added to the PMC on 2017-04-03


Signed-off-by:

  [x](toree) Luciano Resende
     Comments:
  [ ](toree) Reynold Xin
     Comments:
  [x](toree) Hitesh Shah
     Comments:
  [ ](toree) Julien Le Dem
     Comments:
  [x](toree) Ryan Blue
     Comments:

--------------------
Unomi

Unomi is a reference implementation of the OASIS Context Server
specification

currently being worked on by the OASIS Context Server Technical Committee.
It provides a high-performance user profile and event tracking server.

Unomi has been incubating since 2015-10-05.

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

  1. Keep a good pace of releases
  2. Improve communication around the project and improve project web site
  3. Expand the communities (both developers and end-users)

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?

We are seing more new faces in the mailing list, and activity in commit is
steady. We plan to encourage more and more people to communicate through
the mailing list as well as become committers.

How has the project developed since the last report?

We are working on the 1.3.0 features as well as getting ready for version
2.0 that will integrate the new CXS GraphQL API.

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:

  2017-09-20

When were the last committers or PPMC members elected?

2017-01-23


Signed-off-by:

  [ ](unomi) Bertrand Delacretaz
     Comments:
  [X](unomi) Jean-Baptiste Onofré
     Comments: