Incubator PMC report for January 2026

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

As of December, there are 30 podlings under incubation. One successful release was made during the month, and no IP clearances were completed. No podlings graduated, and no podlings retired. There were no additions or removals to IPMC membership.

Mailing list traffic during the month focused on release voting, graduation discussions, and follow-ups on reporting and potential retirement, along with updates to Incubator training materials.

Two new navigation paths for the Incubator Training site were introduced: browsing by theme and browsing by topic, making it easier to locate relevant material. A search page for Incubator training resources was also added to improve discoverability across the training content.

Burr, Fluss and Geaflow were invited to take part in their six-month reviews and all accepted.

Several new Incubator Field Guides were published. These provide practical, experience-based advice for mentors, PPMCs and IPMC members. The guides were created by reviewing and analysing real Incubator mailing list discussions from the past five years, documenting governance in action and how the Incubator has handled recurring issues, with limited AI assistance to identify patterns. Topics added include community governance, community proposals, edge cases, graduation identity, graduation readiness, graduation votes, incubation readiness, initial committer selection, licensing and provenance, naming and branding, naming and trademarks, proposal discussions, release announcements, release review issues, releases and release votes.

A discussion took place regarding how podlings may establish official WeChat channels, along with broader guidance on the responsible use of chat and instant messaging platforms within incubation.

A new guide on the use of emerging technologies was added, focusing on applying ASF values rather than creating new policy, preserving human accountability and highlighting privacy and licensing risks.

The experimental podling health reports are being adopted and are showing measurable improvements in the quality and consistency of podling reporting.

OpenServerless has begun discussion of its first release. Most podlings continue to make steady progress toward graduation.

Livy continues graduation discussions, and Toree completed a release this month and plans to begin graduation discussions after the vote concludes. HugeGraph voted to graduate. A graduation discussion for Gluten uncovered several third-party branding issues, which the podling is addressing. ResilientDB and Polaris are likely to graduate soon. Baremaps is likely to retire.

Pegasus is experiencing significant community attrition, with many core members having left, which has slowed development and is currently blocking both graduation discussions and release progress. The podling is working to encourage new contributors and plans to elect additional committers and PPMC members during 2026 to help revitalise the community.

Fesod attempted its first incubating release (2.0.0-RC1) in late December, which surfaced a number of ASF compliance issues. The podling is addressing those issues and plans to begin a new release vote (2.0.0-RC2) shortly.

One podling, PonyMail, failed to submit a report and will be asked to report next month. All submitted podling reports had mentors` sign-off.

Community

New IPMC members:

People who left the IPMC:

New Podlings

Podlings that failed to report, expected next month

Graduations

• None

The board has motions for the following:

• HugeGraph

Releases

The following releases entered distribution during the month of December:

• Iggy 0.6.0

IP Clearance

• None

Legal / Trademarks

• N/A

Infrastructure

• N/A

Table of Contents

Amoro
Fesod
Fluss
Gluten
HugeGraph
Livy
Pegasus
ResilientDB
GeaFlow

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. Fix possible and potential security vulnerability issues.
2. Release more versions under ASF.
3. Build and grow a 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?

• Added 1 new Committers
• Added 11 new contributors

How has the project developed since the last report?

• Merged 82 PRs

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:

• 2025-09-11, released Amoro 0.8.1-incubatiing

When were the last committers or PPMC members elected?

• 2026-01-07, committer:Fei Wang(turboFei)

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) Justin Mclean
  Comments:
•  (amoro) Zhongyi Tan
  Comments:
•  (amoro) Yu Li
  Comments: Good to see new committer joining and community starting to prepare for graduation.
•  (amoro) Xinyu Zhou
  Comments:
•  (amoro) Kent Yao
  Comments: Nice to see the community grow rapidly and come close to graduate

IPMC/Shepherd notes:

Fesod

Fesod is a high-performance and memory-efficient Java library for reading and writing Excel files, designed to simplify development and ensure reliability.

Fesod has been incubating since 2025-09-17.

Three most important unfinished issues to address before graduating:

1. Ensure that the website and codebase are fully compliant with ASF policies.
2. Release First version(2.0.0) under the Apache Incubator.
3. Continue to grow the community and word towards the ASF maturity Model.

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. The project now has already has several regular contributors.
2. Some contributors have begun proactively designing new features for project.

How has the project developed since the last report?

1. Development of new features for the project is still ongoing.
2. We attempted to release 2.0.0-RC1 at the end of Dec, 2025 (many issues needed improvement).
3. We will begin the release attempt for 2.0.0-RC2 this week.

How would you assess the podling's maturity?

We are currently addressing issues in RC1 that do not comply with ASF specifications. We plan to initiate the release process for 2.0.0-RC2 this week.

•  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?

N/A

Have your mentors been helpful and responsive?

We extend our special thanks to our mentors for their assistance.

Particular gratitude goes to @PJ Fanning for the questions raised during the release.

@tison and @Huajie Wang also provided substantial support as we worked toward releasing RC1.

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

Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246

Signed-off-by:

•  (fesod) tison
  Comments:
•  (fesod) Dave Fisher
  Comments:
•  (fesod) Huajie Wang
  Comments:
•  (fesod) PJ Fanning
  Comments:

IPMC/Shepherd notes:

Fluss

Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures.

Fluss has been incubating since 2025-06-04.

Three most important unfinished issues to address before graduating:

1. The second release (v0.9.0) under the ASF incubator
2. Grow the community and attract more committers, contributors and users.
3. Fill out the maturity model

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

None at this time.

How has the community developed since the last report?

1. Add 2 new committers, currently with total 17 committers.
2. The Fluss PPMC created a LinkedIn page, which now has 1,302 followers, doubling organically over the past three months.
3. Regular Monthly Community Call for October and November; December’s call was skipped due to the holiday season.
4. An “Apache Fluss × Apache Iceberg” joint webinar is scheduled for January 20, 2026, featuring contributors from both communities.
5. Community presentations and outreach:
   • Jark Wu and Giannis Polyzos presented at Flink Forward Barcelona (2025-10-15)
   • Leonard Xu presented Fluss at QCon Shanghai (2025-10-24)
   • Giannis Polyzos spoke at Big Data Europe (2025-11-19)
   • Jark Wu presented to the CMU Database Group (2025-12-08)

How has the project developed since the last report?

• Released v0.8.0 on 2025-11-09 which is the project’s first official release under the Apache Incubator. This milestone represents 4 months of collaborative development with 400+ commits from the community.
• 8 new Fluss Improvement Proposals (FIPs) were submitted over the past quarter; several have already been approved and implemented.
• Active development is underway for v0.9.0, targeted for release by end of January 2026.

How would you assess the podling's maturity?

•  Initial setup
•  Working towards first release
•  Community building
•  Nearing graduation
•  Other:

Commentary: The project has successfully shipped its first Apache release and is actively growing its contributor and user base. Community engagement is strong, with regular calls, public talks, and cross-project collaboration. While still in its incubation, Fluss is steadily progressing toward graduation readiness.

Date of last release:

2025-11-09 (v0.8.0)

When were the last committers or PPMC members elected?

2025-11-28

Have your mentors been helpful and responsive?

Yes.

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

Yes, everything is fine.

Signed-off-by:

•  (fluss) Jean-Baptiste Onofré
  Comments: The podling is operating great. The community is smoothly growing up.
•  (fluss) Becket Qin
  Comments:
•  (fluss) Yu Li
  Comments: Good to see new committers joining and vibrant community activities.
•  (fluss) Jingsong Lee
  Comments:
•  (fluss) Zili Chen
  Comments:

IPMC/Shepherd notes:

Gluten

Gluten is a middle layer responsible for offloading JVM-based SQL engines' execution to native engines.

Gluten has been incubating since 2024-01-11.

Three most important unfinished issues to address before graduating:

1. Complete more Apache releases: Plan for Gluten v1.6.0 in January.
2. Grow the community: Continue attracting and onboarding contributors to strengthen community diversity.
3. Finalize graduation preparations: Complete documentation and community consensus for transition to a top-level project.

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

Yes, under discussing a graduation proposal.

How has the community developed since the last report?

Two new Committers and Two new PPMC members joined on 2025-10-29, currently with 44 committers and 35 PPMC members

How has the project developed since the last report?

The project made significant progress in the last quarter. Apache Gluten (incubating) 1.5.0 was released on 2025-10-29, marking the fifth incubating 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:

2025-10-29

When were the last committers or PPMC members elected?

2 new PPMC members were joint on 2025/10/29.

Have your mentors been helpful and responsive?

Yes. The podling’s mentors (Apache members guiding Gluten’s incubation) have been very supportive and responsive.

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

Yes. The PPMC is adequately managing Apache Gluten’s branding and trademarks. There have been no naming conflicts or misuse of the Apache brand identified.

Signed-off-by:

•  (gluten) Yu Li
  Comments: The community is well-prepared for graduation.
•  (gluten) Wenli Zhang
  Comments:
•  (gluten) Kent Yao
  Comments: Glad to see Gluten entering graduation progress
•  (gluten) Shaofeng Shi
  Comments:
•  (gluten) Felix Cheung
  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 1.7.0 (Already done)
2. Prepare trademark docs / communication (Doing)
3. Start a community discussion for 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?

1. Add 3 new Committers (before graduation)
2. Finished GSoC & OSPP & GLCC (student OSS activities)
3. 2 topic in COC Asia

How has the project developed since the last report?

1. Release 1.7.0 (include a string of improvement / refactor)
2. AI repo/module have got a great change
3. Support ToplingDB as RocksDB Plus

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:

2025-11-28

When were the last committers or PPMC members elected?

2025-09-01

Have your mentors been helpful and responsive?

Yes, thanks for them

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

Trademark transfer is in progress.

Signed-off-by:

•  (hugegraph) Lidong Dai
  Comments:
•  (hugegraph) Trista Pan
  Comments:
•  (hugegraph) Xiangdong Huang
  Comments:
•  (hugegraph) Yu Li
  Comments: The community is well-prepared for graduation.
•  (hugegraph) Willem Ning Jiang
  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. Revitalization of the Community
2. Dependable Release Cadence
3. Keep the project up to date with security fixes and in terms of Spark support

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

None at this time. Currently working on releasing a new version, RC voting will be restarted in a few days.

How has the community developed since the last report?

We have received PRs and merged several PRs, dev mailing list is more active.

How has the project developed since the last report?

PRs merged including JDK 17 upgrade, Spark 2 and Python 2 decommission. New release branch and RC has been created.

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

When were the last committers or PPMC members elected?

October 2023

Have your mentors been helpful and responsive?

Yes

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

No answer

Signed-off-by:

•  (livy) Bikas Saha
  Comments:
•  (livy) Luciano Resende
  Comments:
•  (livy) Jean-Baptiste Onofré
  Comments: I think it's worth to start discussion graduation.
•  (livy) Madhawa Kasun Gunasekara
  Comments:
•  (livy) Larry McCay
  Comments:
•  (livy) Gyorgy Gal
  Comments:

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. The graduation discussion has been initiated, but not enough PPMC members have participated yet; therefore, the discussion is still blocked. And we are working to request the current PPMC members and promote active committers to become PPMC members in order to continue this process.

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

Many core members of the project have left, leading to a decline in community activity and consequently blocking the graduation discussion and releases.

We are working to encourage other contributors in the community to help us accelerate the release process, with the goal of producing a new release within 2026. In addition, we will promote voting to elect active contributors as new committers or PPMC members.

How has the community developed since the last report?

There are 2 new contributors who have joined the project development.

How has the project developed since the last report?

A total of 18 commits from 6 contributors were merged, including fixes for some bugs in unit tests, shell tools and the Go/Python clients, work on the Go collector, as well as some code refactoring.

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-09-26

Have your mentors been helpful and responsive?

No issues were encountered that required mentor assistance.

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

Yes.

Signed-off-by:

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

IPMC/Shepherd notes:

ResilientDB

ResilientDB is a distributed blockchain framework that is open-source, lightweight, modular, and highly performant.

ResilientDB has been incubating since 2023-10-21.

Three most important unfinished issues to address before graduating:

1. Nothing more to be done.

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?

Add three new PPMC members

How has the project developed since the last report?

We are preparing for the graduation process.

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:

2025-10 (1.11.0)

When were the last committers or PPMC members elected?

2025-11

Have your mentors been helpful and responsive?

No issues.

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

No

Signed-off-by:

•  (resilientdb) Junping Du
  Comments:
•  (resilientdb) Kevin Ratnasekera
  Comments:
•  (resilientdb) Jean-Baptiste Onofré
  Comments: The podling is close to graduation. I would suggest a new release at least.

IPMC/Shepherd notes:

Geaflow

GeaFlow is a streaming graph computing engine for distributed large-scale real-time graph storage and analysis. It supports trillion-level graph storage, hybrid graph and table processing, real-time/offline graph computing, and interactive graph analysis.

GeaFlow has been incubating since 2025-06-06.

Three most important unfinished issues to address before graduating:

1. Cultivate a more diverse community by engaging contributors and committers from varied organizations and global regions.
2. Implement predictable release cycles and maintain high project stability to encourage broad participation and adoption.

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?

The GeaFlow community has maintained its core contributor base over the past month, with existing contributors continuing to drive development. The community has remained active with ongoing contributions including new features, optimizations, documentation updates, and dependency maintenance. Additionally, several PRs are currently under review.

How has the project developed since the last report?

Over the past month, the GeaFlow project has focused on feature enhancements, optimizations, and dependency updates. Key changes are including:

• Adding support for vector stores (#637).
• Implementing a classifier to address ISSUE701 (#720).
• Optimizing hardcoded constants and magic numbers (#674).
• Updating documentation URLs (#721).
• Upgrading the lz4-java dependency from 1.9.0 to 1.10.1 (#715).
• Updating the version to 0.8.0-SNAPSHOT after cherry-picking fixes from the 0.7.0 release (#712).

These updates demonstrate continued development in functionality expansion, code quality improvements, and dependency management.

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:

The first community version was released on November 19th.

When were the last committers or PPMC members elected?

This month, we held committer votes for two candidates: Leomrlin has been approved, while kitalkuyo-gita remains under observation to assess whether his contributions align with our project requirements.

Have your mentors been helpful and responsive?

Yes, we have received helpful guidance.

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

N/A.

Signed-off-by:

•  (GeaFlow) Willem Ning Jiang
•  (GeaFlow) xinwang
•  (GeaFlow) lzljs3620320
•  (GeaFlow) jmclean
•  (GeaFlow) paulk