DRAFT DRAFT DRAFT

NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.

If your report is missing please use the clutch2report.py script to generate your report.

It also best to:

Do not change existing formatting. Especially do not change the formatting of the sign-off area.
Keep all lines under 76 characters long.
All content under the ### headings should be indented by two spaces. Do not use tabs.
Please don't change the text in the headings or add new ones.
Include one space after a bullet point or full stop on a numbered list.
Use [X] (X and no spaces) to sign off reports.
Do not include long URLs and use the apache URL shortener https://s.apache.org.
Please note that some lines have two spaces at the end. Do not remove these spaces.

Please make sure you use the current report and don't copy an old one, the headings do change from time to time.

A script will be run on this report before it is submitted to the board. If your lines are too long it may insert line breaks in unexpected places.

Reflow

fold -w 76 -s $1 | cat -s

Timeline

Wed February 04	Podling reports due by end of day
Sun February 08	Shepherd reviews due by end of day
Sun February 08	Summary due by end of day
Tue February 10	Mentor signoff due by end of day
Wed February 11	Report submitted to Board
Wed February 18	Board meeting

Shepherd Assignments

Calvin Kirs	Burr
Dave Fisher	Caldera
Dave Fisher	XTable
Drew Farris	Texera
Justin Mclean	HoraeDB
P. Taylor Goetz	Cloudberry
PJ Fanning	GeaFlow
Timothy Chen	Toree
Willem Jiang	GraphAr
Willem Jiang	Seata
Xuanwo	Fesod
Xuanwo	Hamilton

Incubator PMC report for February 2026

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

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

Burr is a lightweight in-process python framework that standardizes the expression and execution of state machines as action-driven graphs, while making graph execution easily observable. It is particularly suited for AI agent workflows, simulations, and other dynamic systems, and comes with a self-hostable observability UI that integrates with OpenTelemetry.

Burr has been incubating since 2025-05-24.

Three most important unfinished issues to address before graduating:

Build release cadence.
Add a couple more core contributors.
Get more focused on building community.

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

N/A

How has the community developed since the last report?

Discord seeing small growth.
Otherwise largely feels flat-ish.

How has the project developed since the last report?

We have just managed to get our first release out!
We're looking forward to

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:

2026-01-24

When were the last committers or PPMC members elected?

2025-05-24.

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. They helped us figure out a first version release process.

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?

Nothing here that we're aware of.

Signed-off-by:

(burr) Kevin Ratnasekera
Comments:
(burr) Ayush Saxena
Comments:
(burr) PJ Fanning
Comments:
(burr) Jarek Potiuk
Comments:

IPMC/Shepherd notes:

Caldera

Caldera provides a modular platform for modeling, scripting, and executing adversary behavior. It allows users to construct emulation plans, provides agents for communicating with the command and control server, and enables users to evaluate security detections in a structured, scalable, and repeatable way. With the use of plug-ins and community-contributed features, Caldera supports a range of use cases including adversary emulation, purple teaming, detection engineering, and continuous security validation. Using Caldera, defenders can emulate known threat actor behavior and perform other red team activity to evaluate their organization’s defensive capabilities, test analytics, and find detection gaps. As a modular tool based on the MITRE ATT&CK framework, Caldera is designed to be extensible, intelligence-driven, and automation-friendly.

Caldera has been incubating since 2025-12-19.

Three most important unfinished issues to address before graduating:

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:

(caldera) Kevin Ratnasekera
Comments:
(caldera) Francis Chuang
Comments:
(caldera) PJ Fanning
Comments:
(caldera) Gordon King
Comments:

IPMC/Shepherd notes:

Cloudberry

Cloudberry Database, built on the latest PostgreSQL kernel, is one of the most advanced and mature open-source MPP (Massively Parallel Processing) databases available.

Cloudberry has been incubating since 2024-10-11.

Three most important unfinished issues to address before graduating:

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:

(cloudberry) Roman Shaposhnik
Comments:
(cloudberry) Willem Ning Jiang
Comments:
(cloudberry) Kent Yao
Comments:

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:

Ensure that the website and codebase are fully compliant with ASF policies.
Add more core contributors.
Get more focused on building community.

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

N/A

How has the community developed since the last report?

We have a discussion on private mail list about voting first committer.
The project now has several active contributors.

How has the project developed since the last report?

We have already released our first version(2.0.0-incubating).
Since some error in 2.0.0-incubating, we are now voting for 2.0.1-incubating.
The new contributors still contribute for project.

How would you assess the podling's maturity?

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

Date of last release:

2026-01-21

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

Yes. We truly thanks our mentors' help in voting process.

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:

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.

Two most important unfinished issues to address before graduating:

Cultivate a more diverse community by engaging contributors and committers from varied organizations and global regions.
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, and bugfix. 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:

Add ISO-GQL PROPERTY_EXISTS predicate(#702).
Adding Lucene & Embedding-Based Search Operators for LightWeight Context GraphMemory(#716).
Fix memory management in mmap_ipc.cpp(#725).
Support Graph Consolidate algorithm and added GraphMemory Java Server and Client(#729).

These updates reflect ongoing progress in graph-related functionality expansion, code quality improvements, and Graph+AI capabilities.

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 last version was released on November 19, 2025.

When were the last committers or PPMC members elected?

The last committers were elected on January 4, 2026.

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
Comments:
(geaflow) Xin Wang
Comments:
(geaflow) Jingsong Lee
Comments:
(geaflow) Paul Klingelhuber
Comments:
(geaflow) Justin Mclean
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:

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:

(graphar) Calvin Kirs
Comments:
(graphar) tison
Comments:
(graphar) Xiaoqiao He
Comments:
(graphar) Yu Li
Comments:

IPMC/Shepherd notes:

Hamilton

Hamilton is a lightweight in-process framework to define, execute, and observe directed acyclic graphs (DAGs) that express data transformations. In Hamilton, one can express complex DAGs of transformations, e.g. from dataframe transformations (using pandas, polars, PySpark), machine learning pipelines, through to regular software engineering API request and LLM API based workflows. Observability hooks are built into the framework. The Hamilton UI is a self-hostable service to capture observability output from workflow runs.

Hamilton has been incubating since 2025-04-12.

Three most important unfinished issues to address before graduating:

Release all the packages under Apache.
Build release cadance.
Build community.

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

N/A

How has the community developed since the last report?

Feels flat-ish. But new contributors keep passing through.

How has the project developed since the last report?

We managed to get our first release out. Otherwise guiding new contributors that want to help with issues.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first releases [we've done 1 package, 4 more to go].
Community building
Nearing graduation
Other:

Date of last release:

2025-10-09

When were the last committers or PPMC members elected?

2025-04-12

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.

All good. Nothing outstanding right now.

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?

Not aware of any issues.

Signed-off-by:

(hamilton) Kevin Ratnasekera
Comments:
(hamilton) Ayush Saxena
Comments:
(hamilton) PJ Fanning
Comments:
(hamilton) Jarek Potiuk
Comments:

IPMC/Shepherd notes:

HoraeDB

HoraeDB is a high-performance, distributed, cloud native time-series database.

HoraeDB has been incubating since 2023-12-11.

Three most important unfinished issues to address before graduating:

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:

(horaedb) tison
Comments:
(horaedb) Shaofeng Shi
Comments:
(horaedb) Gang Li
Comments:
(horaedb) Von Gosling
Comments:

IPMC/Shepherd notes:

Seata

Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to- use and high-performance distributed transaction solution, used to solve the data consistency problem.

Seata has been incubating since 2023-10-29.

Three most important unfinished issues to address before graduating:

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:

(seata) Sheng Wu
Comments:
(seata) Justin Mclean
Comments:
(seata) Huxing Zhang
Comments:
(seata) Heng Du
Comments:
(seata) Xin Wang
Comments:

IPMC/Shepherd notes:

Texera

Texera is an open-source system to support collaborative data science, AI, and ML using GUI-based workflows. Our vision is to develop a system to support cloud platforms on which users can easily analyze data and use AI/ML techniques provided as operators. Users with various backgrounds, irrespective of whether they know coding or not, can collaborate on the same project to construct a pipeline. Experienced users can use programming languages such as Python, R, Java, and Scala to implement customized computation logic. The platform allows users to pause the execution of a workflow to investigate the operator states, and resume the execution at a later time. The platform can be used by a research community to publish valuable resources such as data sets, workflows, and ML models to share their domain-specific knowledge and support reproducibility of scientific research. The platform also allows users to elastically request computing resources from public clouds for computationally-intensive tasks.

Texera has been incubating since 2025-04-12.

Three most important unfinished issues to address before graduating:

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:

(texera) Cezar Andrei
Comments:
(texera) Gordon King
Comments:
(texera) PJ Fanning
Comments:
(texera) Ian Maxon
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:

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?