What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2026-08-19 | Appointed Kranti Parisa | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2026-08-19 | Establish the Apache Iggy Project | special order | approved |
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. Continue expanding the community 2. Increase the use of GitHub Discussions/Issues integrated with mailing lists ### Are there any issues that the IPMC or ASF Board need to be aware of? Lately, a lot of GitHub CI/CD issues. Hope ASF is actively looking into it. ### How has the community developed since the last report? - Discord members count ~700, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. - Github stars reached 4.3K+ - Crates downloads reached ~220K+ - 2 new committers have been added - Presented at [Rust India 2026 conference](https://hasgeek.com/rustbangalore/rust-india-conference-2026/sub /building-apache-iggy-how-rust-powers-ultra-low-tai-Nh82Mb2cvJXmgH39Yaez8x) ### How has the project developed since the last report? - Released [0.8.0](https://github.com/apache/iggy/releases/tag/server-0.8.0), a major release focused on architecture, clustering readiness, security, SDK maturity, connectors, and infrastructure. - More than 300 commits since the last report (Mar 2026) - Completed a wire protocol unification, removing redundant serialization paths and simplifying the protocol foundation. - Added new zero-copy message primitives, improving the internal data path and preparing the project for higher-performance messaging workloads. - Introduced **`iggy-server-ng`**, a new server binary that serves as the foundation for future cluster-ready Iggy deployments. - Advanced VSR-based clustering, including shard routing, plane abstractions, WAL-backed client tracking, namespaced commit pipelines, deterministic simulator improvements, and persistent WAL journal support. - Improved security and credential handling with user-header encryption, random JWT secret generation, `SecretString` usage, consensus header validation, and regression tests to prevent plaintext secret persistence. - Fixed multiple reliability and correctness issues, including consumer offset handling, segment deletion behavior, hostname handling, CLI behavior, and connector runtime behavior. - Expanded the SDK ecosystem with major improvements across Rust, C++, Java, C#, Go, Python, and Node.js clients, including better transport, TLS, async APIs, testing, and usability. - Added new connectors for InfluxDB, MongoDB, and generic HTTP sinks, along with connector hot-reload support. - Improved developer and operator experience through benchmark dashboard updates, Web UI enhancements, Helm chart improvements, and CLI usability fixes. - Strengthened CI/CD and release quality, including parallel Rust testing, dependency-DAG-scoped test selection, broader Codecov coverage, hardened publish pipelines, Helm chart validation, binary artifact detection, typo checks, version bump tooling, and ASF GitHub Actions allowlist compliance. ### 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 - [X] Other: Expanding Ecosystem ### Date of last release: 2026-04-22 ### When were the last committers or PPMC members elected? - 2026-05-11 [Krishna Vishal] - 2026-05-22 [Atharva Lade] ### Have your mentors been helpful and responsive? Yes, very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues as reported here. VP, Brand approved the project name. ### Signed-off-by: - [ ] (iggy) Hao Ding Comments: - [ ] (iggy) Yonik Seeley Comments: - [X] (iggy) Zili Chen Comments: - [X] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes: JM - Sent an email to the project about CI/CD issues.
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. Continue expanding the community, release more versions under ASF
2. Increase the use of GitHub Discussions/Issues integrated with mailing
lists
### 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?
- Discord members count ~650, new contributors writing proposals
(discussions), submitting PRs for fixing issues, docs, enhancements.
- Github stars reached 3.9K+
- Crates downloads reached 185K+
- Recent blog post on Apache Iggy's migration journey to thread-per-core
architecture powered by io_uring
(https://iggy.apache.org/blogs/2026/02/27/thread-per-core-io_uring) drew a
lot of attention on other sites and social media and attracted critical
talent
- Attending RustINDIA Conference 2026
- The community continues to grow. We are pleased to welcome Łukasz Zborek
as a new Apache Iggy committer. Łukasz has been a core contributor to the
C# SDK and is currently the #8 contributor in the repository. Beyond
building a high-quality C# SDK, he has contributed across the project
including CI improvements, BDD testing, TLS support, reconnection handling,
and high-level consumer/publisher APIs.
### How has the project developed since the last report?
- Released 2 versions
[0.6.0](https://github.com/apache/iggy/releases/tag/server-0.6.0) and
[0.7.0](https://github.com/apache/iggy/releases/tag/server-0.7.0).
- 0.7.0 release had 188 commits from 19 contributors and over 1,200 files
changed
- Deterministic tick-based timeout mechanism for VSR — improves reliability
for Viewstamped Replication workflows, a core building block toward
clustering and distributed coordination.
- New cluster primitives (on_replicate, send_prepare_ok, replicate, view
change, partitions trait) to solidify cluster control paths and prepare for
future distributed expansions.
- Metadata state machine foundation & snapshot interface — essential
groundwork for robust metadata handling and future high-availability
features.
- Embedded Web UI now included in the server and enabled by default — no
extra deployment step required for the dashboard experience.
- NUMA awareness — improves performance on multi-socket hardware by
aligning memory and CPU locality.
- Http.web_ui config option gives users control over Web UI exposure and
configuration.
- Graceful shard shutdown on panic, enhanced async disk I/O availability
handling, and improved critical task failure handling — all contribute to
greater server resilience.
- Retry mechanism and detailed logging for connector HTTP configuration —
increasing robustness when integrating with external systems.
- Prometheus metrics and stats endpoints now exposed for connectors so
observability is first-class.
- Extended Postgres sink & source plugins with integration tests for richer
pipeline ingestion.
- Connector runtime --version flag & other quality-of-life improvements for
ops tooling.
- Java SDK enhancements: fluent builder API, better tests, and async
serialization improvements.
- Python SDK: async iterator support for consumer — smoother integration
for modern async apps.
- Go leader redirection scenario addition — improved client routing logic.
- C# SDK: expanded API surface and .NET 10 support.
- Linux edge binary builds + ARM64 support — expands platform compatibility
for pre-release runners.
- Automated artifacts & enhanced CI workflows (auto-publish, better shared
caches, native runners) to speed iteration and ensure release quality.
- Pre-commit hooks, TOML formatting, auto-publish workflows across SDKs and
languages — boosts contribution hygiene.
- Expanded API tests, integration tests, watchdogs, and crash detection —
better confidence in deployment and regression risk reduction.
- Rust toolchain bump (1.92.0) and widespread dependency updates.
- Replace unmaintained serialization (msgpack replacing old libs) — steers
toward more sustainable and performant internals.
- Migration to up-to-date ecosystem dependencies (e.g., Yew & yew-router)
for UI stack improvements.
- Many other improvements, ecosystem expansion tickets are in progress.
### 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
- [X] Other: Expanding Ecosystem
### Date of last release:
2026-02-25
### When were the last committers or PPMC members elected?
2026-01-13 [Łukasz Zborek is the last committer elected]
### Have your mentors been helpful and responsive?
Yes, mentors are available for voting and approvals. That said, having a
few more active mentors would be beneficial to ensure continuity and help
us address any gaps as we move toward graduation.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported here. VP, Brand
approved the project name.
### Signed-off-by:
- [ ] (iggy) Hao Ding
Comments:
- [ ] (iggy) Yonik Seeley
Comments:
- [ ] (iggy) Zili Chen
Comments:
- [X] (iggy) Hulk Lin
Comments:
### IPMC/Shepherd notes:
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. Continue expanding the community, release more versions under ASF 2. Increase the use of GitHub Discussions/Issues integrated with mailing lists. ### 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? - Discord members count 560+, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. - Github stars reached 3.3K+ - Crates downloads reached 168K+ - Presented Apache Iggy at the ApacheCon in September - Recent blog post on Building WebSocket Protocol in Apache Iggy using io_uring and Completion Based I/O Architecture (https://iggy.apache.org/blogs/2025/11/17/websocket-io-uring) drew a lot of attention on other sites and social media and attracted critical talent ### How has the project developed since the last report? - Release 0.6.0 is under voting process - Rewrite the server to use io_uring with thread-per-core, shared-nothing architecture using compio runtime - Implement WebSocket transport with custom compio-ws library designed for completion-based I/O - Add helpful diagnostic messages for io_uring runtime failures (RLIMIT_MEMLOCK, seccomp) - Harden security with auto-generated root password and Argon2 password hashing (replacing bcrypt) - Replace CRC32 checksums with xxHash3 and use UUIDv4 for random message IDs - Implement GetClusterMetadata command with leader-aware connect mechanism in SDKs - Add foundation for clustering with consensus, metadata modules, and TransportEndpoints - Introduce Iceberg sink connector with S3 storage, REST catalogs, and fan-out routing - Add Elasticsearch sink and source connectors with rustls TLS support - Implement Flink processor and processor infrastructure for stream processing - Extend connectors runtime with configuration provider trait, HTTP config provider, and E2E test suite - Add high-level IggyPublisher and IggyConsumer clients to C# SDK with TCP reconnection, TLS, and AES encryption - Implement async/non-blocking Java SDK client using Netty with CompletableFutures - Add TLS TCP support to Java and C# SDKs - Extend Python SDK with connection string support, bytes data, typing stubs, and musllinux wheels - Improve Go SDK with DeleteConsumerOffset, error handling refactor, and deserialization fixes - Add virtual commands (ensureStream, ensureTopic, ensureGroup) and nullable returns to Node.js SDK - Implement builder pattern for Rust SDK client and unify TransportProtocol enum across codebase - Fix multiple consumer group bugs (offset storage, deletion, validation, hashmap usage) - Fix active segment position inconsistency and Murmur3 hash shard assignment skew - Unify Helm charts for server and UI with environment variable support - Overhaul CI/CD with intelligent change detection, dual caching, and multi-arch Docker builds (~40% faster) - Update to Rust 1.90 and fix Docker builds for macOS (ARM64 support) - Improve Web UI with autocomplete, keyboard navigation, large number rendering, and security fixes - Add -c/--consumer-group flag to CLI for consumer offset commands ### 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 - [X] Other:Expanding ecosystem ### Date of last release: 2025-08-10 (new release 0.6.0 is expected to land by 2025-12-12) ### When were the last committers or PPMC members elected? February 2025, at the time of onboarding to Apache Incubator Program. ### Have your mentors been helpful and responsive? Yes, mentors are helpful and in general responsive. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues as reported here. VP, Brand approved the project name. ### Signed-off-by: - [X] (iggy) Hao Ding Comments: Nice work! - [X] (iggy) Yonik Seeley Comments: - [ ] (iggy) Zili Chen Comments: - [ ] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes:
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. Continue expanding the community, release more versions under ASF 2. Expand connectors / external sinks ecosystem, Clustering 3. Add more documentation on iggy.apache.org as we add more features ### 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? - Discord members count 470+, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. - Github stars reached ~2.9K - Crates downloads reached 157K+ - Presented Apache Iggy at the Rust Poland Meetup: https://www.meetup.com/rust-poland-meetup/events/308832371 - Scheduled to present at ApacheCon in September ### How has the project developed since the last report? Version 0.5.0 has been released - Here is the release notes https://github.com/apache/iggy/releases/tag/server-0.5.0 - Release Announcement thread https://lists.apache.org/thread/tn5onstopj3pxh8vdo651jscsp4lfsgf Dependencies & Build - Upgraded Rust dependencies across the project - Fixed Docker setup action and publishing workflow issues SDKs: Enhancements & CI - Java SDK: version updated, Nexus credentials managed via environment, published to Apache Maven and SNAPSHOTs - Node.js SDK: updated package metadata, proper typings for async methods, packaging fixes - Go SDK: added Go getting-started example and test script, implemented Go publish workflow, integrated BDD tests (godog) across SDK changes, CI workflows, BDD tests added for multiple SDKs, replaced Box with ClientWrapper enum - Python SDK: renamed from iggy_py to apache‑iggy, added support for consumer groups, BDD tests and restructured test layout - C# SDK: updated version header in .csproj, improved package metadata, added CI workflow - Fixed Rust SDK: resolved monotonic time bug Connectors & Core Engine - Various Connectors runtime enhancements - Added state storage using local files - Introduced FlatBuffers schema support - Added PostgreSQL sink and source connectors - Extended runtime with protobuf support and initial HTTP API - Refactored socket handling to better support large messages; added examples; improved singleConsumerStream logic Server & Benchmarks - Updated message header to include decrypted payload length and fixed encrypted message index calculation - Introduced Model Context Protocol (MCP) server - Optimized benchmarking: parallelized report builder, updated platform links, typo fixes - Added Helm chart for Iggy server Web UI & Documentation - Improved message browsing in Web UI for a smoother experience - Readme updates, grammar and wording improvements; added missing license headers across modules - Integrated with DeepWiki for additional documentation on Github - Extended iggy-server --help documentation Infrastructure, CI/CD, and Testing - Established branch protection for io_uring runtime branch - Removed OpenSSL dependency in favor of Rustls for TLS - Consolidated server tests using test matrices; added segment cache index variants to server‑restart tests; fixed restart index saving issues - Workflow improvements: markdown linter, improved CI workflows, publishing for bench and connectors, Docker and examples fixes ### 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 - [X] Other: Expanding ecosystem ### Date of last release: 2025-08-10 ### When were the last committers or PPMC members elected? February 2025, at the time of onboarding to Apache Incubator Program. ### Have your mentors been helpful and responsive? Yes, mentors are helpful and in general responsive. Some of them might be busy with other commitments. Maybe we could benefit from 1 or 2 new mentors to increase the coverage. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues as reported here. VP, Brand approved the project name. ### Signed-off-by: - [X] (iggy) Hao Ding Comments: Actively working project - [ ] (iggy) Yonik Seeley Comments: - [X] (iggy) Zili Chen Comments: - [ ] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes:
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. Continue expanding the community, release more versions under ASF 2. Expand connectors / external sinks ecosystem 3. Add more documentation on iggy.apache.org as we add more features ### Are there any issues that the IPMC or ASF Board need to be aware of? Sometimes, INFRA jira tickets taking more time. Is there a way to expedite the process there? ### How has the community developed since the last report? 1. Discord members count approaching 450, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. 2. Github stars reached 2.7K 3. Crates downloads reached 141K+ 4. Presented at Craft-IT Conference (https://craft-it.pl/#session-216) 5. Scheduled to present at ApacheCon in September ### How has the project developed since the last report? The Iggy project has made significant progress in multiple areas during the reporting period: * *Repository Restructure*: Transitioned the codebase to a monorepo structure to better support modular development across server, client SDKs, connectors, and tooling. * *Connectors Runtime*: Implemented the initial version of the Iggy Connectors Runtime, enabling dynamic loading of source/sink plugins and supporting custom data transformations. * *SDK Migration*: Migrated SDKs for multiple languages including C#, Java, Go, Node.js, Python, and C++ to align with the monorepo architecture and latest server capabilities. * *Web Dashboard*: Migrated the Iggy Web UI dashboard to the new repository structure. * *Benchmarking Platform*: Migrated the benchmarking platform and began preparations to host it under [benchmarks.iggy.apache.org|http://benchmarks.iggy.apache.org]. * *CI Improvements*: Enhanced the CI/CD pipelines to handle multiple languages and projects independently within the monorepo. * *Zero-Copy Support*: Added zero-copy support in the server and integrated recent server changes across all existing SDKs. * *Rust SDK Refactor*: Refactored the Rust SDK into smaller, reusable packages shared between server and client implementations; also updated the Rust edition and dependencies. * *Runtime Refactor (Experimental)*: Published an experimental branch featuring a new runtime architecture based on _io_uring_, thread-per-core model, and shared-nothing design. * *BDD Test Coverage*: Introduced Behavior-Driven Development (BDD) scenarios using Cucumber for validating SDK functionality across multiple languages. * *Benchmarking Enhancements*: Extended the benchmarking CLI with a high-level SDK abstraction, added TLS support, and improved result sharing via unique URLs. * *Website Redesign*: Completed a major website redesign, updated brand assets, and aligned naming conventions with Apache guidelines. * *Release Planning*: Initiated discussions and scoping for the upcoming v0.5.0 release (https://github.com/apache/iggy/discussions/1931) ### 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 - [X] Other: Expanding ecosystem ### Date of last release: 2025-04-17 ### When were the last committers or PPMC members elected? February 2025, at the time of onboarding to Apache Incubator Program. ### Have your mentors been helpful and responsive? Yes, the mentors are very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? - There are no known brand and naming issues as reported here. - VP, Brand approved the project name. ### Signed-off-by: - [X] (iggy) Hao Ding Comments: - [X] (iggy) Yonik Seeley Comments: - [ ] (iggy) Zili Chen Comments: - [X] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes:
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. Continue expanding the community, release more versions under ASF 2. Migrate all the repos from previous OSS repo https://github.com/orgs/iggy-rs/repositories to apache/iggy repo (mono repo with independent CI/CD) 3. Enhance iggy.apache.org with more details, guides, docs, blogs, benchmarks etc ### How has the community developed since the last report? 1. Discord members count approaching 400, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. 2. Github stars approaching 2.5k from 2.4k 3. Creates downloads crosses 124k vs 115k at the time of last report 4. Presented at [Rustmeet 2025](https://www.youtube.com/watch?v=v3bpw7fcjp0) 5. Presented at [Rustikon Conference 2025](https://www.youtube.com/watch?v=GkV306PyvqM) ### How has the project developed since the last report? 1. Apache Iggy (Incubating) [v0.4.300 released](https://lists.apache.org/thread/q3r6l0gcc27k1nj1q8frqwh40o0mhs4h) 2. Enhanced performance and efficiency: zero-copy (de)serialization [implemented](https://iggy.apache.org/blogs/2025/05/08/zero-copy-deserializa tion) for the server & updated SDK client 3. Restructuring the repository to support monorepo with multiple SDKs and other tooling (eg benchmarks) 4. Started migrating the SDKs from old repo (dotnet, java, node, web UI etc) 5. Successful POCs (with quickwit) for steaming messages into external connectors/sinks 6. Submitted detailed report for trademarks and received the [approval for the name](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-236) "Iggy", "Apache Iggy" from Apache's Brand Management Team (Mark Thomas) ### 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 - [X] Other: Expanding ecosystem ### Date of last release: 2025-04-17 ### When were the last committers or PPMC members elected? February 2025, at the time of onboarding to Apache Incubator Program. ### Have your mentors been helpful and responsive? Yes, the mentors are very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? VP, Brand [approved the project name](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-236) ### Signed-off-by: - [ ] (iggy) Hao Ding Comments: - [X] (iggy) Yonik Seeley Comments: - [X] (iggy) Zili Chen Comments: - [X] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes:
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. Continue expanding the community, release more versions under ASF 2. Migrate all the repos from previous OSS repo https://github.com/orgs/iggy-rs/repositories to apache/iggy repo (mono repo with independent CI/CD) 3. Enhance iggy.apache.org with more details, guides, docs, blogs, benchmarks etc ### How has the community developed since the last report? 1. Discord members count approaching 400, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. 2. Github stars approaching 2.5k from 2.4k 3. Creates downloads crosses 124k vs 115k at the time of last report 4. Presented at [Rustmeet 2025](https://www.youtube.com/watch?v=v3bpw7fcjp0) 5. Presented at [Rustikon Conference 2025](https://www.youtube.com/watch?v=GkV306PyvqM) ### How has the project developed since the last report? 1. Apache Iggy (Incubating) [v0.4.300 released](https://lists.apache.org/thread/q3r6l0gcc27k1nj1q8frqwh40o0mhs4h) 2. Enhanced performance and efficiency: zero-copy (de)serialization [implemented](https://iggy.apache.org/blogs/2025/05/08/zero-copy-deserializa tion) for the server & updated SDK client 3. Restructuring the repository to support monorepo with multiple SDKs and other tooling (eg benchmarks) 4. Started migrating the SDKs from old repo (dotnet, java, node, web UI etc) 5. Successful POCs (with quickwit) for steaming messages into external connectors/sinks 6. Submitted detailed report for trademarks and received the [approval for the name](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-236) "Iggy", "Apache Iggy" from Apache's Brand Management Team (Mark Thomas) ### 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 - [X] Other: Expanding ecosystem ### Date of last release: 2025-04-17 ### When were the last committers or PPMC members elected? February 2025, at the time of onboarding to Apache Incubator Program. ### Have your mentors been helpful and responsive? Yes, the mentors are very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? VP, Brand [approved the project name](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-236) ### Signed-off-by: - [ ] (iggy) Hao Ding Comments: - [X] (iggy) Yonik Seeley Comments: - [X] (iggy) Zili Chen Comments: - [X] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes:
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. Continue expanding the community 2. Add client sdk repos under the main repo, setup CI/CD pipelines for release client sdks independently 3. Improve and extend documentation about various optimizations, configs to help onboard more users, developers easily ### 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? - Announced the Apache Incubator acceptance via blogs - Presented at a couple of Rust conferences - New members have joined the discord channel - Started leveraging Github Discussions on a the next set of core features: zero copy deserializaton, connectors, object storage etc - Since the incubation proposal: Number of downloads increased to ~115k from 90k, Github stars increased to 2.4k from 2.2k ### How has the project developed since the last report? - This is the first report - Migrated the external git repo to apache github account - Finished various onboarding tasks with the help from mentors, INFRA team - Created iggy-website git repo, launched the website iggy.apache.org - Updated the source code to use Apache License headers - Resolved various issues related the CI/CD pipelines, PR merge hooks etc - A major rewrite is underway for zero-copy deserialization, significantly increasing the performance and efficiencies, changes are tracked under the branch "zero-copy-no-batching" ### 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: We're still working on the first apache release. ### When were the last committers or PPMC members elected? February 2025, at the time of onboarding to Apache Incubator Program. ### Have your mentors been helpful and responsive? Yes, the mentors are very helpful. ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (iggy) Hao Ding Comments: - [X] (iggy) Yonik Seeley Comments: - [X] (iggy) Zili Chen Comments: - [X] (iggy) Hulk Lin Comments: ### IPMC/Shepherd notes: