Incubator PMC report for June 2024

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 currently 28 podlings incubating. In May, podlings executed 5 distinct releases and no IP clearances occurred. Several incubating proposals have been discussed on the mailing list. At least one new podling will be joining the incubator - OpenServerless. No podling graduated or retired last month. One person retired from the IPMC. Two podlings, Liminal and Toree, failed to report and will be asked to report next month, and a roll call will be performed. Liminal should probably retire at this point. There was a discussion about the requirements of project download pages and why they are needed, most of the other discussions were on releases.

Community

New IPMC members:

• None

People who left the IPMC:

• Rich Bowen

New Podlings

• Gravitino

Podlings that failed to report, expected next month

• Liminal
• Three

Graduations

• None

The board has motions for the following:

• None

Releases

The following releases entered distribution during the month of May:

• Answer 1.3.1
• Fury 0.5.0
• Fury 0.5.1
• Stormcrawler 3.0
• Streampark 2.1.4

IP Clearance

• None

Legal / Trademarks

N/A

Infrastructure

N/A

Miscellaneous

N/A

Table of Contents

Amoro
Annotator
Baremaps
GraphAr
HertzBeat
KIE
Nemo
StormCrawler
Teaclave
Training
Uniffle
Wayang

Amoro

Amoro is a Lakehouse management system built on open data lake formats like Apache Iceberg and Apache Paimon.

Amoro has been incubating since 2024-03-11.

Three most important unfinished issues to address before graduating:

1. Release our first Apache release.
2. Build and grow a diverse community.

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

Currently no.

How has the community developed since the last report?

• Attend an offline meetup hosted by StarRocks community, one of our PPMC Member (id: jinsongzhou) gave a presentation named <<Practice of lakehouse based on Apache Amoro and Apache Iceberg>>.
• 3 new contributors joined the Amoro community.

How has the project developed since the last report?

• Started the first Apache release discussion in the dev mailing list and the release manager is working towards it.
• Merged 47 PRs in last month.

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:    

N/A

When were the last committers or PPMC members elected?

2024-03-11, when the project was accepted into the incubator.

Have your mentors been helpful and responsive?

Yes, Amoro's mentors actively participate in the project, contribute insights, and help advance the project towards graduation.

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

Yes, everything is fine.

Signed-off-by:

•  (amoro) Justn Mclean
  Comments:
•  (amoro) Zhongyi Tan
  Comments:
•  (amoro) Yu Li
  Comments: Good to see new contributors joining and look forward to the ASF release.
•  (amoro) Xinyu Zhou
  Comments:
•  (amoro) Kent Yao
  Comments:

IPMC/Shepherd notes:

Annotator

Annotator provides annotation enabling code for browsers, servers, and humans.

Annotator has been incubating since 2016-08-30.

Three most important unfinished issues to address before graduating:

1. Apache Annotator is unable to produce releases due to low activity
2. PMC is largely inactive
3. Motivation to contribute is low due to inability of producing enough release votes

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

See above. Unless there is interest by new people to join the project and help getting out releases, IMHO it would make more sense to retire the podling, fork it and release it without the three-vote hurdle.

How has the community developed since the last report?

The community has not grown.

How has the project developed since the last report?

Yarn has been dropped from the project in favor of npm. Since then, a number of dependabot issues have piled up.

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: it is so stable that it is probably ready for retirement ;)

Date of last release:

2021-07-14 (0.2.0)

We tried to get out a 0.3.0 in May 2022, but it got stuck in the vote.

When were the last committers or PPMC members elected?

@reckart was the last one to join in August 2022 (waving the flag).

Have your mentors been helpful and responsive?

@BigBlueHat has prepared the previous incubator report for this project and has provided some guidance.

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

I don't know.

Signed-off-by:

•  (annotator) Nick Kew
  Comments:
•  (annotator) Tommaso Teofili
  Comments:
•  (annotator) Benjamin Young
  Comments:

IPMC/Shepherd notes:

Baremaps

Apache Baremaps is a toolkit and a set of infrastructure components for creating, publishing, and operating online maps. Baremaps has been incubating since 2022-10-10.

Three most important unfinished issues to address before graduating:

1. Reviewing the changes made to make the code and documentation website compliant with Apache standards
2. Growing the community
3. Making releases

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

We believe that most of the issues related to licensing have now been addressed. The next step is to remove the DISCLAIMER-WIP in future releases.

How has the community developed since the last report?

No new committer joined the project, but a few issues, documentation improvements, and pull requests were submitted by external contributors.

How has the project developed since the last report?  

We released a new version of Baremaps and the process went relatively smoothly. A nice collaborative effort also started to implement a GeoParquet reader and to support OvertureMaps files.

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:    

2024-04-27

When were the last committers or PPMC members elected?

2023-08-31

Have your mentors been helpful and responsive?

Yes

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

Yes

Signed-off-by:

•  (baremaps) Bertrand Delacretaz
  Comments:
•  (baremaps) Martin Desruisseaux
  Comments:
•  (baremaps) Julian Hyde
  Comments:
•  (baremaps) Calvin Kirs
  Comments:
•  (baremaps) George Percivall
  Comments:
•  (baremaps) Martin Desruisseaux
  Comments:

IPMC/Shepherd notes:

GraphAr

GraphAr is an open-source and language-independent data file format designed for efficient graph data storage and retrieval.

GraphAr has been incubating since 2024-03-25.

Three most important unfinished issues to address before graduating:

1. Release our first Apache release.
2. Growing the community(attracting more committers, contributors and users)

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

Currently no

How has the community developed since the last report?

1. We were selected for OSPP (China's GSoC) 2024.
2. 2 new contributors joined the GraphAr community.

How has the project developed since the last report?

1. Create 26 PRs in last month.
2. Discuss and draw up road map.
3. Implement the definition of format with Protobuf.
4. Improve the release and verify document.

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:

We are working towards our first release

When were the last committers or PPMC members elected?

GraphAr has been in incubation since March 25th, 2024. As of yet, no new committers have been elected for the project.

Have your mentors been helpful and responsive?

Yes

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

We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-221)

Signed-off-by:

•  (graphar) Calvin Kirs
  Comments:
•  (graphar) tison
  Comments:
•  (graphar) Xiaoqiao He
  Comments: LGTM. +1 for looking forward to seeing the first release.
•  (graphar) Yu Li
  Comments: Good to see new contributor joining the community and look forward to the first ASF release.

IPMC/Shepherd notes:

HertzBeat

HertzBeat is an easy-to-use, open source, real-time monitoring system. It features an agentless architecture, high-performance clustering, Prometheus compatibility, and powerful custom monitoring and status page building capabilities.

HertzBeat has been incubating since 2024-04-05.

Three most important unfinished issues to address before graduating:

1. Publish 1st Apache release.  
2. Grow the community and attract more users.

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?

Over the past month, the project has successfully attracted 4 new contributors, some of whom has shown great promise and potential to be considered for committer status in the future. Excluding merges, 26 authors have pushed 105 commits to master and 156 commits to all branches. On master, 792 files have changed and there have been 22,365 additions and 5,961 deletions.

How has the project developed since the last report?

During the past month, HertzBeat has fixed the incompatible protocol LGPL license package, has used Apache Jexl and EclipseLink to replace Hibernate and Avaitor. It has added support for custom pulgin, support hugegraph, openai, Apache Yarn, Hdfs monitoring, support redfish protocol to monitoring server and more. These updates are expected to be included in the upcoming Apache release. And we have conducted three rounds of version release voting.

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:

We haven't published Apache release.

When were the last committers or PPMC members elected?

HertzBeat has been in incubation since April 05th, 2024. As of yet, no committers have been elected for the project.

Have your mentors been helpful and responsive?

Yes, they are very nice.

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

There are no known brand and naming issues.

Signed-off-by:

•  (hertzbeat) Yonglun Zhang
  Comments:  We've started the first release. The team responded quickly, and all issues were handled promptly.
•  (hertzbeat) Yu Xiao
  Comments:
•  (hertzbeat) Justn Mclean
  Comments:
•  (hertzbeat) Francis Chuang
  Comments:

IPMC/Shepherd notes:

KIE

KIE (Knowledge is Everything) is a community of solutions and supporting tooling for knowledge engineering and process automation, focusing on events, rules, and workflows.

KIE has been incubating since 2023-01-13.

Three most important unfinished issues to address before graduating:

1. Release
2. Better website
3. Community building (always ongoing)

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

Nope.

How has the community developed since the last report?

We've really been going steady. There hasn't been a big up-tick in new members or anything else.

How has the project developed since the last report?

We are pushing hard for a release. We're working on getting all of the 't's crossed and 'i's dotted. We were hoping to have a vote already, but we have found some issues in our pipelines and some missing headers in files. We're pushing for all of that.

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:

Haven't had one yet, but we are very close.

When were the last committers or PPMC members elected?

About three months ago.

Have your mentors been helpful and responsive?

No, I don't believe anything is falling through the cracks. We've been pretty constant communication with Infra, the wider Incubator community, and speaking with our mentors as needed.

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

No answer.

Signed-off-by:

•  (kie) Brian Proffitt
  Comments: Are there any concerns around the recent media coverage about the fate of OptaPlanner? It might be something to detail, just to ease any concerns.
•  (kie) Claus Ibsen
  Comments:
•  (kie) Andrea Cosentino
  Comments: All looks good and the project is in good shape

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. Motivate growth in the community
2. Address remaining items before graduation  

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

The issue raised in our previous podling report (Mar. 2024) still exists. This is a project initiated from academia, and many of the committers have graduated with their degree and moved on to something else. The project itself is very promising, known that many outstanding academic papers have been developed on top of Apache Nemo [1-5], so it would be ideal if it finds its purpose, however it seems quite challenging at this particular moment. It is quite disappointing to see the project lose its momentum during the covid-19 pandemics, which made it extremely challenging for us to build the community. Nevertheless, the project itself, I believe, deserved to be in the TLP, but it seems like if there is no breakpoint for the project regarding the project community, I think we could start discussing about sending it to the attic. Any suggestions or opinions are welcome!

[1] https://www.usenix.org/conference/atc19/presentation/yang-youngseok [2] https://dl.acm.org/doi/10.1145/3468144 [3] https://dl.acm.org/doi/10.1145/3064176.3064181 [4] https://dl.acm.org/doi/10.1145/3546591.3547524 [5] https://www.usenix.org/conference/atc23/presentation/song

How has the community developed since the last report?  

Trying to have a discussion towards the issue raised above

How has the project developed since the last report?

Trying to have a discussion towards the issue raised above

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:    

2022-09-02

When were the last committers or PPMC members elected?

September 28, 2021

Have your mentors been helpful and responsive?

Please refer to the issue raised above.

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

The PPMC manages the polling's brand / trademarks.

Signed-off-by:

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

IPMC/Shepherd notes:

StormCrawler

StormCrawler is a collection of resources for building low-latency, customisable and scalable web crawlers on Apache Storm.

StormCrawler has been incubating since 2024-03-19.

Three most important unfinished issues to address before graduating:

1. Community building

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

Nothing yet.

How has the community developed since the last report?

We got some involvement (issues, simple PRs) from outside the usual suspects. We need to increase our outreach to attract more users / developers to foster a healthy community development.

How has the project developed since the last report?

We have published our first release (3.0). We are currently working on adding the feedback received for 3.0.

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:

2024-05-16

When were the last committers or PPMC members elected?

No new committers yet.

Have your mentors been helpful and responsive?

Nothing to note.

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

No answer.

Signed-off-by:

•  (stormcrawler) Dave Fisher
  Comments:
•  (stormcrawler) Lewis John McGibbney
  Comments:
•  (stormcrawler) Ayush Saxena
  Comments:
•  (stormcrawler) PJ Fanning
  Comments:

IPMC/Shepherd notes:

Teaclave

Teaclave is a universal secure computing platform.

Teaclave has been incubating since 2019-08-20.

Three most important unfinished issues to address before graduating:

1.Improve project structure and documentation.
2.Grow the community (attracting more committers, contributors, users).
3.Publish Apache releases (resolving logistics on 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?

Since the last report, we have organized three monthly virtual meetups. For each meetup, we have write-ups published on the Teaclave blog https://teaclave.apache.org/blog/.

• Teaclave Meetup #13: https://teaclave.apache.org/blog/2022-06-29-teaclave-meetup-13/
• Teaclave Meetup #14: https://teaclave.apache.org/blog/2022-12-14-teaclave-meetup-14/
• Teaclave Meetup #15: https://teaclave.apache.org/blog/2022-12-21-teaclave-meetup-15/

Additionally, we introduced a new project Teaclave Java TEE SDK to our community: <https://teaclave.apache.org/blog/2022-10-18-accepting-java-enclave-proposal />

How has the project developed since the last report?

Here are the summaries of recent progress:

Teaclave Faas Platform

• New release 0.6.0: https://github.com/apache/incubator-teaclave/releases/tag/v0.6.0
• Merged PRs:

<https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+me rged%3A2022-05-01..2024-05-31+base%3Amaster>

Teaclave TrustZone SDK

• New 'no-std' branch (set as recommended): https://lists.apache.org/thread/f3l82o89hb0w43n27nw77oqcpo829qjd
• Merged PRs:

<https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+ is%3Aclosed+merged%3A2022-05-01..2024-05-31+base%3Amaster+>

Teaclave SGX SDK

• Preparing release v2.0.0:

https://github.com/apache/incubator-teaclave-sgx-sdk/tree/v2.0.0-preview

• Merged PRs:

<https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Ac losed+merged%3A2022-05-01..2024-05-31+base%3Amaster+>

[NEW] Teaclave Java TEE SDK

• The first release v0.1.0:

https://github.com/apache/incubator-teaclave-java-tee-sdk/releases/tag/v0.1. 0

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:

2023-06-26: Apache Teaclave (incubating) FaaS Platfrom 0.6.0

When were the last committers or PPMC members elected?

2023-05-04: He Sun (Apache ID: hsun), PPMC

Have your mentors been helpful and responsive?

Yes, our mentors work responsively to help us with electing new mentors, developing new features, fixing bugs, and expanding the community.

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

We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175)

Signed-off-by:

•  (teaclave) Felix Cheung
  Comments:
•  (teaclave) Furkan Kamaci
  Comments:
•  (teaclave) Jianyong Dai
  Comments:
•  (teaclave) Matt Sicker
  Comments:
•  (teaclave) Zhijie Shen
  Comments:
•  (teaclave) Gordon King
  Comments:

IPMC/Shepherd notes:

Training

The Training project aims to collect, and share training resources, and develop tools to support training resource creation (templates, etc.). The resulting tools and curated training artefacts can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects.

Training has been incubating since 2019-02-21.

Three most important unfinished issues to address before graduating:

1. Review and eventually simplify the release process for training artefacts - or at least confirm finally, that we use the existing flow as it is to go on
2. Establish a sharing culture with other projects - Apache Training needs a link to other projects so that the training artefacts can be owned but contributed by the creators of the project, but share via Apache Training
3. Grow the community so that non-tech contributors can find a home inside the ASF, by joining Apache Training as tech-writer, translator, or educator who helps us to spread the words.

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

• nothing critical right now

How has the community developed since the last report?

• the last report was delayed, to access issues but now it works.
• the collaboration between Apache Wayang and Apache Training has been established - the joint presentation at the CoC 2024 in Bratislava is a result
• one non-tech contributor (from CISO domain) has been interviewed and we work on his onboarding

How has the project developed since the last report?

• I did multiple attempts to release the tools-subproject, but due to permission issues I am not able to to go through the full procedure.
• I still need support to sort out this access permission issues.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

• [OK] Initial setup
• [OK] Working towards first release
• [W.I.P.] Community building
•  Nearing graduation
•  Other:

Date of last release:

2024-04-XX (last attempt to release the tools subproject)

When were the last committers or PPMC members elected?

August 2024

Have your mentors been helpful and responsive?

• access rights for the release manager, who is blocked in the middle of the release process

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

• no activities on this yet

Signed-off-by:

•  (training) Craig Russell
  Comments:
•  (training) Christofer Dutz
  Comments:
•  (training) Justin Mclean
  Comments:
•  (training) Lars Francke
  Comments:

IPMC/Shepherd notes:

Uniffle

Uniffle is an unified Remote Shuffle Service

Uniffle has been incubating since 2022-06-06.

Three most important unfinished issues to address before graduating:

We're starting to discuss the graduation.

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?

112 pull requests are created and 69 pull requests are merged. 75 issues are created and 61 issues are closed.

How has the project developed since the last report?

We developed many exciting features. First, Netty data transportation is production available. Second, the we polish the feature stage recomputation. Third, we supported K8S operator for new K8S version. Fourth, we break origin limitation of blockId to support long run time job.

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:

2023-12-13. We released 0.8.0. We are preparing to release 0.9.0 now.

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Yes, they are helpful.

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

No.

Signed-off-by:

•  (uniffle) Felix Cheung
  Comments:
•  (uniffle) Junping Du
  Comments:
•  (uniffle) Liu Xun
  Comments:
•  (uniffle) Weiwei Yang
  Comments:
•  (uniffle) Zhankun Tang
  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. Growing community

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?

New PPMC member

How has the project developed since the last report?

New PPMC member and many new features, such as Python API, Tensorflow integration, and initial support for federated data processing

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:    

2024-02-05

When were the last committers or PPMC members elected?

2024-05-13

Have your mentors been helpful and responsive?

Everything good.

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

Everything good

Signed-off-by:

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

IPMC/Shepherd notes: