Incubator PMC report for October 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 32 podlings incubating. In September, podlings executed eight distinct releases, and one IP clearance occurred. Several incubating proposals have been discussed on the mailing list, and we have one new podling who will join the incubator called CloudBerry. No podling graduated or retired last month. No one retired or joined the IPMC. Several podlings failed to report and will be asked to report next month. There was a discussion about making votes easier to understand by specifying the voter name and roles more clearly, and this has been adopted. Most of the other discussions were on releases or new incubating projects. The Community over Code conference was held in Denver. It included an incubating track with several talks on incubating projects and the incubator itself.

Community

New IPMC members:

• None

People who left the IPMC:

• None

New Podlings

• CloudBerry

Podlings that failed to report, expected next month Baremaps

• Gluten
• Gravitino
• KIE
• Livy
• Nemo
• Pony Mail
• ResilientDB
• Teaclave
• Training
• Uniffle
• Wayang

Graduations

• None

The board has motions for the following:

• None

Releases

The following releases entered distribution during the month of September:

• Answer 1.4.0
• Devlake 1.0.1
• Fury 0.7.1
• Gluten 1.2.0
• Gravitino 0.6.0
• Seata 2.1.0
• Seata 2.2.0
• StormCrawler 3.1.0

IP Clearance

• Apache DataFusion sqlparser-rs

Legal / Trademarks

• N/A

Infrastructure

• N/A

Table of Contents

Amoro
Annotator
HertzBeat
HugeGraph
OpenServerless
OzHera
Pegasus
Polaris
StormCrawler
Toree

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. Polish our website and document
2. Release more versions under ASF
3. Build and grow 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?

• Added 3 new committers
• Added 5 new contributors
• Merged 150 PRs

How has the project developed since the last report?

• Released our first apache version 0.7.0-incubating

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-07-17

When were the last committers or PPMC members elected?

• 2024-08-19, committer:Tao Wang(GitHub ID: Aireed)
• 2024-08-19, committer:Paul Lin(GitHub ID: link3280)
• 2024-08-19, committer:Mo Zhang(GitHub ID: zhangmo8)

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:
•  (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. We continue to seek advice on this topic.

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.

There have been a few mails regarding potentially adding support for the Highlight API instead of using mark elements (while keeking the elements as a fallback).

There is wider community interest growing around the Web Annotation specifications again driven by new W3C Web Publishing work rechartering and the Readium groups "profiling down" of the Web Annotation Data Model specification for reading platforms (many of which are DOM based and could benefit from Apache Annotator code): https://github.com/readium/annotations

One key thing the community could work toward is building the code to ingest a full Web Annotation, AnnotationCollection, and/or AnnotationPage and use the existing selection code to anchor these annotations. The demo we have now gets pretty close, but developers seem to not be finding their way there.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

•  Initial setup
•  Working towards first release
•  Community building - we missed several golden opportunities for community growth due to the timing of joining the incubator after the "hype cycle" at the W3C and I Annotate conference hay days. We may have a new opportunity here with the rechartering and new exploration around DOM-based EPUB readers...but we'll need more active contributors to take advantage of the opportunity.
•  Nearing graduation

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

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. Grow the community and attract more users.  
2. Publish more Apache release by different committers.

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?

1. 20 contributors submit 661 commits.
2. We elected 7 new committers to join the community.
3. Participate in OSPP activities to help students participate in open source.

How has the project developed since the last report?

1. new release v1.6.1 is on the voting process.
2. improvements on web ui
3. the java implementation of the impi protocol has been developed.
4. integrate grafana display metrics collect by hertzbeat
5. more huge features and bugfix, doc update

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-06-11

When were the last committers or PPMC members elected?

2024-09-09

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:
•  (hertzbeat) Yu Xiao
  Comments:
•  (hertzbeat) Justn Mclean
  Comments:
•  (hertzbeat) Francis Chuang
  Comments:

IPMC/Shepherd notes:

HugeGraph

A large-scale and easy-to-use graph database

HugeGraph has been incubating since 2022-01-23.

Three most important unfinished issues to address before graduating:

1. Release distributed storage module (include PD/store) & make graph computer easy to use
2. Unified different modules version & introduce a new Graph Dashboard & LLM/AI system (GraphRAG/Agent)
3. At least 2 new PPMC & 5 committers selected and take deep part in the community

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

Some PPMC members are inactive for a while, an adjustment may be required before graduation

How has the community developed since the last report?

1. Finished 4+ tasks in OSPP & GSoC (Open Source Activity)
2. 10+ new contributors take part in the community (with PR/code)
3. After the release of the new distributed version(this month), the system's completeness will significantly increase, and the community will quickly enter the stage of graduation

How has the project developed since the last report?

1. Introduce some new features: include memory management & distributed cluster test modules etc.
2. Merge/unify hugegraph-commons module into the main/core repo (to enhance the dev/release process)
3. The most important/major change (distributed storage system PD & Store has already done, waiting for the release soon)
4. The new graph dashboard/UI & graph computing system are also on the way (should be done in next 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:

2024-04-01

When were the last committers or PPMC members elected?

2024-02-24

Have your mentors been helpful and responsive?

Yes, thanks all of them

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

No answer.

Signed-off-by:

•  (hugegraph) Lidong Dai
  Comments:
•  (hugegraph) Trista Pan
  Comments:
•  (hugegraph) Xiangdong Huang
  Comments:
•  (hugegraph) Yu Li
  Comments:
•  (hugegraph) Willem Ning Jiang
  Comments:

IPMC/Shepherd notes:

OpenServerless

OpenServerless is an open source, cloud-agnostic, serverless platform. It offers a complete environment for serverless applications development, based on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an unified developer experience with a plethora of services (SQL or noSQL databases, key-value stores, object storage, LLMs services, function schedulers) managed by the platform's core: the operator, along with tooling (the CLI) to simplify (and interact with) deployments, integrated ide and starter application and optimized runtimes integrated with the staters.

OpenServerless has been incubating since 2024-06-17.

Three most important unfinished issues to address before graduating:

1. Community Building
2. First Release
3. Comprehensive Documentation

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?

No new members joined the community

How has the project developed since the last report?

1. OpenServerless Operator has been stabilised fixing minor issues for the feature planned for the initial release
2. Implemented OPS CLI as porting of the legacy NUV one
3. Porting of the previous NUV tasks to new OPS format
4. Test suite to verify deployment on supported K8S versions
5. Documentation website (WIP)

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:

None yet

When were the last committers or PPMC members elected?

2024-08-22

Have your mentors been helpful and responsive?

Yes, a big thanks to all of them for their valuable support in addressing issues in a context which new for the majority of the PPMC members

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

https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved

Signed-off-by:

•  (openserverless) Bertrand Delacretaz
  Comments:
•  (openserverless) Enrico Olivelli
  Comments:
•  (openserverless) François Papon
  Comments:
•  (openserverless) JB Onofré
  Comments: Good start for OpenServerless
•  (openserverless) PJ Fanning
  Comments:

IPMC/Shepherd notes:

OzHera

OzHera is an application observation platform (APM) in the era of cloud native, with the application as its core, integrating capabilities such as metric monitoring, trace tracking, logging, and alerting

OzHera has been incubating since 2024-07-11.

Three most important unfinished issues to address before graduating:

1.Set up necessary resources in ASF.

2.Make the first apache release.

3.Build a diverse 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?

Completed the initial construction of the ASF website.

Added 1 new contributor.

Merged 40+ PRs.

How has the project developed since the last report?

We have completed the ASF codebase migration.

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:  

There is no apache release yet.

When were the last committers or PPMC members elected?

Currently all committers and PPMC members are initial committers.

Have your mentors been helpful and responsive?

Yes, mentors are helpful and responsive.

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

Not yet.

Signed-off-by:

•  (ozhera) Yu Xiao
  Comments:
•  (ozhera) Yu Li
  Comments:
•  (ozhera) Kevin Ratnasekera
  Comments:
•  (ozhera) Duo Zhang
  Comments: Glad to see we made progress on migrating to ASF. There are still links which reference old stuff on github page, we should file an infra issue to address it. I see that we already have a CI stage to compile the project, we'd better also introduce a stage to run tests.

IPMC/Shepherd notes:

Pegasus

Pegasus is a distributed key-value storage system which is designed to be simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 2020-06-28.

Three most important unfinished issues to address before graduating:

1. Grow the community (attracting more committers, contributors, users).
2. Make more releases in ASF policy regularly.
3. Improve the Pegasus project performance, stability, and usage scenarios.

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 saw more active users and contributors of Apache Pegasus.

How has the project developed since the last report?

2.6.0 is planning to be released, maybe at the end of 2024.

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-12

When were the last committers or PPMC members elected?

2024-9-10, committer: Jingwei Yu (GitHub ID: Samunroyu)

Have your mentors been helpful and responsive?

Yes, our mentors gave us a lot of help, including version release, holding meetup, prepare the graduation and etc.

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

Yes. Yes. Yes.

Signed-off-by:

•  (pegasus) Duo zhang
  Comments:
•  (pegasus) Liang Chen
  Comments:
•  (pegasus) Von Gosling
  Comments:
•  (pegasus) Liu Xun
  Comments:

IPMC/Shepherd notes:

Polaris

Polaris is a catalog for data lakes. It provides new levels of choice, flexibility and control over data, with full enterprise security and Apache Iceberg interoperability across a multitude of engines and infrastructure.

Polaris has been incubating since 2024-08-09.

Three most important unfinished issues to address before graduating:

1. Prepare the first release
2. Grow the community
3. Promote the project (blogs, events, ...)

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?

Polaris already promoted new committers this month. We see a lot of interest in Polaris, and adoption seems promising.

How has the project developed since the last report?

Polaris already promoted new committers this month. We see a lot of interest in Polaris, and adoption seems promising. We had several events (Chill Data Summit London, Big Data London, CoC NA, ...), webinar, blog posts and articles promoting Apache Polaris (incubating). The website has been published, now powered by Hugo to easily manage versioned documentation.

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?

New committers have been elected this month:

• Anna Filippova
• Eric Maynard
• Michael Collado
• Yufei Gu
• Yuya Ebihara

Have your mentors been helpful and responsive?

Yes

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

All brand usage (or plan to use) is going via the PPMC with support of markpub@apache.org and VP trademark.

Signed-off-by:

•  (polaris) Bertrand Delacretaz
  Comments:
•  (polaris) Holden Karau
  Comments:
•  (polaris) Kent Yao
  Comments:
•  (polaris) Ryan Blue
  Comments: I'm glad to see the list of new committers! That's great news given how long the project has been active, but it indicates that perhaps there's something to report in the report section "How has the project developed since the last report"? Perhaps that's an oversight.
•  (polaris) JB Onofre
  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?

No

How has the community developed since the last report?

Nothing new to report. One contributor showed up and provided some PRs, which is a good sign.

How has the project developed since the last report?

A first release was made.

A slight source of concern is that 3 out of the initial 5 committers have so far shown no or very little involvement in the project since its incubation, which makes it even more urgent to increase the committer base.

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 of note.

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

No progress yet.

Signed-off-by:

•  (stormcrawler) Dave Fisher
  Comments:
•  (stormcrawler) Lewis John McGibbney
  Comments:
•  (stormcrawler) Ayush Saxena
  Comments: Working towards building community
•  (stormcrawler) PJ Fanning
  Comments: Release made but may need more work on community building.

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

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 saw a boost in activity working on the bringup of support for Apache Spark 3.3 and Scala 2.13 which culminate in a new committer, but after that it went back to regular activity flow of a stable/mature project.

We still see much of the users asking questions in the gitter channel rather than using the mailing lists.

The discussion around retirement process was stopped with the boost in community activity.

The Apache Toree project recently had two presentations at the European Community over Code conference, drawing a good audience. The attendees showed great interest, posing several questions. This indicates the community should look into opportunities for us to further promote awareness of the project.

How has the project developed since the last report?

Most of the remaining tasks related to Apache Spark 3.3 and Scala 2.13 are completed and comunity should start planning next 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:

2022-04-11

When were the last committers or PPMC members elected?

Cheng Pan was added to the PPMC on 2023-08-28

Have your mentors been helpful and responsive?

Not applicable as we had not needed mentors attention

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

No Trademark issues

Signed-off-by:

•  (toree) Luciano Resende
  Comments:
•  (toree) Weiwei Yang
  Comments:

IPMC/Shepherd notes: