Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Markdown
=== Report content ===
# Incubator PMC report for December 2023

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

TODOThere are add narrative

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


## IP Clearance


## Legal / Trademarks


## Infrastructure


## Miscellaneous


## Credits

## Table of Contents  
[Answer](#answer)  
[Baremaps](#baremaps)  
[KIE](#kie)  
[Livy](#livy)  
[Nemo](#nemo)  
[Pony Mail](#pony mail)  
[ResilientDB](#resilientdb)    
[Teaclave](#teaclave)  
[Uniffle](#uniffle)  
[Wayang](#wayang)  


--------------------
## Answer

A Q-and-A platform software for teams at any scales.

Answer has been incubating since 2023-10-09.

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

  - [ ] (answer) Willem Ning Jiang  
     Comments:  
  - [ ] (answer) tison  
     Comments:  
  - [ ] (answer) Justin Mclean  
     Comments:  
  - [ ] (answer) Christofer Dutz  
     Comments:  

### IPMC/Shepherd notes:



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

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

Baremaps has been incubating since 2022-10-10.

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

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?
presently 28 podlings incubating. In December, podlings executed 
5 distinct releases.

A new podling has joined the incubator HoraeDB, and there has been 
discussion on several incubating proposals.

There was some cleanup of retired podlings.

The java-driver donation from the Cassandra project did not follow the 
correct process.

Teaclave has not reported for some time, and a roll call will be undertaken.

## Community

### New IPMC members:
  - Enrico Olivelli
  - Ismaël Mejía
  - Kent Yao
  - Rakesh Radhakrishnan

### People who left the IPMC:
  - none

## New Podlings
  - HoraeDB

## Podlings that failed to report, expected next month
  - KIE
  - Teaclave

## Graduations
  - None

  The board has motions for the following:

  - None

## Releases

  The following releases entered distribution during the month of
  November:
  - Answer 1.2.0
  - Opendal 0.42.0
  - Pekko connectors 1.0.1
  - Pekko persistence dynamodb 1.0.0
  - Pekko 1.0.2

## IP Clearance
  - Cassandra java-driver

## Legal / Trademarks
  N/A

## Infrastructure
  N/A

## Miscellaneous
  N/A

## Table of Contents  
[Answer](#answer)  
[Baremaps](#baremaps)  
[Livy](#livy)  
[Nemo](#nemo)  
[Pony Mail](#ponymail)  
[ResilientDB](#resilientdb)    
[Uniffle](#uniffle)  
[Wayang](#wayang)  

--------------------
## Answer

A Q-and-A platform software for teams at any scale.

Answer has been incubating since 2023-10-09.

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

  1. Release more ASF-compliant versions.
  2. Build and grow a diverse community, attracting more committers and PPMC
  members.

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

  - 6 new contributors have joined the community (48 in total).
  - We have launched the contributors' documentation on our official website
  and will keep it regularly updated, aiming to guide users in quickly
  getting involved with contributions.
  https://answer.apache.org/community/contributing
  - We have preliminarily set out our community event plan for 2024, which
  includes participating in events such as GSoC and OSPP to increase external
  contributions, as well as organizing cross-community events in Q1 and Q4 to
  motivate external developers to contribute.
  - We plan to initiate open bi-weekly community meetings after the Chinese
  Lunar New Year in 2024, to which we will invite all external contributors
  and anyone interested in the development of the Answer community.

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


### How has- theThe project developed since the last report?
first ASF-compliant version (v1.2.0) was released.
  - 1 new feature, 7 bug fixes, 2 improvements.
  - answer.dev has been redirected to answer.apache.org

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

  29  XXXX-XX-XXNov, 2023

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


### Have yourIt mentorswas beenin helpfulOctober and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressedsince Apache Answer was accepted into the Apache
  Incubator.

### Have your mentors been helpful and responsive?

  Yes, all the mentors are helpful and responsive.

### Is the PPMC managing the podling's brand / trademarks?
Are
  3rdThere partiesare respectingno andknown correctlybrand usingand thenaming podlingsissues.

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:
### Signed-off-by:

  - [ ] (answer) Willem Ning Jiang  
     Comments:  
  - [ x] (baremapsanswer) Bertrand Delacretaztison  
     Comments: Doing well in releasing and handling security reports.
  - [ ] (baremapsanswer) MartinJustin DesruisseauxMclean  
     Comments:  
  - [ ] (baremapsanswer) JulianChristofer HydeDutz  
     Comments:  

### IPMC/Shepherd - [ ] (baremaps) Calvin Kirs  
     Comments:  
  - [ ] (baremaps) George Percivall  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     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.
  2.
  3.

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


notes:

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

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

Baremaps has been incubating since 2022-10-10.

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

  1. Getting the code and documentation website in compliance with Apache 
  standards.
  2. Growing the community
  3. Making releases

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

  We acknowledge that we need to make progress on community building and will
  try to focus on this aspect in 2024.

### 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:    We had a few external contributions to the project, but no new committer
  joined the community. Most notably, Joe Polastre, from FlightAware, the
  world's largest flight tracking and data platform, created a fast tile
  exporter for Baremaps written in Go [1]. Some of his ideas have already
  been contributed back to the project. We also started interesting
  discussions with the Apache SIS community regarding spatial data codecs [2].

  [1] https://github.com/flightaware/baremaps-exporter

  [2] https://github.com/apache/incubator-baremaps/discussions/805

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

  - We addressed many of the podling requirements for the latest release.
  - We also added support for PMTiles, 3D building extrusion, and
  minutely/hourly/daily diffs from OpenStreetMap.

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

  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] (kie)Working Claustowards Ibsenfirst  release
  - [X] Community Comments:  building
  - [ ] (kie) Andrea Cosentino  Nearing graduation
  - [ ] CommentsOther:  

### IPMC/Shepherd notesDate of last release:



  2023--------------------
## 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.
  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 release11-20

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

  2023-08-31

### Have your mentors been helpful and responsive?

  Yes, the mentors' advice has been very helpful, especially in addressing
  issues that appeared during the last release.

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

  Yes

### Signed-off-by:

  - [ ] (baremaps) Bertrand Delacretaz  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  
  - [X] (baremaps) Julian Hyde  
     Comments:  Podling is going well. The discussions with SIS are 
     encouraging.
  - [ ] Community building
 (baremaps) Calvin Kirs  
   - [ ]Comments: 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:

  - [ ] (livy) Bikas Saha  
     Comments:  
  - [ ] (livy) Luciano Resende  
     Comments:  
  - [ ] (livy) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (livy) Madhawa Kasun Gunasekara  
     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. Motivate growth in the community
  2. Address remaining items before graduation  

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

This is a project initiated from academia, and the major problem here is that many of us have graduated and moved on to something else now. Although the project itself is very promising and is a well-developed system (proved by a number of academic papers), the project is losing a bit of its momentum, and there isn't a clear breakpoint where this can get itself back on track in building its community and users. This project, I personally think, is an unlucky one in the sense that Covid-19 hit at the time when it was actively being promoted in ASF conferences and so, trying to build its user base, and hasn't been able to climb up to TLP since then. I think that there are enough resources for users to pick up on where it stands at the moment, but it is unclear on how it should get back on track, where the lack of community action being the major problem on its way to TLP. Any suggestions or help would be nice, but we may also consider archiving the project as well at this point.

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

We have 1 new contributor.

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

Discussions for community growth.

### 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
  - [x] Nearing graduation
  - [ ] Other:

### Date of last release:

  2022-09-02

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

September 28, 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 addressed.

Please refer to the issue raised above.

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

The PPMC manages the podling's brand / trademarks.

### Signed-off-by:

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

### 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. Growing the community, in particular the user interactions
  2. Growing the co....
  3. Gro....

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

### How has the community developed since the last report?
No material development since last report(baremaps) George Percivall  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     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. Focus on Contributors rather than primarily on Users (Docs for 
  processes)

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

  New PPMC, committers and contributors have emerged through the 0.8.0 
  release effort.
  Focus on security fixes and CI processes in github as well as reviews and 
  merges of contributions from other contributors have been most active.
  0.8.0 Release was security and bug fix oriented with CVEs and log4j being
  a lot of the recent work but with meaningful features as well.

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

  Apache Livy 0.8.0 was released and addressed the previously stated goals
  of security and log4j related fixes as well as numerous improvements and
  features from the community that were long awaited due to lack of community
  and recently added.

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

  - [X] Initial setup
  - [X] Working towards first release (with revitalized community)
  - [X] Community building
  - [ ] Nearing graduation
  - [X] Other: Nearing graduation in code stability but with a re-emerging 
  a dev community supporting it and working toward 0.8.0 release

### 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?
  No issues with mentors to report.

### Is the PPMC managing the podling's brand / trademarks?
  No issues to report.

  Signed-off-by:
  - [ ] (livy) Bikas Saha  
     Comments:
  - [ ] (livy) Luciano Resende  
     Comments:
  - [X] (livy) Jean-Baptiste Onofré  
     Comments: The activity has restarted, mostly maintenance. I think we 
     can have new features and improvements soon, helping to extend the
     community.
  - [ ] (livy) Madhawa Kasun Gunasekara  
     Comments:
  - [X] (livy) Larry McCay  
     Comments:
  - [ ] (livy) Sunil Govindan  
     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. Motivate growth in the community
  2. Address remaining items before graduation  

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

  This is a project initiated from academia, and the major problem here is
  that many of us have graduated and moved on to something else now. Although
  the project itself is very promising and is a well-developed system (proved
  by a number of academic papers), the project is losing a bit of its
  momentum, and there isn't a clear breakpoint where this can get itself back
  on track in building its community and users. This project, I personally
  think, is an unlucky one in the sense that Covid-19 hit at the time when it
  was actively being promoted in ASF conferences and so, trying to build its
  user base, and hasn't been able to climb up to TLP since then. I think that
  there are enough resources for users to pick up on where it stands at the
  moment, but it is unclear on how it should get back on track, where the
  lack of community action being the major problem on its way to TLP. Any
  suggestions or help would be nice, but we may also consider archiving the
  project as well at this point.

### How has the projectcommunity developed since the last report?
No
  We have 1 new developments. Stalled by lack of user engagementcontributor.

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

  Discussions for community growth.

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

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

### Date of last release:

    20192022-0409-2002

### When were the last committers or PPMC members elected?
Sean
 Palmer was elected committer on 2021-04-02
September 28, 2021

### Have your mentors been helpful and responsive?
Are
  thingsPlease fallingrefer throughto the cracks?issue If so, please list any
open issues that need to be addressedraised above.

No### mentorIs engagementthe thisPPMC quarter,managing thoughthe itpodling's hasbrand been very quiet, so no need./ trademarks?

### Is theThe PPMC managingmanages 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?

No issues here.

### Signed-off-by:

  - [ ] (ponymail) John D. Ament### Signed-off-by:

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

### IPMC/Shepherd notes:   

  - [ ] (nemo) Markus Weimer  
     Comments:  

### IPMC/Shepherd notes:

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

## ResilientDBPonyMail

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

ResilientDBmail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.

Pony Mail has been incubating since 20232016-1005-2127.

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

  1. TransferGrowing the codebasecommunity, to [Apache](https://issues.apache.org/jira/browse/INFRA-25211)in particular the user interactions
  2. GrowGrowing the community by facilitating more applications being built on ResDBco....
  3. Improve and extend documentation  Gro....

### Are there any issues that the IPMC or ASF Board need to be aware of? 
The current codebaseNone is still in GitHub and we have a few repositories rather than 
only one. We need some help to transfer these repositories to Apache.
  of note

### How has the community developed since the last report?
  No material development since last report.

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

Our community channelsNo onnew Discorddevelopments. areStalled activeby andlack manyof users are asking questions on 
how to develop their applications based on ResilientDB. We have a live testnet of 
ResilientDB been operational on 5 replicas/replicas for the past two months 
([ResDB explorer](https://explorer.resilientdb.com/)) utilized by over 100 students at both grad/undergrad levels. 
There have been exciting new projects developed over ResDB. We are expecting to 
launch/showcase these projects in the coming weeks (e.g., [Debitable](https://debitable.resilientdb.com/)).  

### How has the project developed since the last report?
The project is being processed on transferring. 
We also addressed the feedback from the users and improved our service. 
We had a new release last week (v1.9) that provided multi-version retrieval 
functionality to allow fetching the history of each key.


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

Please feel free to add your own commentary.

  - [X] Initial setupuser engagement.

### 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:    2019-04-20

### When were the last committers or PPMC members elected?
  Sean Palmer was elected committer on 2021-04-02

### Have your mentors been helpful and responsive?

  No mentor engagement this quarter, though it has been very quiet, so no
  need.

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

  No issues here.

### Signed-off-by:

  - [ ] Working(ponymail) towardsJohn first release
  - [X] Community buildingD. Ament  
  - [ ] Nearing graduation
  - [ ] Other: Comments:  

### Date of last release:

  2023-11-29

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

November of 2023

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

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

### 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:](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-215)  


### Signed-off-by:

  - [ ] (resilientdb) Junping Du   
     Comments:  
  - [ ] (resilientdb) Calvin Kirs  
     Comments:  
  - [ ] (resilientdb) Kevin Ratnasekera  
     Comments:  
  - [ ] (resilientdb) Roman Shaposhnik  
     Comments:  
  - [X] (resilientdb) Christian Grobmeier  
     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?


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. Transfer the codebase to 
  [Apache](https://issues.apache.org/jira/browse/INFRA-25211)
  2. Grow the community by facilitating more applications being built on 
  ResDB
  3. Improve and extend documentation  

### Are there any issues that the IPMC or ASF Board need to be aware of? 
  The current codebase is still in GitHub and we have a few repositories
  rather than
  only one. We need some help to transfer these repositories to Apache.

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

  Our community channels on Discord are active and many users are asking
  questions on
  how to develop their applications based on ResilientDB. We have a live
  testnet of
  ResilientDB been operational on 5 replicas/replicas for the past two months
  ([ResDB explorer](https://explorer.resilientdb.com/)) utilized by over 100
  students at both grad/undergrad levels.
  There have been exciting new projects developed over ResDB. We are
  expecting to
  launch/showcase these projects in the coming weeks (e.g.,
  [Debitable](https://debitable.resilientdb.com/)).

### How has the project developed since the last report?
  The project is being processed on transferring.
  We also addressed the feedback from the users and improved our service.
  We had a new release last week (v1.9) that provided multi-version retrieval
  functionality to allow fetching the history of each key.

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

  Please feel free to add your own commentary.

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

### Date of last release:

  XXXX2023-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:  11-29

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

  November of 2023

### Have your mentors been helpful and responsive?

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

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

  There are no known brand and naming issues as reported
  [here:](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-215)

### Signed-off-by:

  - [ ] (teaclaveresilientdb) FurkanJunping KamaciDu  
     Comments:  
  - [ X] (teaclaveresilientdb) JianyongCalvin DaiKirs  
     Comments:  
  - [ ] (teaclaveresilientdb) MattKevin SickerRatnasekera  
     Comments:  
  - [ ] (teaclaveresilientdb) ZhijieRoman ShenShaposhnik  
     Comments:  
  - [ X] (teaclaveresilientdb) GordonChristian KingGrobmeier  
     Comments:  

### IPMC/Shepherd notes:

[PJ] No podling report done since July. They have been requested to file one for the last number of months but have not done so. 


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

  Promote the project and grow the user and dev community.


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

  No.

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

  1. Regular meeting continues every two weeks.
  2. We're preparing a new post in our website.
  3. 6 new contributors


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

  1. We released 0.8.0.
  2. We have finished many exciting features such as the support of
  dashboard, dynamic allocation, etc.
  3. 106 pull requests are created, 91 pull requests are merged.
  4. 75 issues are created, 61 issues are closed

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

  2023-12-13, we released 0.8.0 version 

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

  
Chenyu Zheng, elected as the committer on 2023.11.04
  Junfan Zhang, elected as the PPMC on 2023.06.25


### Have your mentors been helpful and responsive?

  Yes, they'are helpful in guiding the podding project.

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

  Yes.

### Signed-off-by:

  - [ ] (uniffle) Felix Cheung  
     Comments:  
  - [ ] (uniffle) Junping Du  
     Comments:  
  - [ ] (uniffle) Liu Xun  
     Comments:  
  - [ ] (uniffle) Weiwei Yang  
     Comments:  
  - [ ] (uniffle) Zhankun Tang  
     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 has been incubating since 2020-12-16.

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

  1. Growing community
  2. New website (in progress)
  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? 

  Community has been growing. We received commits from multiple individuals
  and organizations. Also we have a new PPMC member.  

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

  We released Wayang 0.7.1. Next release 1.0.0 will have significant
  additions and code base restructuring.   

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

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

### Date of last release:

  2023-09-03

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

  2023-06-05

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



### Have your mentors been helpful and responsive?

  Yes, no problems.

### 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, no issues here.

### Signed-off-by:

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

### IPMC/Shepherd notes: