DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| Markdown |
|---|
# Incubator PMC report for December 2025 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. TODO add narrative ## Community ### New IPMC members: ### People who left the IPMC: ## New Podlings ## Podlings that failed to report, expected next month ## Graduations - list podling here The board has motions for the following: - Your podling here? ## Releases The following releases entered distribution during the month of November: ## IP Clearance ## Legal / Trademarks ## Infrastructure ## Miscellaneous ## Credits ## Table of Contents [Auron](#auron) [Baremaps](#baremaps) [BifroMQ](#bifromq) [Fesod](#fesod) [Gealfow](#geaflow) [Iggy](#iggy) [KIE](#kie) [OpenServerless](#openserverless) [Otava](#otava) [OzHera](#ozhera) [Polaris](#polaris) [PouchDB](#pouchdb) -------------------- ## Auron Auron accelerates Apache Spark SQL by providing an alternative vectorized execution layer implemented in Rust, enabling native performance while maintaining full Spark compatibility. Auron has been incubating since 2025-08-05. ### Three most important unfinished issues to address before graduating: 1. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? ### How has the community developed since the last report? ### How has the project developed since the last report? ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first 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: - [ ] (auron) Becket Qin Comments: - [ ] (auron) Calvin Kirs Comments: - [ ] (auron) Hao Ding Comments: - [ ] (auron) Nicholas Jiang Comments: ### IPMC/Shepherd notes: -------------------- ## Baremaps Apache Baremaps is a toolkit and a set of infrastructure components for creating, publishing, and operating online maps. Baremaps has been incubating since 2022-10-10. ### Three most important unfinished issues to address before graduating: 1. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? ### 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: - [ ] (baremaps) Bertrand Delacrétaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [ ] (baremaps) Julian Hyde ge Comments: - [ ] (baremaps) Calvin Kirs Comments: - [ ] (baremaps) George Percivall 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. Complete the first Apache Incubator release and establish a regular release cadence. 2. Increase public communication on dev@ and ensure all project decisions and planning are captured on the mailing list. 3. Grow community participation beyond the original contributors, including attracting new reviewers and contributors. ### Are there any issues that the IPMC or ASF Board need to be aware of? The primary concern is low traffic on the dev@ list and limited visibility of development discussions. Recent mentor feedback highlighted the need to move architectural decisions, release planning, and prioritization discussions onto dev@ to comply with ASF governance expectations. In addition, regarding the “BifroMQ” trademark transfer in China: in response to a time-limited office action from the China National Intellectual Property Administration (CNIPA), Baidu submitted the requested supplemental materials before the deadline. We are now waiting for an update from ASF on the status and next steps. ### How has the community developed since the last report? Community activity on GitHub remains steady, but public communication has been low. Following mentor feedback, the PPMC began improving transparency by starting public discussion threads, including a DISCUSS thread for the first release. We also launched the “BifroMQ” WeChat Official Account to support outreach to the Chinese-speaking community. The account name currently uses “BifroMQ” (without the “Apache” prefix) because the platform requires formal authorization to use “Apache” in the account name. The account description clearly identifies the project as “Apache BifroMQ (Incubating)”. Official project discussions and decisions continue to happen on the mailing list. ### How has the project developed since the last report? Work toward the first incubator release has been completed, including architectural refactoring, API stabilization, and Apache compliance work (LICENSE/NOTICE, headers, package renaming, distribution scripts). A DISCUSS thread(https://github.com/apache/bifromq/discussions/192) for the 4.0.0-incubating release has been opened to gather community feedback before preparing RC1. A significant amount of work came from supporting an early enterprise adopter running BifroMQ in production, resulting in important optimizations and bug fixes now included in the upcoming release. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2025-02-25 ### When were the last committers or PPMC members elected? No new committers or PPMC members have been added since incubation started. ### 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. ### 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. The podling name “BifroMQ” has been reviewed by the VP, Brand. We are not aware of any misuse by third parties. For outreach to the Chinese-speaking community, we have created a WeChat Official Account currently named “BifroMQ”. The platform requires an authorization document to use “Apache” in the account name, so we are temporarily using “BifroMQ” as the account name while clearly stating “Apache BifroMQ (Incubating)” in the description. We would appreciate guidance from ASF (Incubator and Brand) on the proper process to obtain authorization for using the full “Apache BifroMQ” name for this account, so that we can align fully with the Incubator publicity policy. ### 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: -------------------- ## Fesod Fesod is a high-performance and memory-efficient Java library for reading and writing Excel files, designed to simplify development and ensure reliability. Fesod has been incubating since 2025-09-17. ### Three most important unfinished issues to address before graduating: 1. Ensure that the website and codebase are fully compliant with ASF policies. 2. Publish the first release under the Apache Incubator. 3. Continue to grow the community and word towards the ASF 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 project now has several active new contributors. 2. We have created a Slack channel (under ASF) to facilitate communication. ### How has the project developed since the last report? We will initiate the community vote for the first release within the next two weeks, 1. We refactored several core classes to ensure full compliance with licensing requirements. 2. Formal preparation for the project's first official release has commenced. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] 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? Are things falling through the cracks? If so, please list any open issues that need to be addressed. Yes. They are very nice and helpful. ### 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. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246 ### Signed-off-by: - [x] (fesod) tison Comments: - [x] (fesod) Dave Fisher Comments: - [ ] (fesod) Huajie Wang Comments: - [x] (fesod) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## Geaflow GeaFlow is a streaming graph computing engine for distributed large-scale real-time graph storage and analysis. It supports trillion-level graph storage, hybrid graph and table processing, real-time/offline graph computing, and interactive graph analysis. GeaFlow has been incubating since 2025-06-06. ### Three most important unfinished issues to address before graduating: 1. Cultivate a more diverse community by engaging contributors and committers from varied organizations and global regions. 2. Implement predictable release cycles and maintain high project stability to encourage broad participation and adoption. ### 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. Two new contributors have joined the community. ### How has the project developed since the last report? 1. Over the past month，12 pull requests have been merged, development has focused on new features, code quality, and documentation. Key additions include a Paimon stream source and support for Jaccard similarity. Infrastructure saw the introduction of a cluster coefficient and GitHub Actions condition checks. Code health was improved by standardizing editor configs, removing unnecessary files/methods, and fixing a data loss bug after failover. 2. The first community edition: V0.7.0 has been released on November 19th. ### 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: The first community version was released on November 19th. ### When were the last committers or PPMC members elected? After reviewing our active community contributors, we have selected two qualified candidates. The process now advances to a period of discussion followed by a formal voting process. ### Have your mentors been helpful and responsive? Yes, we have received helpful guidance. ### Is the PPMC managing the podling's brand / trademarks? N/A. ### Signed-off-by: - [ ] (GeaFlow) Willem Ning Jiang - [ ] (GeaFlow) xinwang - [ ] (GeaFlow) lzljs3620320 - [ ] (GeaFlow) jmclean - [ ] (GeaFlow) paulk ### 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? ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: XXXX-XX-XX ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? ### Signed-off-by: - [ ] (kie) Brian Proffitt Comments: - [ ] (kie) Claus Ibsen Comments: - [ ] (kie) Andrea Cosentino Comments: ### IPMC/Shepherd notes: -------------------- ## OpenServerless OpenServerless is an open source, cloud-agnostic, serverless platform. It offers a complete environment for serverless applications development, based on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an unified developer experience with a plethora of services (SQL or noSQL databases, key-value stores, object storage, LLMs services, function schedulers) managed by the platform's core: the operator, along with tooling (the CLI) to simplify (and interact with) deployments, integrated ide and starter application and optimized runtimes integrated with the staters. OpenServerless has been incubating since 2024-06-17. ### Three most important unfinished issues to address before graduating: 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 Delacrétaz Comments: - [ ] (openserverless) Enrico Olivelli Comments: - [ ] (openserverless) François Papon Comments: - [ ] (openserverless) JB Onofré Comments: - [ ] (openserverless) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## Otava Apache Otava (incubating), a command-line tool, written in Python, detects and alerts about statistically significant changes in performance test results (more generally, time-series data) stored in CSV files or a number of supported databases. A typical use-case of Otava is as follows: 1. A set of performance tests is scheduled repeatedly, such as after each commit is pushed. 2. The resulting metrics of the test runs are stored in a time series database (Graphite) or appended to CSV files. 3. Otava is launched by a Jenkins/Cron job (or an operator) to analyze the recorded metrics regularly. 4. Otava notifies about significant changes in recorded metrics by outputting text reports or sending Slack notifications. 5. 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. ### Three most important unfinished issues to address before graduating: 1. Upgrade to support the latest versions of Python, including upgrading to the latest signal-processing-algorithms library. 2. Do more releases, so that it is a routine, repeatable process. 3. Grow the community and ultimately vote to admit new committers and PPMC members. Do more publicity around the releases and the project in general. This is an item where we certainly hope to see new contributors. ### 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? In our previous report we already shared our successfully completing the first release as an Apache Incubator process. This first release was mostly focused on a) bringing together various github forks under the a unified ASF upstream project, and b) releasing one release with the new project name, and following the ASF process, but one that did not in itself contain a lot of new features or changes beyond (a). With such an inaugural release out of the way, we have seen over the past 4 months a handful of patches that make more substantive changes to the codebase. We still have a couple foundational tasks remaining that are holding us back from accepting new code contributors and contributions without any friction, but the door is at least more open than it was before the July release (0.6.1). The remaining foundational tasks are: 1. Doing another release, 0.7.x, that is still focused on backward compatibility with our past, and merely introduces small fixes in the functionality itself, as well as the release process. Re-rehearsing the actions related to releasing, and related collaboration among the project committers seems a significant part of the process of becoming a fully graduated ASF project. 2. Cutting the dependency on an external implementation of the "E-Divisive means" algorithm, which is the very heart of what Otava does. This is the so called "signal-processing-algorithms" pip module released by MongoDB under the Apache 2.0 License, but not donated to ASF. We have come to the conclusion we need this very core functionality to be part of our own code base and version control, and since we didn't manage to get the MongoDB team's attention, we decided to rewrite an independent implementation. 3. Upgrading from the unsupported python versions 3.8 and 3.9 to the most recent versions. 1 above is already undergoing voting, and 2 is in review and approved, waiting to be merged. The 0.7.x release also brings back an additional distribution format: docker images. For the rewrite of the E-Divisive algorithm we are glad to report we found a completely new contributor to the project, with sufficient mathematical education to take on this somewhat daunting task. In the process of re-implementing the algorithm directly from its academic publication, the contributor managed to discover a bug/omission in the implementation we have been using for almost a decade now. The effect of this discovery is that the new implementation will find change points that the original algorithm tends to miss, in situations where there are 2 or more changes close to each other. The fact that the new implementation of the E-divisive algorithm was done by a completely new contributor, that did not look at the MongoDB implementation before creating the new implementation, means that our new implementation ought to qualify as a properly independent, clean room implementation. While this was not a strict requirement for this task, now that this is the outcome, we wish to record it in the board minutes. Altogether we have during our first year as an ASF incubator now received code contributions from 3 founding project members and 3 new contributors and one of the project mentors. In addition to these 7 there have been several more that contributed either a bug report or participated in an email thread, or voting for a release. One of these was a developer from the Tarantool open source database, that started using Otava as part of their Continuous Benchmarking. As discussed in this update, we believe there are more interested contributors that are still held back by our old python version and untangling a major legacy dependency. We have not yet approved new committers or PPMC members to the project, as there was not yet sufficient time and opportunity to demonstrate significant and sustained contributions to the project. We are optimistic that we are moving in the right direction where this could be happening in a near future. On the topic of committers and PPMC members it is notable that several of the past contributors that were listed in our project proposal a year ago, and approved as founding PPMC members, have not actually shown up on the ASF mailing list during our first year. We will follow up with these individuals to confirm their desired status with the project, and take appropriate action based on that outreach. (From a community diversity and robustness perspective, it should be mentioned that the 3 founding contributors that have been the most active, still represent 3 different employers, and to the best of our knowledge, the new contributors are also employed by 3 net new employers.) ### How has the project developed since the last report? (See above, it felt meaningful to combine these two answers.) ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [x] Initial setup - [x] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: We are progressing well with the community building, but not yet nearing graduation. A self review based on https://s.apache.org/727vc Code 5/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 ### Date of last release: 2025-07-25 ### When were the last committers or PPMC members elected? None yet. ### 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. ### 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? VP, Brand approved the new project name in February. Our life as an ASF incubating project really only started after that date. We are not aware of any trademark issues related to the new project name. ### Signed-off-by: - [x] (otava) Dave Fisher Comments: An amazing amount of detail, thanks. - [ ] (otava) Enrico Olivelli Comments: - [ ] (otava) Lari Hotari Comments: - [x] (otava) Mick Semb Wever 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. Check the Polaris existing trademarks at the ASF (transfer has been done, to be verified) ### 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? Between 2025-07-31 and 2025-10-31: - 2 new releases - 17 new contributors - 649 PRs opened / 517 PR merged - 745 messages on the dev@ mailing list - Apache Polaris is now integrated to analytics.apache.org which shows **10,000** monthly visitors to polaris.apache.org across the globe [[website link](https://analytics.apache.org/index.php?module=CoreHome&action=index&date=yesterday&period=day&idSite=81#?period=month&date=2025-10-31&idSite=81&category=General_Visitors&subcategory=UserCountry_SubmenuLocations)] We are happy to see new contributors who contributed important new features: - OPA support. - Polaris Console (UI) is coming. - S3 KMS support. ### How has the project developed since the last report? We did 1.1.0-incubating and 1.2.0-incubating releases since the last report. 1.3.0-incubating release is also in preparation. Here's the highlights about project development since the last report: - Improvement on the website, adding new blog posts (StarRocks and Polaris integration) - Moving forward on NoSQL support - New OPA Authorizer - New MetricsReport interface - New JDBC schema evolution support - A lot of improvements on Python (CLI, ...) - Enhanced support for S3-compatible (on-prem) storage - Automated release workflows are in place, ongoing work to support ATR ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-10-27 ### When were the last committers or PPMC members elected? Last PPMC member has been elected on 2025-11-19 (Yong Zheng). ### 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. Mentors are 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, the podling manages the brand/trademarks, especially working with 3rd parties organizing meetups. ### Signed-off-by: - [ ] (polaris) Holden Karau Comments: - [ ] (polaris) Kent Yao Comments: - [ ] (polaris) Ryan Blue Comments: - [ ] (polaris) Jean-Baptiste Onofré Comments: - [ ] (polaris) François Papon 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: |
...