Versions Compared

Old Version 34

changes.mady.by.user Unknown User (asorokoumov)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (jmclean)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: marked final

DRAFT DRAFT DRAFTFINAL DO NOT EDIT

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

...

Markdown
# Incubator PMC report for February 2025

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

TODOThere add narrative

## Community

### New IPMC members:

  - Anshum Gupta (anshum)
  - Yonik Seeley (yonik)
  - Lari Hotari (lhotari)

### People who left the IPMC:

  - Guillaume Nodet (gnodet)

## New Podlings


## Podlings that failed to report, expected next month


## Graduations
  - StreamPark
  - Answer (Dec 2024)

  The board has motions for the following:
  - Uniffle


## Releases

  The following releases entered distribution since last report:

Jan 2025:
  - Gravitino 0.8.0
  - Gluten 1.3.0
  - Uniffle 0.9.2

Dec 2024:
  - BareMaps 0.8.1
  - HugeGraph 1.5.0
  - HoraeDB python client 2.0.0
  - Gluten 1.2.1
  - KIE 10.0.0
  - StormCrawler 3.2.0
  - Uniffle 0.9.1

Nov 2024:
  - Answer 1.4.1
  - Amoro 0.7.1
  - HoraeDB 2.1.0
  - Fury 0.9.0

Oct 2024:
  - Hertzbeat 0.6.1
  - Gravitino 0.6.1
  - StreamPark 2.1.5
  - Fury 0.8.0


## IP Clearance


## Legal / Trademarks


## Infrastructure


## Miscellaneous


## Credits

## Table of Contents  
[Baremaps](#baremaps)  
[DevLake](#devlake)  
[Fury](#fury)  
[GraphAr](#graphar)  
[Gravitino](#gravitino)  
[HertzBeat](#hertzbeat)  
[HoraeDB](#horaedb)  
[KIE](#kie)  
[Nemo](#nemo)  
[NLPCraft](#nlpcraft)  
[OpenServerless](#openserverless)  
[OzHera](#ozhera)  
[Polaris](#polaris)  
[Pony Mail](#ponymail)  
[ResilientDB](#resilientdb)  
[Seata](#seata)  
[StormCrawler](#stormcrawler)  
[Teaclave](#teaclave)  
[Toree](#toree)  
[Training](#training)  
[Uniffle](#uniffle)  
[Wayang](#wayang)  
[XTableXTable](#xtable)  
[Hunter](#hunter)

--------------------
## Baremaps

Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.

Baremaps has been incubating since 2022-10-10.

### Three most important unfinished issues to address before graduating:

  1. Reviewing compliance with Apache standards.
  2. Expanding the community.
  3. Making releases.are currently 33 podlings incubating. In January, podlings executed
three distinct releases, and no IP clearance occurred. Several incubating
proposals have been discussed on the mailing list, and we have one new
podling who will join the incubator called Iggy. YuniKorn graduated last 
month
and no podlings have retired. DevLake and Wayang are close to graduation.
Several podlings failed to report and will be asked to report next month.

The incubator hasn't reported for several months. While there have been no 
urgent issues for the board, and thing have been progresing as normal, this 
is not an ideal state of affairs. The incubator, unlike other projects, 
needs to report every month, and it takes a lot of work to put the report 
together. This month, several IPMC members helped out with the 
reporting.Hopefulkly this will continue to ensure that reports are 
submitted every month, and people involved and the wider IPMC will be 
encouraged to help out.

Conversations on the list have been mostly about releases. A few other 
topics have been discussed recently, which will be included in next month's 
report.

The project maturity model has been updated to include a section on 
trademark and branding, as there have been a number of recent podlings that 
have had issues with this.

There is ongoing discussion on several new potential incubating projects.

## Community

### New IPMC members:

  - Anshum Gupta (anshum)
  - Yonik Seeley (yonik)
  - Lari Hotari (lhotari)

### People who left the IPMC:

  - Guillaume Nodet (gnodet)

## New Podlings
  - Iggy
  - Hunter (Nov 2024)

## Podlings that failed to report, expected next month
  - Gravitino
  - Nemo
  - Pony Mail
  - Teaclave
  - Toree
  - Training 

## Graduations
  - StreamPark
  - Answer (Dec 2024)

  The board has motions for the following:
  - Uniffle

## Releases

  The following releases have entered distribution since the last report:

Jan 2025:
  - Gravitino 0.8.0
  - Gluten 1.3.0
  - Uniffle 0.9.2

Dec 2024:
  - BareMaps 0.8.1
  - HugeGraph 1.5.0
  - HoraeDB python client 2.0.0
  - Gluten 1.2.1
  - KIE 10.0.0
  - StormCrawler 3.2.0
  - Uniffle 0.9.1

Nov 2024:
  - Answer 1.4.1
  - Amoro 0.7.1
  - HoraeDB 2.1.0
  - Fury 0.9.0
  - XTable 0.2.0

Oct 2024:
  - Hertzbeat 0.6.1
  - Gravitino 0.6.1
  - StreamPark 2.1.5
  - Fury 0.8.0

## IP Clearance
 - Apache Groovy receiving Geb

## Legal / Trademarks
 Updated project maturity model.

## Infrastructure
  N/A

## Table of Contents    
[Baremaps](#baremaps)  
[Cloudberry](#cloudberry)  
[DevLake](#devlake)  
[Fury](#fury)  
[GraphAr](#graphar)  
[HertzBeat](#hertzbeat)  
[HoraeDB](#horaedb) 
[Hunter](#hunter) 
[KIE](#kie)  
[NLPCraft](#nlpcraft)  
[OpenServerless](#openserverless)  
[OzHera](#ozhera)  
[Polaris](#polaris)  
[ResilientDB](#resilientdb)  
[Seata](#seata)  
[StormCrawler](#stormcrawler)  
[Uniffle](#uniffle)  
[Wayang](#wayang)  
[XTable](#xtable)

--------------------
## Baremaps

Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.

Baremaps has been incubating since 2022-10-10.

### Three most important unfinished issues to address before graduating:

  1. Reviewing compliance with Apache standards.
  2. Expanding the community.
  3. Making releases.

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

  Several animated discussions allowed us to address licensing issues.
  The fact that practices vary widely across top-level projects does not 
make
  the process easier.

### How has the community developed since the last report?

  Since the last release in December 2024, there has been an uptick in
  contributions.
  We still struggle with the pace of releases, but the overall involvement
  seems to be increasing.

### How has the project developed since the last report?

  The last release effectively summarizes the project's development since 
the
  previous report.
  https://github.com/apache/incubator-baremaps/releases/tag/v0.8.1

  More recently, we welcomed three new contributors.
  Yongjun Hong contributed issue templates and github actions to facilitate
  the onboarding of new commers.
  Alex Gacon fixed performance issues affecting the latest release.
  Rohit Yaduvanshi improved the maven artifacts.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:

  0.8.1 in December 2024

### When were the last committers or PPMC members elected?

  Sébastien Riollet in June 2024

### Have your mentors been helpful and responsive?

  Julian Hyde and Calvin Kirs provided valuable feedback.
  More generally, we struggle to get sufficient votes from PPMC members on
  our dev mailing list, which slows down the release process.

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

  Yes

### Signed-off-by:

  - [ ] (baremaps) Bertrand Delacretaz  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  
  - [ ] (baremaps) Julian Hyde  
     Comments:  
  - [X] (baremaps) Calvin Kirs  
     Comments:  
  - [ ] (baremaps) George Percivall  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  

### IPMC/Shepherd notes:

Justin Mclean:
I would take care in copying what TLP do, as you may not understand why they
did things in a certain way, you are better off following teh current 
Incubator guidances.

  --------------------
## Cloudberry

Cloudberry is one advanced and mature open-source Massively Parallel
Processing (MPP) database, which evolves from the open-source version of
the Pivotal Greenplum Database®️ but features a newer PostgreSQL kernel and
more advanced enterprise capabilities. It can serve as a data warehouse and
can also be used for 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. Finish the source code cleanup.  
      * Rename the old brand: 
  https://github.com/apache/cloudberry/pull/731.
      * Update the NOTICE and LICENSE files
  https://github.com/apache/cloudberry/pull/812.
      * Check the Apache License headers.  
  2. Publish the first Apache release.  
  3. Grow the community and attract more contributors and users.  

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

Several animated discussions allowed us to address licensing issues.
The fact that practices vary widely across top-level projects does not make the process easier.

### How has the community developed since the last report?

Since the last release in December 2024, there has been an uptick in contributions.
We still struggle with the pace of releases, but the overall involvement seems to be increasing  No.

### How has the community developed since the last report?

  1. We shared project updates across social channels and encouraged
  community members to submit sessions for upcoming conferences.
  2. Our Slack community has grown to 128 members.
  3. Key topics are actively discussed on the mailing list (92
  messages in Nov 2024, 110 messages in Dec 2024, and 49 messages in Jan
  2025).
  4. 6 new contributors to the main repo since joining the Apache
  Incubator.

### How has the project developed since the last report?

The last release effectively summarizes the project's development since the previous report.
https://github.com/apache/incubator-baremaps/releases/tag/v0.8.1

More recently, we welcomed three new contributors.
Yongjun Hong contributed issue templates and github actions to facilitate the onboarding of new commers.
Alex Gacon fixed performance issues affecting the latest release.
Rohit Yaduvanshi improved the maven artifacts  - We established a basic CI/CD workflow using GitHub Actions to support
  daily development activities.
  - We initiated and finalized the Cloudberry roadmap discussion.
  Currently, we’re focusing on high-priority tasks, including cherry-picking
  commits from the open-source Greenplum project into Cloudberry.
  - Additionally, we’ve been enriching documentation and enhancing the site
  user experience.

### How would you assess the podling's maturity?

  Please feel free to add your own commentary.

  - [xX] Initial setup
  - [xX] Working towards first release
  - [xX] Community building
  - [x ] Nearing graduation
  - [ ] Other:

### Date of last release:

  0.8.1 in December 2024N/A

### When were the last committers or PPMC members elected?

  SébastienNo Riolletnew incommitters June 2024

### Have your mentorsor PPMC members have been helpful and responsive?elected yet.

###  JulianHave Hyde and Calvin Kirs provided valuable feedback.
  More generally, we struggle to get sufficient votes from PPMC members on our dev mailing list, which slows down the release processyour mentors been helpful and responsive?

  Yes, a lot of help on the project bootstrap and community growth.

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

  Yes

### Signed-off-by:

  - [ ] (baremaps) Bertrand Delacretaz  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  There are no known brand and naming issues. The VP, Brand has approved
  the project name. (PODLINGNAMESEARCH-227)

### Signed-off-by:

  - [ ] (baremapscloudberry) JulianRoman HydeShaposhnik  
     Comments:   
  - [xX] (baremapscloudberry) CalvinWillem Ning KirsJiang  
     Comments:  
  - [ ] (baremaps) George Percivall  
     Comments:: Good to see the project moving to ASF smoothly   
  - [ X] (baremapscloudberry) MartinKent DesruisseauxYao  
     Comments: Glad to see community growth

### 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 that the IPMC or ASF Board need to be aware of?
  We would like to seek guidance regarding the IPMCgraduation orof ASFDevLake. BoardPlease
 need tolet beus aware of?


### How has the community developed since the last report?


know what we should do step by step. Thank you.

### How has the projectcommunity 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: 1. 25 new contributors have joined the community (181 contributors in 
  total)
  2. 156 new community members in Slack (1458 in total)
  3. 2 new committers were elected, and 1 PPMC was elected.

### How has the project developed since the last report?  
  1. Made a major release v1.0.1 with no compliance issues.
  2. Fix the data sync error in the incremental mode.
  3. Optimize the scope config configurations.
  4. Optimize the DORA related metrics and dashboards.
  5. Tons of UX refinement.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] (devlake) Felix Cheung  
     Comments:  Initial setup
  - [ ] Working towards first release
  - [ ] (devlake) Liang Zhang  Community building
  - [X] Nearing Comments:  graduation
  - [ ] (devlake) Lidong Dai  
     Comments:  Other:

### Date of last release:

  2024-9-23 [ ] (devlake) Sijie Guo  
     Comments:  
  - [ ] (devlake) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (devlake) Willem Ning Jiang  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## 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. Improve project documentation and align the implementation of Java/Python/JavaScript/Golang/Rust.  
  3. 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

### How has the project developed since the last report?

2 releases. The most recent was v0.9.0 on Nov 10, 2024.  

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

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

### Date of last release:

  2024-11-10

### When were the last committers or PPMC members elected?
   
  2024-11-30, added new committer pandalee99

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

### Signed-off-by:

  - [ ] (fury) tison  
     Comments:  
  - [x] (fury) PJ Fanning  
     Comments: Steady Progress 
  - [ ] (fury) Yu Li  
     Comments:  
  - [ ] (fury) Xin Wang  
     Comments:  

### 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:  
  - [X] (devlake) Jean-Baptiste Onofré  
     Comments:  I think DevLake is close to graduation. Maybe we should 
     make a pass on Maturity Model
     
(https://community.apache.org/apache-way/apache-project-maturity-model.html)
     to evaluate the current state.
  - [X] (devlake) Willem Ning Jiang  
     Comments:  Let's go through the graduation evaluation process.

### IPMC/Shepherd notes:

--------------------
## 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. Improve project documentation and align the implementation of 
  Java/Python/JavaScript/Golang/Rust.
  3. 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

### How has the project developed since the last report?

  2 releases. The most recent was v0.9.0 on Nov 10, 2024.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] (fury)Working Enricotowards Olivellifirst  release
  - [X] Community Comments:  building
  - [ ] (fury) Hao Ding  Nearing graduation
  - [ ] CommentsOther:  

### 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.Improve the robustness of GraphAr's submodules.

### 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. Attracted 1 contributor from the OSPP 2024 and we plan to
   make him as our new committer.

### How has the project developed since the last report?

1. Merged 50 PRs since the last report.
2. Initialized the CLI submodule of GraphAr library.


### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [x] Initial setup
  - [x] Working towards first release
  - [WIP] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2024-07-02

### When were the last committers or PPMC members elected?
  2024-08-15


### Have your mentors been helpful and responsive?

Yes, the mentors are very helpful and responsive.

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

We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-221)

### Signed-off-by:

  - [ ] (graphar) Calvin Kirs  
     Comments:  
  - [ ] (graphar) tison  
     Comments:  
  - [ ] (graphar) Xiaoqiao He  
     Comments:  
  - [ ] (graphar) Yu Li  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Gravitino

Gravitino is a high-performance, geo-distributed, and federated metadata
like designed to manage metadata seamlessly across diverse data sources,
vendors, and regions. Its primary goal is to provide users with unified
metadata access for both data and AI assets.

Gravitino has been incubating since 2024-06-04.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

### 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:

  - [ ] (gravitino) Daniel Dai  
     Comments:  
  - [ ] (gravitino) Junping Du  
     Comments:  
  - [ ] (gravitino) Justin McLean  
     Comments:  
  - [ ] (gravitino) Shaofeng Shi  
     Comments:  
  - [ ] (gravitino) Larry McCay  
     Comments:  
  - [ ] (gravitino) Jean-Baptiste Onofré  
     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.
  2.
  3.

### 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?
Date of last release:

  2024-11-10

### When were the last committers or PPMC members elected?

  2024-11-30, added new committer pandalee99

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

  There are no known brand and naming issues.

### Signed-off-by:

  - [ ] (fury) tison  
     Comments:  
  - [X] (fury) PJ Fanning  
     Comments: Steady Progress 
  - [ ] (fury) Yu Li  
     Comments:  
  - [X] (fury) Xin Wang  
     Comments: Steady progress
  - [ ] (fury) Enrico Olivelli  
     Comments:  
  - [ ] (fury) Hao Ding  
     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.Improve the robustness of GraphAr's submodules.

### 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. Attracted 1 contributor from the OSPP 2024 and we plan to
   make him as our new committer.

### How has the project developed since the last report?

  1. Merged 50 PRs since the last report.
  2. Initialized the CLI submodule of GraphAr library.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:

  2024-07-02

### When were the last committers or PPMC members elected?
  2024-08-15

### Have your mentors been helpful and responsive?

  Yes, the mentors are very helpful and responsive.

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

  We don't find any 3rd parties incorrectly using the podling's name and
  brand. The VP, Brand has approved the project name. 
(PODLINGNAMESEARCH-221)

### Signed-off-by:

  - [X] (graphar) Calvin Kirs  
     Comments:  
  - [ ] (graphar) tison  
     Comments:  
  - [ ] (graphar) Xiaoqiao He  
     Comments:  
  - [ ] (graphar) Yu Li  
     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.    
  2. Publish more Apache release by different committers.

### 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. 26 contributors submit 251 commits.
  2. Now the community total has 251 contributors.
  3. Students participate in OSPP activities all have done a good job.  

### How has the project developed since the last report?

  1. New version v1.6.1 has released. 
  2. The version 1.7.0 is under active development
  3. Integration with Apache Arrow.
  4. New alarm module has been developed.
  5. More features and bugfix, doc update

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:

  XXXX2024-XX11-XX22

### When were the last committers or PPMC members elected?

  2024-09-09

### Have your mentors been helpful and responsive?
Are
 things falling through the cracks? If so Yes, pleasethey listare any
open issues that need to be addressedvery nice.

### 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? HasThere theare VP,no Brandknown approvedbrand theand projectnaming name?issues.

### Signed-off-by:

  - [ ] (hertzbeat) Yonglun Zhang  
     Comments:  
  - [ ] (hertzbeat) Yu Xiao  
     Comments:  
  - [ ] (hertzbeat) Justn Mclean  
     Comments:  
  - [ X] (hertzbeat) Francis Chuang  
     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.
  2.
  3.

### 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 thebeen projectincubating developed since the last report?2023-12-11.


### HowThree wouldmost youimportant assess the podling's maturity?
Please feel free to add your own commentary.unfinished issues to address before graduating:

  -1. [Release ]more Initial setupversion
  -2. [Grow ]community(attract 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: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?

  One committer added.

### How has the project developed since the last report?

  We are starting our new metric engine. It's currently a bit slow, and 
we'll
  dedicate more time to its development after the Chinese New Year holidays.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ X] (horaedb) tison  Initial setup
  - [X] Working Comments:towards first release
  - [ X] (horaedb) Shaofeng Shi  Community building
  - [ ] Comments:Nearing  graduation
  - [ ] (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. Licensing issues (some MPL, Hibernate, EPL)
  2. Migrating some builds to Apache Infra
  3. Continued releases

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

I don't believe so, things have been discussed on lists or JIRA.

### How has the community developed since the last report?

We just voted two new community members in earlier this week, however, they haven't accepted yet. There was also one other member voted in August.

### How has the project developed since the last report?

We're making progress. It is a little painful right now, but we're making progress. We're trying to simplify our builds, better understand how to communicate as a whole and move forward. Slower progress than I'd like to see, but progress nonetheless.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [X] Initial setup
  - [X] Working towards first release
  - [X] Community building
  - [ ] Nearing graduation - I don't think we're close just yet, maybe toward the end of the year?
  - [ ] Other:

### Date of last release:

  2024-12-12

### When were the last committers or PPMC members elected?

Two this past week.

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

Doing okay now, I believe. We do need to get the info out to the new committers though, but it has only been a couple of days.

### 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, we're doing well with this.

### Signed-off-by:

  - [X] (kie) Brian Proffitt  
     Comments:  
  - [ ] (kie) Claus Ibsen  
     Comments:  
  - [ ] (kie) Andrea Cosentino  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Nemo

Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

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


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:  
  - [X] (horaedb) Shaofeng Shi  
     Comments:  Hope to see more use cases or tech blogs from Horeadb 
     community, so that users know how mature it is.
  - [X] (horaedb) Gang Li  
     Comments:  
  - [ ] (horaedb) Von Gosling  
     Comments:  

### IPMC/Shepherd notes:

--------------------

## Hunter

Hunter performs statistical analysis of performance test results 
and finds change-points and notifies about possible performance 
regressions. A typical use-case of hunter is as follows:
* A set of performance tests is scheduled repeatedly.
* The resulting metrics of the test runs are stored in a time 
series database (e.g, Graphite) or appended to CSV files.
* Hunter is launched by a Jenkins/Cron job (or an operator) to 
analyze the recorded metrics regularly.
* Hunter notifies about significant changes in recorded metrics 
by outputting text reports or sending Slack notifications.

Hunter has been incubating since 2024-11-27.

### Three most important unfinished issues to address before graduating:

  1. Finish project setup:
   a. Rename - PODLINGNAMESEARCH-230.
   b. Add Apache License headers https://github.com/apache/hunter/issues/31.
  2. Create a project website.
  3. Publish the first release under the new name.

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

  The original project name has been rejected in
  
[PODLINGNAMESEARCH-228](https://issues.apache.org/jira/browse/PODLINGNAMESEA
  RCH-228)
  and the proposal for the new name
  
[PODLINGNAMESEARCH-230](https://issues.apache.org/jira/browse/PODLINGNAMESEA
  RCH-230)
  has been blocked on review for a couple of weeks.

### How has the community developed since the last report?

  We have the first engagements in GH issues. We do not have any new
  contributors,
  but also we haven’t been promoting the project because we do not have the
  new approved name to promote.

### How has the project developed since the last report?

  Since the incubation started, there have been several notable 
developments:
  1. The project has migrated from datastax-labs/hunter to apache/hunter
  repository ([HUNTER-1](https://issues.apache.org/jira/browse/HUNTER-1)).
  2. Nyrkiö upstreamed all changes from their private fork -
  https://github.com/apache/hunter/pull/27.
  3. A complete overhaul of documentation has been done to lower the entry
  barrier - https://github.com/apache/hunter/pull/28.

### How would you assess the podling's maturity?
Please
 feel freeWe toare addfinishing yourthe owninitial commentarysetup.

###  - [ ] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [ ] Nearing graduationSigned-off-by:

  - [ X] 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:

  - [ ] (nemo) Hyunsik Choi  
     Comments:  
  - [ ] (nemo) Byung-Gon Chun  
     Comments:  
  - [ ] (nemo) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (nemo) Markus Weimer  
     Comments:  

### IPMC/Shepherd notes:



--------------------
 ## NLPCraft

A Scala library for NLU applications

NLPCraft has been incubating since 2020-02-13.

### Three most important unfinished issues to address before graduating:

  1. Community growth.
  2. Extending the technology stack
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?
None(hunter) Dave Fisher  
     Comments:   
  - [ ] (hunter) Enrico Olivelli  
     Comments:   
  - [ ] (hunter) Lari Hotari  
     Comments:   
  - [ ] (hunter) Michael Semb Wever  
     Comments:   

### IPMC/Shepherd notes: 

Justin MClean:
VP, Brand Management has approved the new name.

--------------------
## 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. Licensing issues (some MPL, Hibernate, EPL)
  2. Migrating some builds to Apache Infra
  3. Continued releases

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

  I don't believe so, things have been discussed on lists or JIRA.

### How has the community developed since the last report?

  We just voted two new community members in earlier this week, however, 
they
  haven't accepted yet. There was also one other member voted in August.

### How has the communityproject developed since the last report?
-
  We're engaged with Python community developers interested in contributing.
- We began investigating LLM integration to enhance current functionality (especially sLLMs).
- We initiated discussions with potential customers and users, including LoomHR.ai and Humatron.ai, whose developers may join the community.

### How has the project developed since the last report?
- Examples extended.
- Technical PRs processed.
- Research and investigation tasks related to sLLMsmaking progress. It is a little painful right now, but we're making
  progress. We're trying to simplify our builds, better understand how to
  communicate as a whole and move forward. Slower progress than I'd like to
  see, but progress nonetheless.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [X] Initial setup
  - [X] Working towards first release
  - [X] Community building
  - [ ] Nearing graduation
 ] Nearing graduation - I don't think we're close just yet, maybe 
  toward the end of the year?
  - [ ] Other:

### Date of last release:

2023  2024-0212-3012

### When were the last committers or PPMC members elected?

August of 2021  Two this past week.

### Have your mentors been helpful and responsive?
Are things fallingDoing through the cracks? If sookay now, 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:

  - [ ] (nlpcraft) Roman Shaposhnik  
     Comments:  
  - [ ] (nlpcraft) Furkan Kamaci  
     Comments:  
  - [ ] (nlpcraft) Evans YeI believe. We do need to get the info out to the new
  committers though, but it has only been a couple of days.

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

  Yes, we're doing well with this.

### Signed-off-by:

  - [X] (kie) Brian Proffitt  
     Comments:  
  - [ ] (nlpcraftkie) PaulClaus KingIbsen  
     Comments:  
  - [ ] (nlpcraftkie) KonstantinAndrea ICosentino Boudnik  
     Comments:  

### IPMC/Shepherd notes:

--------------------
 ## OpenServerlessNLPCraft

A Scala library for NLU applications

OpenServerlessNLPCraft ishas anbeen openincubating source, cloud-agnostic, serverless platform. It
offers a complete environment for serverless applications development, based
on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an
unified developer experience with a plethora of services (SQL or noSQL
databases, key-value stores, object storage, LLMs services, function
schedulers) managed by the platform's core: the operator, along with tooling
(the CLI) to simplify (and interact with) deployments, integrated ide and
starter application and optimized runtimes integrated with the staters.

OpenServerless has been incubating since 2024-06-17.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

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


since 2020-02-13.

### Three most important unfinished issues to address before graduating:

  1. Community growth.
  2. Extending the technology stack
  3.

### 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 engaged with Python community developers interested in contributing.
  - We began investigating LLM integration to enhance current functionality
  (especially sLLMs).
  - We initiated discussions with potential customers and users, including
  LoomHR.ai and Humatron.ai, whose developers may join the community.

### How has the communityproject developed since the last report?
  - Examples extended.

### How has the project developed since the last report?
  - Technical PRs processed.
  - Research and investigation tasks related to sLLMs

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:

  XXXX2023-XX02-XX30

### When were the last committers or PPMC members elected?
  August of 2021.

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressedNo answer.

### 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:

No answer.

### Signed-off-by:

  - [ ] (nlpcraft) Roman Shaposhnik  
     Comments:  
  - [ ] (nlpcraft) Furkan Kamaci  
     Comments:  
  - [ ] (openserverlessnlpcraft) BertrandEvans DelacretazYe  
     Comments:  
  - [ ] (openserverlessnlpcraft) EnricoPaul OlivelliKing  
     Comments:  
  - [ ] (openserverlessnlpcraft) FrançoisKonstantin I PaponBoudnik  
     Comments:  

### IPMC/Shepherd notes:

---- [ ] (openserverless) JB Onofré  
     Comments:  
  - [ ] (openserverless) PJ Fanning  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## OzHera

OzHera is an application observation platform (APM) in the era of cloud
native, with the application as its core, integrating capabilities such as
metric monitoring, trace tracking, logging, and alerting

OzHera----------------
## OpenServerless

OpenServerless is an open source, cloud-agnostic, serverless platform. It
offers a complete environment for serverless applications development, based
on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an
unified developer experience with a plethora of services (SQL or noSQL
databases, key-value stores, object storage, LLMs services, function
schedulers) managed by the platform's core: the operator, along with tooling
(the CLI) to simplify (and interact with) deployments, integrated ide and
starter application and optimized runtimes integrated with the staters.

OpenServerless has been incubating since 2024-0706-1117.

### Three most important unfinished issues to address before graduating:

  1. Community Building
  2. Review the status of all subprojects and align documentation
  3. Assess the requirements for the First Release

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


### How has1. theWe projecttried, developedthrough sinceposts theon 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:

  - [ ] (ozhera) Yu Xiao  
     Comments:  
  - [ ] (ozhera) Yu Li  
     Comments:  
  - [ ] (ozhera) Kevin Ratnasekera  
     Comments:  
various social networks, to give visibility 
  to the project
  2. We organized and publicized a training course focused on the use of 
  Apache OpenServerless and IA.
  3. Started a Discord channel to support people learning OpenServerless 
  with the AI course

### How has the project developed since the last report? 

  1. The porting from the community version of Nuvolaris has been completed
  2. We have therefore focused on making the system stable, making the CLI 
  more robust and the openserverless-tasks sub-project that collects the
  automation and integration scripts more organic
  3. We have brought the test suite to verify the functioning of the 
  Kubernetes operator on all supported versions (k3s, k8s, docker, aks, eks,
  gks, openshift)
  4. We have published the site with the official documentation and made 
  various updates to it

### How would you assess the podling's maturity?

  - [ ] (ozhera) Duo Zhang  Initial setup
  - [X] Working Comments:towards first release

### IPMC/Shepherd notes:



--------------------
## Polaris

Polaris is a catalog for data lakes. It provides new levels of choice,
flexibility and control over data, with full enterprise security and Apache
Iceberg interoperability across a multitude of engines and infrastructure.

Polaris has been incubating since 2024-08-09.

### Three most important unfinished issues to address before graduating:

  1. Finalize the first 0.9.0 release
  2. Grow the community, especially in terms of contributors
  3. Following 0.9.0 release, we are heading to 1.0.0 that will be a larger release, including binary distributions.

### Are there any issues that the IPMC or ASF Board need to be aware of?
We already see growth of the community:
- we have new users on Slack, deploying and using Polaris
- we have more contributors and new committers

### How has the community developed since the last report? We have good growth in the community with new users (we see more and more interest on Slack), and also new contributors and committers.  ### How has the project developed since the last report?
This is the first Polaris report.
We are working on a lot of important changes for the project, allowing Polaris to support more use case (especially storage backends).
We also have discussions about new features: Table Maintenance Policy, Federated Catalogs, ...

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

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

### Date of last release:

  N/A

### When were the last committers or PPMC members elected?
New committers have been elected on Jan 13, 2025.

### Have your mentors been helpful and responsive?
Yes, a lot of help for LICENSE/NOTICE fixes.

### 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:

  - [ ] (polaris) Bertrand Delacretaz  
     Comments:   [X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  None Yet

### When were the last committers or PPMC members elected?

  2024-08-22

### Have your mentors been helpful and responsive?

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

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

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

### Signed-off-by:

  - [ ] (openserverless) Bertrand Delacretaz  
     Comments:  
  - [ ] (openserverless) Enrico Olivelli  
     Comments:  
  - [ ] (openserverless) François Papon  
     Comments:  
  - [X] (openserverless) JB Onofré  
     Comments: Nice progress ! 
  - [X] (openserverless) PJ Fanning  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## OzHera

OzHera is an application observation platform (APM) in the era of cloud
native, with the application as its core, integrating capabilities such as
metric monitoring, trace tracking, logging, and alerting

OzHera has been incubating since 2024-07-11.

### Three most important unfinished issues to address before graduating:

  1.Set up necessary resources in ASF.  
  2.Make the first apache release.  
  3.Build a diverse 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?
  Updated the website layout and added necessary ASF website page elements.
  Added a new committer.
  Added a new contributor.
  Merged 30 PRs.

### How has the project developed since the last report?
  We have completed the overall cleanup of the code and started the first
  release.
  Complete the basic construction of the intelligent agent module.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] (polaris) Holden Karau  Initial setup
  - [X] Working Comments:towards first release
  - [ X] (polaris) Kent Yao  Community building
  - [ ] Comments:Nearing  graduation
  - [ ] (polaris) Ryan Blue  Other:

### Date of last release:
  There is no Comments:apache release yet.

### When were -the [X] (polaris) JB Onofre  
     Comments:  last committers or PPMC members elected?
  2025-01-13

### IPMC/Shepherd notes:



--------------------
## Pony Mail

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:

  1.
  2.
  3.

### 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:



--------------------
## 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.Release more applications.

### 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 bunch of new applications and will release them in a few weeks.
Have your mentors been helpful and responsive?
  Yes, mentors are helpful and responsive.

### Is the PPMC managing the podling's brand / trademarks?
  Not yet.

### Signed-off-by:

  - [ ] (ozhera) Yu Xiao  
     Comments:  
  - [ ] (ozhera) Yu Li  
     Comments:  
  - [ ] (ozhera) Kevin Ratnasekera  
     Comments:  
  - [ ] (ozhera) Duo Zhang  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Polaris

Polaris is a catalog for data lakes. It provides new levels of choice,
flexibility and control over data, with full enterprise security and Apache
Iceberg interoperability across a multitude of engines and infrastructure.

Polaris has been incubating since 2024-08-09.

### Three most important unfinished issues to address before graduating:

  1. Finalize the first 0.9.0 release
  2. Grow the community, especially in terms of contributors
  3. Following 0.9.0 release, we are heading to 1.0.0 that will be a larger 
  release, including binary distributions.

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

  - All discussions (design proposals, process improvements) are discussed 
on
  the mailing list (94 messages on the dev mailing in Dec 24, 196 in Jan 25
  for instance)
  - New users showed on Slack:
  - New contributors interested to work on key features for Polaris (2
  expressed interest for storage backend and TMS)
  - Two new committers have been elected during the last quarter (Dmitri
  Bourlatchkov, Dennis Huo)

### How has the project developed since the last report?

  We are working on a lot of important changes for the project, allowing
  Polaris to support more use case (especially storage backends).
  We also have discussions about new features: Table Maintenance Policy,
  Federated Catalogs, ... (on the mailing list with the GitHub Issues for
  tracking).

### How would you assess the podling's maturity?

  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ X] Working towards first release
  - [xX] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:    

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

### When were the last committers or PPMC members elected? 
November of 2023

  New committers have been elected on Jan 13, 2025.

### Have your mentors been helpful and responsive?

The mentors helpedYes, tremendouslya throughoutlot theof projecthelp build-up and transferfor LICENSE/NOTICE fixes.


### Is the PPMC managing the podling's brand / trademarks?
There
 are no known brand and naming issues as reported here. Yes

### Signed-off-by:

  - [ ] (resilientdbpolaris) JunpingBertrand DuDelacretaz  
     Comments:  
  - [ ] (resilientdbpolaris) CalvinHolden KirsKarau  
     Comments:  
  - [ ] (resilientdbpolaris) KevinKent RatnasekeraYao  
     Comments:  
  - [ X] (resilientdbpolaris) RomanRyan ShaposhnikBlue  
     Comments:  Fixed some formatting in the report. For community 
  - [ ] (resilientdb) Christian Grobmeier  
     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.
  2.
  3.

### 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:

  - [ ] (seata) Sheng Wu  
     Comments:  
  - [ ] (seata) Justin Mclean  
     Comments:  
  - [ ] (seata) Huxing Zhang  
     Comments:  
  - [ ] (seata) Heng Du  
     Comments:  
  - [ ] (seata) Xin Wang  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## StormCrawler

StormCrawler is a collection of resources for building low-latency,
customisable and scalable web crawlers on Apache Storm.

StormCrawler has been incubating since 2024-03-19.

### Three most important unfinished issues to address before graduating:

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

StormCrawler remains a rather mature and stable project, continuing to serve its niche effectively. While there isn’t much new to report in terms of major developments, we did have a contributor show up recently and provide some pull requests, which is always a positive sign.

It’s worth noting that, even in the age of AI, the number of people conducting their own large-scale web crawls remains relatively low. Many opt to leverage datasets like Common Crawl rather than setting up and maintaining their own crawling infrastructure. This makes community contributions even more valuable, as StormCrawler continues to be a reliable solution for those who do require custom crawling capabilities.


### How has the project developed since the last report?

A new release of StormCrawler was made. 

However, one area of concern is the level of engagement among the initial committers. Out of the five original committers, only three have been actively contributing, while the remaining two have shown little to no involvement since the project's incubation. While it's not uncommon to see fluctuations in contributor activity due to shifting priorities and time constraints, this does highlight the need to expand the committer base. Therefore, we are happy that we could add an additional committer and PPMC member since incubationdevelopment, are there more specific data points (other than "more")? 
How
     many contributions are coming from contributors outside of the 
original set
     of contributors and companies? In these reports, try to focus more on
     community growth and development than project development.
  - [X] (polaris) JB Onofre  
     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.Release more applications.

### 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 bunch of new applications and will release them in a 
few
  weeks.

  1. New  Projects:
  Coinsensus - A decentralized financial application integrating ResilientDB
  for real-time transactions, fraud detection, and group budgeting.
    GitHub: https://github.com/ResilientApp/Coinsensus-Backend
  ResCanvas - A decentralized collaborative drawing platform leveraging
  ResilientDB for real-time multi-user drawings.
    GitHub: https://github.com/ResilientApp/ResCanvas
  ResAuc - A blockchain-based online auction platform ensuring transparent
  and tamper-proof bidding.
    GitHub: https://github.com/ResilientApp/DDS-Backend-main
  ResVote - A scalable and secure online voting system built on ResilientDB
  to ensure election integrity.
    GitHub: https://github.com/ResilientApp/ResVote
  MemLens - A continuous profiling tool for ResilientDB, providing real-time
  performance monitoring and debugging insights.
    GitHub: https://github.com/ResilientEcosystem/MemLens
  ResCash - A secure and user-friendly financial accounting solution
  integrating ResilientDB for transaction transparency.
    GitHub: https://github.com/ResilientApp/ResCash 

  2. NPM Module Updates:
  create-resilient-app - A CLI tool for scaffolding React/Vue projects with
  ResVault SDK integration, supporting both JS and TS.
  Features: Automatic setup, interactive prompts, and streamlined project
  initialization.
      NPM: https://www.npmjs.com/package/create-resilient-app
  resvault-sdk - A lightweight SDK to integrate ResVault into web
  applications for secure transactions and communication.
  Features: Simplified API, event listening, and transaction handling via
  postMessage.
      NPM: https://www.npmjs.com/package/resvault-sdk
  resilient-node-cache - A TypeScript library for syncing ResilientDB data
  with MongoDB via WebSocket and HTTP, ensuring seamless reconnection.
  Features: Automatic reconnection, real-time sync, and high-performance
  batching.
      NPM: https://www.npmjs.com/package/resilient-node-cache

  3. PyPI Module Updates:
  resilient-python-cache - A Python library for real-time synchronization
  between ResilientDB and MongoDB via WebSocket and HTTP.
  Features: Auto-reconnection, configurable sync intervals, and efficient
  data fetching.
  PyPI: https://pypi.org/project/resilient-python-cache/

  4. ResVault Enhancements:
  ResVault Smart Contract Key Management—This feature now supports smart
  contract key management, enabling the generation of an owner’s key from
  public/private key pairs and registering the owner’s address with ResDB
  smart contract services. It also facilitates smart contract deployment for
  enhanced decentralized application interactions.

### How would you assess the podling's maturity?

  Please feel free to add your own commentary.

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

### Date of last release:

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

### When were the last committers or PPMC members elected? 
  
November of 2024-09-212023

### Have your mentors been helpful and responsive?
  The mentors helped tremendously throughout the project build-up and

Nothing of notetransfer.

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

The name wasThere approvedare byno VP,known Brandbrand afterand consultingnaming theissues Apacheas Stormreported projecthere.

### Signed-off-by:

  - [x ] (stormcrawlerresilientdb) DaveJunping FisherDu  
     Comments:  
  The podling knows that community growth is required.- [ ] (resilientdb) Calvin Kirs  
     Comments:  
  - [ ] (stormcrawlerresilientdb) LewisKevin John McGibbneyRatnasekera  
     Comments:  
  - [ ] (stormcrawlerresilientdb) AyushRoman SaxenaShaposhnik  
     Comments:  
  - [x ] (stormcrawlerresilientdb) PJChristian FanningGrobmeier  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Teaclave

Teaclave is a universal secure computing platform.

Teaclave has been incubating since 2019-08-20.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

### 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:

  - [ ] (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:



--------------------
## 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.
  2.
  3.

### 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?
  Dave Fisher:
    Why are new sub-projects all in a third party org (ResilientApp) with 
  releases coming in weeks?
    Substantial work remains to move to the Incubator and this includes 
  careful work on branding.

  Justin Mclean:
   Thanks, Dave, for noticing this. I've brought it up with the project. I 
also not that code 
   in those repos do not follow ASF policy i.e. no code headers or NOTICE 
files.

--------------------
## 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. Handle security vulnerabilities more efficiently and set up a security 
  page for the project.

### 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. 40 new code contributors have joined the community (550 contributors in
  total)
  2. 8 new committers were elected, and 2 PPMC members were elected.
  3. On the Seata GitHub page, there are around 3,500 "used by" listings,
  which means over 500 more projects are now depending on Seata since the
  last report.

### How has the project developed since the last report?

  1. Since the last report, we've merged 268 PRs, which include over 21 new
  features, plus a bunch of optimizations and bug fixes.
  2. Since the last report, versions 2.1.0 and 2.2.0 have been released.
  We're currently voting on 2.3.0. Additionally, the Golang SDK project has
  completed its first major milestone for entering the ASF and is preparing
  for release.
  3. Since the last report, we have received several vulnerability reports,
  and we have fixed four of them. We disclosed one CVE, and the other three
  vulnerabilities (two CVEs) will be closed with the release of version 
2.3.0.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:

  XXXX2024-XX10-XX12

### When were the last committers or PPMC members elected?

  2025-01-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  Our mentors have been very helpful and responsive. During this period, we
  added a new mentor, Xin Wang.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd partiesA respectingcompany andattempted correctlyto usingregister thesome podlings
namedomains andrelated brand?to IfSeata, not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?and we
  responded with a rejection.

### Signed-off-by:

  - [ X] (toreeseata) LucianoSheng ResendeWu  
     Comments:  
  - [ X] (toreeseata) RyanJustin BlueMclean  
     Comments:  
  - [ X] (toreeseata) WeiweiHuxing YangZhang  
     Comments:  

### IPMC/Shepherd notes:

[PJF] Mailing lists show little activity. PPMC is ignoring an important privacy  
issue (TOREE-559). There was discussion in November about a release but nothing  
since. Podling over 9 years old. Maybe time to consider retirement.  

  
  - [X] (seata) Heng Du  
     Comments:  
  - [X] (seata) Xin Wang  
     Comments: Steady progress

### IPMC/Shepherd notes:

--------------------
## TrainingStormCrawler

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.

TrainingStormCrawler is a collection of resources for building low-latency,
customisable and scalable web crawlers on Apache Storm.

StormCrawler has been incubating since 20192024-0203-2119.

### Three most important unfinished issues to address before graduating:

  1. Community building
  2.
  3.

### 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:

  - [ ] (training) Craig Russell  
     Comments:  
  - [ ] (training) Christofer Dutz  
     Comments:  
  - [ ] (training) Justin Mclean  
     Comments:  
  - [ ] (training) Lars Francke  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Uniffle

Uniffle is an unified Remote Shuffle Service

Uniffle has been incubating since 2022-06-06.

### Three most important unfinished issues to address before graduating:

  1.
  2.
  3.

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

### How has the community developed since the last report?

  StormCrawler remains a rather mature and stable project, continuing to
  serve its niche effectively. While there isn’t much new to report in terms
  of major developments, we did have a contributor show up recently and
  provide some pull requests, which is always a positive sign.

  It’s worth noting that, even in the age of AI, the number of people
  conducting their own large-scale web crawls remains relatively low. Many
  opt to leverage datasets like Common Crawl rather than setting up and
  maintaining their own crawling infrastructure. This makes community
  contributions even more valuable, as StormCrawler continues to be a
  reliable solution for those who do require custom crawling capabilities.

### How has the project developed since the last report?

  A new release of StormCrawler was made.

  However, one area of concern is the level of engagement among the initial
  committers. Out of the five original committers, only three have been
  actively contributing, while the remaining two have shown little to no
  involvement since the project's incubation. While it's not uncommon to see
  fluctuations in contributor activity due to shifting priorities and time
  constraints, this does highlight the need to expand the committer base.
  Therefore, we are happy that we could add an additional committer and PPMC
  member since incubation.

### How would you assess the podling's maturity?

  Please feel free to add your own commentary.

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

### Date of last release:

  XXXX2024-XX12-XX03

### When were the last committers or PPMC members elected?

  2024-09-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 

  Nothing of note.

### Is the PPMC managing the podling's brand / trademarks?
Are
 3rd parties respecting and correctly using the podlings
The name andwas brand?approved Ifby notVP, whatBrand actionsafter hasconsulting the PPMCApache taken toStorm
correct this? Has the VP, Brand approved the project name?project.

### Signed-off-by:

  - [ X] (unifflestormcrawler) FelixDave CheungFisher  
     Comments:  
The podling -knows [that ]community (uniffle)growth Junping Du  
     Comments:  is required.
  - [ ] (unifflestormcrawler) Lewis LiuJohn XunMcGibbney  
     Comments:  
  - [ X] (unifflestormcrawler) WeiweiAyush YangSaxena  
     Comments:  
  - [ X] (unifflestormcrawler) ZhankunPJ TangFanning  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Wayang

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

Wayang-
## Uniffle

Uniffle is an unified Remote Shuffle Service

Uniffle has been incubating since 20202022-1206-1606.

### Three most important unfinished issues to address before graduating:

  1.The Growingvote theof communitygraduation /passed attractingin morethe committersmail andlist developers 
  2. Automate release process	
  3. Build FedML further 
of incubatr.

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

  NoneNo.

### How has the community developed since the last report?

  374 pull requests are merged. 201 issues Stagnateare closed.

### How has the project developed since the last report?

  Slow progress374 pull requests are merged. 201 issues are closed.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:

    

2023-09-20   2025-01-09.

### When were the last committers or PPMC members elected?

  Baolong Mao, elected at 2024-0910-16 28.
	
### Have your mentors been helpful and responsive?
Are things fallingYes. throughThey the cracks? If so, please list any
open issues that need to be addressedare helpful.

All good.

### 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 approvedYes, the project name?

Yes, is approved.

### Signed-off-by:

  - [ ] (wayanguniffle) ChristoferFelix DutzCheung  
     Comments:  
  - [ ] (wayanguniffle) LarsJunping GeorgeDu  
     Comments:  
  - [ X] (wayanguniffle) BerndLiu FondermannXun  
     Comments:  
  - [ ] (wayanguniffle) Jean-BaptisteWeiwei OnofréYang  
     Comments:  

### IPMC/Shepherd notes:

[PJF] Have been discussing graduation. Some issues with invalid content in releases but  
these are being addressed.


  - [ ] (uniffle) Zhankun Tang  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Wayang

Wayang is a cross-
## XTable

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

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

Wayang has been incubating since 20242020-0212-1116.

### 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 requested in GitHub issues and discussions.
  3. Establishing a consistent ASF release cadence, targeting a well planned release every 2 months to align with ASF best practices and ensure stability Growing the community / attracting more committers and developers 
  2. Automate release process	
  3. Build FedML further 

### 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. Launched a bi-weekly 45min developer sync to discuss features, ideas and issues with growing attendance in each session.
2. Created a slack channel to reduce friction in collaboration.
3. Welcomed four first time contributors last month and two new people planning to contribute this month.
    since the last report?
  Stagnate

### How has the project developed since the last report?
1. ASF release process streamlined and 0.2.0 release published in November 2024.
2. Created an RFC process for working on new features in collaboration with the community, with one of them close to completion, one in progress and one of them in early stage.    
3. GH issues are being actively triaged and closed, 34 PR's merged since Nov 2024.  

### How would you assess?
  Slow progress

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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

### Date of last release:    

  2023-09-20

### When were the last committers or PPMC members elected?

  2024-09-16

### Have your mentors been helpful and responsive?

  All good.

### Is the PPMC managing the podling's maturitybrand / trademarks?

Please feel free to add your own commentary.Yes, approved.

### Signed-off-by:

  - [x ] Initial setup(wayang) Christofer Dutz  
  - [x] Working towardsComments: first release
  - [x] Community building
  - [ ] Nearing graduation ] (wayang) Lars George  
     Comments:  
  - [ ] 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 really helpful on the release process.

### 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:

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

### IPMC/Shepherd notes:     

--------------------
## Hunter

Hunter performs statistical analysis of performance test results 
and finds change-points and notifies about possible performance 
regressions. A typical use-case of hunter is as follows:
* A set of performance tests is scheduled repeatedly.
* The resulting metrics of the test runs are stored in a time 
series database (e.g, Graphite) or appended to CSV files.
* Hunter is launched by a Jenkins/Cron job (or an operator) to 
analyze the recorded metrics regularly.
* Hunter notifies about significant changes in recorded metrics 
by outputting text reports or sending Slack notifications.


Hunter has been incubating since 2024-11-27.

### Three most important unfinished issues to address before graduating:

1. Finish project setup:
   a. Rename - PODLINGNAMESEARCH-230.
   b. Add Apache License headers https://github.com/apache/hunter/issues/31.
2. Create a project website.
3. Publish the first release under the new name.

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

The original project name has been rejected in 
[PODLINGNAMESEARCH-228](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-228)
 and the proposal for the new name 
[PODLINGNAMESEARCH-230](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-230)
 has been blocked on review for a couple of weeks.

### How has the community developed since the last report?

We have the first engagements in GH issues. We do not have any new contributors, 
but also we haven’t been promoting the project because we do not have the new 
approved name to promote.

### How has the project developed since the last report?

Since the incubation started, there have been several notable developments:
1. The project has migrated from datastax-labs/hunter to apache/hunter 
repository ([HUNTER-1](https://issues.apache.org/jira/browse/HUNTER-1)).
2. Nyrkiö upstreamed all changes from their private fork -
https://github.com/apache/hunter/pull/27.
3. A complete overhaul of documentation has been done to lower the entry 
barrier - https://github.com/apache/hunter/pull/28. 

### How would you assess the podling's maturity?

We are finishing the initial setup.(wayang) Bernd Fondermann  
     Comments:  
  - [X] (wayang) Jean-Baptiste Onofré  
     Comments:  

### IPMC/Shepherd notes:

  [PJF] Have been discussing graduation. Some issues with invalid content in
  releases but these are being addressed.

--------------------
## XTable

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

 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 requested in GitHub 
  issues and discussions.
  3. Establishing a consistent ASF release cadence, targeting a well 
  planned release every 2 months to align with ASF best practices and ensure
  stability

### 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. Launched a bi-weekly 45min developer sync to discuss features, ideas 
and
  issues with growing attendance in each session.
  2. Created a slack channel to reduce friction in collaboration.
  3. Welcomed four first time contributors last month and two new people
  planning to contribute this month.

### How has the project developed since the last report?
  1. ASF release process streamlined and 0.2.0 release published in November
  2024.
  2. Created an RFC process for working on new features in collaboration 
with
  the community, with one of them close to completion, one in progress and
  one of them in early stage.
  3. GH issues are being actively triaged and closed, 34 PR's merged since
  Nov 2024.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [X] Initial setup
  - [X] Working towards first release
  - [X] 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 really helpful on the release process.

### Is the PPMC managing the podling's brand / trademarks?
  Yes.

### Signed-off-by:

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

### IPMC/Shepherd notes:  

--------------------