DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
DRAFT DRAFT DRAFTFINAL DO NOTEDIT
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 March 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: ### 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 March: ## IP Clearance ## Legal / Trademarks ## Infrastructure ## Miscellaneous ## Credits ## Table of Contents [Baremaps](#baremaps) [Gravitino](#gravitino) [ResilientDB](#resilientdb) [Iggy](#iggy) [KIE](#kie) [Nemo](#nemo) [OpenServerless](#openserverless) [Otava](#otava) [OzHera](#ozhera) [Polaris](#polaris) [PonyMail](#ponymail) [Teaclave](#teaclave) [Toree](#toree) [Training](#training) [Uniffle](#uniffleare currently 32 podlings incubating. In February, podlings executed four distinct releases, and one IP clearance occurred. Several incubating proposals have been discussed on the mailing list, and we have one podling called Iggy. No podlings have retired, but a couple are talking about it. Baremaps, Gravitin, Toree and Training are close to graduation. A few podlings failed to report and will be asked to report next month. Conversations on the list have been chiefly about releases. There was a conversation about performing trademark name searches early at the start of the incubator process to ensure that polling names are not rejected close to graduation. A few podlings needed to update their data files to indicate that they had graduated. There is ongoing discussion on several new potential incubating projects, and we have four proposals being worked on. ## Community ### New IPMC members: - None ### People who left the IPMC: - None ## New Podlings - Iggy ## Podlings that failed to report, expected next month - Iggy - Otava - PonyMail - Teaclave ## Graduations - Uniffle The board has motions for the following: - None ## Releases The following releases entered distribution during the month of March: - Baremaps 0.8.2 - Fury 0.10.0 - Polaris 0.9.0 - Wayang 1.0.0 ## IP Clearance - Cassandra Cluster Manager (CCM) ## Legal / Trademarks - N/A ## Infrastructure - N/A ## Table of Contents [Baremaps](#baremaps) [Cloudberry](#cloudberry) [Gravitino](#gravitino) [ResilientDB](#resilientdb) [KIE](#kie) [Nemo](#nemo) [OpenServerless](#openserverless) [OzHera](#ozhera) [Polaris](#polaris) [Teaclave](#teaclave) [Training](#training) [Wayang](#wayang) -------------------- ## 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? ### 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: 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? No. ### How has the community developed since the last report? Since the December release in 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 February release summarizes well the latest developments: https://github.com/apache/incubator-baremaps/releases/tag/v0.8.2 ### 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 - [ ] (baremaps) Bertrand Delacretaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [ ] (baremaps) Julian Hyde Comments: - [ ] (baremaps) Calvin Kirs Comments: Other: ### Date of last release: 2025-02-26 ### When were the last committers or PPMC members elected? Sébastien Riollet in June 2024. ### Have your mentors been helpful and responsive? Yes, the mentors are helpful. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (baremaps) GeorgeBertrand PercivallDelacretaz Comments: - [ ] (baremaps) Martin Desruisseaux 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.Preparing the new repo folowing ASF policy to be released. ### 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? 1. We are preparing a release for the Repo [ResVault](https://github.com/apache/incubator-resilientdb-resvault) and [ResilientDB-GraphQL](https://github.com/apache/incubator-resilientdb-graphql) which are built on ResilientDB platform to provide interfaces to access the blockchain system. 2. We developed new smart contract features within current version on ResilientDB platform. ### 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: 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: -------------------- ## 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: -------------------- ## Iggy Iggy is a high-performance, ultra-low latency and large-scale persistent message streaming platform written in Rust. Iggy has been incubating since 2025-02-04. ### Three most important unfinished issues to address before graduating: 1. 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: - [ ] (iggy) Hao Ding Comments: - [ ] (iggy) Yonik Seeley Comments: - [ ] (iggy) Zili Chen Comments: - [ ] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes: -------------------- ## KIE KIE (Knowledge is Everything) is a community of solutions and supporting tooling for knowledge engineering and process automation, focusing on events, rules, and workflows. KIE has been incubating since 2023-01-13. ### Three most important unfinished issues to address before graduating: 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? [X] (baremaps) Julian Hyde Comments: Project is indeed near graduation. I recommend that they start graduation discussions on dev@. My takeaway from the recent release is diversity of contributors; 12 issues fixed by 6 contributors is an indication that the project is becoming more broad-based. - [X] (baremaps) Calvin Kirs Comments: We're going to start assessing what still needs to be done before graduation. - [ ] (baremaps) George Percivall Comments: - [ ] (baremaps) Martin Desruisseaux Comments: ### IPMC/Shepherd notes: -------------------- ## Cloudberry Cloudberry is an advanced and mature open-source Massively Parallel Processing (MPP) database, derived from the open-source version of Pivotal Greenplum Database®️ but built on a more modern PostgreSQL 14 kernel, whereas Greenplum is based on PostgreSQL 12. This upgrade brings enhanced enterprise capabilities, making Cloudberry well-suited for data warehousing, large-scale analytics, and AI/ML workloads. Cloudberry has been incubating since 2024-10-11. ### Three most important unfinished issues to address before graduating: 1. Complete the source code cleanup to ensure ASF compliance. 2. Publish the first Apache release following ASF release processes. 3. Expand the contributor base and community engagement to ensure long-term sustainability. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? - Mailing List Activity: 63 messages on the Dev mailing list in Feb 2025, covering technical discussions and roadmap planning. - Slack Activity: 8 new threads on the `#general` channel, though no new users joined. - GitHub Discussions: 27 new discussions since Cloudberry entered incubation in October 2024, reflecting engagement on technical topics and project direction. - Outreach & Advocacy: - Promoted Cloudberry ecosystem updates (e.g., DBeaver and WAL-G support). - Encouraged community members to submit conference sessions. - Meetup: A Cloudberry Meetup hosted by HashData in Shanghai attracted 40+ attendees. - Recent Webinar: Apache Cloudberry™ (Incubating): The Latest Database for SQL at Scale - Event: Postgres World Webinar Series 2024 - Date: December 10, 2024 - Webinar Link: https://s.apache.org/slop6 - Upcoming Conference Talk: From Greenplum to Apache Cloudberry - Event: PostgresConf Global 2025 - Date: March 20, 2025, 10:30 EDT - Conference Link: https://s.apache.org/6ufdx ### How has the project developed since the last report? - Codebase Updates: - Integrated key contributions from the open-source Greenplum project while aligning them with Cloudberry’s roadmap. - Ongoing source code cleanup to ensure ASF compliance and prepare for the first official release. - Continuous Integration & Testing: - CI is now in place for the Rocky Linux 9 platform. - Testing has been extensively expanded since incubation, covering all PRs and main branch submissions. - GitHub Actions Workflows leverage automated builds for required resources (e.g., Docker containers). - The developer community has played a key role in shaping the CI and development processes, contributing feedback, enhancements, and best practices. - We have adopted an Infrastructure as Code (IaC) methodology to manage CI resources efficiently. - Potential Integration of Apache MADlib: - There has been discussion within the community about potentially incorporating Apache MADlib into Cloudberry. - Current interest appears to be low, but we will hold an official vote on this topic soon to determine the next steps. - Documentation Improvements: - Added and updated technical documentation to improve onboarding for new users and contributors. ### 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? No new committers or PPMC members have been elected yet. ### Have your mentors been helpful and responsive? Yes, a lot of help on the license. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (cloudberry) Roman Shaposhnik Comments: - [ ] (cloudberry) Willem Ning Jiang Comments: - [X] (cloudberry) Kent Yao Comments: LGTM ### IPMC/Shepherd notes: [PJF] Progress looks ok but there is still some missing data for the Incubator status https://incubator.apache.org/clutch/cloudberry.html -------------------- ### 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.Preparing the new repo folowing ASF policy to be released. ### 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? 1. We are preparing a release for the Repo [ResVault](https://github.com/apache/incubator-resilientdb-resvault) and [ResilientDB-GraphQL](https://github.com/apache/incubator-resilientdb-graphql) which are built on ResilientDB platform to provide interfaces to access the blockchain system. 2. We developed new smart contract features within current version on ResilientDB platform. ### 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: Apache XXXX-XX-XXResilientDB 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? 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? ### Signed-off-by: There are no known brand and naming issues as reported here. ### Signed-off-by: - [ ] (resilientdb) Junping Du Comments: - [ ] (resilientdb) Calvin Kirs Comments: - [ ] (kieresilientdb) BrianKevin ProffittRatnasekera Comments: - [ ] (kieresilientdb) ClausRoman IbsenShaposhnik Comments: - [ ] (kieresilientdb) AndreaChristian CosentinoGrobmeier Comments: ### IPMC/Shepherd notes: -------------------- ## NemoGravitino NemoGravitino 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? ### 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: high-performance, geo-distributed, and federated metadata lake 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. Fix all the potential license issues. 2. Release a version with non-WIP disclaimer. 3. Fill out the maturity model. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? 1. The Gravitino community added two new committers: Can Cai, Qian Xia. 2. The Gravitino community added two PPMC members: He Qi, Hui Yu. ### How has the project developed since the last report? 1. A new version 0.8.0-incubating has released. 2. Reaching to 153 commmitters and with 5+ commits per day. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] (nemo) Byung-Gon Chun Comments: Initial setup - [ ] Working towards first release - [ ] (nemo) Jean-Baptiste Onofré X] Community building - [X] Nearing graduation - [ ] CommentsOther: ### Date -of [ ] (nemo) Markus Weimer Comments: ### IPMC/Shepherd notes: [PJF] It is sad to say but this podling looks like it is moribund. There is no active traffic on the mailing lists and there was minimal reponse to a recent roll call (https://lists.apache.org/thread/5y2m4nglbh3qwgb7nkvqj6r4v4nx37rx) -------------------- ## 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: 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: - [ ] (openserverless) Bertrand Delacretaz Comments: - [ ] (openserverless) Enrico Olivelli Comments: - [ ] (openserverless) François Papon Comments: - [ ] (openserverless) JB Onofré Comments: - [ ] (openserverless) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## Otava Otava, a command-line tool, written in Python, that detects statistically significant changes in time-series data stored either in databases or CSV files. Otava entered Incubation as Hunter Otava has been incubating since 2024-11-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: - [ ] (otava) Dave Fisher Comments: - [ ] (otava) Enrico Olivelli Comments: - [ ] (otava) Lari Hotari Comments: last release: 2025-01-24 ### When were the last committers or PPMC members elected? 2025-03-13 ### Have your mentors been helpful and responsive? The mentors are helpful, and there are no special issues that need to be addressed. ### Is the PPMC managing the podling's brand / trademarks? Yes, there's no branding issue, and 3rd parties use the name and brand correctly. ### Signed-off-by: - [ ] (gravitino) Daniel Dai Comments: - [ ] (gravitino) Junping Du Comments: - [X] (gravitino) Justin McLean Comments: - [ ] (gravitino) Shaofeng Shi Comments: - [ ] (gravitino) Larry McCay Comments: - [X] (gravitino) Jean-Baptiste Onofré 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. We wrote a report last month, nothing has changed. ### Three most important unfinished issues to address before graduating: 1. Build the community 2. Make sure sure our dependencies are in compliance 3. More releases ### 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? No change since last month ### How has the project developed since the last report? No meaningful changes since last month ### 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-12-11 ### When were the last committers or PPMC members elected? A couple of months back. ### Have your mentors been helpful and responsive? Pretty good so far. ### Is the PPMC managing the podling's brand / trademarks? N/A ### 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: 1. Remove the dependency on REEF 2. Revitalize the community 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? - There is no activity in the community. ### How has the community developed since the last report? - There has been no notable activity since the last report. ### How has the project developed since the last report? - There has been no notable activity 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 - [X] Other: ### Date of last release: 2022-09-22 ### When were the last committers or PPMC members elected? September 28, 2021 ### Have your mentors been helpful and responsive? N/A ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (otavanemo) MickHyunsik Semb WeverChoi 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. 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: - [ ] (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. Prepare 1.0.0 release including binary distribution 2. Grow the community ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? Regarding the users community: - on Slack (#general channel), in February, we had questions from 11 new users, evaluating Polaris. These users are not active on the dev mailing list (only Slack). - on GitHub Issues, in February, we had 2 new issues created by non committers users, and non affiliated to initial committed companies. Some users are the same active on Slack (for instance https://github.com/apache/polaris/issues/996) Regarding the contributors community: - in February, we had 7 PRs from 5 new contributors (individual contributors, not affiliated to companies already active in Polaris) - in February, we had several GitHub issues and PRs created by 3 new contributors from Snowflake and a new contributor from Dremio. In February, we had several Community Meetings (recorded and shared on the dev mailing list and website): - 2 Polaris Community Meetings - Discussion about the Policy Management proposal - Discussion about Polaris Persistence improvement proposal On these meetings, we were pleased to see several new people (around 15 people show up for the first time in February). We continue to promote Polaris in order to grow our community. We strongly believe 1.0.0 release (with the binary distributions) will help to grow even faster our community. ### How has the project developed since the last report? 0.9.0 have been released. This release is the first one on the project, only including source distribution. We are now working on 1.0.0 release that will include binary distributions. We published a roadmap proposal (https://github.com/apache/polaris/discussions/1028), and we added a 1.0-blocker label on GH Issues. In February, we had 3 new proposals in discussion (relayed on the dev mailing list): - Persistence layer improvement (https://github.com/apache/polaris/issues/985) - Policy Management (https://github.com/apache/polaris/issues/999) - Generic Table Support (https://github.com/apache/polaris/issues/1048) We are now focusing on 1.0.0 preparation, including fixes and the persistence layer improvement. ### 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: 2025-02-25 ### When were the last committers or PPMC members elected? Last committer: Dennis Huo and Dmitri Bourlatchkov elected on 2024-12-23 ### Have your mentors been helpful and responsive? Yes, helpful in release and report review. ### Is the PPMC managing the podling's brand / trademarks? Polaris PPMC is working with 3rd parties willing to use Polaris brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html. ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [ ] (polaris) Kent Yao Comments: - [ ] (polaris) Ryan Blue Comments: - [X] (polaris) JB Onofre Comments: I'm looking forward 1.0.0 release ! ### IPMC/Shepherd notes: -------------------- ## PonyMail Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms. Pony Mail has been incubating since 2016-05-27. ### Three most important unfinished issues to address before graduating: 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: -------------------- ## 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? [X] (nemo) Byung-Gon Chun Comments: - [X] (nemo) Jean-Baptiste Onofré Comments: Following the roll call, I think we should consider retirement. - [ ] (nemo) Markus Weimer Comments: ### IPMC/Shepherd notes: [PJF] It is sad to say but this podling looks like it is moribund. There is no active traffic on the mailing lists and there only a small response to a recent roll call (https://lists.apache.org/thread/5y2m4nglbh3qwgb7nkvqj6r4v4nx37rx) [JBO] Agree with PJ, according to the roll call, we should consider retirement. -------------------- ## 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: 1. Community Building 2. Continue the process of align documentation, since there are still several parts that neeed a review. 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? 1. The Apache OpenServerless and AI course - currently in Italian - is underway: it has involved many people and is a model to be proposed also in English with respect to a larger community. 2. We're evaluating sessions to support those who need it in the installation of the development environment. 3. Finally, we are trying to involve people in the development by proposing them to take charge of some open tasks on GitHub. ### How has the project developed since the last report? 1. Closed 8 issues. Opened 3 new issues. 2. We improved the Kubernetes operator, further optimizing the image size and introducing some new features. 3. Introduced some new features also in the openserverless-task project. 4. We improved the stability of the functions that affect the Apache OpenServerlesss IDE ### 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: None ### 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: Good progress! We should promote OpenServerless more to grow the community. - [X] (openserverless) PJ Fanning Comments: Steady progress ### 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? Solved the existing problem of the website not complying with the ASF standard. Merged 24 PRs. ### How has the project developed since the last report? Complete the version release revision work and initiate the version release voting process. Completed log parsing related optimization. ### 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: There is no apache release yet. ### When were the last committers or PPMC members elected? 2025-01-13. ### 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. Prepare 1.0.0 release including binary distribution 2. Grow the community ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? Regarding the users community: - on Slack (#general channel), in February, we had questions from 11 new users, evaluating Polaris. These users are not active on the dev mailing list (only Slack). - on GitHub Issues, in February, we had 2 new issues created by non committers users, and non affiliated to initial committed companies. Some users are the same active on Slack (for instance https://github.com/apache/polaris/issues/996) Regarding the contributors community: - in February, we had 7 PRs from 5 new contributors (individual contributors, not affiliated to companies already active in Polaris) - in February, we had several GitHub issues and PRs created by 3 new contributors from Snowflake and a new contributor from Dremio. In February, we had several Community Meetings (recorded and shared on the dev mailing list and website): - 2 Polaris Community Meetings - Discussion about the Policy Management proposal - Discussion about Polaris Persistence improvement proposal On these meetings, we were pleased to see several new people (around 15 people show up for the first time in February). We continue to promote Polaris in order to grow our community. We strongly believe 1.0.0 release (with the binary distributions) will help to grow even faster our community. ### How has the project developed since the last report? 0.9.0 has been released. This release is the first one on the project, only including source distribution. We are now working on 1.0.0 release that will include binary distributions. We published a roadmap proposal (https://github.com/apache/polaris/discussions/1028), and we added a 1.0-blocker label on GH Issues. In February, we had 3 new proposals in discussion (relayed on the dev mailing list): - Persistence layer improvement (https://github.com/apache/polaris/issues/985) - Policy Management (https://github.com/apache/polaris/issues/999) - Generic Table Support (https://github.com/apache/polaris/issues/1048) We are now focusing on 1.0.0 preparation, including fixes and the persistence layer improvement. ### 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: XXXX2025-XX02-XX25 ### When were the last committers or PPMC members elected? Last committer: Dennis Huo and Dmitri Bourlatchkov elected on 2024-12-23 ### 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, helpful in release and report review. ### 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: Polaris PPMC is working with 3rd parties willing to use Polaris brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html. ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [ ] (toreepolaris) LucianoKent ResendeYao Comments: - [ X] (toreepolaris) Ryan Blue Comments: Comments: I think "working towards first release" can be unchecked. Thanks for the additional detail on community growth! - [ X] (toreepolaris) WeiweiJB YangOnofre Comments: I'm looking forward 1.0.0 release ! ### IPMC/Shepherd notes: -------------------- ## TrainingToree TheToree Trainingprovides projectapplications aimswith toa developmechanism resources which can be used for training purposes in various media formats, languagesto interactively and for various Apache and non-Apache target projectsremotely access Apache Spark. TrainingToree has been incubating since 20192015-12-02-21. ### Three most important unfinished issues to address before graduating: 1. Increase 2. 3.active contributors ### 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? Slow activity with discussions about 0.6 release before incorporating Scala 2.13 support ### How has the project developed since the last report? Few prs around Scala 2.13 and other small enhancements Updates to remove Google Analytics from website ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ X] Nearing graduation - [ ] Other: ### Date of last release: XXXX2022-XX04-XX11 ### When were the last committers or last committers or PPMC members elected? - Cheng Pan was added to the PPMC members elected? on 2023-08-28 ### 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? None ### Is the PPMC managing the podling's brand / trademarks? No trademark issues ### Signed-off-by: - [X] (toree) Luciano Resende Comments: The podling should push for release and start graduation process - [ ] (toree) Ryan Blue Comments: - [ ] (toree) Weiwei Yang Comments: ### IPMC/Shepherd notes: -------------------- ## 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: 1. Name clearance 2. n/a 3. n/a ### 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? One new contributor in the past quarter. ### How has the project developed since the last report? We are working with several projects to improve, or create, their sample training decks. A new contributor is working on github actions to automatically build content to lower the barrier to entry. The podling is discussing graduation. ### 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: 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: Date of last release: 2024/04 ### When were the last committers or PPMC members elected? August 2024 ### Have your mentors been helpful and responsive? Mentors have been helpful in discussions. ### Is the PPMC managing the podling's brand / trademarks? Attempting to start a name search. ### Signed-off-by: - [ ] (uniffletraining) JunpingCraig DuRussell Comments: - [ ] (uniffletraining) LiuChristofer XunDutz Comments: - [ X] (uniffletraining) WeiweiJustin YangMclean Comments: - [ ] (uniffletraining) ZhankunLars TangFrancke Comments: ### IPMC/Shepherd notes: -------------------- ## Wayang Apache Wayang is a layered ML framework that connects your applications to various data processing platforms, automatically translating your requests into a common format and optimizing tasks for each platform. Its flexible design also makes it easy to add new features or support additional technologies dynamically. 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? Slowly growing ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Structure setup, voting established - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2025-09-02 ### When were the last committers or PPMC members elected? 20242024-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, and approved. ### Signed-off-by: - [ ] (wayang) Christofer Dutz Comments: - [ ] (wayang) Lars George Comments: - [ ] (wayang) Bernd Fondermann Comments: - [ X] (wayang) Jean-Baptiste Onofré Comments: I don't think Wayang is in initial setup phase. I would say more community building. ### IPMC/Shepherd notes: |