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

Incubator PMC report for May 2025

The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts.  

There are currently 36 podlings incubating. In April, podlings executed four distinct releases, and no IP clearances occurred. Several incubating proposals have been discussed on the mailing list, and we have three podlings called BifroMQ, Hamilton and PouchDB. The discussion around SAFplus found some licensing and activity issues, and it's unlikely to be accepted as an incubating project. Two people were added to the IPMC.

No podlings have retired, but a couple are talking about it. A few podlings failed to report and will be asked to report next month.

Conversations on the list have been chiefly about releases and new incubating projects. The discussion to perform name searches early at the start of the incubator process continued. This originally came up as a podling Fury needing to change its name close to graduation.

Several projects have been incubating for a long time. Toree looks to be starting that process. Annotator has not replied and has failed to report again this month. Livy is discussing what to do slowly. NLPCraft also failed to report this month, and a roll call sent two weeks ago has received no response.

There was also a discussion on selecting which reporting group a podling goes in.

Community

New IPMC members:

• Jingsong Lee
• Keyong Zhou

People who left the IPMC:

• None

New Podlings

• Hamilton
• BifroMQ
• PouchDB

Podlings that failed to report, expected next month

• Annotator
• NLPCraft
• PonyMail
• Teaclave
• Training
• Texera

Graduations

• None

The board has motions for the following:

• Gravitino
• StormCrawler

Releases

The following releases entered distribution during the month of May:

• Amoro 0.8.0
• Fury 0.10.1
• Iggy 0.4.300
• Hertzbeat 1.7.0

IP Clearance

• None

Legal / Trademarks

See discussion on approving podlings' names.

Infrastructure

N/A

Table of Contents

Amoro
Cloudberry
DevLake
Fury
HugeGraph
GraphAr
HoraeDB
Iggy
ResilientDB
Otava
PouchDB
Seata
Toree
XTable

---

Amoro

Amoro is a Lakehouse management system built on open data lake formats like Apache Iceberg and Apache Paimon.

Amoro has been incubating since 2024-03-11.

Three most important unfinished issues to address before graduating:

1. Polish our website and document.
2. Release more versions under ASF.
3. Build and grow community

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

Currently no.

How has the community developed since the last report?

• Added 1 new PPMC member
• Added 11 new contributors
• Hosted an online Amoro meetup, inviting 5 Amoro users to share their best practices in using Amoro in 2024-12-21.

How has the project developed since the last report?

• Released Amoro 0.7.1-incubatiing
• Amoro 0.8.0-incubating is currently undergoing a release vote in the incubator.
• Merged 200 PRs

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-11-20

When were the last committers or PPMC members elected?

2024-12-02, PPMC member:Congxian Qiu(GitHub ID: Klion26)

Have your mentors been helpful and responsive?

Yes, Amoro's mentors actively participate in the project, contribute insights, and help advance the project towards graduation.

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

Yes, everything is fine.

Signed-off-by:

•  (amoro) Justin Mclean
  Comments:
•  (amoro) Zhongyi Tan
  Comments:
•  (amoro) Yu Li
  Comments:
•  (amoro) Xinyu Zhou
  Comments:
•  (amoro) Kent Yao
  Comments:

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. Complete the source code cleanup to ensure ASF compliance.
2. Publish the first Apache release following ASF release processes.
3. 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?

No.

How has the community developed since the last report?

• Mailing list Activity: 59 messages and 92 messages on the Dev mailing list in March and April 2025, covering technical and Apache-related discussions.
• Slack Activity: 16 new threads in general channel, 27 new members since last report.
• GitHub Discussions: 4 new threads in March and 7 new threads in April.
• New Committer: welcomed our first committer since joining the incubator.
• Mar 19, 2025 - Xiong Tong
• Events:
• Join OSPP 2025 to attract university students to join the open-source development
• A Cloudberry Meetup hosted by HashData in Hangzhou attracted 30~ attendees.
• The contributor @Leonid Borchuk and PPMC Member @Kirill Reshke presented their talks on Cloudberry at the sql-ninja conference in Moscow on 03/22, 2025.
• PPMC member Shine Zhang presented "From Greenplum to Apache Cloudberry" at Postgres Conference 2025, Orlando / United States, March 20, 2025
• 6+ Cloudberry proposals are submitted to CommunityOverCode NA/Asia 2025 (still in review and waiting for the final approval).
• Create website pages to guide on how to invite the new committer.

How has the project developed since the last report?

• Create the Wiki space in GitHub to organize the collective knowledge from community practices, including the release process.
• Security:
• Integrated two code analysis tools to enhance our code quality and identify potential issues in the development process: Coverity Scan and SonarQube Scan.
• Fix the PostgreSQL security issue CVE-2025-1094.
• CICD:
• Working on adding the Ubuntu build and test environment support to Cloudberry
• Codebase Updates:
• Evolve the Cloudberry code following the Roadmap: Contributed back the row-column hybrid storage engine -PAX to the Cloudberry codebase;
• Completed the first stage of cherry-picking commits from the open-source Greenplum project to Cloudberry (80%+ progress of plan).
• Work for the first Apache Cloudberry (Incubating) 2.0.0 release
• Pull Request management through the GitHub project: https://github.com/orgs/apache/projects/490
• License-related updates:
  • Update the NOTICE and LICENSE files.
  • List the third-party licenses under the licenses directory.
  • Replace the Pylint with a license-compatible one - ruff.
  • Update the license headers with the Apache license header for the newly created files.
  • Add RAT license audit config and compliance metadata.
• Brand updates: rebrand old names to the latest Apache Cloudberry brand both in the main codebase and the site source.
• Cleanup the old unused files from the source code for a clearer codebase and ASF compliance (including concourse/, hd-ci/, deploy/*, and so on).

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?

• Mar 19, 2025 - Xiong Tong (committer)

Have your mentors been helpful and responsive?

Yes, we can get quick responses on the license-related issues, and glad to see the mentors' guidance to the PPMC on the new committer's workflow.

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

Yes.

Signed-off-by:

•  (cloudberry) Roman Shaposhnik
  Comments:
•  (cloudberry) Willem Ning Jiang
  Comments:
•  (cloudberry) Kent Yao
  Comments:

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. Grow the project, support more data sources and use cases, and improve the user experience.

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

We are currently working toward the graduation of DevLake, but we’re concerned that the recent drop in contribution metrics (e.g., number of commits) might not meet the graduation criteria.

At this stage, DevLake is in a stable phase. Over the past few months, our focus has shifted primarily to bug fixes and maintenance, rather than the development of new features—hence the decline in contribution statistics.

That said, our community remains active. You'll find ongoing engagement in our Slack workspace, especially in the #questions channel, where committers and PPMC members continue to support users.

We’d really appreciate your guidance on what we should prioritize or pay special attention to during this maintenance-focused phase to ensure we remain on track for graduation.

How has the community developed since the last report?

1. 13 new contributors have joined the community (194 contributors in total)
2. 103 new community members in Slack (1561 in total)

How has the project developed since the last report?

1. Introduce a new QA domain to DevLake, allowing users to integrate with the test data.
2. Bug fixes and UX refinement.
3. Initiate the releasing process for a new ASF version 'v1.0.2-rc1'.

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-09-23. There is one in progress.

When were the last committers or PPMC members elected?

2024-12-7

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?

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: Thanks for sharing your concern about graduation and activity. If it's a "temporary" reduce of activity, it's not a problem, and not a blocker for graduation. If this lower activity is related to change in the community, that's a good point to share. I would say that the maturity matrix is also welcome to evaluate graduation.
•  (devlake) Willem Ning Jiang
  Comments:

IPMC/Shepherd notes:

Justin Mclean: As JB states, it is not a graduation concern, but I suggest you look at graduating sooner rather than later.

---

Fury

A blazing fast multi-language serialization framework powered by jit and zero-copy

Fury has been incubating since 2023-12-15.

Three most important unfinished issues to address before graduating:

1. Grow the community(attracting more committers, contributors, and users).
2. Add more PPMC members and release managers

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?

Steady progress. Made 3 releases, and added two new release managers.

How has the project developed since the last report?

3 releases. The most recent was v0.10.2 on May 6, 2025.

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

When were the last committers or PPMC members elected?

2025-04-06, added new committer LofiSu

Have your mentors been helpful and responsive?

Yes, the mentors helped a lot for version releases and community governance.

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

Apache Fury will renamed to Apache Fory. The VP has approved the new name.

Signed-off-by:

•  (fury) tison
  Comments:
•  (fury) PJ Fanning
  Comments: Project name is due to change to Fory over the next few months.
•  (fury) Yu Li
  Comments:
•  (fury) Xin Wang
  Comments:
•  (fury) Enrico Olivelli
  Comments:
•  (fury) Hao Ding
  Comments:

IPMC/Shepherd notes:

---

HugeGraph

A large-scale and easy-to-use graph database/computing/AI system

HugeGraph has been incubating since 2022-01-23.

Three most important unfinished issues to address before graduating:

1. Release new graph dashboard & make graph computer easy to use
2. Release a stable Graph LLM/AI system
3. At least 2 new PPMC & 5 committers selected and take deep part in the community

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

Some PPMC members are inactive for a while, an adjustment may be required before graduation

How has the community developed since the last report?

1. Release 1.5.0(include the new distributed design) , the most important version before graduating
2. Submit a task in GSoC & 4+ tasks in OSPP (Open Source Activity)
3. 12+ new contributors take part in the community (with PR/code)
4. Elected first new PPMC + 1 committer

How has the project developed since the last report?

1. Move forward to 1.7.0 (Maybe the last version before graduating)
2. Enhance GraphAI system/repo to follow the user needs
3. Release the most important/major change (distributed storage system PD & Store) & keep improving it
4. The new graph dashboard/UI & graph computing system are also on the way (should be done in next 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:

2024-12-10

When were the last committers or PPMC members elected?

2025-04-21

Have your mentors been helpful and responsive?

Yes, thanks all of them

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

No answer.

Signed-off-by:

•  (hugegraph) Lidong Dai
  Comments:
•  (hugegraph) Trista Pan
  Comments:
•  (hugegraph) Xiangdong Huang
  Comments:
•  (hugegraph) Yu Li
  Comments:
•  (hugegraph) Willem Ning Jiang
  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. Implementing key features requested in GitHub issues and discussions.

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 one new committer.
2. Attracted one new contributor.

How has the project developed since the last report?

1. Merged 9 PRs since the last report.
2. Remove Hadoop dependency and shade protobuf dependency in Java 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-02-17

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 declarative python DAG framework with an optional observability solution.

Hamilton has been incubating since 2025-05-01.

Three most important unfinished issues to address before graduating:

1. Get podling resources set up
2. Expand community

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?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

N/A

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

N?A

Signed-off-by:

•  (hamilton) PJ Fanning
  Comments: Still setting up
•  (hamilton) Ayush Saxena
  Comments:
•  (hamilton) Kevin Ratnasekera
  Comments:

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?

No

How has the community developed since the last report?

We submit one OSPP task to attract more developers.

How has the project developed since the last report?

The structure of the new metric engine is finished, other components are in WIP status.

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:

---

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. Migrate all the repos from previous OSS repo https://github.com/orgs/iggy-rs/repositories to apache/iggy repo (mono repo with independent CI/CD)
3. Enhance iggy.apache.org with more details, guides, docs, blogs, benchmarks etc

How has the community developed since the last report?

1. Discord members count approaching 400, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements.
2. Github stars approaching 2.5k from 2.4k
3. Creates downloads crosses 124k vs 115k at the time of last report
4. Presented at Rustmeet 2025
5. Presented at Rustikon Conference 2025

How has the project developed since the last report?

1. Apache Iggy (Incubating) v0.4.300 released
2. Enhanced performance and efficiency: zero-copy (de)serialization [implemented](https://iggy.apache.org/blogs/2025/05/08/zero-copy-deserializa tion) for the server & updated SDK client
3. Restructuring the repository to support monorepo with multiple SDKs and other tooling (eg benchmarks)
4. Started migrating the SDKs from old repo (dotnet, java, node, web UI etc)
5. Successful POCs (with quickwit) for steaming messages into external connectors/sinks
6. Submitted detailed report for trademarks and received the approval for the name "Iggy", "Apache Iggy" from Apache's Brand Management Team (Mark Thomas)

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

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, the mentors are very helpful and responsive.

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

VP, Brand approved the project name

Signed-off-by:

•  (iggy) Hao Ding
  Comments:
•  (iggy) Yonik Seeley
  Comments:
•  (iggy) Zili Chen
  Comments:
•  (iggy) Hulk Lin
  Comments:

IPMC/Shepherd notes:

---

ResilientDB

ResilientDB is a distributed blockchain framework that is open-source, lightweight, modular, and highly performant.

ResilientDB has been incubating since 2023-10-21.

Three most important unfinished issues to address before graduating:

1.Grow the community by facilitating more applications being built on ResDB. 2.Improve and extend documentation to help external users to set up easily. 3.

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?

Regular meeting continues every week.

How has the project developed since the last report?

We are preparing a new [release](https://dist.apache.org/repos/dist/dev/incubator/resilientdb/1.11. 0-rc0/) to publish new applicatioins built on top of ResilientDB core platform.

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:

Apache ResilientDB v1.10.0-incubation (2024-7-11)

When were the last committers or PPMC members elected?

November of 2023

Have your mentors been helpful and responsive?

The mentors helped tremendously throughout the project build-up and transfer.

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

There are no known brand and naming issues as reported here.

Signed-off-by:

•  (resilientdb) Junping Du
  Comments:  
•  (resilientdb) Calvin Kirs
  Comments:
•  (resilientdb) Kevin Ratnasekera
  Comments:
•  (resilientdb) Roman Shaposhnik
  Comments:
•  (resilientdb) Christian Grobmeier
  Comments:

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:

1. Publish the first release under the new name. (https://github.com/apache/otava/issues/51) The first release was under voting as the deadline to submit this report to the Incubator PMC passed.
2. Publish the existence of Apache Otava (Incubating), and our first release.
3. Nurture a growing community that includes also new members/contributors that have not used Otava (Hunter) before we joined Apache Incubator
4. Make more releases. In particular, the first release intentionally is not that different from what already existed before we became an Incubator project. It is merely a change of project name and ownership (ASF) and the license, and a re-union of many forks into a clear upstream project. For future releases we hope to modernize python version, build tooling, and of course add new features and integrations.

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

Nothing is blocking us now.

How has the community developed since the last report?

We recently accepted the first (documentation) contribution from a user who does not belong to the pre-ASF group of Otava users and contributors. A handful of more people submitted issues or sent an email to the mailing list. This level of attention is already more than we are used to receiving during the previous 8 years developing this code base.

The interactions we had, were mostly held back by the fact we have not yet made our first release, and that until then, Otava only supported python 3.8, which is no longer officially supported. We expect interest in the project to increase after the first release (as ASF incubating project) and upgrading python version. (The release will include support for python 3.9 and 3.10 and will likely happen within hours after the deadline to submit this report.

How has the project developed since the last report?

The last time we submitted a report was in February 2025.

We apologize for twice failing to submit a report. There seems to still be teething issues with basic project governance tasks and responsibilities. We know we can do better, there's just a lot to absorb when becoming a proper ASF project for the first time.

Shortly after our previous report, a new name "Otava" was approved for the project. Otava is the Finnish name for the "Big Bear" constellation, one of the largest and brightest star constellations in the Northern night sky. Otava historically had an important function in navigating, as it was commonly used to find the North Star, which is at the other end of a straight line drawn from the right most 2 stars in Otava.

Most work in the project since then was to

• Change the project name across ASF infrastructure
• Change the project name everywhere in code and documentation. This includes file names, executable names and tar file name.
• Publish a project website at otava.apache.org
• As this report was submitted, our first release was undergoing voting on the incubator general mailing list.

How would you assess the podling's maturity?

A self review based on https://community.apache.org/apache-way/apache-project-maturity-model.html

• Code 3/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 first release was happening as this report was submitted

When were the last committers or PPMC members elected?

So far, the initial committers and PPMC members were those listed in the initial proposal.

Some of those, haven't actually showed up in the incubator project now that we are active.

Have your mentors been helpful and responsive?

Yes!

Submitting this report is a routine we need to get more accustomed to doing.

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

Not an issue yet, as the name is new.

Signed-off-by:

•  (otava) Dave Fisher
  Comments:
•  (otava) Enrico Olivelli
  Comments:
•  (otava) Lari Hotari
  Comments:
•  (otava) Mick Semb Wever
  Comments:

IPMC/Shepherd notes:

---

PouchDB

PouchDB is an open-source JavaScript database inspired by [Apache CouchDB] (http://couchdb.apache.org/) that is designed to build offline-capable web applications.

PouchDB has been incubating since 2025-04-15.

Three most important unfinished issues to address before graduating:

1. Get the project up and running (no blockers)
2. Follow the graduation progression, in particular make a new release under the ASF Incubator.
3. 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?

N/A, still in setup phase.

How has the project developed since the last report?

N/A, still in setup phase.

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, still in setup phase.

When were the last committers or PPMC members elected?

N/A, still in setup phase.

Have your mentors been helpful and responsive?

N/A, still in setup phase.

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

N/A, still in setup phase.

Signed-off-by:

•  (pouchdb) Jan Lehnardt
  Comments:
•  (pouchdb) PJ Fanning
  Comments:  

IPMC/Shepherd notes:

---

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. More international contributors are joining the community.
2. Put more time into double-checking the compliance checklist to catch any gaps.

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. 22 new code contributors have joined the community (572 contributors in total)
2. 4 new committers were elected, and 1 PPMC members were elected.
3. The community actively participates in various open-source events. We've submitted 3 project proposals for GSoC, 3 projects for OSPP (an open-source event similar to GSoC), and 3 topics for CommunityOverCode Asia 2025, all guided by different mentors.
4. On the Seata GitHub page, there are around 3,500 "used by" listings.  

How has the project developed since the last report?

1. Since the last report, we've merged 136 PRs, which include over 10 new features.
2. Since the last report, versions 2.3.0 have been released. We're currently voting on 2.4.0.
3. Since the last report, we have received and addressed several vulnerability reports and published CVE-2024-47552 and CVE-2024-54016.Additionally, we resolved 17 dependency vulnerabilities through project dependency upgrades.

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

When were the last committers or PPMC members elected?

2025-05-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: The community begins to consider starting pre-graduation check.
•  (seata) Justin Mclean
  Comments:
•  (seata) Huxing Zhang
  Comments: The project looks in good shape towards graduation.
•  (seata) Heng Du
  Comments:
•  (seata) Xin Wang
  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 incorporating Scala 2.13 support

Release activity started

How has the project developed since the last report?

Few prs around Scala 2.13 and other small enhancements Updates to remove Google Analytics from website

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:

---

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. Strengthening community building by actively engaging with users.
2. Increasing adoption by implementing key features planned - XTable REST service in collaboration with Apache Polaris(Incubating) community, Deletion Vectors, CatalogSync support for new catalogs etc.
3. Ironing out license issues with bundled jars for new 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?

1. Slack channel grew to zero to 67 members in last 2 months.
2. Three new first time contributors have merged their first PR's.
3. More users are trying to use XTable in production environments and community has been helping them succeed.

How has the project developed since the last report?

1. The RFC for catalog sync was implemented and is planned for inclusion in the upcoming 0.3.0 release.
2. Three new RFC's - Deletion Vectors support, ACL Policy synchronization and XTable REST service are actively in progress.
3. There has been active engagement on slack/GH with the community - addressing issues, answering questions and fixing bugs reported by users running XTable in production.

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:

Nov 8,2024

When were the last committers or PPMC members elected?

Feb 2024

Have your mentors been helpful and responsive?

Yes, our mentors have been helpful and responsive overall. However for the licensing of new bundled jars, there's conflicting interpretations of the ASF documentation between the dev vote, the general incubator vote. We would benefit from additional guidance and support specifically on resolving these licensing issues for bundled jars and "what content" to write in LICENSE/NOTICE files.

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

Yes

Signed-off-by:

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

IPMC/Shepherd notes: