This was extracted (@ 2025-10-29 19:10) from a list of  minutes
which have been approved by the Board.  
  
  Please Note
      The Board typically approves the minutes of the previous meeting at the
      beginning of every Board meeting; therefore, the list below does not
      normally contain details from the minutes of the most recent Board meeting.
      ASF Members may have access to a
  private draft
  
  
  WARNING: these pages may omit some original contents of the minutes.
  
  
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: