FINAL DO NOT EDIT

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

Shepherd Assignments

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

Incubator PMC report for September 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 August, there are 31 podlings in incubation. Podlings executed 7 releases during the month, and no IP clearances were completed.

Several new proposals were discussed. Three podlings, Teaclave, HeertzBeat and Training, graduated to Top-Level Projects. One new podling entered incubation, Auron (previously named Blaze), no podlings retired, and no IP clearances were completed this month. No changes were made to IPMC membership.

Only PonyMail failed to submit a report and will be asked again to report next month. Given its repeated lapses, it may be time to revisit earlier discussions about the project’s future, as past conversations have not reached a clear consensus.

Several talks were given at Community Over Code Asia in the Incubator Track.

A discussion on the mailing list in August focused on graduations, with Teaclave and DevLake both moving toward top-level status. A proposal was raised for OpenOffice Cloud+AI. Discussions also covered mentor engagement, including reminders about missing reports, handling inactive mentors, and onboarding guidance for new mentors. Work continued on training resources, and some cleanup of retired podlings.

Among the long-term podlings, both Toree and Livy appear to have stalled in their progress toward graduation and have been contacted regarding their progress. All other long-running podlings have either graduated or retired.

Note: OzHera did not have a mentor sign-off when submitted; they have been contacted about this.

Community

New IPMC members:

Huajie Wang
Ed Espino

People who left the IPMC:

Sharan Foga
Woonsan Ko

New Podlings

Auron

Podlings that failed to report, expected next month

PonyMail

Graduations

HertzBeat
Teaclave
Training

The board has motions for the following:

None

Releases

The following releases entered distribution during the month of August:

Cloudberry 2.0.0
Fluss Shaded 1.0
GraphAr 0.13.0
Iggy 0.5.0
Seata 2.5.0
Polaris 1.0.1
Wayang 1.1.0

IP Clearance

None

Legal / Trademarks

N/A

Infrastructure

N/A

Auron

The Auron accelerator for big data engine (e.g., Spark, Flink) leverages native vectorized execution to accelerate query processing. It combines the power of the Apache DataFusion library and the scale of the distributed computing framework.

Auron has been incubating since 2025-08-05.

Three most important unfinished issues to address before graduating:

Finish the source code cleanup.
Publish the first Apache release.
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?

One new committer joined the project.

How has the project developed since the last report?

No

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?

Sept. 1, 2025 - Fei Wang(turboFei)

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

Signed-off-by:

(auron) Becket Qin
Comments:
(auron) Calvin Kirs
Comments: Progressing well.
(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:

Expanding the community
Making releases
Discussing the future of the project

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

We recognize the need to further expand the community and strengthen contributor retention. We aim to make progress on this in the coming year. If these challenges cannot be addressed, we will initiate a discussion on the project’s future, including the possibility of retiring it from the Apache Incubator. In that case, development may continue under a lighter process within its original organization.

How has the community developed since the last report?

The project activity slowed during the summer but is expected to resume in the coming months.

How has the project developed since the last report?

We have addressed security issues and introduced security guidelines.

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, Julian Hyde and Calvin Kirs remain responsive and provide support as needed.

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

Yes

Signed-off-by:

(baremaps) Bertrand Delacretaz
Comments:
(baremaps) Martin Desruisseaux
Comments:
(baremaps) Julian Hyde
Comments:
(baremaps) Calvin Kirs
Comments: The community has shown very little activity.
(baremaps) George Percivall
Comments:
(baremaps) Martin Desruisseaux
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:

Complete the first incubator release.
Gain more public exposure and user base.
Attract more contributors.

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

We received confirmation from Mark that the paperwork for the trademark transfer has been submitted. The process is expected to take around six months to complete.

How has the community developed since the last report?

One contributor joined the community.
A press release was published via a company media channel to promote Apache BifroMQ.
One of the largest smart home appliance companies adopted Apache BifroMQ.

How has the project developed since the last report?

Working toward a code freeze for the first incubator release (9 PRs merged).
Fixed multiple issues identified in real production usage.

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?

None since entering the incubator.

Have your mentors been helpful and responsive?

Yes, we have received helpful guidance.

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

The transfer of BifroMQ’s trademark is in progress.

Signed-off-by:

(bifromq) Christofer Dutz
Comments:
(bifromq) Xiangdong Huang
Comments:
(bifromq) Calvin Kirs
Comments:
(bifromq) Penghui Li
Comments: Good progress on stabilizing the project and preparing for the first release. Encouraging to see ongoing community growth.
(bifromq) Sheng Wu
Comments:

IPMC/Shepherd notes:

Burr

Burr is a lightweight in-process python framework that standardizes the expression and execution of state machines as action-driven graphs, while making graph execution easily observable. It is particularly suited for AI agent workflows, simulations, and other dynamic systems, and comes with a self-hostable observability UI that integrates with OpenTelemetry.

Burr has been incubating since 2025-05-24.

Three most important unfinished issues to address before graduating:

Finish docs
Add licenses to all files
Make a release

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

We're slow.

How has the community developed since the last report?

New discord members.

How has the project developed since the last report?

We have a user wanting to contribute a major UI feature.

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?

May

Have your mentors been helpful and responsive?

We're just slow to get through all the red-tape to release.

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

No answer.

Signed-off-by:

(burr) Kevin Ratnasekera
Comments:
(burr) Ayush Saxena
Comments: Progressing slowly
(burr) PJ Fanning
Comments: This podling has member overlap with Hamilton and the focus appears to be on Hamilton right now so Burr progress is slow

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:

Release the first version.
Establish a well-defined community governance framework.
Enhance the diversity of community (attracting more committers, contributors, and users).
Drive the community forward in accordance with the technial roadmap in issues.

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?

Several active users and contributors joined the community since the last report.
Update the community governance. #586
Participated in open source activities such as GLCC and OSPP, and assisted students with coding tasks.
TuGraph × AWS User Group Tech Meetup: LITAO LIN attended the event and presented an introduction of Apache GeaFlow to the audience. The Meetup attracted over 150 technical professionals and AI enthusiasts. Meetup introduction (in chinese)

How has the project developed since the last report?

Since the last report, 4 new features have been merged, including support for asynchronous writing in Paimon, Paimon source, Hive source, and MCP. Additionally, several bug fixes and improvements have been made.
All content for the GeaFlow website is now fully prepared, and we are currently seeking support from the Apache Infra team to deploy the site. We expect it to go live within the next month.
Prepare for the first release version.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release (IMPORTANT)
Update the community governance
Update the doucments
Community building
Nearing graduation
Others

Date of last release:

We will launch the first version int the next one weeks.

When were the last committers or PPMC members elected?

None since entering the incubator.

Have your mentors been helpful and responsive?

Yes, we have received helpful guidance.

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

N/A

Signed-off-by:

(geaflow) Willem Ning Jiang
Comments:
(geaflow) xinwang
Comments:
(geaflow) lzljs3620320
Comments:
(geaflow) jmclean
Comments:
(geaflow) paulk
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:

Continue expanding the community, release more versions under ASF
Expand connectors / external sinks ecosystem, Clustering
Add more documentation on iggy.apache.org as we add more features

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 470+, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements.
Github stars reached ~2.9K
Crates downloads reached 157K+
Presented Apache Iggy at the Rust Poland Meetup: https://www.meetup.com/rust-poland-meetup/events/308832371
Scheduled to present at ApacheCon in September

How has the project developed since the last report?

Version 0.5.0 has been released

Here is the release notes https://github.com/apache/iggy/releases/tag/server-0.5.0
Release Announcement thread https://lists.apache.org/thread/tn5onstopj3pxh8vdo651jscsp4lfsgf

Dependencies & Build

Upgraded Rust dependencies across the project
Fixed Docker setup action and publishing workflow issues

SDKs: Enhancements & CI

Java SDK: version updated, Nexus credentials managed via environment, published to Apache Maven and SNAPSHOTs
Node.js SDK: updated package metadata, proper typings for async methods, packaging fixes
Go SDK: added Go getting-started example and test script, implemented Go publish workflow, integrated BDD tests (godog) across SDK changes, CI workflows, BDD tests added for multiple SDKs, replaced Box with ClientWrapper enum
Python SDK: renamed from iggy_py to apache‑iggy, added support for consumer groups, BDD tests and restructured test layout
C# SDK: updated version header in .csproj, improved package metadata, added CI workflow
Fixed Rust SDK: resolved monotonic time bug

Connectors & Core Engine

Various Connectors runtime enhancements
Added state storage using local files
Introduced FlatBuffers schema support
Added PostgreSQL sink and source connectors
Extended runtime with protobuf support and initial HTTP API
Refactored socket handling to better support large messages; added examples; improved singleConsumerStream logic

Server & Benchmarks

Updated message header to include decrypted payload length and fixed encrypted message index calculation
Introduced Model Context Protocol (MCP) server
Optimized benchmarking: parallelized report builder, updated platform links, typo fixes
Added Helm chart for Iggy server

Web UI & Documentation

Improved message browsing in Web UI for a smoother experience
Readme updates, grammar and wording improvements; added missing license headers across modules
Integrated with DeepWiki for additional documentation on Github
Extended iggy-server --help documentation

Infrastructure, CI/CD, and Testing

Established branch protection for io_uring runtime branch
Removed OpenSSL dependency in favor of Rustls for TLS
Consolidated server tests using test matrices; added segment cache index variants to server‑restart tests; fixed restart index saving issues
Workflow improvements: markdown linter, improved CI workflows, publishing for bench and connectors, Docker and examples fixes

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

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. Some of them might be busy with other commitments. Maybe we could benefit from 1 or 2 new mentors to increase the coverage.

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: Actively working project
(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.

KIE REPORTED IN AUGUST. There has been no material change since the report last month. Unsure why we are being asked to report each month.

Three most important unfinished issues to address before graduating:

Continuing to build the community
Removing dependencies which do not comply (almost there)
Ensuring branding is correct

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

No, we’re moving along well. Slowly, but still making progress.

How has the community developed since the last report?

Last report last month, nothing has changed.

How has the project developed since the last report?

Last report last month, nothing has changed.

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?

Start of the year

Have your mentors been helpful and responsive?

Nothing to the report. The mentors are doing well.

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

Yes

Signed-off-by:

(kie) Brian Proffitt
Comments: Not much changed since last month's report, all set here.
(kie) Claus Ibsen
Comments:
(kie) Andrea Cosentino
Comments: All looks 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:

Community Building.
Consolidation and alignment of the documentation site project.
The verification of the requirements for the first release is still underway: the project has undergone a series of changes based on community requests.

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?

After completing the first course, a second course is being implemented focusing on modern AI topics according to the serverless paradigm.
Opened a Discord server with over 300 users.
Updated the tutorial OpenServerless Tutorial.
We are trying to bring the product closer to the user: infact, based on community requests, we have created a version of OpenServerless called "mini", capable of running on desktop systems by scaling down the RAM and CPU requirements, but preserving all the components for local development (from the OpenWhisk controller to the vector database, streamer, runtimes, database, etc.) and installable with one single command. Documented on Apache OpenServerless website.
Recently we published two articles about Apache OpenServerless on Opensource.net.

How has the project developed since the last report?

24 issues closed since last update. There are about 30 open tasks, divided between additional features (for which community support is required), bug fixes and new features.
We have spent several efforts in trying to simplify the setup and make it easier and more understandable.
We are aiming to refactor the operator, to make it modular.
Another important challenge is to make OpenServerless task scripts completely cross-platform as well.

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?

Yes, and we renew our thanks to all of them for their continued support in developing this project, allowing us to meet the required standards.

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

https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved

Signed-off-by:

(openserverless) Bertrand Delacretaz
Comments:
(openserverless) Enrico Olivelli
Comments:
(openserverless) François Papon
Comments: Same comment as PJ Fanning, actual installation process is with curl that is not possible with bit.ly. A solution needs to be find.
(openserverless) JB Onofré
Comments:
(openserverless) PJ Fanning
Comments: No official release yet and users are being encouraged to download via a bit.ly link that loads the app from OpenServerless' GitHub repo. I don't think that this should go on indefinitely.

IPMC/Shepherd notes:

Otava

Apache Otava (incubating) performs statistical analysis of performance test results stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It finds change-points and notifies about possible performance regressions.

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. The project name Otava was approved by VP Brand 2025-02-09.

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?

We've seen engagement in the mailing lists and/or PRs from four out of five of the project's committers since the last report.

Three new contributors have reached out via the mailing list and/or GitHub, showing interest in the project and starting work on open issues.

How has the project developed since the last report?

We have completed our first release.
Updated our build system to use uv instead of poetry.
Changed our configuration management for ease of use.
Starting the work to migrate to modern python versions.

How would you assess the podling's maturity?

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

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:

The last release was on July 17, 2025.

When were the last committers or PPMC members elected?

The major contributors during the past 8 years were listed as PPMC members in the project application phase. We have not elected any new members after that.

Have your mentors been helpful and responsive?

Our mentors have been helpful and responsive. Nothing is falling through the cracks.

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

This isn't yet an issue, as the new name of the project is quite unknown yet.

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

Improve the community website and prepare to deploy the online demo in the new environment. Develop more committers and contributors.

How has the project developed since the last report?

1、Enhance intelligent link analysis capabilities.
2、Optimize trace data collection strategy and processing performance, with an added degradation control switch. 3、Introduce intelligent log analysis functionality.
4、Optimize log collection across multiple dimensions, including configuration management, distribution logic, and dedicated collection thread pool. 5、Refactor the custom metric monitoring SDK.
6、Add business metrics support in the monitoring module.

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:

Review 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?

Regarding the user community:

On Slack, we note an increase of 7% of the number of messages (with a peak of 580 messages during last month). These Slack messages happen 77% on public channels and 21% as direct messages (which is a good ratio). NB: we are using the free plan for Slack, meaning that the messages retention is 90 days. It's interesting to note that we got messages from 21 threads started by new Slack users.
On GitHub Issues, we had 19 issues created by new users.
On the dev mailing list, we had 196 messages in August, 278 messages in July, and 311 messages in June.

Regarding the dev community:

We had 46 Pull Requests from 13 new contributors
Community meetings happened on 2025-06-12, 2025-06-26, 2025-07-24, 2025-08-28, all recorded and shared publicly (on the dev mailing list and the website, see https://polaris.apache.org/community/meetings/)

We participated in events to promote Apache Polaris:

Apache Beam Summit 25 New York City
Apache Iceberg Meetup Paris June 25
Snowflake Summit SF June 25
Data and AI - Lakehouse MiniSummit SF June 25

How has the project developed since the last report?

We released 1.0.0-incubating, which is an important milestone for the podling:

Binary distributions (.tgz/.zip) and Docker images
Official Helm chart for Kubernetes
Quarkus runtime for fast startup
Policy store with built-in data TMS policies
Rollback compaction on conflicts
3rd Party IdP integration
Federation and generic table support (experimental)

We also released 1.0.1-incubating, mostly to fix an issue on the Helm chart.

In order to faster ship fixes and new features, we agreed about a monthly release cadence.

We are also discussing several proposals:

Table Source
Client/Authentication API
Event API
Async & Reliable Tasks
Commit Deconfliction
Row and Column Based Access Control
S3 Remote Signing
FGAC
...

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-08-16

When were the last committers or PPMC members elected?

Last committers: Yun Zou elected on 2025-06-08 Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on 2025-03-25

Have your mentors been helpful and responsive?

Yes, helpful in releases review mostly.

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

Polaris PPMC is working with 3rd parties willing to use Polaris brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html.

Signed-off-by:

(polaris) Bertrand Delacretaz
Comments:
(polaris) Holden Karau
Comments:
(polaris) Kent Yao
Comments: The community is very active in project developing, delivering releases and community building.
(polaris) Ryan Blue
Comments: Good progress on the project. I think that the community is getting more used to the Apache Way but still needs guidance. This is based on uncertainty about when to use the private list and when to use a vote (vs asking for further discussion).
(polaris) JB Onofre
Comments: I'm happy to see new contributors and people active in the Polaris community. Also the podling did good progress on the releases front.

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:

Get the project up and running (no blockers, currently working on crypto and import)
Follow the graduation progression, in particular make a new release under the ASF Incubator.
Grow the 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?

No changes, still booting up.

How has the project developed since the last report?

We started looking at crypto notice requirements and cleared up all questions we had.

Next up is code import prep.

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?

All good.

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

n/a

Signed-off-by:

(pouchdb) PJ Fanning
Comments: Not much activity generally in the podling. Minimal mailing list activity, source not yet imported to ASF git, no website.
(pouchdb) Jean-Baptiste Onofré
Comments: Podling is in "starting mode" for now.

IPMC/Shepherd notes:

Texera

Texera is an open-source system to support collaborative data science, AI, and ML using GUI-based workflows. Our vision is to develop a system to support cloud platforms on which users can easily analyze data and use AI/ML techniques provided as operators. Users with various backgrounds, irrespective of whether they know coding or not, can collaborate on the same project to construct a pipeline. Experienced users can use programming languages such as Python, R, Java, and Scala to implement customized computation logic. The platform allows users to pause the execution of a workflow to investigate the operator states, and resume the execution at a later time. The platform can be used by a research community to publish valuable resources such as data sets, workflows, and ML models to share their domain-specific knowledge and support reproducibility of scientific research. The platform also allows users to elastically request computing resources from public clouds for computationally-intensive tasks.

Texera has been incubating since 2025-04-12.

Three most important unfinished issues to address before graduating:

Set up the Apache Texera webpage http://texera.apache.org/. Work is underway to consolidate user guides, developer setup instructions, and governance policies. We are analyzing the documentation structures of successful projects like Apache Flink and Spark to ensure an optimal user experience.

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?

August 06, 2025: The repository has officially transferred to Apache organization
August 28, 2025: We conducted our monthly group sync meeting with the PPMC members, committers, and contributors.

How has the project developed since the last report?

Cloud Deployment: Investigated on AWS ECS for low cost deployment of Texera.
Preparing for NIH: Added option to allow owner to give download access to public datasets.
UI Enhancements:
- Added user's activeness to admin dashboard
- Displayed file upload speed and time
- Added dashboard tab for computing units
Docs: All design decisions are documented in issues tab in Github.

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-04-04 (not an ASF release)

When were the last committers or PPMC members elected?

July 4 2025.

Have your mentors been helpful and responsive?

Yes, our mentors were highly responsive and joined our meetings. They also actively worked on our JIRA tickets.

Signed-off-by:

(texera) PJ Fanning
Comments: Next priority must be to get the web site working
(texera) Ian Maxon
Comments: It's great to see the code donation cleared up. Looking forward to an incubating release in the near future!

IPMC/Shepherd notes:

Wayang

Wayang is a cross-platform data processing system that aims at decoupling the business logic of data analytics applications from concrete data processing platforms, such as Apache Flink or Apache Spark. Hence, it tames the complexity that arises from the "Cambrian explosion" of novel data processing platforms that we currently witness.

Wayang has been incubating since 2020-12-16.

Three most important unfinished issues to address before graduating:

We are prepared for, and ready to initiate discussion for graduation.

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

(wayang) Christofer Dutz
Comments:
(wayang) Lars George
Comments:
(wayang) Bernd Fondermann
Comments:
(wayang) Jean-Baptiste Onofré
Comments:

Page tree

Timeline

Shepherd Assignments