Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

TODO add narrative

## Community

### New IPMC members:


### People who left the IPMC:


## New Podlings


## Podlings that failed to report, expected next month


## Graduations
  - list podling here

  The board has motions for the following:

  - Your podling here?

## Releases

  The following releases entered distribution during the month of
  June:


## IP Clearance


## Legal / Trademarks


## Infrastructure


## Miscellaneous


## Credits

## Table of Contents  
[AGE](#age)  
[brpc](#brpc)  
[Crail](#crail)  
[Hivemall](#hivemall)  
[Hop](#hop)  
[Livy](#livy)  
[Marvin-AI](#marvin-ai)  
[Nemo](#nemo)  
[Pinot](#pinot)  
[ShenYu](#shenyu)  
[Spot](#spot)  
[StreamPipes](#streampipes)  
[Wayang](#wayang)  


--------------------
## AGE

AGE is a multi-model database that enables graph and relational models built
on PostgreSQL.

AGE has been incubating since 2020-04-29.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (age) Kevin Ratnasekera  
     Comments:  
  - [ ] (age) Von Gosling  
     Comments:  
  - [ ] (age) Raphael Bircher  
     Comments:  
  - [ ] (age) Felix Cheung  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## brpc

brpc is an industrial-grade RPC framework for building reliable and high-
performance services.

brpc has been incubating since 2018-11-13.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (brpc) Kevin A. McGrail  
     Comments:  
  - [ ] (brpc) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (brpc) Von Gosling  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## 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 unfinished issues to address before graduating:

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (crail) Julian Hyde  
     Comments:  
  - [ ] (crail) Luciano Resende  
     Comments:  
  - [ ] (crail) Felix Cheung  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Hivemall

Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.

Hivemall has been incubating since 2016-09-13.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (hivemall) Daniel Dai  
     Comments:  
  - [ ] (hivemall) Koji Sekiguchi  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Hop

Hop is short for the Hop Orchestration Platform. Written completely in Java
it aims to provide a wide range of data orchestration tools, including a
visual development environment, servers, metadata analysis, auditing
services and so on. As a platform, Hop also wants to be a reusable library
so that it can be easily reused by other software.

Hop has been incubating since 2020-09-24.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (hop) Tom Barber  
     Comments:  
  - [ ] (hop) Julian Hyde  
     Comments:  
  - [ ] (hop) Maximilian Michels  
     Comments:  
  - [ ] (hop) Francois Papon  
     Comments:  
  - [ ] (hop) Kevin Ratnasekera  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## 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 unfinished issues to address before graduating:

  1. Decision to graduate or retire
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?
The project is stable and being used for its desired purpose by a many organizations and users. 
Without any pressing need for new features there is no active development happening.
If the project retires then its unclear how users would be able to get security fixes like the one that got release in Feb 21.
Seeking the boards guidance on this situation.


### How has the community developed since the last report?
Community is quiet with some user activity.


### How has the project developed since the last report?
We have new users, but the dev community activity is pretty low.

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

### Date of last release:

  Feb 3 2021

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


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [X] (livy) Bikas Saha  
     Comments:  
  - [ ] (livy) Luciano Resende  
     Comments:  
  - [X] (livy) Jean-Baptiste Onofré  
     Comments:  I've been in touch with some potential new users/contributors.

### IPMC/Shepherd notes:



--------------------
## Marvin-AI

Marvin-AI is an open-source artificial intelligence (AI) platform that helps
data scientists, prototype and productionalize complex solutions with a
scalable, low-latency, language-agnostic, and standardized architecture
while simplifies the process of exploration and modeling.

Marvin-AI has been incubating since 2018-08-21.

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

  1. Increase activity from current contributors and community.
  2. Finish the new version of Toolbox.
  3. Release a new architecture.

### Are there any issues that the IPMC or ASF Board need to be aware of?
No.

### How has the community developed since the last report?
We had an online meeting to confirm inicial steps for the new architectural with most of members.
Our "Marvin-lab" at the university keeps attracting new postgraduate students in the artificial intelligence field.

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

  1. Minor bug fix.
  2. Last adjustments on the new toolbox version.
  3. New Architecture confirmation meeting finished.

### 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:

  2019-07-18

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

Wei Chen added as new PPMC member (2019-06-07)

### Have your mentors been helpful and responsive?

Yes.

### Is the PPMC managing the podling's brand / trademarks?

Yes.

### Signed-off-by:

  - [ ] (marvin-ai) Luciano Resende  
     Comments:  
  - [ ] (marvin-ai) William Colen  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Nemo

Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (nemo) Hyunsik Choi  
     Comments:  
  - [ ] (nemo) Byung-Gon Chun  
     Comments:  
  - [ ] (nemo) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (nemo) Markus Weimer  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Pinot

Pinot is a distributed columnar storage engine that can ingest data in real-
time and serve analytical queries at low latency.

Pinot has been incubating since 2018-10-17.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (pinot) Kishore Gopalakrishna  
     Comments:  
  - [ ] (pinot) Jim Jagielski  
     Comments:  
  - [ ] (pinot) Olivier Lamy  
     Comments:  
  - [ ] (pinot) Felix Cheung  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## ShenYu

ShenYu is a high performance Microservices API gateway in Java ecosystem, 
compatible with a variety of mainstream framework systems, supports hot 
plug. Users can write their own plugin meet the current requirement and 
future needs in a variety of scenarios, especially in large-scale scenes.

ShenYu has been incubating since 2021-05-03.

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

  1. Code repositories migration to Incubator.
  2. Website transition to Incubator.
  3. Make an Apache Release

### Are there any issues that the IPMC or ASF Board need to be aware of?

  None.

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

  * 10+ new contributors participate in the community since entered the 
  Incubator. There are currently 171 contributors and 24 committers.
  * There is regular traffic on the mailing list 
  (~217 mailing list discussions/month).
  * Number of GitHub stars increased 
  (before incubating: 3940, currently: 4689).
  * Held Bi-weekly online meetings between committers. Mainly discussed new
  features and community building.

### How has the project developed since the last report?
  
  * Rename the project name from Soul to ShenYu.
  * Establish the official website for ShenYu.
  * Refactor PredicateJudge module using SPI.
  * Optimization of GRPC plugin.
  * Add JWT plugin.
  * Add Request plugin.

### 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:

  No Release yet.

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

  May 2021

### Have your mentors been helpful and responsive?

  Our mentors have been helpful and responsive.

### Is the PPMC managing the podling's brand / trademarks?

  The PPMC manages the podling's brand / trademarks.

### Signed-off-by:

  - [ ] (shenyu) Willem Ning Jiang  
     Comments:  
  - [ ] (shenyu) Jincheng Sun  
     Comments:  
  - [ ] (shenyu) Duo Zhang  
     Comments:  
  - [ ] (shenyu) Kevin Ratnasekera  
     Comments:  
  - [ ] (shenyu) Atri Sharma  
     Comments:  
  - [ ] (shenyu) Justin Mclean  
     Comments:  

### IPMC/Shepherd notes:


--------------------
## 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 unfinished issues to address before graduating:

  1. Revive community activity (Discussion in mailing lists, increase frequency of commits)
  2. Create a new roadmap and release plan that will improve adoption
  3. Make it easier to contribute to the project (e.g. documentation, framework).

### Are there any issues that the IPMC or ASF Board need to be aware of?

  There is confusing communication with the organization.  We submitted our quarterly
  report last month.  The final report from last month noted that our report was not 
  accepted because it was not signed off.  However, we read the minutes from the Board
  that said all submitted reports were accepted, so we assumed we didn't need to worry
  about a report for another quarter.  Last night at midnight we were notified for the 
  first time that our report was due the same day.  With less than 24 hours notice, it 
  seems unlikely we'll be able to get sign-off from our mentor.

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

  We're continuing to solidify a short term and long term on a roadmap with the community 
  that will allow more contributors to focus and work on different levels of the project 
  (i.e. data modeling and schema design, use-cases, ingestion, ml, ui, dev ops, docs, etc). 
  These discussions have been delayed this quarter due to COVID and getting schedules aligned 
  relative to other workloads.

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

  The master branch of Apache Spot was largely developed for commercial but freely 
  available Hadoop software (i.e. Cloudera, Hortonworks) that now have been either 
  End of Life’d (or will be in 2022) in favor of the newer Cloudera Data Platform 
  (CDP), or have been put behind a paywall to get updates. The cloud provider 
  landscape has also changed drastically in the last few years and it's time that 
  we start looking at better support for Quickstart options in each major cloud 
  providers so we can further develop the project for the community with wider 
  platform support, and give committers better options for creating development 
  environments to more efficiently contribute to the project.

  The following topics are planned for the next set of discussions with the community 
  to determine what we focus on for the next several quarters:

  * Add more native support on cloud infrastructure and software (i.e. AWS, Azure, GCP)
    * In the short-term we can focus on AWS EMR on standing up Spot and fixing any issues 
      related to getting the software installed and working.  
    * In the long term we will want to support several cloud providers and on-premise 
      options depending on the interest of the community.  
  * Add an infrastructure module to Spot to automate creating clusters in each providers 
    we plan to support.  
    * Initially we can focus on Cloudformation support with AWS EMR.  
    * Our goal will be to generalize further in the long term with Terraform across each 
      provider.
  * Investigate and explore alternative replacement for Spot UI (i.e. Apache Supersets)
    * In the short-term Apache Supersets may give us a basic authentication and visualization 
      layer into the data landed and processed by Spot.
    * In the long-term we will need to develop a more comprehensive security and use-case 
      roadmap for the UI and determine if it makes sense to develop something from scratch.

  The next step will be to create Jira Epic’s and tasks for these items so we can start to distribute the work across 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
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2017-09-08

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

  2019-09-02

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

  Yes our mentors have been helpful. We will be engaging them more soon for guidance 
  on on-boarding new committers, as well as a few other items related to the Whimsy 
  and Clutch reports and also updating the Apache Spot Podling website as this is 
  missing a number of updates.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

  Yes.

### Signed-off-by:

  - [ ] (spot) Uma Maheswara Rao G  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## StreamPipes

StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
technical users to connect, analyze and explore (Industrial) IoT data
streams.

StreamPipes has been incubating since 2019-11-11.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed 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.

  - [ ] 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?


### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (streampipes) Christofer Dutz  
     Comments:  
  - [ ] (streampipes) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (streampipes) Julian Feinauer  
     Comments:  
  - [ ] (streampipes) Justin Mclean  
     Comments:  
  - [ ] (streampipes) Kenneth Knowles  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Wayang

Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.

Wayang has been incubating since 2020-12-16.

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

  1. Educate the new PPMCs to be able to do Apache releases
  2. Do our first Apache release
  3. Grow the community

### Are there any issues that the IPMC or ASF Board need to be aware of?


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


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


 be aware of?

Until the moment of this report it was created and didn't have any issue, because all the important issues got solved.

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

The community members are in the applying process to present in a few conferences to show Apache Wayang to the Processing Platform Community and other communities that could be interested in the project.

Also, different members of the community had meetings with possible contributors, however, nothing is concrete until the writing point of the report.

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

The main focus is the first release. The team is focusing on cleaning the code, refactoring some parts and preparing the documentation. However, it is taking more time than the estimated one, but the community members are pushing to have it done as soon as possible.

### 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:

No  XXXX-XX-XXRelease yet.

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

2021-03-05 : Committer

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

Yes, the mentors and champions are very responsive and helpful 

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

No answer.

### Signed-off-by:

  - [ ] (wayang) Christofer Dutz  
     Comments:  
  - [ ] (wayang) Lars George  
     Comments:  
  - [ ] (wayang) Bernd Fondermann  
     Comments:  
  - [ ] (wayang) Jean-Baptiste Onofré  
     Comments:  

### IPMC/Shepherd notes:




...