You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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 March 04

Podling reports due by end of day

Sun March 08

Shepherd reviews due by end of day

Sun March 08

Summary due by end of day

Tue March 10

Mentor signoff due by end of day

Wed March 11

Report submitted to Board

Wed March 18

Board meeting


Shepherd Assignments

Calvin Kirs
PouchDB
Dave Fisher
OzHera
Drew Farris
Caldera
Justin Mclean
Baremaps
P. Taylor Goetz
HoraeDB
PJ Fanning
Otava
Timothy Chen
Auron
Timothy Chen
BifroMQ
Willem Jiang
Iggy
Xuanwo
KIE
Xuanwo
OpenServerless

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

Infrastructure

Miscellaneous

Credits

Table of Contents

Auron
Baremaps
BifroMQ
Caldera
Iggy
KIE
OpenServerless
Otava
OzHera
Polaris
PouchDB


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:

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:

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

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:

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:

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:

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

Otava, a command-line tool, written in Python, that detects statistically significant changes in time-series data stored either in databases or CSV files. Otava entered Incubation as Hunter

Otava has been incubating since 2024-11-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:

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

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:

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:

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:

  •  (pouchdb) PJ Fanning
    Comments:
  •  (pouchdb) Jean-Baptiste Onofré
    Comments:

IPMC/Shepherd notes:

  • No labels