DRAFT DRAFT DRAFT

NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.

If your report is missing please use the clutch2report.py script to generate your report.

It also best to:

  • Do not change existing formatting. Especially do not change the formatting of the sign-off area.

  • Keep all lines under 76 characters long.

  • All content under the ### headings should be indented by two spaces. Do not use tabs.

  • Please don't change the text in the headings or add new ones.
  • Include one space after a bullet point or full stop on a numbered list.
  • Use [X] (X and no spaces) to sign off reports.
  • Do not include long URLs and use the apache URL shortener https://s.apache.org.
  • Please note that some lines have two spaces at the end. Do not remove these spaces.

Please make sure you use the current report and don't copy an old one, the headings do change from time to time.

A script will be run on this report before it is submitted to the board. If your lines are too long it may insert line breaks in unexpected places.

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


Timeline

Wed July 02

Podling reports due by end of day

Sun July 06

Shepherd reviews due by end of day

Sun July 06 

Summary due by end of day

Tue July 08

Mentor signoff due by end of day

 Wed July 09

Report submitted to Board

Wed July 16

Board meeting


Shepherd Assignments

Calvin KirsHertzBeat
Calvin KirsResilientDB
Calvin KirsTexera
Dave FisherBurr
Dave FisherTeaclave
Drew FarrisBifroMQ
Drew FarrisGluten
Justin McleanPony Mail
P. Taylor GoetzIggy
P. Taylor GoetzPouchDB
PJ Fanning Grails
PJ Fanning HugeGraph
Timothy ChenHamilton
Timothy ChenKIE
Willem JiangAnnotator
Willem JiangFluss
Willem JiangPegasus
XuanwoAmoro
XuanwoLivy

Incubator PMC report for July 2025

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

Nemo has been retired.

Community

New IPMC members:

People who left the IPMC:

New Podlings

Podlings that failed to report, expected next month

Graduations

  • list podling here

The board has motions for the following:

  • Your podling here?

Releases

The following releases entered distribution during the month of June:

IP Clearance

Legal / Trademarks

Infrastructure

Miscellaneous

Credits

Table of Contents

Amoro
Annotator
BifroMQ
Burr
Fluss
Gluten
Grails
Hamilton
HertzBeat
HugeGraph
Iggy
KIE
Livy
Pegasus
PonyMail
PouchDB
ResilientDB
Teaclave
Texera

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 4 new contributors

How has the project developed since the last report?

  • Released Amoro 0.8.0-incubatiing
  • Merged 40+ 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:

2025-05-08, released Amoro 0.8.0-incubatiing

When were the last committers or PPMC members elected?

2025-06-09, PPMC member:Wang Tao(GitHub ID: Aireed)

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) Justn Mclean
    Comments:
  •  (amoro) Zhongyi Tan
    Comments:
  •  (amoro) Yu Li
    Comments: Good to see new contributor and PPMC member joining, as well as new release published.
  •  (amoro) Xinyu Zhou
    Comments:
  •  (amoro) Kent Yao
    Comments: Nice to have new PPMC on board

IPMC/Shepherd notes:

Annotator

Annotator provides annotation enabling code for browsers, servers, and humans.

Annotator has been incubating since 2016-08-30.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

  •  (annotator) Nick Kew
    Comments:
  •  (annotator) Tommaso Teofili
    Comments:
  •  (annotator) Benjamin Young
    Comments:

IPMC/Shepherd notes:

BifroMQ

BifroMQ is a Java-based, high-performance, distributed MQTT broker with native multi-tenancy support, designed for large-scale connections and message delivery.

BifroMQ has been incubating since 2025-04-22.

Three most important unfinished issues to address before graduating:

  1. The first incubator release
  2. Community growth

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

None at this time.

How has the community developed since the last report?

  • Migrated the official website to ASF infrastructure and updated the contents to comply with ASF requirements.
  • Published roadmap on the website to address common concerns from potential contributors.

How has the project developed since the last report?

We are still working on the first incubator release, but have completed the following tasks:

  • Added license headers to all source files and set up a corresponding CI action for checking
  • Updated LICENSE and NOTICE files with third-party dependency information for both source and binary distributions
  • Renamed all Java packages to org.apache.bifromq.*

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 joining 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: So far not much discussion has been happening on any of the mailing-lists.
  •  (bifromq) Xiangdong Huang
    Comments:
  •  (bifromq) Calvin Kirs
    Comments: Things are going well, The new website looks great.
  •  (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. Publish docs
  2. Publish a release

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

N/A

How has the community developed since the last report?

N/A

How has the project developed since the last report?

Still setting up.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

Yes - responsive. On us PMC to get the ball rolling faster.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

  •  (burr) Kevin Ratnasekera
    Comments:
  •  (burr) Ayush Saxena
    Comments: Setting up the project
  •  (burr) PJ Fanning
    Comments:

IPMC/Shepherd notes:

Fluss

Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures.

Fluss has been incubating since 2025-06-04.

Three most important unfinished issues to address before graduating:

  1. Ensure website and code are full compliance with ASF policie
  2. Publish the first release under the ASF incubator
  3. Grow the community and fill out the 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?

We are still in the setup phase, but we have seen some active contributors that deserved to be committer candidates.

Jark Wu is going to Flink Forward Asia 2025 (Singapore) to present Fluss on July 3rd.

How has the project developed since the last report?

The community is developing for the next release v0.8 which is expected to be released at September.

The community has established the Fluss Improvement Proposal (FIP) process [1] to facilitate design discussions for major features. Currently, there are already five FIPs in progress.

[1] https://cwiki.apache.org/confluence/display/FLUSS/Fluss+Improvement+Proposals

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

We are still in the process of initial setup. We have migrated the GitHub repository and website to the Apache organization. We will set up the CI/CD pipelines to streamline future development and deployment.

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

Yes

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

N/A

Signed-off-by:

  •  (fluss) Jean-Baptiste Onofré
    Comments: Good work on the initial setup. Congrats !
  •  (fluss) Becket Qin
    Comments:
  •  (fluss) Yu Li
    Comments: Initial setup is completed and look forward to the further development of the project.
  •  (fluss) Jingsong Lee
    Comments:
  •  (fluss) Zili Chen
    Comments:

IPMC/Shepherd notes:

Gluten

Gluten is a middle layer responsible for offloading JVM-based SQL engines' execution to native engines.

Gluten has been incubating since 2024-01-11.

Three most important unfinished issues to address before graduating:

  1. Apache Official Release: Quarterly publish Apache Official Release
  2. Enhanced User Experience to update the latest documentations to the site
  3. Community Growth

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

N/A

How has the community developed since the last report?

How has the project developed since the last report?

  • Gluten 1.4.0 has been released as 4th Apache release(major update) on Jun. 19th 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-06-19

When were the last committers or PPMC members elected?

2025-05-26 for vote result published

Have your mentors been helpful and responsive?

Yes, they remain actively engaged with the project and provide valuable input, such as reminders about the release process and insights into the overall health of the community.

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

Yes, everything is fine.

Signed-off-by:

  •  (gluten) Yu Li
    Comments: Good to see new committers joining and new release published. The community is built in a good shape.
  •  (gluten) Wenli Zhang
    Comments:
  •  (gluten) Kent Yao
    Comments: Looks good to me for seeing new reliable releases
  •  (gluten) Shaofeng Shi
    Comments: Good to see the community is growing. Maybe it is time to discuss the graduation plan.
  •  (gluten) Felix Cheung
    Comments:

IPMC/Shepherd notes:

Grails

A powerful Groovy-based web application framework for the JVM built on top of Spring Boot

Grails has been incubating since 2025-01-25.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

  •  (grails) Paul King
    Comments:
  •  (grails) Soeren Glasius
    Comments:

IPMC/Shepherd notes:

[PJF] It appears that Paul King is reporting for Grails as part of the Groovy report. Grails is not part of Apache Incubator. It is part of Apache Groovy.

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. Finally publish a release
  2. Publish releases of all other components

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

How has the community developed since the last report?

Organizing a meet-up in July.

How has the project developed since the last report?

Gotten some docs out -- still missing a few ASF things.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  •  Initial setup
  •  Working towards first release -- currently here.
  •  Community building
  •  Nearing graduation
  •  Other:

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed. N/A

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

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

IPMC/Shepherd notes:

HertzBeat

HertzBeat is an easy-to-use, open source, real-time monitoring system. It features an agentless architecture, high-performance clustering, Prometheus compatibility, and powerful custom monitoring and status page building capabilities.

HertzBeat has been incubating since 2024-04-05.

Three most important unfinished issues to address before graduating:

  1. Grow the community and attract more users.  

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

No.

How has the community developed since the last report?  

  1. Now the community total has 271 contributors, attracted 12 new contributors since last report.
  2. Two new committer and a new PPMC join the community since last report.
  3. The community participated in the Google Summer of Code and OSPP.

How has the project developed since the last report?

  1. Has publish the new version 1.7.1.
  2. The new version 1.7.2 is in the process of release.
  3. More features and bugfix, doc update
  4. In the past month, excluding merges, 18 authors have pushed 21 commits to master and 43 commits to all branches. On master, 88 files have changed and there have been 1,654 additions and 830 deletions.

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

When were the last committers or PPMC members elected?

2025-06-17

Have your mentors been helpful and responsive?

Yes, they are very nice.

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

There are no known brand and naming issues.

Signed-off-by:

  •  (hertzbeat) Yonglun Zhang
    Comments:
  •  (hertzbeat) Yu Xiao
    Comments:
  •  (hertzbeat) Justn Mclean
    Comments:
  •  (hertzbeat) Francis Chuang
    Comments:

IPMC/Shepherd notes:

HugeGraph

A large-scale and easy-to-use graph database

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 1 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. Completed the internal trademark approval process, now awaiting the next steps for transferring the trademark to the ASF.
  2. Submitted 8+ tasks for open-source promotional activities and delivered 2 HugeGraph-related presentations at the Conference on Open Source (COC) Asia.
  3. Elected 1 new committer, with 2 more candidates currently in the nomination process.

How has the project developed since the last report?

  1. Actively planning the 1.7.0 release as a key preparation step before graduation.
  2. Advancing the integration of an optional proprietary vector engine to enhance the graph database's capabilities.
  3. Further refactoring and merging the distributed storage and computation layers for better synergy and performance.
  4. Restructured the documentation and enriched it with extensive LLM-powered source code analysis to improve developer onboarding.

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

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

YES & Thanks

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Waiting the next steps for transferring the trademark to the ASF

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:

[PJF] Hopefully will push towards graduation soon

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. Expand connectors / external sinks ecosystem
  3. 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?

Sometimes, INFRA jira tickets taking more time. Is there a way to expedite the process there?  

How has the community developed since the last report?

  1. Discord members count approaching 450, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements.
  2. Github stars reached 2.7K
  3. Crates downloads reached 141K+
  4. Presented at Craft-IT Conference (https://craft-it.pl/#session-216)
  5. Scheduled to present at ApacheCon in September

How has the project developed since the last report?

The Iggy project has made significant progress in multiple areas during the reporting period:

  • Repository Restructure: Transitioned the codebase to a monorepo structure to better support modular development across server, client SDKs, connectors, and tooling.
  • Connectors Runtime: Implemented the initial version of the Iggy Connectors Runtime, enabling dynamic loading of source/sink plugins and supporting custom data transformations.
  • SDK Migration: Migrated SDKs for multiple languages including C#, Java, Go, Node.js, Python, and C++ to align with the monorepo architecture and latest server capabilities.
  • Web Dashboard: Migrated the Iggy Web UI dashboard to the new repository structure.
  • Benchmarking Platform: Migrated the benchmarking platform and began preparations to host it under [benchmarks.iggy.apache.org|http://benchmarks.iggy.apache.org].
  • CI Improvements: Enhanced the CI/CD pipelines to handle multiple languages and projects independently within the monorepo.
  • Zero-Copy Support: Added zero-copy support in the server and integrated recent server changes across all existing SDKs.
  • Rust SDK Refactor: Refactored the Rust SDK into smaller, reusable packages shared between server and client implementations; also updated the Rust edition and dependencies.
  • Runtime Refactor (Experimental): Published an experimental branch featuring a new runtime architecture based on io_uring, thread-per-core model, and shared-nothing design.
  • BDD Test Coverage: Introduced Behavior-Driven Development (BDD) scenarios using Cucumber for validating SDK functionality across multiple languages.
  • Benchmarking Enhancements: Extended the benchmarking CLI with a high-level SDK abstraction, added TLS support, and improved result sharing via unique URLs.
  • Website Redesign: Completed a major website redesign, updated brand assets, and aligned naming conventions with Apache guidelines.
  • Release Planning: Initiated discussions and scoping for the upcoming v0.5.0 release (https://github.com/apache/iggy/discussions/1931)

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?

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

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

Signed-off-by:

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

IPMC/Shepherd notes:

KIE

KIE (Knowledge is Everything) is a community of solutions and supporting tooling for knowledge engineering and process automation, focusing on events, rules, and workflows.

KIE has been incubating since 2023-01-13.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

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

IPMC/Shepherd notes:

Livy

Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important unfinished issues to address before graduating:

  1. Revitalization of the Community
  2. Dependable Release Cadence
  3. Keep the project up to date with security fixes and in terms of Spark support

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

None at this time. There was a recent ping of the PPMC to make sure there were enough folks monitoring the pivate@ list which resulted in 5 +1's and a couple 0's.

How has the community developed since the last report?

We have received PRs and merged mostly bug fixes and smaller enhancements.

How has the project developed since the last report?

A new PR for the upcoming release is support for the latest Spark 3.5.x has been submitted and is currently waiting for reviews. We will need to spin up the next release within this next quarter.

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:

2023-10-10

When were the last committers or PPMC members elected?

October 2023

Have your mentors been helpful and responsive?

Yes

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

No answer

Signed-off-by:

  •  (livy) Bikas Saha Comments:
  •  (livy) Luciano Resende Comments:
  •  (livy) Jean-Baptiste Onofré Comments: I think it would be great to have a kind of roadmap about releases (0.8.0-incubating is two years old) and community growth (blog post, ...).
  •  (livy) Madhawa Kasun Gunasekara Comments:
  •  (livy) Larry McCay Comments:
  •  (livy) György Gál Comments:

IPMC/Shepherd notes:

Pegasus

Pegasus is a distributed key-value storage system which is designed to be simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 2020-06-28.

Three most important unfinished issues to address before graduating:

  1. There are still about 10 documents on the official website that need to be provided and updated.
  2. Improve the stability of project builds and unit tests.
  3. Make more releases in ASF policy regularly.

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

None.

How has the community developed since the last report?

We saw more active users and contributors of Apache Pegasus.

How has the project developed since the last report?

More useful features are continuously being merged. The upcoming release is version 2.6.0, but since two major features — support for FQDN and the refactoring of the metrics system — are still in progress, it may take a few more months to complete.

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:

2023-12-12

When were the last committers or PPMC members elected?

2024-09-26

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

Yes, our mentors gave us a lot of help, including version release, holding meetup, prepare the graduation and etc.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Yes.

Signed-off-by:

  •  (pegasus) Duo zhang
    Comments:
  •  (pegasus) Liang Chen
    Comments:
  •  (pegasus) Von Gosling
    Comments:
  •  (pegasus) Liu Xun
    Comments:

IPMC/Shepherd notes:

PonyMail

Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

  •  (ponymail) John D. Ament
    Comments:

IPMC/Shepherd notes:

PouchDB

PouchDB is an open-source JavaScript database inspired by Apache CouchDB that is designed to run well within the browser.

PouchDB has been incubating since 2025-04-15.

Three most important unfinished issues to address before graduating:

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

We are still in the setup phase, IP clearance and source import is next.

How has the project developed since the last report?

All but two CLAs are in place, in addition, two Code Grants have been received from the former major PouchDB contributors in preparation for IP clearance.

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?

Helpful and proactive.

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

N/A

Signed-off-by:

  •  (pouchdb) PJ Fanning
    Comments:
  •  (pouchdb) Jean-Baptiste Onofré
    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?

Add one new PPMC

How has the project developed since the last report?

We are preparing a new rc (v1.11.0)

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:    

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

When were the last committers or PPMC members elected?

2025-5-20

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

One of our mentors is not touchable (email is not available). Currently we only have two mentors, would like to add one more.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

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

Signed-off-by:

  •  (resilientdb) Junping Du
    Comments:
  •  (resilientdb) Kevin Ratnasekera
    Comments:

IPMC/Shepherd notes:

Teaclave

Teaclave is a universal secure computing platform, enabling writing memory-safe trusted applications in Rust running inside Trusted Execution Environment.

Teaclave has been incubating since 2019-08-20.

The Teaclave community is now working towards graduation.

Three most important unfinished issues to address before graduating:

  1. Complete all requirements of the Project Maturity Assessment.
  2. Practice future releases by adhering to a quarterly release schedule.
  3. Conduct a thorough self-assessment to ensure all Apache graduation criteria are met.

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

As the Teaclave community works toward graduation, we welcome guidance along the process. We also invite any active IPMC members interested in the project to consider becoming mentors. Thank you.

How has the community developed since the last report?

  • We have a new mentor joining the project.
  • We have a new participant contributing to the project.
  • We have a new release manager working on the Teaclave TrustZone SDK v0.5.0 release.

How has the project developed since the last report?

  • Initiated releasing Teaclave TrustZone SDK v0.5.0, pending for collecting binding votes in the general incubator mailing list.
  • Working on the Teaclave Maturity Assessment. During the assessment, we identified several areas for improvement, including the website page and repository reorganization. Work is in progress to address these and meet all requirements.

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

When were the last committers or PPMC members elected?

2025-01-21

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

We have faced challenges with slow release cycles, partly due to the limited number of binding votes from mentors. To address this, we have invited new mentors to join the community and are actively engaging with contributors to ensure smoother release processes. We have also reached out to existing mentors and received positive responses and renewed support. We plan to continue this proactive approach in future releases to ensure timely and successful outcomes.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Yes.

Signed-off-by:

  •  (teaclave) Felix Cheung
    Comments:
  •  (teaclave) Furkan Kamaci
    Comments:
  •  (teaclave) Jianyong Dai
    Comments:
  •  (teaclave) Matt Sicker
    Comments:
  •  (teaclave) Zhijie Shen
    Comments:
  •  (teaclave) Gordon King
    Comments:

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:

  1. Complete the SGA form.
  2. Donate the Texera codebase from the Texera/texera GitHub repo to the Apache/Texera repo.
  3. Set up the Apache Texera webpage http://texera.apache.org/.

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?

  • 2025-06-12: Ian Maxon (imaxon) has been added as a Texera mentor.
  • 2025-06-25: We got approval from UCI on realeasing their copyright to us. We are finalizing the paperwork. After this, we can sign and submit the SGA form.
  • 2025-06-30: We conducucted a monthly group sync meeting, meeting minutes and recording can be found in this email thread.
  • 2025-06-30: PPMC started voting for a new PPMC member.
  • 2025-06-30: There were six more contributors onboarding.
  • 2025-06-30: There were four more users showing interests through other channels. We will gradually move to use general@texera.apache.org to let potential users contact us.

How has the project developed since the last report?

  1. Logo & Branding: Complete refresh of branding assets (NEW LOGO!):        

  2. Execution Engine

    • Improved schema propagation. #3501
    • Refactored messaging classes for better semantic clarity: ControlPayload → Direct Control Message (DCM), ChannelMarker → Embedded Control Message (ECM). #3492, #3472
    • Enhanced execution stability and correctness. #3488, #3491, #3470, #3471, #3482

  3. Services & Configuration

  4. UI & Usability

    • Added Parquet as a supported export format and alpha channel support for scatter plots. #3478, #3498
    • Improved operator usability. #3479, #3411

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

When were the last committers or PPMC members elected?

We conducted a group sync meeting on 2025-06-30 (see email thread for meeting minutes, slides and recordings). We discussed about adding a new PPMC member and voting the case on email list. the vote is to be conducted on 2025-07-03.

Have your mentors been helpful and responsive?

Yes, our mentors have been both helpful and highly responsive, and we sincerely appreciate their continued support throughout the incubation process. We would especially like to thank PJ Fanning for his outstanding guidance and active engagement. We also warmly welcome our new mentor, Ian Maxon, and look forward to benefiting from his valuable experience with the successful incubation of Apache AsterixDB.

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

Texera PPMC just released a new logo for branding purpose. The new logo is based on a peacock. Texera PPMC is working with third parties who are willing to use Texera brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html.

Signed-off-by:

  •  (texera) Cezar Andrei
    Comments:
  •  (texera) Gordon King
    Comments:
  •  (texera) PJ Fanning
    Comments:
  •  (texera) Ian Maxon
    Comments: Looks good to me. I think the project is making great progress toward adopting good practices around project discussions and license management.

IPMC/Shepherd notes:

  • No labels