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

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.

As of November, there are 29 podlings under incubation. Three releases were made during the month, and three IP clearances were completed. One podling, Apache Wayang, graduated during the month, and no podlings retired. There were no additions to IPMC membership, and one person stepped down.

Mailing list traffic in November covered the usual Incubator topics, including release votes, graduation, IP clearance, and incubation governance and mentor practices.

A discussion was held on how podlings can use existing tooling and automation to validate releases. It was noted that there has been a shift from release issues that these tools can detect toward issues that require greater human judgment and review.

A new public Mentor attribution page was created, listing mentors and the podlings they have supported over time. This improves transparency and recognition of mentoring contributions, provides an additional oversight signal for identifying mentor load, and assists the IPMC in selecting mentors for new incubation projects.

The Incubator Training Hub and wiki were expanded with additional materials.

New Incubator guides include:

• Neutrality in Practice: a practical guide on maintaining neutrality in projects.
• Mentor Engagement Patterns: examines how mentoring impacts podling health, independence, and graduation.
• Mentor Trends: reviews long-term changes in podling challenges and mentor focus areas.
• Mentor Replacement: guidance on how and when to replace mentors.
• Select Your Mentors: guidance on how to select mentors for a podling.

New Incubator case studies:

• Incubator Health: a review of the Incubator over 20 years.
• 10 Years of the Incubator: a detailed look at the last decade.
• IPMC Governance: analysis of participation, continuity, and how governance capacity rises and falls with podling load.
• Governance Patterns: a broader view of governance patterns in the Incubator.
• Podling Governance Patterns: how podlings develop governance practices during incubation.
• Community and Governance Growth: analysis based on data from more than 100 podlings.
• Incubator Discussion Trends: analysis of 10 years of Incubator discussions.

This detailed analysis of 20 years of Incubator data, covering governance threads, release votes, subject-line activity, podling population records, and contributor participation, shows consistent long-term improvement in the Incubator's operations. Governance activity tracks podling load, with lower podling numbers corresponding to more predictable behaviour and steadier reviewer availability. Across the last decade, release cadence has improved, first-release success rates are significantly higher, repeated release candidates are less common, and release-vote data show a higher number of releases over time. These improvements reflect more precise guidance, stronger documentation, and sustained mentor support. Podling reporting reliability has also strengthened, with far fewer missed or incomplete reports and closer alignment with expectations. Graduation and retirement patterns remain consistent with historical norms. The Incubator no longer experiences the governance irregularities, bottlenecks, or shock events that appeared in earlier years.

A small program-level risk remains that fewer opportunities for new contributors to participate in governance activities may slow future renewal. However, recent improvements in mentor onboarding, documentation of cultural knowledge, and broader availability of guidance for both podlings and mentors are likely to offset this.

Practising the Apache Way was also delivered as reusable learning materials, a workshop, and a micro-learning course.

The Mentor Topic of the Month discussion continued, with October’s topic focused on engaging new contributors. November’s topic focused on using chat and instant messaging responsibly during incubation.

An optional six-month community health review experiment is underway, with BifroMQ invited to participate. This uncovered some governance issues that the podling is now addressing. BifroMQ is also continuing with the trademark registration in China.

There was a minor documentation update to clarify how podlings should add PPMC members, as the previous guidance was outdated.

The experimental podling health reports are being adopted and are showing direct improvements in podling reporting.

There is ongoing discussion about the future of Apache Baremaps, and the project may retire if activity does not improve.

Apache PouchDB reported that earlier incubation delays have now been resolved, and the project is working toward the first Apache-compliant release.

Apache Polaris continues to show strong and sustained activity. Several IPMC members have suggested the podling should begin discussions about graduation.

OpenServerless has not made a release yet and has been encouraged to do so, and to move more of its discussion to the mailing list. The project has now started a discussion on its first release.

Most podlings continue to make progress toward graduation. Both Livy and Toree are working on their next releases, and once those are completed, they are expected to continue discussing and working toward graduation.

Those with keen eyes may notice that this is the second Incubator report in a row where all podling reports have been submitted.

Community

New IPMC members:

• None

People who left the IPMC:

• Lewis McGibbney

New Podlings

• None

Podlings that failed to report, expected next month

• None

Graduations

• Wayang

  The board has motions for the following:

• None

Releases

The following releases entered distribution during the month of November:

• Apache Fluss 0.8.0
• Apache GeaFlow 0.7.0
• Apache HugeGraph 1.7.0

IP Clearance

• Cassandra Python driver
• Cassandra CPP driver
• Phoenix Adapters

Legal / Trademarks

N/A

Infrastructure

N/A

Table of Contents

Auron
Baremaps
BifroMQ
Fesod
Gealfow
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:

1. Ensure that the website and codebase are fully compliant with ASF policies.
2. Increase public communication on dev@ and ensure all project decisions and planning are captured on the mailing list.
3. Grow the community and attract more contributors and users.

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?

1. One new committers added: Ruilei Ma
2. 20 active code contributors, including 10 new contributors.
3. made a presentation at RustChinaConf 2025.

How has the project developed since the last report?

1. The community has published its first incubating release (apache-auron-incubating-v6.0.0)
2. 179 commits since 2025-08-31
3. The community continues to improve Spark on Auron, including the implementation of numerous native functions, enhancements to test cases, and improvements to build scripts.
4. The community is making progress on Flink on Auron, having completed the design proposal document, and refactored the common core module (auron-core).

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-17

When were the last committers or PPMC members elected?

2025-09-22

Have your mentors been helpful and responsive?

 Yes, all the mentors are helpful and responsive on the project bootstrap and community growth.

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

Yes. The podling name “Auron” has been reviewed by the VP, Brand. We are not aware of any misuse by third parties.

Signed-off-by:

•  (auron) Becket Qin
  Comments:
•  (auron) Calvin Kirs
  Comments:
•  (auron) Hao Ding
  Comments: keep working
•  (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. Discussing the future of the project

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

The project is used in production by a few companies, but we struggle to build a sustainable community. We will initiate a discussion on the project's future early in 2026. A possibility would be to retire it from the Apache Incubator and to continue the development under a lighter process within its original organization.

How has the community developed since the last report?

The project activity decreased further since the last report.

How has the project developed since the last report?

We fixed minor issues.

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-02-07

When were the last committers or PPMC members elected?

In June 2024.

Have your mentors been helpful and responsive?

Yes.

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

Yes.

Signed-off-by:

•  (baremaps) Bertrand Delacrétaz
  Comments:
•  (baremaps) Martin Desruisseaux
  Comments:
•  (baremaps) Julian Hyde Comments: Activity is low, and even though Baremaps has users in production, the community is not increasing in size. The project should consider retirement. (And it is.)
•  (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. Complete the first Apache Incubator release and establish a regular release cadence.
2. Increase public communication on dev@ and ensure all project decisions and planning are captured on the mailing list.
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?

The primary concern is low traffic on the dev@ list and limited visibility of development discussions. Recent mentor feedback highlighted the need to move architectural decisions, release planning, and prioritization discussions onto dev@ to comply with ASF governance expectations.

In addition, regarding the “BifroMQ” trademark transfer in China: in response to a time-limited office action from the China National Intellectual Property Administration (CNIPA), Baidu submitted the requested supplemental materials before the deadline. We are now waiting for an update from ASF on the status and next steps.

How has the community developed since the last report?

Community activity on GitHub remains steady, but public communication has been low. Following mentor feedback, the PPMC began improving transparency by starting public discussion threads, including a DISCUSS thread for the first release.

We also launched the “BifroMQ” WeChat Official Account to support outreach to the Chinese-speaking community. The account name currently uses “BifroMQ” (without the “Apache” prefix) because the platform requires formal authorization to use “Apache” in the account name. The account description clearly identifies the project as “Apache BifroMQ (Incubating)”.

Official project discussions and decisions continue to happen on the mailing list.

How has the project developed since the last report?

Work toward the first incubator release has been completed, including architectural refactoring, API stabilization, and Apache compliance work (LICENSE/NOTICE, headers, package renaming, distribution scripts). A DISCUSS thread(https://github.com/apache/bifromq/discussions/192) for the 4.0.0-incubating release has been opened to gather community feedback before preparing RC1.

A significant amount of work came from supporting an early enterprise adopter running BifroMQ in production, resulting in important optimizations and bug fixes now included in the upcoming release.

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-02-25

When were the last committers or PPMC members elected?

No new committers or PPMC members have been added since incubation started.

Have your mentors been helpful and responsive?

Yes, our mentors are very helpful.

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

Yes. The podling name “BifroMQ” has been reviewed by the VP, Brand. We are not aware of any misuse by third parties.

For outreach to the Chinese-speaking community, we have created a WeChat Official Account currently named “BifroMQ”. The platform requires an authorization document to use “Apache” in the account name, so we are temporarily using “BifroMQ” as the account name while clearly stating “Apache BifroMQ (Incubating)” in the description.

We would appreciate guidance from ASF (Incubator and Brand) on the proper process to obtain authorization for using the full “Apache BifroMQ” name for this account, so that we can align fully with the Incubator publicity policy.

Signed-off-by:

•  (bifromq) Christofer Dutz
  Comments: The "last release" was a pre-Apache release. Since I last brought up the issue of the lack of public discussions, more discsussions are showing up. I hope the project will continue doing that and not only for trivial things.
•  (bifromq) Xiangdong Huang
  Comments:
•  (bifromq) Calvin Kirs
  Comments:
•  (bifromq) Penghui Li
  Comments: LGTM
•  (bifromq) Sheng Wu
  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:

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?

1. The project now has several active new contributors.
2. 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,

1. We refactored several core classes to ensure full compliance with licensing requirements.
2. 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?

Yes. They are very nice and helpful.

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

Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246

Signed-off-by:

•  (fesod) tison
  Comments:
•  (fesod) Dave Fisher
  Comments:
•  (fesod) Huajie Wang
  Comments:
•  (fesod) PJ Fanning
  Comments:

IPMC/Shepherd notes:

---

Geaflow

GeaFlow is a streaming graph computing engine for distributed large-scale real-time graph storage and analysis. It supports trillion-level graph storage, hybrid graph and table processing, real-time/offline graph computing, and interactive graph analysis.

GeaFlow has been incubating since 2025-06-06.

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?

1. Two new contributors have joined the community.

How has the project developed since the last report?

1. Over the past month，12 pull requests have been merged, development has focused on new features, code quality, and documentation. Key additions include a Paimon stream source and support for Jaccard similarity. Infrastructure saw the introduction of a cluster coefficient and GitHub Actions condition checks. Code health was improved by standardizing editor configs, removing unnecessary files/methods, and fixing a data loss bug after failover.
2. The first community edition: V0.7.0 has been released on November 19th.

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 first community version was released on November 19th.

When were the last committers or PPMC members elected?

After reviewing our active community contributors, we have selected two qualified candidates. The process now advances to a period of discussion followed by a formal voting process.

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
•  (GeaFlow) xinwang
•  (GeaFlow) lzljs3620320
•  (GeaFlow) jmclean
•  (GeaFlow) paulk

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. Continue expanding the community, release more versions under ASF
2. Increase the use of GitHub Discussions/Issues integrated with mailing lists.

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

None

How has the community developed since the last report?

• Discord members count 560+, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements.
• Github stars reached 3.3K+
• Crates downloads reached 168K+
• Presented Apache Iggy at the ApacheCon in September
• Recent blog post on Building WebSocket Protocol in Apache Iggy using io_uring and Completion Based I/O Architecture (https://iggy.apache.org/blogs/2025/11/17/websocket-io-uring) drew a lot of attention on other sites and social media and attracted critical talent

How has the project developed since the last report?

• Release 0.6.0 is under voting process
• Rewrite the server to use io_uring with thread-per-core, shared-nothing architecture using compio runtime
• Implement WebSocket transport with custom compio-ws library designed for completion-based I/O
• Add helpful diagnostic messages for io_uring runtime failures (RLIMIT_MEMLOCK, seccomp)
• Harden security with auto-generated root password and Argon2 password hashing (replacing bcrypt)
• Replace CRC32 checksums with xxHash3 and use UUIDv4 for random message IDs
• Implement GetClusterMetadata command with leader-aware connect mechanism in SDKs
• Add foundation for clustering with consensus, metadata modules, and TransportEndpoints
• Introduce Iceberg sink connector with S3 storage, REST catalogs, and fan-out routing
• Add Elasticsearch sink and source connectors with rustls TLS support
• Implement Flink processor and processor infrastructure for stream processing
• Extend connectors runtime with configuration provider trait, HTTP config provider, and E2E test suite
• Add high-level IggyPublisher and IggyConsumer clients to C# SDK with TCP reconnection, TLS, and AES encryption
• Implement async/non-blocking Java SDK client using Netty with CompletableFutures
• Add TLS TCP support to Java and C# SDKs
• Extend Python SDK with connection string support, bytes data, typing stubs, and musllinux wheels
• Improve Go SDK with DeleteConsumerOffset, error handling refactor, and deserialization fixes
• Add virtual commands (ensureStream, ensureTopic, ensureGroup) and nullable returns to Node.js SDK
• Implement builder pattern for Rust SDK client and unify TransportProtocol enum across codebase
• Fix multiple consumer group bugs (offset storage, deletion, validation, hashmap usage)
• Fix active segment position inconsistency and Murmur3 hash shard assignment skew
• Unify Helm charts for server and UI with environment variable support
• Overhaul CI/CD with intelligent change detection, dual caching, and multi-arch Docker builds (~40% faster)
• Update to Rust 1.90 and fix Docker builds for macOS (ARM64 support)
• Improve Web UI with autocomplete, keyboard navigation, large number rendering, and security fixes
• Add -c/--consumer-group flag to CLI for consumer offset commands

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:Expanding ecosystem

Date of last release:

  2025-08-10 (new release 0.6.0 is expected to land by 2025-12-12)

When were the last committers or PPMC members elected?

February 2025, at the time of onboarding to Apache Incubator Program.

Have your mentors been helpful and responsive?

Yes, mentors are helpful and in general responsive.

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

There are no known brand and naming issues as reported here. VP, Brand approved the project name.

Signed-off-by:

•  (iggy) Hao Ding
  Comments: Nice work!
•  (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. Category X libraries (we're making progress, next release should substantially cut down the number of Category X issues)
2. Community Building
3. More releases

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

None

How has the community developed since the last report?

We just finished a vote for a new committer today!

How has the project developed since the last report?

Working towards another release, early 2026.

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-07-10

When were the last committers or PPMC members elected?

Today!

Have your mentors been helpful and responsive?

Mentors have been good so far. No issues.

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

Yes

Signed-off-by:

•  (kie) Brian Proffitt
  Comments:
•  (kie) Claus Ibsen
  Comments:
•  (kie) Andrea Cosentino
  Comments: All good.

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. Community building is still under effort.
2. Consolidation and alignment of the documentation site project.
3. Started a discussion on ML on how to make the build ASF compliant.

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

None

How has the community developed since the last report?

Since last report, nothing changed.

How has the project developed since the last report?

Since the last report the project was extended / improved by:

• adding a devcontainer with a development environment integrated inside the platform.
• adding an Admin API component with some REST api (for authentication purposes and for building custom runtime images on the fly)
• replacing MinIO component inside the operator with SeaweedFS (which is under Apache License 2.0)

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:

None

When were the last committers or PPMC members elected?

2024-08-22

Have your mentors been helpful and responsive?

No answer.

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

No answer.

Signed-off-by:

•  (openserverless) Bertrand Delacrétaz
  Comments:
•  (openserverless) Enrico Olivelli
  Comments:
•  (openserverless) François Papon
  Comments: Low activity on the mailing list, no release since the start of the incubation, no new committer.
•  (openserverless) JB Onofré
  Comments: OpenServerless report ?
•  (openserverless) PJ Fanning
  Comments: I agree with what François says above

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. Upgrade to support the latest versions of Python, including upgrading to the latest signal-processing-algorithms library.
2. Do more releases, so that it is a routine, repeatable process.
3. 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:

1. 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.
2. 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.
3. 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?

Yes.

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

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:

1. Make more apache release.
2. Build and grow community.

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?

More contributors have become active and have collectively completed a total of 16 PR submissions.
Expand our contributor base continuously, and actively cultivate and develop future committers and PPMC members.

How has the project developed since the last report?

The primary accomplishments include the iteration of system optimization and intelligent analysis.

1.System Stability & Performance Optimization.
Memory and Resource Management: Enhanced memory handling to prevent out-of-memory errors; introduced inode change detection to prevent resource leaks;
optimized resource cleanup to improve long-term operational stability.

File and Logging Management: Added file read exception retry mechanism; increased frequency of file truncation detection and log rotation; resolved data loss issues to ensure logging continuity.
Task Scheduling and Execution: Optimized the message-sending order in PingTask and added server list validation to prevent startup blocking; supports customizable collection intervals and control state export periods.

2.Enhanced Analysis and Problem Diagnosis.
Core Feature: Implemented traceId-based root cause analysis, enabling rapid tracing and pinpointing of issue origins.
Module Enhancement: Refactored the intelligent analysis module to improve log processing and automated issue identification, providing stronger support for operational decision-making.

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-03-26.

When were the last committers or PPMC members elected?

2025-01-13

Have your mentors been helpful and responsive?

Yes, mentors are helpful and responsive.

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

Not yet.

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. Check the Polaris existing trademarks at the ASF (transfer has been done, to be verified)
2. Perform a namesearch (for the record as previous point)

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

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
• Apache Polaris website is now integrated to analytics.apache.org

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?

Mentors are helpful and responsive.

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

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

Signed-off-by:

•  (polaris) Holden Karau
  Comments:
•  (polaris) Kent Yao
  Comments:
•  (polaris) Ryan Blue
  Comments:
•  (polaris) Jean-Baptiste Onofré
  Comments: Again a solid activity on the podling, I can see new contributors and consistent interest. Maybe the podling should consider starting discussion about graduation soon ?
•  (polaris) François Papon
  Comments: As new mentor, I can see a lot of dicussion on the mailing list, the community looks to be safe and growing. The project has released several version and it's closed to the graduation.

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. Finish the initial code import (see below)
2. Making a release   3. Adding contributors

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

After a good start in Q2, the project was stalled in Q3 and first month of Q4 because of champion unavailability. The champion (me, jan@) had communicated to the rest of the incubating PPMC to clear out everything needed for the initial code import and then had to step away for personal reasons.

Those have resolved now, the code is now in ASF territory and we are doing the initial adjustments (file headers etc) as we speak and the following tasks are starting to be distributed among the rest of the team, so a single-person bottleneck should not hold the project back.

How has the community developed since the last report?

No noticeable changes yet, but some external contribution activity has occurred.

How has the project developed since the last report?

After clearing all hurdles with importing a 15 year old code base, we have the sources finally under ASF control. We are aiming to get to be in an ASF-releasable state in a few weeks.

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?

Mentors have flagged the slow progress and contributed to things resolving and moving forward.

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

PPMC have not yet requested a Podling Suitable Names Search

Signed-off-by:

•  (pouchdb) PJ Fanning
  Comments: Some progress happening now. No Podling Suitable Names Search done yet and that could cause issues if name is rejected.   - [x] (pouchdb) Jean-Baptiste Onofré
  Comments: Slow start in the podling, but now it seems to move forward. If the podling doesn't have time to report this month, maybe report next month ?

IPMC/Shepherd notes: