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 May 06	Podling reports due by end of day
Sun May 10	Shepherd reviews due by end of day
Sun May 10	Summary due by end of day
Tue May 12	Mentor signoff due by end of day
Wed May 13	Report submitted to Board
Wed May 20	Board meeting

Shepherd Assignments

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

Incubator PMC report for May 2026

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 under incubation. In April, the Incubator made 6 releases, and some release votes are currently underway. There were two additions and no removals to IPMC membership.

Mailing list discussion in April focused primarily on release voting activity. There was also a discussion about using MCP-based tooling with publicly available data to generate Incubator insights, which sparked interest on the mailing list. This tooling was subsequently used, with human oversight, to help produce this report. A new incubation proposal for PIC Standard was discussed. A graduation discussion for Apache Livy has started.

Caldera has shown very limited engagement with ASF since entering incubation. Project communication has not been taking place on the mailing lists, and initial setup tasks, including ICLAs, accounts, and SGA progress, have not been progressing visibly. The IPMC raised these concerns with the project, and the podling has confirmed it will change course to address them and is making progress.

OpenServerless has been incubating for nearly two years and has not yet released an ASF release. Mailing list activity is almost entirely automated GitHub messages. No new committers or PPMC members have been elected since August 2024, and a private message sent to the podling about one month ago has not received a response. Mentor comments in the most recent reports and on the general list directly reflect these concerns. The IPMC has raised the question of whether to initiate a discussion about retirement. OpenServerless has started to move towards marking a release.

OzHera has not made an ASF release in over a year despite ongoing development activity. The project has been asked to outline the current status of release preparation, what is blocking the next release, and to address low mentor engagement across recent reporting periods.

PouchDB has been in incubation for 12 months with no ASF release. The project website at pouchdb.apache.org needs some work (which looks to have been done), and the previous project site at pouchdb.com still exists where it shouldn't. The IPMC raised these issues with the project's mentors, and the project is working to address them.

Community

New IPMC members:

Jark Wu - Russell Spitzer

People who left the IPMC:

No one

New Podlings

None

Podlings that failed to report, expected next month

TODO

Graduations

None

The board has motions for the following:

None

Releases

The following releases entered distribution during the month of April:

Cloudberry 2.1.0
Fluss-rust 0.1.0
Hamilton 1.90.0
Iggy 0.8.0
KIE 10.2.0 - ResilientDB 1.12.0

IP Clearance

None

Legal / Trademarks

N/A

Infrastructure

N/A

Burr

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:

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:

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

Casbin

Casbin is a powerful, open-source access control framework that provides a unified, model-driven approach to authorization.

Casbin has been incubating since 2026-02-07.

Three most important unfinished issues to address before graduating:

Establish a clear release process aligned with ASF guidelines and perform the first official Apache release. 2. Grow the community by onboarding new contributors from diverse organizations and transitioning discussions to Apache mailing lists. 3. Complete the formal transfer of domains and trademarks to the ASF.

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?

Officially announced Casbin's acceptance into the Apache Incubator and published the news via project blogs and community channels
Raised community activity: a new group of developers have joined the discussions on Discord and GitHub Discussions
Maintained steady growth in GitHub stars (the main repository increased from 19.4k to 20.1k)
During the incubation period, the download volume of packages across all language versions has kept rising, with the overall ecological adoption growing steadily
dev@casbin.apache.org saw 44 emails (mostly Dependabot bot notifications), including a community discussion proposal, with new subscribers joining.

How has the project developed since the last report?

This is the first official monthly report for Casbin following its admission to the Apache Incubator
Added standardized configuration files and optimized the project's overall configuration management system
Implemented ASF compliance requirements: added the official .asf.yaml configuration file and Apache disclaimer file to ensure the project is fully compliant with the foundation's norms
Completed the addition of standard Apache License 2.0 headers to the entire codebase and initiated the preliminary intellectual property transfer process to the ASF
A total of 30 PRs merged and 40 issues closed during the incubation period

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:

No apache release yet.

When were the last committers or PPMC members elected?

2026-02-07

Have your mentors been helpful and responsive?

Yes, very helpful and responsive.

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?

Name is approved: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-251

Signed-off-by:

(casbin) Hao Ding
Comments:
(casbin) Huajie Wang
Comments:
(casbin) Hulk Lin
Comments:
(casbin) Jerry Shao
Comments:
(casbin) Zili Chen
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:

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:

(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. Currently, the community is actively advancing the development of Graph Memory, aiming to serve as the underlying infrastructure for Agent Memory.

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, and bugfix. Additionally, several PRs are currently under review.

Furthermore, multiple community contributors are actively participating in CoC Asia 26, which will be held in Beijing, China, and have prepared multiple proposals for the associated Incubator, Streaming, and Data+AI tracks.

How has the project developed since the last report?

Over the past month, the GeaFlow project has continued its progress with a focus on code robustness, dependency management, and community facilitation. Key developments include:

Introduced the CONTRIBUTING.md file to outline contribution guidelines, facilitating easier onboarding for new developers (#765).
Enhanced code stability by adding checks for empty search results to prevent array out of bounds errors (#769) and handling null/empty inputs in average methods (#760).
Optimized code quality by defining the BYTES_PER_KB constant for consistency (#770), replacing raw type usage with type-safe methods (#766), and excluding conflicting lucene-core dependencies (#778).
Improved CI infrastructure by formatting build and test commands for better readability (#763).
New pull requests were opened targeting production GCN inference pipelines, hot-reload mechanisms, and vector implementation, indicating active development in AI capabilities and architecture optimization.

These updates demonstrate continued advancement in codebase health, project infrastructure stability, and the expansion of Graph+AI features.

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:

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:

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

IPMC/Shepherd notes:

Pony Mail

Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

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:

(ponymail) John D. Ament
Comments:
(ponymail) Dave Fisher
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:

None

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

None, Nothing much of news from previous report

How has the community developed since the last report?

The community has focused heavily on getting Release 0.6.0 through the incubator review process. A significant portion of the recent mailing list discussions involved working through review feedback to ensure the project is fully compliant with graduation requirements, specifically around the proper attribution and packaging of legal files.

The community wants to finalize and publish Release 0.6.0 and then push for graduation once the release process completes.

How has the project developed since the last report?

The project progressed through Release 0.6.0 preparation, moving from RC3 up to RC5 votes. The main technical work involved fixing the assembly process so the fat jar correctly includes all licenses and notices from bundled dependencies. We also had some minor repository maintenance, such as updating GitHub Actions for SBT setup.

The upcoming release officially brings support for Scala 2.13 and Spark 3.4.4.