You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

DRAFT DRAFT DRAFT

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

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

It also best to:

  • Do not change existing formatting. Especially do not change the formatting of the sign-off area.
  • Keep all lines under 76 characters long.

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

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

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

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

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


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


Timeline

Wed February 05Podling reports due by end of day
Sun February 09Shepherd reviews due by end of day
Sun February 09Summary due by end of day
Tue February 11Mentor signoff due by end of day
Wed February 12

Report submitted to Board

Wed February 19Board meeting


Shepherd Assignments

Calvin KirsNemo
Calvin KirsTeaclave
Calvin KirsXTable
Dave FisherOpenServerless
Dave FisherPony Mail
Drew FarrisGraphAr
Drew FarrisResilientDB
Justin McleanKIE
P. Taylor GoetzSeata
P. Taylor GoetzTraining
PJ Fanning StreamPark
PJ Fanning Toree
PJ Fanning Wayang
Timothy ChenDevLake
Timothy ChenHertzBeat
Timothy ChenUniffle
Willem JiangGravitino
Willem JiangHoraeDB
Willem JiangOzHera
Hao DingFury
Hao DingPolaris



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.

TODO 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
  • XTable 0.2.0

Oct 2024:

  • Hertzbeat 0.6.1
  • Gravitino 0.6.1
  • StreamPark 2.1.5
  • Fury 0.8.0

IP Clearance

Infrastructure

Miscellaneous

Credits

Table of Contents

Baremaps
DevLake
Fury
GraphAr
Gravitino
HertzBeat
HoraeDB
KIE
Nemo
NLPCraft
OpenServerless
OzHera
Polaris
Pony Mail
ResilientDB
Seata
StormCrawler
Teaclave
Toree
Training
Uniffle
Wayang
XTable
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 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.

  •  Initial setup
  •  Working towards first release
  •  Community building
  •  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:
  •  (baremaps) Calvin Kirs
    Comments:
  •  (baremaps) George Percivall
    Comments:
  •  (baremaps) Martin Desruisseaux
    Comments:

IPMC/Shepherd notes:


DevLake

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

DevLake has been incubating since 2022-04-29.

Three most important unfinished issues to address before graduating:

  1. Grow the community and attract more users.
  2. Add more committers and PPMC members.
  3. Grow the project, support more data sources and use cases, and improve the user experience.  

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

We would like to seek guidance regarding the graduation of DevLake. Please let us know what we should do step by step. Thank you.  

How has the community developed since the last report?

  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.

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

Date of last release:

2024-9-23

When were the last committers or PPMC members elected?

2024-12-7

Have your mentors been helpful and responsive?

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

Yes, the mentors helped tremendously throughout 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:

  •  (devlake) Felix Cheung
    Comments:
  •  (devlake) Liang Zhang
    Comments:
  •  (devlake) Lidong Dai
    Comments:
  •  (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
  •  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:
  •  (fury) PJ Fanning
    Comments: Steady Progress
  •  (fury) Yu Li
    Comments:
  •  (fury) Xin Wang
    Comments:
  •  (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.

  •  Initial setup
  •  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:

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:

2025-01-26 (v0.8.0)

When were the last committers or PPMC members elected?

2024-12-2

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: Waiting the first sections to review.

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:

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:

  •  (hertzbeat) Yonglun Zhang
    Comments:
  •  (hertzbeat) Yu Xiao
    Comments:
  •  (hertzbeat) Justn Mclean
    Comments:
  •  (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. Release more version
  2. Grow community(attract more users/committers)
  3. Finish the new metrics engine

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

No

How has the community developed since the last report?

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.

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

Date of last release:

2024-12-10

When were the last committers or PPMC members elected?

  • Neo Chen, at 2024-12-25

Have your mentors been helpful and responsive?

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

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

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:

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

  •  Initial setup
  •  Working towards first release
  •  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:

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

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:

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

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 project developed since the last report?

  • Examples extended.
  • 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.

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

Date of last release:

2023-02-30

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 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 Ye
    Comments:
  •  (nlpcraft) Paul King
    Comments:
  •  (nlpcraft) Konstantin I Boudnik
    Comments:

IPMC/Shepherd notes:


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-06-17.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

  •  (openserverless) Bertrand Delacretaz
    Comments:
  •  (openserverless) Enrico Olivelli
    Comments:
  •  (openserverless) François Papon
    Comments:
  •  (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 has been incubating since 2024-07-11.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

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
  •  Working towards first release
  •  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:
  •  (polaris) Holden Karau
    Comments:
  •  (polaris) Kent Yao
    Comments:
  •  (polaris) Ryan Blue
    Comments:
  •  (polaris) JB Onofre
    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:

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.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:    

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

When were the last committers or PPMC members elected?

November of 2023

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:


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:

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

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2024-12-03

When were the last committers or PPMC members elected?

2024-09-21

Have your mentors been helpful and responsive?

Nothing of note.

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

The name was approved by VP, Brand after consulting the Apache Storm project.

Signed-off-by:

  •  (stormcrawler) Dave Fisher
    Comments: The podling knows that community growth is required.
  •  (stormcrawler) Lewis John McGibbney
    Comments:
  •  (stormcrawler) Ayush Saxena
    Comments:
  •  (stormcrawler) PJ Fanning
    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:

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:

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:

  •  (toree) Luciano Resende
    Comments:
  •  (toree) Ryan Blue
    Comments:
  •  (toree) Weiwei Yang
    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.


Training

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

Training has been incubating since 2019-02-21.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

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:

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

Stagnate

How has the project developed since the last report?

Slow progress

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:    

2023-09-20  

When were the last committers or PPMC members elected?

2024-09-16

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.

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 approved the project name?

Yes, approved.

Signed-off-by:

  •  (wayang) Christofer Dutz
    Comments:
  •  (wayang) Lars George
    Comments:
  •  (wayang) Bernd Fondermann
    Comments:
  •  (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.

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

Date of last release:

Nov 8, 2024

When were the last committers or PPMC members elected?

Feb 2024

Have your mentors been helpful and responsive?

Yes, our mentors have been 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 and the proposal for the new name 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).
  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.

IPMC/Shepherd notes:



  • No labels