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

Incubator PMC report for August 2025

The Apache Incubator is the entry path into the ASF for projects and codebases seeking to join the Foundation.

As of July, there are 34 podlings in incubation. Podlings executed 10 releases during the month, and two IP clearances were completed. ResilientDB encountered difficulties in following the correct ASF release process.

Several new proposals were discussed, and one new podling, Blaze, entered incubation. Fory graduated last month, while Annotator and NLPCraft were retired by the IPMC. No changes were made to IPMC membership.

Only PonyMail failed to submit a report and will be asked 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.

Discussion on the mailing list in July focused on releases, new projects and graduations, mentor involvement, clarification of ICLA requirements for non-committers, and further development of mentor onboarding and training materials, including scenario-based learning material for mentors and IPMC members. There is concern about the lack of activity in HoraeDB.

Among the long-term podlings, Toree continues to make very gradual progress toward graduation, and the Livy PPMC is also moving forward slowly. All other long-running podlings have either graduated or retired.

Community

New IPMC members:

• none

People who left the IPMC:

• none

New Podlings

• Blaze (renamed Auron)

Podlings that failed to report, expected next month

• PonyMail

Graduations

• Fory

The board has motions for the following:  - Teaclave

• Training

Releases

The following releases entered distribution during the month of July:

• Devlake 1.0.2
• Fory 0.11.2
• Gluten 1.4.0
• Hertzbeat 1.7.2
• KIE 10.1.0
• Seata 2.4.0
• Teaclave 0.5.1
• Otava 0.6.1
• Polaris 1.0.0
• XTable 0.3.0

IP Clearance

• OpenDAL Reqsign
• Spark Connect Rust

Legal / Trademarks

• N/A

Infrastructure

• N/A

Table of Contents

BifroMQ
Burr
Cloudberry
DevLake
GeaFlow
GraphAr
Hamilton
HoraeDB
KIE
NLPCraft
Seata
Texera
Toree
Training
XTable

---

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 incubator release
2. Gain more public exposure and grow the community

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

The signed documents for transferring the trademark have been accepted. We are waiting for the process to be completed and for a copy of the ASF-stamped agreement, so we can complete the donation contract workflow.

How has the community developed since the last report?

I attended Apache Community Over Code Asia and spoke at the Incubator Track, making connections with potential users and adopters.

How has the project developed since the last report?

• We are working toward a code freeze for the first incubator release
• Updated the website with a detailed contribution guide in the community section

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 get helpful and timely guidance from the mentors

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

1. Finish check list to be able to make a release
2. Start releasing
3. Enable more contributors

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

How has the community developed since the last report?

Flat. Discord continues to trickle in. One user wants to contribute a UI.

How has the project developed since the last report?

1. One new feature was merged.
2. Some PRs were merged for licensing etc. But still more work needed for first release.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

•  Initial setup
•  Working towards first release <== here
•  Community building
•  Nearing graduation
•  Other:

Date of last release:

N/A

When were the last committers or PPMC members elected?

May 2025

Have your mentors been helpful and responsive?

Time for the committers has been an issue this summer to get through the checklist required to release under Apache.

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

I think so. No issues thus far.

Signed-off-by:

•  (burr) Kevin Ratnasekera
  Comments:
•  (burr) Ayush Saxena
  Comments:
•  (burr) PJ Fanning
  Comments: Podling name is approved. We got it approved before setting up ASF resources.

IPMC/Shepherd notes:

---

Cloudberry

Cloudberry is an advanced and mature open-source Massively Parallel Processing (MPP) database, derived from the open-source version of Pivotal Greenplum Database®️ but built on a more modern PostgreSQL 14 kernel, whereas Greenplum is based on PostgreSQL 12. This upgrade brings enhanced enterprise capabilities, making Cloudberry well-suited for data warehousing, large-scale analytics, and AI/ML workloads.

Cloudberry has been incubating since 2024-10-11.

Three most important unfinished issues to address before graduating:

1. Publish the first Apache release following ASF release processes.
2. Grow the contributor and community to ensure long-term sustainability.

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

We're working on the first ever Apache release. Hope to get enough reviews and binding votes when the first Release vote email is sent to the Incubator mailing list.

How has the community developed since the last report?

• Mailing list Activity: 221 new emails on the Dev mailing list since the last report (98 emails in May, 60 emails in June and 63 emails in July), covering technical and Apache-related discussions.
• Slack Activity: 15 new threads in general channel, 5 new members since last report.
• GitHub Discussions: 16 new threads since last report (8 new in May, 5 new in June, 3 new in July).
• New Committers:
  • May 21, 2025 - Wenchao Zhang (zhangwenchao-123)
  • July 9, 2025 - Xun Gong (gongxun0928)
• Events:
  • Community Over Code Asia 2025: six presentations on Cloudberry at this conference, covering AI, Data Warehouse, OLAP and Incubator tracks. There was one Cloudberry booth.
  • HOW2025: PostgreSQL & IvorySQL Eco Conference in Jinan, China: PPMC members Dianjin Wang and Max Yang attended this conference and introduced Apache Cloudberry to the audience.
  • 10-minute T3D session on Apache Cloudberry from PPMC Member Tushar Pednekar with the host Joshua Drake: https://youtu.be/0mPCoEXG0XU
  • PPMC member Tushar Pednekar had a presentation on Cloudberry + Flink at Flink Forward Asia, Singapore 2025: https://www.youtube.com/watch?v=K9d572vOvNY
  • Presentation recording available at https://www.youtube.com/watch?v=lMYqOoE4p5A, by contributor @Leonid Borchuk and PPMC Member @Kirill Reshke at the sql-ninja conference.

How has the project developed since the last report?

• Compliance with ASF policy:
  • Renamed greenplum_path to cloudberry-env.sh for better compliance with ASF rules.
  • Updated Apache RAT license metadata for release.
  • Changed PAX's cpp-stub from submodule to subdir to avoid introducing binary files.
  • Changed Python modules for gpMgmt from bundling their source tarballs to downloading them during the build process via pip3 install.
• Working on the first Apache Cloudberry (Incubating) 2.0.0 release:
  • Already had RC1 & RC2 rounds and fixed some license issues, will have an RC3 round for the dev vote and Apache Incubator vote.
• PostgreSQL Kernel upgrade: the community developer has started the kernel upgrade work from PG 14.4 to PG 16.6.
• 130 new commits to main branch since the last report, focusing on performance improvements, bug fixes and new features.
• Ecosystem:
  • Apache SeaTunnel added official connector support for Apache Cloudberry in its latest 2.3.11 release (See https://s.apache.org/baj30).
  • Flink JDBC Connector v3.3.0+ now supports Cloudberry via PR https://s.apache.org/jt29r
• Our GitHub main repo has reached 1k+ GitHub stars!

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 21, 2025 - Wenchao Zhang (zhangwenchao-123)
• July 9, 2025 - Xun Gong (gongxun0928)

Have your mentors been helpful and responsive?

Yes, we can get suggestions and support on licensing and release matters.

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

Yes.

Signed-off-by:

•  (cloudberry) Roman Shaposhnik
  Comments:
•  (cloudberry) Willem Ning Jiang
  Comments: PPMC is trying they best to cut the first release by following ASF release policy.
•  (cloudberry) Kent Yao
  Comments: The community is active

IPMC/Shepherd notes:

---

DevLake

DevLake is a development data platform, providing the data infrastructure for developer teams to analyze and improve their engineering productivity.

DevLake has been incubating since 2022-04-29.

Three most important unfinished issues to address before graduating:

1. Grow the community and attract more users.
2. Add more committers and PPMC members.
3. Maintain the project, fix bugs, and improve the user experience based on the feedback from 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?

1. 11 new contributors have joined the community (205 contributors in total).
2. 79 new community members in Slack (1640 in total).
3. 2 new committers were elected, and 2 PPMCs were elected.

How has the project developed since the last report?

1. Support importing QA domain data via CSV templates.
2. Release a new ASF version 'v1.0.2'.
3. Bugfixes and UX refinement.

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:

With the help of our mentors, we have started the graduation process of DevLake. We just finished the maturity analysis and will start the vote in our dev channel. Check details at: https://devlake.apache.org/community/maturity

Date of last release:

2025-07-02

When were the last committers or PPMC members elected?

2025-06-25

Have your mentors been helpful and responsive?

Yes, the mentors helped tremendously throughout version releases and community governance.

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

Yes. There are no known brand and naming issues.

Signed-off-by:

•  (devlake) Felix Cheung
  Comments:
•  (devlake) Liang Zhang
  Comments:
•  (devlake) Lidong Dai
  Comments:
•  (devlake) Sijie Guo
  Comments:
•  (devlake) Jean-Baptiste Onofré
  Comments: I would suggest to start discussion about graduation.
•  (devlake) Willem Ning Jiang
  Comments: The project is a good sharp of graduation.

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. Release the first version.
2. Establish a well-defined community governance framework.
3. Enhance the diversity of community (attracting more committers, contributors, and users).
4. 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?

1. 4 new contributors have joined the community.
2. Submit a task in OSPP(Open Source Promotion Plan)2025.

How has the project developed since the last report?

1. Group id, documents and ASF configuration file updates.
2. Some fixes by community developers.
3. The feature development of 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
•  Community building
•  Nearing graduation
•  Other:

Date of last release:

We are actively preparing for the first release version.

When were the last committers or PPMC members elected?

When the incubator GeaFlow project is officially approved through voting.

Have your mentors been helpful and responsive?

Yes, the montors are very helpful and responsive.

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

N/A

Signed-off-by:

•  (geaflow) Willem Ning Jiang
  Comments: Get started
•  (geaflow) Xin Wang
  Comments:
•  (geaflow) Jingsong Lee
  Comments:
•  (geaflow) Paul King
  Comments:
•  (geaflow) Justin Mclean
  Comments:

IPMC/Shepherd notes:

---

GraphAr

GraphAr is an open-source and language-independent data file format designed for efficient graph data storage and retrieval.

GraphAr has been incubating since 2024-03-25.

Three most important unfinished issues to address before graduating:

1. Growing the community(attracting more committers, contributors and users)
2. Release more ASF-compliant versions
3. Extend the GraphAr format to support more systems

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. Voted and accepted 1 new committer.
2. Attend the OSPP 2025 activity with two projects.

How has the project developed since the last report?

1. Merged 14 PRs since the last report
2. Support WriterOption in SDK to allow users to configure writer options
3. Support multi-property in GraphAr format and C++ SDK

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:

2024-07-02

When were the last committers or PPMC members elected?

2025-07-14

Have your mentors been helpful and responsive?

Yes, the mentors are very helpful and responsive.

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

There are no known brand and naming issues.

Signed-off-by:

•  (graphar) Calvin Kirs
  Comments:
•  (graphar) tison
  Comments:
•  (graphar) Xiaoqiao He
  Comments:
•  (graphar) Yu Li
  Comments:

IPMC/Shepherd notes:

---

Hamilton

Hamilton is a lightweight in-process framework to define, execute, and observe directed acyclic graphs (DAGs) that express data transformations. In Hamilton, one can express complex DAGs of transformations, e.g. from dataframe transformations (using pandas, polars, PySpark), machine learning pipelines, through to regular software engineering API request and LLM API based workflows. Observability hooks are built into the framework. The Hamilton UI is a self-hostable service to capture observability output from workflow runs.

Hamilton has been incubating since 2025-04-12.  

Three most important unfinished issues to address before graduating:

1. Finish check list to be able to make a release
2. Start releasing
3. Enable more contributors

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

How has the community developed since the last report?

Flat. Slack continues to trickle in. Non PPMC users contributed some code.

How has the project developed since the last report?

1. We have many merged features that haven't been released.
2. Some PRs were merged for licensing etc. Docs were updated.
3. But still more work needed for first release.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

•  Initial setup
•  Working towards first release <== here
•  Community building
•  Nearing graduation
•  Other:

Date of last release:

N/A

When were the last committers or PPMC members elected?

April 2025

Have your mentors been helpful and responsive?

Time for the committers has been an issue this summer to get through the checklist required to release under Apache.

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

I think so. No issues thus far.

Signed-off-by:

•  (hamilton) Kevin Ratnasekera
  Comments:
•  (hamilton) Ayush Saxena
  Comments:
•  (hamilton) PJ Fanning
  Comments: Podling name is approved. We got it approved before setting up ASF resources.

IPMC/Shepherd notes:

---

HoraeDB

HoraeDB is a high-performance, distributed, cloud native time-series database.

HoraeDB has been incubating since 2023-12-11.

Three most important unfinished issues to address before graduating:

1. Release more version
2. Grow community(attract more users/committers)
3. Finish the new metrics engine

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

Several core developers have left the project, causing a slowdown in development this year. We expect development to get back on track next year.

How has the community developed since the last report?

Attend the OSPP 2025 with one project.

How has the project developed since the last report?

There has been no significant progress 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:

2024-12-10

When were the last committers or PPMC members elected?

Neo Chen, at 2024-12-25

Have your mentors been helpful and responsive?

Yes, they are helpful when release version and other trivial things.

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

Yes, we're doing well with this.

Signed-off-by:

•  (horaedb) tison
  Comments:
•  (horaedb) Shaofeng Shi
  Comments:
•  (horaedb) Gang Li
  Comments:
•  (horaedb) Von Gosling
  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. Continuing to build the community
2. Removing dependencies which do not comply (almost there)
3. 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?

We have some new people submitting changes and are looking at add more to the list of committers, but we would like them to be more active on the mailing lists besides just submitting code.

How has the project developed since the last report?

We're in the process of redirecting the old community sites to the new Apache KIE website. We released 10.1.0 July 10th!

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: Thank you for the clarifications.
•  (kie) Claus Ibsen
  Comments:
•  (kie) Andrea Cosentino
  Comments: All good.

IPMC/Shepherd notes:    

[PJF] GPL licensed source and libs (and similar Category X licenses) are proving to be a major roadblock on the path to graduation.

---

Seata

Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to- use and high-performance distributed transaction solution, used to solve the data consistency problem.

Seata has been incubating since 2023-10-29.

Three most important unfinished issues to address before graduating:

1. Complete the transfer of Seata's existing trademarks to the ASF.  
2. Finalize pre-graduation discussions and address any remaining gaps in required tasks.

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

No issues at the moment.

How has the community developed since the last report?  

1. 24 new code contributors have joined the community (596 contributors in total)
2. 5 new committers were elected, and 1 PPMC members were elected.
3. We presented two sessions on Apache Seata at the CommunityOverCode Asia conference and organized a face-to-face community meetup offline.
4. We have finalized the Apache Seata (incubating) Maturity Model Assessment and facilitated community-driven discussions.

How has the project developed since the last report?

1. Since the last report, we've merged 194 PRs, which include over 10 new features.
2. Since the last report, we have released two official versions: 2.4.0 and 2.5.0.
3. Since the last report, we have addressed and disclosed two CVEs: CVE-2025-32897 and CVE-2025-53606.

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

When were the last committers or PPMC members elected?

2025-08-06

Have your mentors been helpful and responsive?

Our mentors have been very helpful and responsive.

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

No Trademark issues.

Signed-off-by:

•  (seata) Sheng Wu
  Comments: Work on
•  (seata) Justin Mclean
  Comments:
•  (seata) Huxing Zhang
  Comments: The project is in good progress working towards graduation.
•  (seata) Heng Du
  Comments:
•  (seata) Xin Wang
  Comments:

IPMC/Shepherd notes:

[PJF] Discussing Graduation

---

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:

1. Donate the codebase to Apache.
2. Clean up parts in the codebase that are conflicting with Apache
3. 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 02, 2025: We have completed the SGA form. It has been submitted and documented by Apache. We are ready to donate codebase now!
• July 30, 2025: We conducted our monthly group sync meeting with the PPMC members, committers, and contributors.
• July 31, 2025: Zuozhi Wang joined as a PPMC member.
• We have engaged in significant community outreach and educational activities this month, increasing the users, including 17 undergraduate students, 34 students from high schools and community colleges, and 32 middle school students.
• Texera has been deployed and used for research at the UCI Department of Ophthalmology.

How has the project developed since the last report?  

• Cloud Deployment: Texera now runs on AWS EKS with better resource management.
• Machine Learning: Added scikit-learn training operators.
• UI Enhancements: Dynamic workflow setup and richer port-level metrics.
• Performance: Faster Texera Hub resource access.
• Docs: New tutorial videos in the works.

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 (non ASF)

When were the last committers or PPMC members elected?  

The PPMC voted to add a new member on July 4 2025.

Have your mentors been helpful and responsive?

Yes, our mentors were highly responsive and joined our meetings. We thank PJ for guiding us on the SGA form. We also thank Ian for his help with his experience from Apache AsterixDB.

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

No answer.

Signed-off-by:

•  (texera) Cezar Andrei
  Comments:
•  (texera) Gordon King
  Comments:
•  (texera) PJ Fanning
  Comments: SGA is now accepted by ASF Secretary and Git repo has been moved to ASF
•  (texera) Ian Maxon
  Comments:

IPMC/Shepherd notes:  

---

Toree

Toree provides applications with a mechanism to interactively and remotely access Apache Spark.

Toree has been incubating since 2015-12-02.

Three most important unfinished issues to address before graduating:

1.Increase active contributors

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

None, Nothing much of news from previous report

How has the community developed since the last report?

Slow activity with discussions about 0.6 release before merging Scala 2.13 support. Having said that, actions started and slowed down.

How has the project developed since the last report?

Few prs and activity around release started

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:

2022-04-11

When were the last committers or PPMC members elected?

• Cheng Pan was added to the PPMC on 2023-08-28

Have your mentors been helpful and responsive?

None

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

No trademark issues

Signed-off-by:

•  (toree) Luciano Resende
  Comments: The podling should push for release and start graduation process
•  (toree) Ryan Blue
  Comments:
•  (toree) Weiwei Yang
  Comments:

IPMC/Shepherd notes:

---

Training

The Training project aims to develop resources which can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects.

Training has been incubating since 2019-02-21.

A graduation discussion has been started at https://lists.apache.org/thread/5d87do2wl6yxvgt6kxwx6b90p7zb8dro and there's a vote underway for graduation.

Three most important unfinished issues to address before graduating:

1. Nothing. We are ready to graduate.

How has the community developed since the last report?

We have determined to graduate. Please see link above.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

•  Ready for graduation

Date of last release:

While we have done a formal release, this is more of a content-producing project, rather than releasing software artifacts. The most recent content artifact was an update to the Airflow presentation, which lives at https://training.apache.org/presentations/airflow/index.html#/table-of-conte nts

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Mentors have been very helpful and responsive.

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

Yes. Since our name is "Training", which is generic, we use the full "Apache Training", which is unique and protected by the ASF name. We have passed a name search.

Signed-off-by:

•  (training) Craig Russell
  Comments:
•  (training) Christofer Dutz
  Comments:
•  (training) Justin Mclean
  Comments:
•  (training) Lars Francke
  Comments:

IPMC/Shepherd notes:

---

XTable

XTable is an omni-directional converter for table formats that facilitates interoperability across data processing systems and query engines.

XTable has been incubating since 2024-02-11.

Three most important unfinished issues to address before graduating:

1. Ironing out license issues with bundled jars for new features. This is becoming increasingly relevant as we add new modules for integrations with other projects and for our own REST service that allows
2. Strengthening community building by actively engaging with users.
3. Removing dependency on Spark for our project. This dependency adds friction for users and makes it harder to quickly build and run the project.

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?

1. We have been collaborating with the Polaris community to provide a conversion service that their catalog service can use to convert metadata between table formats.

How has the project developed since the last report?

1. A REST Service was added so that users can run the project as a long running service and call an endpoint to perform the conversion. This will help users more easily integrate with the project, especially when callers are not in the Java ecosystem.
2. We release 0.3.0 which includes the ability to sync tables to catalogs in multiple table formats. The sync to a catalog was required for users to query their data in the table format of their choice and helps operationalize this data.

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-06-05

When were the last committers or PPMC members elected?

Feb 2024

Have your mentors been helpful and responsive?

No answer.

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

No answer.

Signed-off-by:

•  (xtable) Jesús Camacho Rodríguez
  Comments:
•  (xtable) Stamatis Zampetakis
  Comments:
•  (xtable) Jean-Baptiste Onofré
  Comments:

IPMC/Shepherd notes:

[PJF] Mailing list traffic remains low. It seems like most of the interactions happen in GitHub.