Incubator PMC report for December 2021

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

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 38 podlings incubating. In November, podlings executed 7 distinct releases. We added two new IPMC members, and none retired. There was one IP clearance. A couple of new podlings are under discussion, and SeaTurtle has joined the Incubator. There where no graduations last month.

A couple of podlings are heading towards graduation in the next few months. This month we were missing reports from Hivemall, Livy, PageSpeed, SDAP, Spot and Training, and they will be asked to report next month. All podlings mentioned have had a history of misisng the occasional report, and most have low levels of activity. Training is discussing possible retirement. Spot has very low activity levels and has missed multiple reports. Spots last roll call only attracted 2 PPMC members. I've requested another roll call and asked them if it is time to consider retirement.

Multiple projects were asked to use the correct URL for their KEYS files. A few projects have been using the WIP disclaimer a little too widely, and their release votes attracted -1 values. We usually had a top level project ask for a vote on their release and were unable to help them.

In recent time some of the incubator reports have been submitted late and board members have not had adequate time to review. To improve this situation:

• Report generation tools have been updated to be able to produce future report templates
• One full year (2022) of report templates have been produced
• The dates due for all of 2022 Incubator reports have been published
• ISC calendar files have been produced for all of these dates in 2022

As usual, most discussions on the mailing list were around graduations, releases, and new project proposals.

Community

New IPMC members:

• Xiangdong Huang
• Guo William

People who left the IPMC:

• None

New Podlings

• SeaTurtle

Podlings that failed to report, expected next month

Graduations

• none

The board has motions for the following:

• Hop

Releases

The following releases entered distribution during the month of November:

• Age 0.6.0
• Annotator 0.2.0
• Doris 0.15.0
• Inlong 0.11.0
• Nuttx 10.2.0
• Pegasus 2.3.0
• Sedona 1.1.1

IP Clearance

• Mvndaemon

Legal / Trademarks

N/A

Infrastructure

N/A

Miscellaneous

N/A

Table of Contents

AGE
brpc
Crail
Hop
Kyuubi
Marvin-AI
Nemo
StreamPipes
Toree
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.Community Vote for TLP graduation is started on the AGE dev mailing list.

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?

We have a new PPMC member, four new committers, and new contributors.

How has the project developed since the last report?

The project had two new releases.

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:

2021-11-30

When were the last committers or PPMC members elected?

2021-11-02

Have your mentors been helpful and responsive?

Yes.

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

Yes, PPMC is managing the podling's brand / trademarks.

Signed-off-by:

•  (age) Kevin Ratnasekera
  Comments:
•  (age) Von Gosling
  Comments: More voices come from community, we are activly discussing are we ready for graduation.
•  (age) Raphael Bircher
  Comments:
•  (age) Felix Cheung
  Comments:
•  (age) Juan Pan
  Comments: I can see more guys joining this community, good signal.
•  (age) Suneel Marthi
  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. Regular apache release
2. Adding more committer
3. Fix Branding issue

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 added one new committer named wangwei, he is an active contributor from Vivo Mobile. And we have our offline dinner meeting together on 12/3 in beijing, to get to know each other face2face.

How has the project developed since the last report?

we got our 1.0.0 version released, Since then, we will branch 1.0 out for stable release, and accept bigger feature into trunk.

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:

2021-11-30 1.0.0

When were the last committers or PPMC members elected?

2021-09-14 Wangwei

Have your mentors been helpful and responsive?

Pan Juan is very helpful, she gave us many intructions.

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

I will check it out before next pod report.

Signed-off-by:

•  (brpc) Kevin A. McGrail
  Comments:
•  (brpc) Jean-Baptiste Onofré
  Comments:
•  (brpc) Von Gosling
  Comments:
•  (brpc) Juan Pan
  Comments: Congrats, our 1.0.0 release.

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.More frequent/steady code contributions 2.New release 3.More committers

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?

No new committer since last report

How has the project developed since the last report?

Some pending issues were closed. The latest elasticity extensions we are aware of are not yet presented as a PR, unfortunately.

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:

2021-05-03

When were the last committers or PPMC members elected?

2021-05-16

Have your mentors been helpful and responsive?

Mentors are helpful and always responsive.

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

The PPMC took steps to get one non compliant use of the 'Crail' name on a web page corrected.

Signed-off-by:

•  (crail) Julian Hyde
  Comments: Activity is very low. Crail is discussing ways to increase activity.
•  (crail) Luciano Resende
  Comments:
•  (crail) Felix Cheung
  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. the community has voted on graduation and will (re)start the discussion on the incubator mailing list.

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?

The community is active and growing. Hop has hundreds of followers on each of the social media accounts. The PPMC sees an increased traction around Hop.

How has the project developed since the last report?

Hop 1.0 was released in early October. The project is working towards graduation and continues to work towards Hop 1.1.

How would you assess the podling's maturity?

•  Initial setup
•  Working towards first release
•  Community building
•  Nearing graduation: community vote passed and resolution accepted
•  Other:

Date of last release:

2021-10-05

When were the last committers or PPMC members elected?

2021-07-05 (Dave Campen)

Have your mentors been helpful and responsive?

Julian, Kevin and Francois have always been available when the Hop PPMC needed help or advice.

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

No known issues. The Hop project name was approved with [PODLINGNAMESEARCH-191](https://issues.apache.org/jira/browse/PODLINGNAMESEA RCH-191)

Signed-off-by:

•  (hop) Tom Barber
  Comments:
•  (hop) Julian Hyde
  Comments: Hop has approved the graduation resolution. Good luck with graduation!
•  (hop) Maximilian Michels
  Comments:
•  (hop) Francois Papon
  Comments:
•  (hop) Kevin Ratnasekera
  Comments:

IPMC/Shepherd notes:

Kyuubi

Kyuubi is a distributed multi-tenant Thrift JDBC/ODBC server for large-scale data management, processing, and analytics, built on top of Apache Spark and designed to support more engines.

Kyuubi has been incubating since 2021-06-21.

Three most important unfinished issues to address before graduating:

1.Gain more active contributors/committers to build a diverse community 2.Make Apache releases regularly and keep the quality for all releases 3.Improve project structure and documentation

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?

1. 4 new contributors participate in the community since the last one. There are currently 54 contributors and 9 committers.
2. 22 authors have pushed 89 commits to master and 108 commits to all branches. On master, 395 files have changed and there have been 22,900 additions and 3,545 deletions.
3. Several discussions/bug reports on the GitHub Issues/WeChat groups, etc.
4. Participate in 1 online and 1 offline meetup to share kyuubi

How has the project developed since the last report?

1. v1.4.0-incubating is in the middle of voting process
2. the community is working on implementation of RESTful API
3. Flink engine support in progress
4. Support cloud native service discovery
5. Support execute scala/spark programing code snippet

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:

2021-10-25

When were the last committers or PPMC members elected?

None

Have your mentors been helpful and responsive?

No answer.

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

 No answer.

Signed-off-by:

•  (kyuubi) Willem Ning Jiang
  Comments: It's good to see the community is growing.
•  (kyuubi) Jeff Zhang
  Comments:
•  (kyuubi) Duo Zhang
  Comments:
•  (kyuubi) Akira Ajisaka
  Comments:

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. Push packages of next release to repositories.
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?

Community has discussed new approaches to integrate Apache Marvin-AI to new schedulling softwares like Apache Airflow, Kubeflow Pipelines and Tekton. It can simplify the codebase and make Marvin more useful for many more users.

How has the project developed since the last report?

New functionalities (Minor Airflow integration, CLI capabilities) and preparation to release a new version in progress.

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:    

2019-07-18

When were the last committers or PPMC members elected?

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

New committer Lucas Cardoso (2021-09-17).

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. Address a few remaining items in the Apache Project Maturity Model
2. Grow the community

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?

• Successfully hosted three GSoC students to contribute to Nemo
• New committer added: Hwarim Hyun

How has the project developed since the last report?

• Added stream processing metrics
• Added stream processing applications
• Added hierarchical aggregation
• Explored various stream processing scheduling policies

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:

2020-12-07

When were the last committers or PPMC members elected?

September 28, 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:

•  (nemo) Hyunsik Choi
  Comments:
•  (nemo) Byung-Gon Chun
  Comments:
•  (nemo) Jean-Baptiste Onofré
  Comments:
•  (nemo) Markus Weimer
  Comments: It might be time for anothe release.

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. Make more releases
2. Complete Maturity assessment
3. Prepare graduation process

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

There are no issues right now.

How has the community developed since the last report?

• Multiple of the contributors that we mentioned in the previous report were elected as committers
• We've seen increased discussions on the dev mailing list (159 mails in October, 97 mails in November) and have many fruitful discussions
• We received an increased amount of bug reports and questions from users, which shows increased adoption
• We've seen a few applied research papers where StreamPipes was used as a basis for digital twin management
• An article about StreamPipes in the US Linux magazine which was published in March is now also available online:

https://www.linuxpromagazine.com/Issues/2021/244/Apache-StreamPipes/(languag e)/eng-US

• Community members held two talks in the ApacheCon IoT track
• Number of Twitter followers has increased (last report: 199, currently:

• Number of Github stars increased (last report: 255, currently: 274)

How has the project developed since the last report?

• During the reporting period multiple large improvements were developed by the community
• A completely renewed data explorer to visualise historic time-series data
• Advanced user and role management to handle multiple users and define individual data access
• A new stateless authentication system
• A testing framework for e2e tests to continually improve the software quality
• The community decided to merge the three repositories (incubator-streampipes, incubator-streampipes-extensions, and incubator-streampipes-installer) into one to ease the release process which had previously three release artifacts
• Currently preparations for the next release 0.69.0 are performed and we are slowly but steadily nearing towards a 1.0 release

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:

2021-07-22

When were the last committers or PPMC members elected?

2021-12-04: Patrick Philipp

2021-11-30: Hrushikesh Rao

2021-10-20: Stefan Obermeier

Have your mentors been helpful and responsive?

Yes, our mentors are helpful and responsive as usual.

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

We are actively managing the brand and did not discover any issues related to incorrect brand use. The new logo is now available in the current development version and the full rebranding will take place right after the next release.

Signed-off-by:

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

IPMC/Shepherd notes:

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

1.Increase active contributors 2. 3.

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?

Not much, the community has been trying to vote a release without much success. I am starting to think that maybe the best solution might be to try to reboot the podling and see if we can inject more new blood to the project and see if it could make a change. I will think more about this and propose something for the next report.

How has the project developed since the last report?

Very minimum discussions towards the release vote.

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:

2020-07-31

When were the last committers or PPMC members elected?

Kevin Bates was added to the PPMC on 2019-08-14

Have your mentors been helpful and responsive?

There was nothing requiring mentor intervention on the last quarter.

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

No Trademark issues

Signed-off-by:

•  (toree) Luciano Resende
  Comments:
•  (toree) Julien Le Dem
  Comments:
•  (toree) Ryan Blue
  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. Make sure that every PPMC is able to manage a release
2. Release the first version of Apache Wayang under the umbrella of the Apache Software Foundation
3. We have significant growth (stars / forks at GitHub), but we want to gain more popularity and growth the community further

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

Apache Wayang is doing the first release, and it has many iterations; almost all the -1 votes comes from license issues or related. Many members of the community comment about the lack of documentation and examples in the incubator page in a case like:

• set up well the license when you bring pieces of code from another project.
• what happens when you bring code from another source.
• How need to be the headers if you bring the code from the repository that it said is apache but does not contain headers licenses.
• How to need to be the license when you bring a code snippet or similar.
• and some another cornet cases that could happen.

How has the community developed since the last report?

The community growth is significant (according to Github), the team around Apache Wayang was present at the BOSS conference ’21 and the Apache @home conference. We also signed an LOI with the TU of Berlin to cooperate with “AGORA-EO: Indexing and Querying Earth from Federated Big Data Archives”. The TU Berlin will add federated image processing to Apache Wayang.

How has the project developed since the last report?

As we had to import and rebrand a running project we needed some time to rework the code base for fitting the ASF standards, which resulted in 8 release candidates. The incubator community spottet the issues we weren’t aware of, which allows us now to present the first release of Apache Wayang without a WIP disclaimer. We have chosen this route to make sure that the project will always fit the standards, even when we had different views. At the end all concerns and issues were solved, thanks to the Sheppards.

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:

Technology wise the Podling is a productive state, which is also reflected by cooperating with the TU Berlin. We see growing adaption in the market, especially from companies with large data processing pipelines.

Date of last release:  

No Release yet. At the moment of this report, the RC9 is under votes.

When were the last committers or PPMC members elected?

2021-03-05 : Committer

Have your mentors been helpful and responsive?

Yes, the mentors are very responsive and helpful

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

No Answer

Signed-off-by:

•  (cdutz) Christofer Dutz
  Comments: The team has done a great amount of work ruling out all issues before the first release. They didn't want to go with the WIP and wanted to get things right ... I liked that.
•  (wayang) Lars George
  Comments:
•  (wayang) Bernd Fondermann
  Comments:
•  (wayang) Jean-Baptiste Onofré
  Comments:

IPMC/Shepherd notes: