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 December 03	Podling reports due by end of day
Sun December 07	Shepherd reviews due by end of day
Sun December 07	Summary due by end of day
Tue December 09	Mentor signoff due by end of day
Wed December 10	Report submitted to Board
Wed December 17	Board meeting

Shepherd Assignments

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

Incubator PMC report for December 2025

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

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:

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:

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:

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:

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:

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:

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:

(bifromq) Christofer Dutz
Comments:
(bifromq) Xiangdong Huang
Comments:
(bifromq) Calvin Kirs
Comments:
(bifromq) Penghui Li
Comments:
(bifromq) Sheng Wu
Comments:

Fesod

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

Fesod has been incubating since 2025-09-17.

Three most important unfinished issues to address before graduating:

1.Ensure that the website and codebase are fully compliant with ASF policies. 2.Publish the first release under the Apache Incubator. 3.Continue to grow the community and word towards the ASF maturity Model.

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

No

How has the community developed since the last report?

The project now has several active new contributors.
We have created a Slack channel (under ASF) to facilitate communication.

How has the project developed since the last report?

We will initiate the community vote for the first release within the next two weeks,

We refactored several core classes to ensure full compliance with licensing requirements.
Formal preparation for the project's first official release has commenced.

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:

N/A

When were the last committers or PPMC members elected?

N/A

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 are very nice and helpful.

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?

No

Signed-off-by:

(fesod) tison
Comments:
(fesod) Dave Fisher
Comments:
(fesod) Huajie Wang
Comments:
(fesod) PJ Fanning
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

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:

A set of performance tests is scheduled repeatedly, such as after each commit is pushed.
The resulting metrics of the test runs are stored in a time series database (Graphite) or appended to CSV files.
Otava is launched by a Jenkins/Cron job (or an operator) to analyze the recorded metrics regularly.
Otava notifies about significant changes in recorded metrics by outputting text reports or sending Slack notifications.
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:

Upgrade to support the latest versions of Python, including upgrading to the latest signal-processing-algorithms library.
Do more releases, so that it is a routine, repeatable process.
Grow the community and ultimately vote to admit new committers and PPMC members. Do more publicity around the releases and the project in general. This is an item where we certainly hope to see new contributors.

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?

In our previous report we already shared our successfully completing the first release as an Apache Incubator process. This first release was mostly focused on a) bringing together various github forks under the a unified ASF upstream project, and b) releasing one release with the new project name, and following the ASF process, but one that did not in itself contain a lot of new features or changes beyond (a).

With such an inaugural release out of the way, we have seen over the past 4 months a handful of patches that make more substantive changes to the codebase. We still have a couple foundational tasks remaining that are holding us back from accepting new code contributors and contributions without any friction, but the door is at least more open than it was before the July release (0.6.1).

The remaining foundational tasks are:

Doing another release, 0.7.x, that is still focused on backward compatibility with our past, and merely introduces small fixes in the functionality itself, as well as the release process. Re-rehearsing the actions related to releasing, and related collaboration among the project committers seems a significant part of the process of becoming a fully graduated ASF project.
Cutting the dependency on an external implementation of the "E-Divisive means" algorithm, which is the very heart of what Otava does. This is the so called "signal-processing-algorithms" pip module released by MongoDB under the Apache 2.0 License, but not donated to ASF. We have come to the conclusion we need this very core functionality to be part of our own code base and version control, and since we didn't manage to get the MongoDB team's attention, we decided to rewrite an independent implementation.
Upgrading from the unsupported python versions 3.8 and 3.9 to the most recent versions.

1 above is already undergoing voting, and 2 is in review and approved, waiting to be merged.

The 0.7.x release also brings back an additional distribution format: docker images.

For the rewrite of the E-Divisive algorithm we are glad to report we found a completely new contributor to the project, with sufficient mathematical education to take on this somewhat daunting task. In the process of re-implementing the algorithm directly from its academic publication, the contributor managed to discover a bug/omission in the implementation we have been using for almost a decade now. The effect of this discovery is that the new implementation will find change points that the original algorithm tends to miss, in situations where there are 2 or more changes close to each other.

The fact that the new implementation of the E-divisive algorithm was done by a completely new contributor, that did not look at the MongoDB implementation before creating the new implementation, means that our new implementation ought to qualify as a properly independent, clean room implementation. While this was not a strict requirement for this task, now that this is the outcome, we wish to record it in the board minutes.

Altogether we have during our first year as an ASF incubator now received code contributions from 3 founding project members and 3 new contributors and one of the project mentors. In addition to these 7 there have been several more that contributed either a bug report or participated in an email thread, or voting for a release. One of these was a developer from the Tarantool open source database, that started using Otava as part of their Continuous Benchmarking. As discussed in this update, we believe there are more interested contributors that are still held back by our old python version and untangling a major legacy dependency.

We have not yet approved new committers or PPMC members to the project, as there was not yet sufficient time and opportunity to demonstrate significant and sustained contributions to the project. We are optimistic that we are moving in the right direction where this could be happening in a near future.

On the topic of committers and PPMC members it is notable that several of the past contributors that were listed in our project proposal a year ago, and approved as founding PPMC members, have not actually shown up on the ASF mailing list during our first year. We will follow up with these individuals to confirm their desired status with the project, and take appropriate action based on that outreach. (From a community diversity and robustness perspective, it should be mentioned that the 3 founding contributors that have been the most active, still represent 3 different employers, and to the best of our knowledge, the new contributors are also employed by 3 net new employers.)

How has the project developed since the last report?

(See above, it felt meaningful to combine these two answers.)

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:

We are progressing well with the 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: 4/5 Quality: 5/5 Community: 7/7 Consensus: 4/5 (Missing: CS10) Independence: 2/2 Brand: 4/4

Date of last release:

2025-07-25

When were the last committers or PPMC members elected?

None yet.

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.

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?

VP, Brand approved the new project name in February. 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: An amazing amount of detail, thanks.
(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:

Check the Polaris existing trademarks at the ASF (transfer has been done, to be verified)

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?

Between 2025-07-31 and 2025-10-31:

2 new releases
17 new contributors
649 PRs opened / 517 PR merged
745 messages on the dev@ mailing list
Apache Polaris is now integrated to analytics.apache.org which shows 10,000 monthly visitors to polaris.apache.org across the globe [website link]

We are happy to see new contributors who contributed important new features:

OPA support.
Polaris Console (UI) is coming.
S3 KMS support.

How has the project developed since the last report?

We did 1.1.0-incubating and 1.2.0-incubating releases since the last report. 1.3.0-incubating release is also in preparation.

Here's the highlights about project development since the last report:

Improvement on the website, adding new blog posts (StarRocks and Polaris integration)
Moving forward on NoSQL support
New OPA Authorizer
New MetricsReport interface
New JDBC schema evolution support
A lot of improvements on Python (CLI, ...)
Enhanced support for S3-compatible (on-prem) storage
Automated release workflows are in place, ongoing work to support ATR

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2025-10-27

When were the last committers or PPMC members elected?

Last PPMC member has been elected on 2025-11-19 (Yong Zheng).

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.

Mentors are 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?

Yes, the podling manages the brand/trademarks, especially working with 3rd parties organizing meetups.