Page History

# Incubator PMC report for March 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

## Community

### New IPMC members:


### People who left the IPMC:


## New Podlings


## 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
  February:


## IP Clearance


## Legal / Trademarks


## Infrastructure


## Miscellaneous


## Credits

## Table of Contents  
[Auron](#auron)  
[Baremaps](#baremaps)  
[BifroMQ](#bifromq)  
[Caldera](#caldera)  
[Iggy](#iggy)  
[KIE](#kie)  
[OpenServerless](#openserverless)  
[Otava](#otava)  
[OzHera](#ozhera)  
[Polaris](#polaris)  
[PouchDB](#pouchdb)  
[GeaFlow](#geaflow)  

--------------------
## Auron

Auron accelerates Apache Spark SQL by providing an alternative vectorized
execution layer implemented in Rust, enabling native performance while
maintaining full             Spark compatibility.

Auron has been incubating since 2025-08-05.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

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

  - [ ] (auron) Becket Qin  
     Comments:  
  - [ ] (auron) Calvin Kirs  
     Comments:  
  - [ ] (auron) Hao Ding  
     Comments:  
  - [ ] (auron) Nicholas Jiang  
     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.
  2.
  3.

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

  - [ ] (baremaps) Bertrand Delacrétaz  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  
  - [ ] (baremaps) Julian Hyde  
     Comments:  
  - [ ] (baremaps) Calvin Kirs  
     Comments:  
  - [ ] (baremaps) George Percivall  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## BifroMQ

BifroMQ is a Java-based, high-performance, distributed MQTT broker with native multi-tenancy support, designed for large-scale connections and message delivery.

BifroMQ has been incubating since 2025-04-22.

### Three most important unfinished issues to address before graduating:

  1. Increase public exposure to expand the community user base and improve project visibility.

  2. Continue delivering regular releases, streamline the release management process, and rotate the Release Manager role among key contributors.

  3. Grow community participation beyond the original contributors, including attracting new reviewers and contributors.

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

We understand that the trademark transfer has been completed based on publicly available trademark ownership information (e.g. via https://aiqicha.baidu.com/mark/s?q=BIFROMQ&t=7).
However, we would appreciate receiving an official confirmation from ASF (a scanned copy of the signed transfer agreement would be sufficient) so that our company can properly archive the transfer documentation for internal compliance purposes.

### How has the community developed since the last report?

We have observed increasing activity on GitHub and the dev@ mailing list.
Our mentor (Chris) helped initiate a valuable discussion with the Apache IoTDB community, which may lead to potential collaboration between the two projects.
We have set up a WeChat Account (“BifroMQ”) to publish Chinese translations of release announcements. All published content is derived from or links back to the official Apache BifroMQ website, and the account is not used for community discussions.

### How has the project developed since the last report?

We completed our first incubating release after 3 RC votes.


### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2026-01-28

### When were the last committers or PPMC members elected?
None so far

### 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.

Our mentors have been 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?

We attempted to rename our WeChat account by adding the “Apache” prefix, based on PPMC consensus reached on the private mailing list. However, the request was rejected by the WeChat platform due to tightened naming policies, which now require an official authorization document from ASF to use “Apache” as an account prefix.
We would appreciate guidance on whether there is a formal ASF process to request such an authorization letter for external platform compliance purposes.

### Signed-off-by:

  - [ ] (bifromq) Christofer Dutz  
     Comments:  
  - [ ] (bifromq) Xiangdong Huang  
     Comments:  
  - [ ] (bifromq) Calvin Kirs  
     Comments:  
  - [ ] (bifromq) Penghui Li  
     Comments:  
  - [ ] (bifromq) Sheng Wu  
     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:

  1.
  2.
  3.

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



--------------------
## Iggy

Iggy is a high-performance, ultra-low latency and large-scale persistent
message streaming platform written in Rust.

Iggy has been incubating since 2025-02-04.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

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

  - [ ] (iggy) Hao Ding  
     Comments:  
  - [ ] (iggy) Yonik Seeley  
     Comments:  
  - [ ] (iggy) Zili Chen  
     Comments:  
  - [ ] (iggy) Hulk Lin  
     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.
  2.
  3.

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

  - [ ] (kie) Brian Proffitt  
     Comments:  
  - [ ] (kie) Claus Ibsen  
     Comments:  
  - [ ] (kie) Andrea Cosentino  
     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.
  2.
  3.

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

  - [ ] (openserverless) Bertrand Delacrétaz  
     Comments:  
  - [ ] (openserverless) Enrico Olivelli  
     Comments:  
  - [ ] (openserverless) François Papon  
     Comments:  
  - [ ] (openserverless) JB Onofré  
     Comments:  
  - [ ] (openserverless) PJ Fanning  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Otava

Apache Otava (incubating), a command-line tool, written in Python, detects and alerts about statistically significant changes in performance test results (more generally, time-series data) stored in CSV files or a number of supported databases.

A typical use-case of Otava is as follows:
1. A set of performance tests is scheduled repeatedly, such as after each commit is pushed.
2. The resulting metrics of the test runs are stored in a time series database (Graphite) or appended to CSV files.
3. Otava is launched by a Jenkins/Cron job (or an operator) to analyze the recorded metrics regularly.
4. Otava notifies about significant changes in recorded metrics by outputting text reports or sending Slack notifications.
5. Otava is capable of finding even small, but persistent shifts in metric values, despite noise in data. It adapts automatically to the level of noise in data and tries to notify only about persistent, statistically significant changes, be it in the system under test or in the environment.

Otava has been incubating since 2024-11-27. Otava entered Incubation as Hunter.


### Three most important unfinished issues to address before graduating:

  1. Establish frequent releases as a routine, repeatable process
  2. Improve documentation to lower the entry barrier for users and contributors.
  3. Define and document the desired long-term architecture. The goals of the long-term architecture are:
    a. Modularity: Keep the core library lightweight while making external dependencies (data sources and notification channels) pluggable.
    b. API stabilization: Clearly define and stabilize public interfaces prior to a 1.0.0 release.


### 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 community added one new committer and a PMC member, who contributeda a rewrite of the core changepoint detection algorithm and authored an introductory doc on changepoint detection theory in Otava.

Since the last report, there have been 4 additional contributors participated through patches and discussions. One contributor is a developer from RedPanda, who reports using Otava extensively for both continuous benchmarking and finding regressions in PRs.  Another contributor developed a visualization tool that allows users to model and explore changepoint detection results across different time series. This tool improves understanding of the algorithm’s behavior and provides a practical aid for internal development and experimentation.

Additionally, open-source projects that position performance as a key feature (e.g., [hardwood](https://github.com/hardwood-hq/hardwood/issues/25)) have expressed interest in using Otava for continuous benchmarking.

### How has the project developed since the last report?

The project addressed 3 out of 4 main previously stated priorities:
1. Upgraded to supported Python versions. Re-implement the core changepoint detection algorithm and drop the dependency on signal-processing-algorithms.
2. Added a new PPMC member. 
3. Publicity around the project. Since the last report, Henrik Ingo did a talk about Continuous Performance Engineering at FOSDEM 2026.

The remaining issue is making frequent releases a routine. As a first step, the project added a step-by-step release guide to facilitate repeatable releases.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [x] Initial setup
  - [x] Working towards first release
  - [x] Community building
  - [ ] Nearing graduation
  - [ ] Other:

We are seeing a slow positive trend in community building, but not yet nearing graduation.

A self review based on https://s.apache.org/727vc

Code 5/5 Licenses and Copyright: 5/5 Releases: 5/5 Quality: 5/5 Community: 7/7 Consensus: 4/5 (Missing: CS10) Independence: 2/2 Brand: 4/4


### Date of last release:

  2025-12-12

### When were the last committers or PPMC members elected?

March 2 2026


### Have your mentors been helpful and responsive?

Yes.

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

VP, Brand approved the new project name in February 2025. Our life as an ASF incubating project really only started after that date.
We are not aware of any trademark issues related to the new project name.

### Signed-off-by:

  - [ ] (otava) Dave Fisher  
     Comments:  
  - [ ] (otava) Enrico Olivelli  
     Comments:  
  - [ ] (otava) Lari Hotari  
     Comments:  
  - [ ] (otava) Mick Semb Wever  
     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.
  2.
  3.

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

  - [ ] (ozhera) Yu Xiao  
     Comments:  
  - [ ] (ozhera) Yu Li  
     Comments:  
  - [ ] (ozhera) Kevin Ratnasekera  
     Comments:  
  - [ ] (ozhera) Duo Zhang  
     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.
  2.
  3.

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

  - [ ] (polaris) Holden Karau  
     Comments:  
  - [ ] (polaris) Kent Yao  
     Comments:  
  - [ ] (polaris) Ryan Blue  
     Comments:  
  - [ ] (polaris) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (polaris) François Papon  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## PouchDB

PouchDB is an open-source JavaScript database inspired by Apache CouchDB
that             is designed to run well within the browser.

PouchDB has been incubating since 2025-04-15.

### Three most important unfinished issues to address before graduating:

  1. Making a release
  2. Adding contributors
  3. Finish infrastructure migration (currently working on the website)

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


### How hasAfter delays last year and the communitypromise to developedkeep sinceproject themomentum lastup, report?
this
has been the case.

### How has the projectcommunity developed since the last report?


###- HowWe wouldhave youadded assessa thenew podling's maturity?
Please feel free committer and PPMC member.
- Work continues on a first release

### How has the project developed since the last report?

We have migrated our website tech to a more modern platform that can
make use of the ASF website hosting infrastructure. Final steps are
taken at the moment of writing.

We also have received multiple external contributions from people
previously not affiliated with the project at a volume and quality
that exceeds the usual pace.

Finally, we have formalised our stance on LLM-generated code.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ X] Initial setup
  - [ X] Working towards first release
  - [ X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  XXXX-XX-XXn/a

### When were the last committers or PPMC members elected? elected?

  January 28th 2026


### Have your mentors been helpful and responsive?
Are
Mentors thingscontinue fallingto throughbe theactive cracks? If so, please list any
open issues that need to be addressed.and helpful


### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If
PPMC have not whatyet actionsrequested hasa thePodling PPMCSuitable takenNames to
correct this? Has the VP, Brand approved the project name?Search


### Signed-off-by:

  - [ ] (pouchdb) PJ Fanning  
     Comments:  
  - [ ] (pouchdb) Jean-Baptiste Onofré  
     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:

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.

### How has the project developed since the last report?

Over the past month, the GeaFlow project has continued its progress 
with a focus on feature enhancements, code quality improvements, 
and infrastructure updates. Key developments include: 

- Introduced the CASTS operator to enhance GeaFlow's reasoning 
capabilities within the AI component (#737). 
- Refactored varint encoding/decoding constants to improve code 
readability and maintainability (#744). 
- Updated repository references in documentation to reflect 
the official Apache location (#746). 
- Fixed typos in log messages and comments across multiple files (#752). 
- New issues were opened, covering topics such as architecture design, 
documentation consistency, contributor guidance, and potential overflow 
bugs, indicating active community scrutiny and roadmap discussions.

These updates demonstrate continued advancement in Graph+AI 
functionality, codebase health, project branding alignment, 
and community-driven evolution.


### How would you assess the podling's maturity?

Please feel free to add your own commentary.
  - [ ] Initial setup
  - [ ] Working towards first release
  - [X] 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
  - [x] (GeaFlow) xinwang
  - [ ] (GeaFlow) lzljs3620320
  - [ ] (GeaFlow) jmclean
  - [ ] (GeaFlow) paulk

### IPMC/Shepherd notes: