DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
DRAFT DRAFT DRAFTFINAL DO NOT EDIT
NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.
...
| Markdown |
|---|
# Incubator PMC report for June 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 May: ## IP Clearance ## Legal / Trademarks ## Infrastructure ## Miscellaneous ## Credits ## Table of Contents [Annotator](#annotator) [Baremaps](#baremaps) [BifroMQ](#bifromq) [Grails](#grails) [Hamilton](#hamilton) [Iggy](#iggy) [KIE](#kie) [Nemo](#nemo) [NLPCraft](#nlpcraft) [OpenServerless](#openserverless) [Otava](#otava) [OzHera](#ozhera) [Polaris](#polaris) [PonyMail](#ponymail) [PouchDB](#pouchdb) [Teaclave](#teaclave) [Texera](#texera) [Training](#training) [Wayang](#wayang) -------------------- ## Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator has been incubating since 2016-08-30. ### Three most important unfinished issues to address before graduating: 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: - [ ] (annotator) Nick Kew Comments: - [ ] (annotator) Tommaso Teofili Comments: - [ ] (annotator) Benjamin Young Comments: ### IPMC/Shepherd notes: are currently 35 podlings incubating. In May, podlings executed six distinct releases, and two IP clearances occurred. Several incubating proposals have been discussed and are presently undergoing voting on the mailing list (GeaFlowa and Fluss), and a new project Caldera, is being discussed. We also have one new podling called Burr, and two projects, Gravitinto and StormCrawler graduated last month. One person was added to the IPMC. No podlings have retired, but a couple are still talking about it. Five podlings failed to report and will be asked to report next month. Conversations on the list have been focused on releases, new incubating projects, and the incubation process. Tracking projects that have been incubating for a long time, Annotator is discussing retirement, Nemo is votng for it, and Toree is slowly moving towards graduation. The Livy PPMC has been slow to respond, and there is a roll call to see if they have an active PMC. NLPCraft did report this month, but the roll call sent a month ago has received two responses. Training is ready to graduate. Finally, note that last month’s incubator report was submitted on time but did not receive sufficient Director sign-offs. It is available here: https://whimsy.apache.org/board/agenda/2025-05-21/flagged/Incubator ## Community ### New IPMC members: - Nicholas Jiang ### People who left the IPMC: - None ## New Podlings - Burr ## Podlings that failed to report, expected next month - Annotator - Grails - Iggy - KIE - PonyMail ## Graduations - Gravitino - StormCrawler The board has motions for the following: - None ## Releases The following releases entered distribution during the month of May: - Amoro 0.8.0 - Fury 0.10.2 - Fury 0.10.3 - Gravitino 0.8.1 - Gravitino 0.9.0 - Hertzbeat 1.7.1 ## IP Clearance - Arrow Flight SQL ODBC Driver - easy-cass-stress ## Legal / Trademarks - N/A ## Infrastructure - N/A ## Table of Contents [Baremaps](#baremaps) [BifroMQ](#bifromq) [Hamilton](#hamilton) [Nemo](#nemo) [NLPCraft](#nlpcraft) [OpenServerless](#openserverless) [Otava](#otava) [OzHera](#ozhera) [Polaris](#polaris) [PouchDB](#pouchdb) [Teaclave](#teaclave) [Texera](#texera) [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. Expanding the community 2. Making releases 3. Starting the graduation process ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? ### How There has thebeen projectan developeduptick sincein theactivity 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: - [ ] (baremaps) Bertrand Delacretaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [ ] (baremaps) Julian Hyde Comments: early this year, which has since slowed down. One difficulty we face is related to the onboarding and retention of new contributors. We have a number of easy bug fixes that are suitable for newcomers, but we also have advanced features that require a deeper understanding of the codebase. This can be intimidating for new contributors, leading to a lack of engagement after initial contributions. ### How has the project developed since the last report? We released version 0.8.2 in February 2025. Since then, we have added support for Apache Calcite, which will open the door to spatial SQL queries on various data sources (flatgeobuf, PostGIS, geopackage, geoparquet, etc.). We also fixed a number of bugs and upgraded dependencies. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] (baremaps) Calvin Kirs Comments: - [ ] (baremaps) George Percivall Comments: - [ ] (baremaps) Martin Desruisseaux Comments: ### IPMC/Shepherd notes: -------------------- ## BifroMQ BifroMQ is a Java-based, high-performance, distributed MQTT broker with native multi-tenancy support, designed for large-scale connections and message delivery. BifroMQ has been incubating since 2025-04-22. ### Three most important unfinished issues to address before graduating: 1. 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: - [ ] (bifromq) Christofer Dutz Comments: - [ ] (bifromq) Xiangdong Huang Comments: - [ ] (bifromq) Calvin Kirs Comments: - [ ] (bifromq) Penghui Li Comments: - [ ] (bifromq) Sheng Wu Comments: ### IPMC/Shepherd notes: -------------------- ## Grails A powerful Groovy-based web application framework for the JVM built on top of Spring Boot Grails has been incubating since 2025-01-25. ### Three most important unfinished issues to address before graduating: 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 Other: ### Date of last release: 2025-02-07 ### When were the last committers or PPMC members elected? Sébastien Riollet in June 2024 ### Have your mentors been helpful and responsive? Yes, Julian Hyde and Calvin Kirs provided valuable feedback. ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (baremaps) Bertrand Delacretaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [ ] (baremaps) Julian Hyde Comments: - [X] (baremaps) Calvin Kirs Comments: - [ ] (baremaps) George Percivall Comments: - [ ] (baremaps) Martin Desruisseaux Comments: ### IPMC/Shepherd notes: PJF: The BareMaps active community remains small. Possibly, too small to be be able to become a self-managing PMC on graduation. JM: They have added 3 committers. I would suggest they look to see if any of those or any other committers can be made PPMC members. -------------------- ## BifroMQ BifroMQ is a Java-based, high-performance, distributed MQTT broker with native multi-tenancy support, designed for large-scale connections and message delivery. BifroMQ has been incubating since 2025-04-22. ### Three most important unfinished issues to address before graduating: 1. Successful repository migration and completion of the first release process 2. Website building and grow the community 3. Complete the Trademark Assignment process ### Are there any issues that the IPMC or ASF Board need to be aware of? Baidu manages the SGA, CCLA, and Trademark Assignment as a unified "Corporate Contract" workflow. The SGA and CCLA documents have been successfully submitted to the ASF. We are eager to advance the Trademark Assignment process to finalize the Corporate Contract workflow, rather than delaying it until graduation from the incubator. ### How has the community developed since the last report? - Added 2 contributors since incubation began ### How has the project developed since the last report? - Two repositories have been transferred to the Apache GitHub organization (apache/bifromq, apache/bifromq-sites). ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ X] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: XXXX2025-XX02-XX25 ### When were the last committers or PPMC members elected? None since joining the incubator ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so Yes, pleasewe listget any openhelpful issuesand thattimely needguidance tofrom bethe addressed.mentors ### Is the PPMC managing the podling's brand / trademarks? Are 3rdYes, partiesThe respectingname and'BifroMQ' correctlyhas usingpassed the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? search: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-237 ### Signed-off-by: - [ ] (grailsbifromq) PaulChristofer KingDutz Comments: - [ ] (grailsbifromq) SoerenXiangdong GlasiusHuang Comments: ### IPMC/Shepherd notes: -------------------- ## Hamilton Hamilton is a lightweight in-process framework to define, execute, and observe directed acyclic graphs (DAGs) that express data transformations. In Hamilton one can express complex DAGs of transformations, e.g. from dataframe transformations (using pandas, polars, PySpark), machine learning pipelines, through to regular software engineering API request and LLM API based workflows. Observability hooks are built into the framework. The Hamilton UI [X] (bifromq) Calvin Kirs Comments: Progress is going well. - [ ] (bifromq) Penghui Li Comments: - [ ] (bifromq) Sheng Wu Comments: ### IPMC/Shepherd notes: -------------------- ## Hamilton Hamilton is a lightweight in-process framework to define, execute, and observe directed acyclic graphs (DAGs) that express data transformations. In Hamilton one can express complex DAGs of transformations, e.g. from dataframe transformations (using pandas, polars, PySpark), machine learning pipelines, through to regular software engineering API request and LLM API based workflows. Observability hooks are built into the framework. The Hamilton UI is a self- hostable service to captureobservability output from workflow runs. Apache Software Foundation incubation will establish Hamilton as a community-driven standard. Hamilton has been incubating since 2025-04-12. ### Three most important unfinished issues to address before graduating: 1. Finish repo setup. 2. Go through first release process. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? N/A ### How has the project developed since the last report? N/A ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: No apache release yet. ### When were the last committers or PPMC members elected? 2025-04-12 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressedNo answer. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand?Name If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?is approved: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-235 ### Signed-off-by: - [ ] (hamilton) Kevin Ratnasekera Comments: - [X] (hamilton) Ayush Saxena Comments: In the initial stage: setting up resource & gearing up for the first ASF release - [ X] (hamilton) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## IggyNemo IggyNemo is a high-performance, ultra-low latency and large-scale persistent message streaming platform written in Rust. Iggydata processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics. Nemo has been incubating since 20252018-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? ### How - There has been theno projectnotable developedactivity since the last report? . ### How has the wouldproject youdeveloped assesssince the podling'slast maturityreport? Please feel free- toThere addhas yourbeen own 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: XXXX2022-XX09-XX22 ### When were the last committers or PPMC members elected? September 28, 2021 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. N/A ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? ### Signed-off-by: Yes ### Signed-off-by: - [ ] (nemo) Hyunsik Choi Comments: - [ X] (iggynemo) HaoByung-Gon DingChun Comments: The podling is -considering [retirement. ] (iggy) Yonik Seeley Comments: - [ X] (iggynemo) ZiliJean-Baptiste ChenOnofré Comments: The podling is retired. - [ ] (iggynemo) HulkMarkus LinWeimer Comments: ### IPMC/Shepherd notes: --- CalvinKirs[kirs]: The podling is considering retirement. JM: There is a vote underway to retire the project. -------------------- ## KIENLPCraft KIEA (Knowledge is Everything) is a community of solutions and supporting toolingScala library for knowledge engineering and process automation, focusing on events, rules, and workflows. KIENLU applications NLPCraft has been incubating since 20232020-0102-13. ### Three most important unfinished issues to address before graduating: 1. Take 2. a clear 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? niche in NLP development by focusing on supporting deterministic functions and their advantages over the LLM-based approach in some application domains. 2. Extending the technology stack 3. Community growth. ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the projectcommunity developed since the last report? ### How would- youWe assesscontinue theinvestigating podling's maturity? Please feel free to add your own commentary. LLM integration and experimenting with the MCP approach. - [We ]continue 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?research mini-projects 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? - Technical PRs processed. - Research and investigation tasks related to sLLMs and MCP approach. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2023-02-30 ### When were the last committers or PPMC members elected? August of 2021. ### Have your mentors been helpful and responsive? No Answer. ### Is the PPMC managing the podling's brand / trademarks? No Answer. ### Signed-off-by: - [X] (nlpcraft) Furkan Kamaci Comments: - [ ] (kienlpcraft) BrianEvans ProffittYe Comments: - [ ] (kienlpcraft) ClausPaul IbsenKing Comments: - [ ] (kienlpcraft) Konstantin AndreaI CosentinoBoudnik Comments: ### IPMC/Shepherd notes: -------------------- ## Nemo Nemo is a data processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics. Nemo has been incubating since 2018-02-04. ### Three most important unfinished issues to address before graduating: 1. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? ### How has the community developed since the last report? ### How has the project developed since the last report? ### 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. Take a clear niche in NLP development by focusing on supporting deterministic functions and their advantages over the LLM-based approach in some application domains. 2. Extending the technology stack 3. Community growth. ### 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 continue investigating LLM integration and experimenting with the MCP approach. - We continue research mini-projects 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? - Technical PRs processed. - Research and investigation tasks related to sLLMs and MCP approach PJF: The NLPCraft active community is quite small. Possibly, too small to be able to operate as a self-managing PMC on graduation. JM: The recent roll call got one person who wants to continue development and one who wants to continue mentoring. A dev list email on next steps got no responses. The IPMC may have to consider retiring the project. -------------------- ## 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. Strengthen the community 2. Assess the requirements for the First Release 3. continue the process of documenting the entire platform. ### 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 - was completed by at least a couple hundred developers and some of them are using actively the platform. 2. The AI course is being extended to support also MCP api. 3. Two new contributors joined the projects. 4. We're in the process of release some videos to show installation on local machines and cloud servers. 5. We've published an article on the [Opensource.net](https://opensource.net/apache-openserverless-is-the-easiest -way-to-build-your-cloud-native-ai-application/) blog. ### How has the project developed since the last report? 1. We improved various parts of the project, fixing bugs and reviewed the documentation. 2. Closed 19 issues. Opened 6 new issues. 3. Improved the OpenServerless streamer (openserverless-streamer), introducing new code and documentation. 4. Preparing an upgrade to OpenWhisk 2. 5. We have opened a new PR towards the Apache OpenWhisk project to support JDK17 based builds. 6. We have added a new openserverless-build project with the objective of preparare OpenWhisk 2 multiplatform images tailor made for our project and we aim to provide a native executable for the standalone component, with the objective of providing a lighter development environment. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X ] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2023-02-30None ### When were the last committers or PPMC members elected? August of 2021.2024-08-22 ### Have your mentors been helpful and responsive? Are things fallingYes, through the cracks? If so, please list any open issues that need to be addressedand 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? 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? https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved ### Signed-off-by: - [ ] (nlpcraftopenserverless) FurkanBertrand KamaciDelacretaz Comments: - [ ] (nlpcraftopenserverless) EvansEnrico YeOlivelli Comments: - [ ] (nlpcraftopenserverless) PaulFrançois KingPapon Comments: - [X] (openserverless) JB Onofré Comments: - [X] (nlpcraftopenserverless) KonstantinPJ I BoudnikFanning Comments: ### IPMC/Shepherd notes: -------------------- ## OpenServerlessOtava OpenServerless Apache isOtava an(incubating) openperforms 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. Strengthen the community 2. Assess the requirements for the First Release 3. continue the process of documenting the entire platform. ### 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 - it is being extended to support also MCP api. 2. Two new contributors joined the projects ### How has the project developed since the last report? 1. We improved various parts of the project, fixing bugs and reviewed the documentation. 2. We have opened a new PR towards the Apache OpenWhisk project to support JDK17 based builds. 3. We have added a new openserverless-build project with the objective of preparare OpenWhisk 2 multiplatform images tailor made for our project and we aim to provide a native executable for the standalone component, with the objective of providing a lighter development environment. ### 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: statistical analysis of performance test results stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It finds change-points and notifies about possible performance regressions. A typical use-case of otava is as follows: * A set of performance tests is scheduled repeatedly, such as after each commit is pushed. * The resulting metrics of the test runs are stored in a time series database (Graphite) or appended to CSV files. * Otava is launched by a Jenkins/Cron job (or an operator) to analyze the recorded metrics regularly. * Otava notifies about significant changes in recorded metrics by outputting text reports or sending Slack notifications. * Otava is capable of finding even small, but persistent shifts in metric values, despite noise in data. It adapts automatically to the level of noise in data and tries to notify only about persistent, statistically significant changes, be it in the system under test or in the environment. * Otava has been incubating since 2024-11-27. Otava entered Incubation as Hunter. The project name Otava was approved by VP Brand 2025-02-09. ### Three most important unfinished issues to address before graduating: 1. Publish the first release under the new name. ( htts://s.apache.org/ahsxx) We are still iterating on getting Incubator PMC passed. 2. Publish the existence of Apache Otava (Incubating), and our first release. 3. ??? ### How has the community developed since the last report? Unchanged. Everone is now waiting for the first release. Henrik participated in International Conference on Performance Engineering 2025 and gave a short presentation on the 8 year history of Otava. (The talk had initially been proposed to the conference before we became and Apache incubating project. We learned of some users that we weren't previously aware of. Most notably Red Hat uses Otava (née Hunter) to analyze performance test results from OpenShift. ### How has the project developed since the last report? We are focused on making our first release. ### How would you assess the podling's maturity? - [X] Initial setup - [X] Working towards first release - [ ] (openserverless) François Papon Comments: Community building - [ ] Nearing graduation - [ X] (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: Other: A self review based on https://s.apache.org/727vc * Code 3/5 * Licenses and Copyright: 5/5 * Releases: 4/5 * Quality: 5/5 * Community: 7/7 * Consensus: 4/5 (Missing: CS10) * Independence: 2/2 * Brand: 4/4 The first release was happening as this report was submitted ### Date of last release: We are actively working on our first release, trying to get all the details of the release process right. ### When were the last committers or PPMC members elected? The major contributors during the past 8 years were listed as PPMC members in the project application pase. We have not elected any new members after that. ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? This isn't yet an issue, as the new name of the project is quite unknown yet. ### Signed-off-by: - [ ] (otava) Dave Fisher Comments: - [ ] (otava) Enrico Olivelli Comments: - [ ] (otava) Lari Hotari Comments: - [ ] (otava) Mick DaveSemb FisherWever Comments: ### - [ ] (otava) Enrico Olivelli Comments: - [ ] (otava) Lari Hotari Comments: - [ ] (otava) Mick Semb Wever Comments: ### IPMC/Shepherd notes: IPMC/Shepherd notes: JM: Thanks for the detailed report and the maturity model self-review. -------------------- ## 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.Make more apache release. 2.Build and grow community. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? 1.Collectively discuss plans for community promotion and development. 2.Actively participate in community activities and seek development channels for projects(Apply propsal for Community Over Asia Session 2025). ### How has the project developed since the last report? 1.Completed the first version release of apache. 2.Development of basic functions for intelligent analysis of link root causes. 3.Expand business indicator alarm capabilities. 4.Log function iteration and optimization. 5.Clean up and correct historical error paths and information references. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [xX] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2025-03-26 ### 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. Finalize "complete" release (including binary distributions and artifacts), and adopt regular releases pace 2. Grow the community 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? Regarding the user community: * On Slack, since March, we have 17 threads from new users. * On(28 GitHub Issues, new users in May, 53 new users in April, 53 new users in March) * On GitHub Issues, we had 11 new issues created by new users. * On the dev mailing list, we had 196 messages in March, 144 in April, 279 in May, mostly from Polaris committers/contributors. It seems the users prefer to ask questions on Slack. Regarding the dev community: * We had 7 Pull Requests from 7 new contributors * We are discussing with the Apache XTable community (for multi table formats support) * Community meetings happened on 2025-04-03 and 2025-04-17 (recorded and publicly available) ### How has In order to build/grow the projectPolaris developedcommunity, sincewe theparticipated lastto report? We added thedifferent polaris-tools repo (https://github.com/apache/polaris-toolsevents (meetups, etc) to hostintroduce partsApache ofPolaris: the project* (benchmarkOpen tool,Source catalogsData migrator, ...) not directly related to the Polaris "catalog server". Highlights in the project developed: * We refactored the persistence layer to use pure JDBC now and we deprecated EclipseLink use. * We are working on gather server and tool in an unique distribution * Several proposals are in discussion right now (event/observe API, async tasks, spark client, ...) In preparation for 1.0-incubating release, we are voting 0.10-incubating release. We are focusing on 1.0-incubating release, the release process should start quickly after 0.10-incubating release vote pass. ### 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: 2025-02-25 ### When were the last committers or PPMC members elected? Last committers: Ajantha Bhat, Pierre Laporte, Prashant Singh, Jonas Jiang elected on 2025-04-30 Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on 2025-03-25 ### Have your mentors been helpful and responsive? Yes, helpful in releases review and reporting issues. ### 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: - [x] (polaris) Kent Yao Comments: LGTM - [ ] (polaris) Ryan Blue Comments: - [ ] (polaris) JB Onofre Comments: ### IPMC/Shepherd notes: -------------------- ## PonyMail Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms. Pony Mail has been incubating since 2016-05-27. ### Three most important unfinished issues to address before graduating: 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: -------------------- ## PouchDB PouchDB is an open-source JavaScript database inspired by Apache CouchDB that is designed to run well within the browser. PouchDB has been incubating since 2025-04-15. ### Three most important unfinished issues to address before graduating: 1. 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: - [ ] (pouchdb) PJ Fanning Comments: - [ ] (pouchdb) Jean-Baptiste Onofré 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: -------------------- ## Texera Texera is an open-source system to support collaborative data science, AI, and ML using GUI-based workflows. Our vision is to develop a system to support cloud platforms on which users can easily analyze data and use AI/ML techniques provided as operators. Users with various backgrounds, irrespective of whether they know coding or not, can collaborate on the same project to construct a pipeline. Experienced users can use programming languages such as Python, R, Java, and Scala to implement customized computation logic. The platform allows users to pause the execution of a workflow to investigate the operator states, and resume the execution at a later time. The platform can be used by a research community to publish valuable resources such as data sets, workflows, and ML models to share their domain- specific knowledge and support reproducibility of scientific research. The platform also allows users to elastically request computing resources from public clouds for computationally- intensive tasks. Texera has been incubating since 2025-04-12. ### Three most important unfinished issues to address before graduating: 1. 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? Deep Dive: London (2025-05-21) * Current 25 London (2025-05-20) * Open Source Data Deep Dive: Barcelona (2025-05-15) * Munich Database Meetup: Analytics Data Stack (2025-05-13) ### How has the project developed since the last report? We added the polaris-tools repo (https://github.com/apache/polaris-tools) to host parts of the project (benchmark tool, catalogs migrator, ...) not directly related to the Polaris "catalog server". Highlights in the project developed: * We refactored the persistence layer to use pure JDBC now and we deprecated EclipseLink use. * We are working on gather server and tool in an unique distribution * Several proposals are in discussion right now (event/observe API, async tasks, spark client, ...) In preparation for 1.0-incubating release, we are voting 0.10-incubating release. We are focusing on 1.0-incubating release, the release process should start quickly after 0.10-incubating release vote pass. ### 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: 2025-02-25 ### When were the last committers or PPMC members elected? Last committers: Ajantha Bhat, Pierre Laporte, Prashant Singh, Jonas Jiang elected on 2025-04-30 Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on 2025-03-25 ### Have your mentors been helpful and responsive? Yes, helpful in releases review and reporting issues. ### 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: - [X] (polaris) Kent Yao Comments: LGTM - [ ] (polaris) Ryan Blue Comments: - [X] (polaris) JB Onofré Comments: ### IPMC/Shepherd notes: -------------------- ## PouchDB PouchDB is an open-source JavaScript database inspired by Apache CouchDB that is designed to run well within the browser. PouchDB has been incubating since 2025-04-15. ### Three most important unfinished issues to address before graduating: 1. Get the project up and running (no blockers) 2. Follow the graduation progression, in particular make a new release under the ASF Incubator. 3. Grow the community ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? We are still in the setup phase. ### How has the project developed since the last report? TLD & mailing lists have been created, initial committers have started filing their CLAs. We have cleared all remaining code-import issues with Infra. Once CLAs are all in place, we can tackle IP-clearance and coder import. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? N/A ### Have your mentors been helpful and responsive? Helpful and proactive. ### Is the PPMC managing the podling's brand / trademarks? N/A ### Signed-off-by: - [X] (pouchdb) PJ Fanning Comments: - [X] (pouchdb) Jean-Baptiste Onofré Comments: ### IPMC/Shepherd notes: -------------------- ## Teaclave Teaclave is a universal secure computing platform, enabling writing memory-safe trusted applications in Rust running inside Trusted Execution Environment. Teaclave has been incubating since 2019-08-20. The Teaclave community is now working towards graduation. ### Three most important unfinished issues to address before graduating: 1. Complete all requirements of the Project Maturity Assessment. 2. Practice future releases by adhering to a quarterly release schedule. 3. Conduct a thorough self-assessment to ensure all Apache graduation criteria are met. ### Are there any issues that the IPMC or ASF Board need to be aware of? As the Teaclave community works toward graduation, we welcome guidance along the process. We also invite any active IPMC members interested in the project to consider becoming mentors. Thank you. ### How has the community developed since the last report? - Two new participants have joined the project. - Ecosystem growth: The newly published crates on `crates.io` have collectively surpassed 4,000 downloads. ### How has the project developed since the last report? - Completed the process for releasing Teaclave TrustZone SDK v0.4.0. - Initiated the Teaclave Maturity Assessment. During the assessment, we identified several areas for improvement, including the website page and repository documentation. Work is in progress to address these and meet all requirements. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-06-03 Apache Teaclave TrustZone SDK (incubating) v0.4.0 ### When were the last committers or PPMC members elected? 2025-01-21 ### Have your mentors been helpful and responsive? We appreciate the support of our mentors. However, due to the length of the incubation period, some mentors have become less active. This has impacted our release process, with the most recent release vote taking approximately 10 weeks to close, involving two binding votes from our mentors. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [X] (teaclave) Felix Cheung Comments: - [X] (teaclave) Furkan Kamaci Comments: - [ ] (teaclave) Jianyong Dai Comments: - [ ] (teaclave) Matt Sicker Comments: - [ ] (teaclave) Zhijie Shen Comments: - [ ] (teaclave) Gordon King Comments: ### IPMC/Shepherd notes: JM: Feel free to remove inactive mentors and ask for new ones on the IPMC mailing list. -------------------- ## Texera Texera is an open-source system to support collaborative data science, AI, and ML using GUI-based workflows. Our vision is to develop a system that supports cloud platforms on which users can easily analyze data and use AI/ML techniques provided as operators. Users with various backgrounds, irrespective of whether they know coding or not, can collaborate on the same project to construct a pipeline. Experienced users can use programming languages such as Python, R, Java, and Scala to implement customized computation logic. The platform allows users to pause the execution of a workflow to investigate operator states and resume execution at a later time. The platform can be used by a research community to publish valuable resources such as data sets, workflows, and ML models to share their domain-specific knowledge and support reproducibility of scientific research. The platform also allows users to elastically request computing resources from public clouds for computationally intensive tasks. Texera has been incubating since 2025-04-12. ### Three most important unfinished issues to address before graduating: 1. Complete the SGA form. 2. Donate the Texera codebase from the [Texera/texera](https://github.com/Texera/texera) GitHub repo to the Apache/Texera repo. 3. Set up the Apache Texera webpage http://texera.apache.org/. ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? - 2025-04-12: The project enters the incubation phase. - 2025-05-12: We have expanded our PPMC members to 12 members. All of them have signed and submitted their iCLA forms. The latest members (excluding mentors) are listed as follows: | # | ID | GitHub Username | Public Name | |----|--------------|------------------|----------------| | 1 | aicam | aicam | Ali Risheh | | 2 | chenli | | Chen Li | | 3 | kunwp1 | | Chris Park | | 4 | jiadongb | | Jiadong Bai | | 5 | shengquan | | Shengquan Ni | | 6 | xiaozhenliu | | Xiaozhen Liu | | 7 | linxinyuan | aglinxinyuan | Xinyuan Lin | | 8 | yiconghuang | Yicong-Huang | Yicong Huang | | 9 | yunyd | | Yunyan Ding | - 2025-05-12: We have identified 3 mentors: | # | ID | GitHub Username | Public Name | |----|------------|------------------|------------------------| | 1 | cezar | cezarfx | Cezar Cristian Andrei | | 2 | garyw | bigdata-memory | Gordon King | | 3 | fanningpj | pjfanning | PJ Fanning | - 2025-05-12: 10/12 PPMC members (excluding two mentors) have subscribed to mailing lists. - 2025-05-18: We have gathered 52 approvals (in the form of email replies) from past codebase committers to donate the [Texera/texera](https://github.com/Texera/texera) codebase to Apache/Texera. - 2025-05-25: We are in discussion with Ian Maxon (Apache ID: imaxon), PMC Chair of Apache AsterixDB and a long-time contributor, about his joining as a mentor for Apache Podling-Texera. Ian is currently in the process of self-nominating to join the Incubator PMC in order to become eligible to serve as a mentor. - 2025-06-01: As Texera is a research project conducted at University of California, Irvine (UCI), the university owns the copyright of the codebase/software. We are talking to the UCI licensing office about releasing their copyright to the committers of the codebase, with Chen Li as the representative. After the UCI licensing office releases the copyright, we will prepare the SGA form. - 2025-06-01: As of today, we are actively designing a new logo for Texera. ### How has the project developed since the last report? - We released Texera [v1.0.0](https://github.com/Texera/texera/releases/tag/1.0.0) on April 04, 2025. - Many codebase clean ups to prepare codebase for the donation to Apache. - Created a `NOTICE` file to comply with ASF requirements [#3388](https://github.com/Texera/texera/pull/3388) - Added ASF license headers to JOOQ-generated files [#3414](https://github.com/Texera/texera/pull/3414) - Added ASF license headers to source files and enabled Release Audit Tool (RAT)) in CI [#3415](https://github.com/Texera/texera/pull/3415) - New major features: - Added new visualization operators: Bullet Chart [#3362](https://github.com/Texera/texera/pull/3362), RangeSlider [#3374](https://github.com/Texera/texera/pull/3374), Nested Table [#3397](https://github.com/Texera/texera/pull/3397), and Volcano Plot [#3418](https://github.com/Texera/texera/pull/3418) - Improved file handling with MultipartUpload implementation for file uploads [#3396](https://github.com/Texera/texera/pull/3396) and pre-checks for file size/type before preview [#3427](https://github.com/Texera/texera/pull/3427) - Enhanced result exportation with support for the HTML format and large Apache Arrow files [#3429](https://github.com/Texera/texera/pull/3429) - Added size metadata to a workflow JSON for better visibility [#3256](https://github.com/Texera/texera/pull/3256) - Enabled email notifications to users and administrators for inactive or unauthorized login attempts [#3391](https://github.com/Texera/texera/pull/3391), [#3393](https://github.com/Texera/texera/pull/3393) - Added admin account configuration and restricted local sign-ups [#3387](https://github.com/Texera/texera/pull/3387) - Added support for new R libraries and fixed job ordering in the Helm chart [#3386](https://github.com/Texera/texera/pull/3386) - Enabled adjustable shared memory settings for the computing unit [#3451](https://github.com/Texera/texera/pull/3451) - UI improvements - Improved the layout and interface, including the change to the "terminate button icon" [#3424](https://github.com/Texera/texera/pull/3424) and dynamic height adjustment of the operator property sidebar [#3437](https://github.com/Texera/texera/pull/3437) - Enhanced interactivity with auto-expansion of the result panel on an operator click [#3435](https://github.com/Texera/texera/pull/3435) and improved the comment box usability [#3436](https://github.com/Texera/texera/pull/3436) - Added individual progress indicators for concurrent file uploads [#3426](https://github.com/Texera/texera/pull/3426) - General UI consistency and refinements [#3359](https://github.com/Texera/texera/pull/3359), [#3372](https://github.com/Texera/texera/pull/3372) - Refactoring - Reimplemented the User Quota Service to remove the MongoDB dependency [#3402](https://github.com/Texera/texera/pull/3402) - Replaced cache source operators with input port materialization reader threads [#3425](https://github.com/Texera/texera/pull/3425) - Bug fixes - Fixed the Helm chart metric resolution, cluster export issues, and Envoy HTTP timeout/configuration problems [#3376](https://github.com/Texera/texera/pull/3376), [#3378](https://github.com/Texera/texera/pull/3378), [#3380](https://github.com/Texera/texera/pull/3380), [#3382](https://github.com/Texera/texera/pull/3382) - Updated the base image in Dockerfile for compatibility [#3413](https://github.com/Texera/texera/pull/3413) - Fixed the UI layout and state issues, including centering operators, incorrect workflow reloading, and auto-persistence logic [#3342](https://github.com/Texera/texera/pull/3342), [#3344](https://github.com/Texera/texera/pull/3344), [#3412](https://github.com/Texera/texera/pull/3412) - Resolved errors in dataset display for unauthenticated users and improved handling of compressed files in File Scan operator [#3373](https://github.com/Texera/texera/pull/3373), [#3385](https://github.com/Texera/texera/pull/3385) - Fixed multiple ChannelMarker issues across Java and Python layers, including transmission, partitioning, and worker routing [#3434](https://github.com/Texera/texera/pull/3434), [#3439](https://github.com/Texera/texera/pull/3439), [#3445](https://github.com/Texera/texera/pull/3445), [#3448](https://github.com/Texera/texera/pull/3448) - Corrected backend query versioning and execution order, and fixed Python Lambda operator compilation [#3410](https://github.com/Texera/texera/pull/3410), [#3438](https://github.com/Texera/texera/pull/3438) ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ X] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: XXXX2025-XX04-XX04 ### When were the last committers or PPMC members elected? On 2025-05-12, the last Texera PPMC members (yunyad, aicam) were added. ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed Yes, our mentors have been both helpful and highly responsive. We are grateful for their continued support throughout the incubation process. In particular, we would like to extend a special thanks to PJ Fanning for his outstanding guidance and engagement. ### 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? Texera PPMC is working with third parties who are willing to use Texera brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html. Texera PPMC is also working on a new design of the Texera logo/trademark. Name is approved: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-233 ### Signed-off-by: - [ ] (texera) Cezar Andrei Comments: - [ ] (texera) Gordon King Comments: - [ X] (texera) PJ Fanning Comments: I will ask the Texera team to provide a shorter report in future. The SGA is not yet signed so we have not yet transferred the code. ### 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. For the last few months we have been discussing graduation, and getting our various ducks in rows. We believe we are ready to graduate, but have only four people who have elected to stay on as PMC members, which seems to us too small a number. So right now we are discussing what the next steps are -- go ahead and graduate, or attempt to grow that number a little. ### Three most important unfinished issues to address before graduating: A. Grow the community a little more. -- or -- B. Decide that a small dedicated community is better than languishing in obscurity forever. ### 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? While discussing graduation, we had a number of people indicate that they are no longer engaged enough to move to that final step. ### How has the project developed since the last report? We have continued to slowly work on content. And one of our number got a talk accepted at Community Over Code 2025 to present about the project, so hopefully several of us will be there for that. ### ### How would you assess the podling's maturity? We believe that we're ready to move out of our parents' basement and into the real world. Any day now. - [ x ] Nearing graduation ### Date of last release: XXXX2024-XX09-XX30 ### When were the last committers or PPMC members elected? rbowen was added to the PPMC in September 2024. ### Have your mentors been helpful and responsive? The mentors are awesome. ### Is the PPMC managing the podling's brand / trademarks? Our brand/trademarks are fine, and we have done a name check. ### Signed-off-by: - [ ] (training) Craig Russell Comments: - [ ] (training) Christofer Dutz Comments: - [ X] (training) Justin Mclean Comments: - [ ] (training) Lars Francke Comments: ### IPMC/Shepherd notes: JM: I agree the mentors are awesome. :-) -------------------- ## 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. Working on one more release before graduation. ### 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 more PPMC member, 7 new contributors, 1 new slack member since the last report. ### How has the project developed since the last report? Progress on multiple fronts: - Upgraded to Java 17 - Extended functionality for Wayang's ML capabilities - Extended functionality for Wayang's FL capabilities - Extended functionality for Wayang's Scala API - Extended functionality for Wayang's SQL API - Several new operators ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [xX] Nearing graduation - [ ] Other: ### Date of last release: 2025-02-07 ### When were the last committers or PPMC members elected? 2025-02-05 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. elected? 2025-02-05 ### Have your mentors been helpful and responsive? Yes, they have been helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? Yes. ### Signed-off-by: - [ ] (wayang) Christofer Dutz Comments: - [ ] (wayang) Lars George Comments: - [ ] (wayang) Bernd Fondermann Comments: - [ X] (wayang) Jean-Baptiste Onofré Comments: We will review the maturity model in preparation for graduation proposal ### IPMC/Shepherd notes: |