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 |
|---|---|---|
| 2025-07-16 | Appointed Chaokun Yang | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2025-07-16 | Establish the Apache Fory Project | special order | approved |
The Apache Fory is a high-performance, multi-language serialization framework that enables efficient data exchange across systems and programming languages. Leveraging JIT compilation and zero-copy techniques, Fory delivers low-latency, high-throughput serialization for modern distributed applications. Project Status: Ongoing with high activity. Board-Level Issues: There are no issues requiring Board action at this time. Over the past quarter, the Apache Fory project has made significant progress in core development, documentation, and community growth. Key efforts have focused on advancing compiler/python/go/java/csharp/javascript/swift implementations, and enhancing user experience through better documentation. The community remains active and engaged, with steady contributions from both long-standing and new contributors. Recent Releases: The project has maintained a strong release cadence over the past quarter: - v0.16.1 May 17, 2026 - v0.15.0 Feb 10, 2026 These releases include performance improvements, bug fixes, expanded language support, and enhanced developer tooling. We released official support for Fory Compiler, CSharp, Swift in last quarter. Project Activity: Development activity remains robust, with ongoing work across multiple fronts: Continuous improvement of documentation for users and contributors; Active development on Fory implementations in compiler, csharp, and swift Current Plans: The project’s roadmap for the coming months includes: - Cleanup API, docs and Release 1.0 - Add GRPC support - Attracting new contributors via outreach and improved contribution guides Further enhancing user and contributor documentation to lower entry barriers We are also exploring opportunities for collaboration with other Apache projects to demonstrate cross-project interoperability. New Committers and PMC Members: Committer: Yuyang Liu was added on Oct 04, 2025 PMC Member: Pan Li was added on June 4, 2025 These additions reflect the project’s healthy growth and commitment to empowering active contributors. Branding and Legal Considerations: There are no known branding or legal issues at this time. The project continues to use its name and marks in accordance with Apache policies. All official project materials reflect proper branding and attribution. Infrastructure and Strategic Needs: No critical infrastructure issues have been encountered. The project is satisfied with current tooling and services provided by the Apache Infrastructure team.
The Apache Fory is a high-performance, multi-language serialization framework that enables efficient data exchange across systems and programming languages. Leveraging JIT compilation and zero-copy techniques, Fory delivers low-latency, high-throughput serialization for modern distributed applications. Project Status: Ongoing with high activity. Over the past quarter, the Apache Fory project has made significant progress in core development, documentation, and community growth. Key efforts have focused on advancing rust/python/go/java implementations, and enhancing user experience through better documentation. The community remains active and engaged, with steady contributions from both long-standing and new contributors. Recent Releases: The project has maintained a strong release cadence over the past quarter: v0.14.1 Dec 26, 2025 v0.14.0 Dec 15, 2025 v0.13.2 Dec 05, 2025 v0.13.1 Nov 06, 2025 v0.13.0 — Oct 27, 2025 These releases include performance improvements, bug fixes, expanded language support, and enhanced developer tooling. We released official support for Fory Rust and C++ in last quarter. Project Activity: Development activity remains robust, with ongoing work across multiple fronts: Continuous improvement of documentation for users and contributors; Active development on Fory implementations in Rust, Python, and Go Current Plans: The project’s roadmap for the coming months includes: Reaching General Availability (GA) status for the C++, and Go language bindings Expanding adoption through outreach and integration examples Attracting new contributors via outreach and improved contribution guides Further enhancing user and contributor documentation to lower entry barriers We are also exploring opportunities for collaboration with other Apache projects to demonstrate cross-project interoperability. New Committers and PMC Members: Committer: Yuyang Liu was added on Oct 04, 2025 PMC Member: Pan Li was added on June 4, 2025 These additions reflect the project’s healthy growth and commitment to empowering active contributors. Branding and Legal Considerations: There are no known branding or legal issues at this time. The project continues to use its name and marks in accordance with Apache policies. All official project materials reflect proper branding and attribution. Infrastructure and Strategic Needs: No critical infrastructure issues have been encountered. The project is satisfied with current tooling and services provided by the Apache Infrastructure team. Board-Level Issues: There are no issues requiring Board action at this time.
The Apache Fory is a high-performance, multi-language serialization framework that enables efficient data exchange across systems and programming languages. Leveraging JIT compilation and zero-copy techniques, Fory delivers low-latency, high-throughput serialization for modern distributed applications. Project Status: Ongoing with high activity. Over the past quarter, the Apache Fory project has made significant progress in core development, documentation, and community growth. Key efforts have focused on advancing rust/python/go/java implementations, and enhancing user experience through better documentation. The community remains active and engaged, with steady contributions from both long-standing and new contributors. Recent Releases: The project has maintained a strong release cadence over the past quarter: 1) v0.12.3 September 23, 2025 2) v0.12.2 September 8, 2025 3) v0.12.1 September 1, 2025 4) v0.12.0 August 18, 2025 5) v0.11.2 — July 10, 2025 These releases include performance improvements, bug fixes, expanded language support, and enhanced developer tooling. Project Activity: Development activity remains robust, with ongoing work across multiple fronts: 1) Continuous improvement of documentation for users and contributors; 2) Active development on Fory implementations in Rust, Python, and Go Current Plans: The project’s roadmap for the coming months includes: 1) Reaching General Availability (GA) status for the Python, Rust, and Go language bindings 2) Expanding adoption through outreach and integration examples 3) Attracting new contributors via outreach and improved contribution guides 4) Further enhancing user and contributor documentation to lower entry barriers We are also exploring opportunities for collaboration with other Apache projects to demonstrate cross-project interoperability. New Committers and PMC Members: 1) Committer: Yuyang Liu was added on Oct 04, 2025 2) PMC Member: Pan Li was added on June 4, 2025 These additions reflect the project’s healthy growth and commitment to empowering active contributors. Branding and Legal Considerations: There are no known branding or legal issues at this time. The project continues to use its name and marks in accordance with Apache policies. All official project materials reflect proper branding and attribution. Infrastructure and Strategic Needs: No critical infrastructure issues have been encountered. The project is satisfied with current tooling and services provided by the Apache Infrastructure team. Board-Level Issues: There are no issues requiring Board action at this time.
The Apache Fory is a high-performance, multi-language serialization framework that enables efficient data exchange across systems and programming languages. Leveraging JIT compilation and zero-copy techniques, Fory delivers low-latency, high-throughput serialization for modern distributed applications. Project Status: Ongoing with high activity. Over the past quarter, the Apache Fory project has made significant progress in core development, documentation, and community growth. Key efforts have focused on advancing language implementations, improving release infrastructure, and enhancing user experience through better documentation. The community remains active and engaged, with steady contributions from both long-standing and new contributors. Recent Releases: The project has maintained a strong release cadence over the past quarter: 1) v0.12.1 September 1, 2025 2) v0.12.0 August 18, 2025 3) v0.11.2 — July 10, 2025 4) v0.11.1 June 27, 2025 5) v0.11.0 June 17, 2025 These releases include performance improvements, bug fixes, expanded language support, and enhanced developer tooling. Project Activity: Development activity remains robust, with ongoing work across multiple fronts: 1) Continuous improvement of documentation for users and contributors; 2) Refinement of the release pipeline to improve reliability and automation 3) Active development on Fory implementations in Rust, Python, and Go Current Plans: The project’s roadmap for the coming months includes: 1) Reaching General Availability (GA) status for the Python, Rust, and Go language bindings 2) Expanding adoption through outreach and integration examples 3) Attracting new contributors via outreach and improved contribution guides 4) Further enhancing user and contributor documentation to lower entry barriers We are also exploring opportunities for collaboration with other Apache projects to demonstrate cross-project interoperability. New Committers and PMC Members: 1) Committer: Emre Şafak was added on August 28, 2025 2) PMC Member: Pan Li was added on June 4, 2025 These additions reflect the project’s healthy growth and commitment to empowering active contributors. Branding and Legal Considerations: There are no known branding or legal issues at this time. The project continues to use its name and marks in accordance with Apache policies. All official project materials reflect proper branding and attribution. Infrastructure and Strategic Needs: No critical infrastructure issues have been encountered. The project is satisfied with current tooling and services provided by the Apache Infrastructure team. Board-Level Issues: There are no issues requiring Board action at this time.
No report was submitted.
A blazing fast multi-language serialization framework powered by jit and zero-copy Fury has been incubating since 2023-12-15. ### Three most important unfinished issues to address before graduating: 1. Grow the community(attracting more committers, contributors, and users). 2. Add more PPMC members and release managers ### 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? Steady progress. Made 3 releases, and added two new release managers. ### How has the project developed since the last report? 3 releases. The most recent was v0.10.2 on May 6, 2025. ### 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-05-06 ### When were the last committers or PPMC members elected? 2025-04-06, added new committer LofiSu ### Have your mentors been helpful and responsive? Yes, the mentors helped a lot for version releases and community governance. ### Is the PPMC managing the podling's brand / trademarks? Apache Fury will renamed to Apache Fory. The VP has approved the new name. ### Signed-off-by: - [X] (fury) tison Comments: - [X] (fury) PJ Fanning Comments: Project name is due to change to Fory over the next few months. - [ ] (fury) Yu Li Comments: - [X] (fury) Xin Wang Comments: - [ ] (fury) Enrico Olivelli Comments: - [ ] (fury) Hao Ding Comments: ### IPMC/Shepherd notes:
A blazing fast multi-language serialization framework powered by jit and zero-copy Fury has been incubating since 2023-12-15. ### Three most important unfinished issues to address before graduating: 1. Grow the community(attracting more committers, contributors, and users). 2. Add more PPMC members and release managers ### 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? Steady progress. Made 3 releases, and added two new release managers. ### How has the project developed since the last report? 3 releases. The most recent was v0.10.2 on May 6, 2025. ### 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-05-06 ### When were the last committers or PPMC members elected? 2025-04-06, added new committer LofiSu ### Have your mentors been helpful and responsive? Yes, the mentors helped a lot for version releases and community governance. ### Is the PPMC managing the podling's brand / trademarks? Apache Fury will renamed to Apache Fory. The VP has approved the new name. ### Signed-off-by: - [X] (fury) tison Comments: - [X] (fury) PJ Fanning Comments: Project name is due to change to Fory over the next few months. - [ ] (fury) Yu Li Comments: - [X] (fury) Xin Wang Comments: - [ ] (fury) Enrico Olivelli Comments: - [ ] (fury) Hao Ding Comments: ### IPMC/Shepherd notes:
A blazing fast multi-language serialization framework powered by jit and zero-copy Fury has been incubating since 2023-12-15. ### Three most important unfinished issues to address before graduating: 1. Grow the community(attracting more committers, contributors, and users). 2. Improve project documentation and align the implementation of Java/Python/JavaScript/Golang/Rust. 3. Add more PPMC members and release managers. ### 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? Steady progress ### How has the project developed since the last report? 2 releases. The most recent was v0.9.0 on Nov 10, 2024. ### 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: 2024-11-10 ### When were the last committers or PPMC members elected? 2024-11-30, added new committer pandalee99 ### Have your mentors been helpful and responsive? Yes, the mentors helped a lot for version releases and community governance. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues. ### Signed-off-by: - [ ] (fury) tison Comments: - [X] (fury) PJ Fanning Comments: Steady Progress - [ ] (fury) Yu Li Comments: - [X] (fury) Xin Wang Comments: Steady progress - [ ] (fury) Enrico Olivelli Comments: - [ ] (fury) Hao Ding Comments: ### IPMC/Shepherd notes:
A blazing fast multi-language serialization framework powered by jit and zero-copy Fury has been incubating since 2023-12-15. ### Three most important unfinished issues to address before graduating: 1. Grow the community(attracting more committers, contributors, and users) 2. Publish Apache releases 3. Improve project documentation and align the implementation of Java/Python/JavaScript/C++/Golang/Rust. ### 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. Nominated a new committer @LiangliangSui 2. 3 new contributors joined the Fury community ### How has the project developed since the last report? 1. Created 89 PR in last month 2. Implemented meta string encoding 3. Implemented streaming deserialization in java 4. Implemented chunk based map serialization in javascript 5. Performance improvements ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] The first release is expected to be released within next days - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: We haven't make a release since join Apache incubator, but the first release is expected to be released within next days. ### When were the last committers or PPMC members elected? 2024-04-23 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No ### Signed-off-by: - [X] (fury) tison Comments: The first source release is out. You can work on the multilingual libraries and advocate to more users and contributors. - [X] (fury) PJ Fanning Comments: Progress has been good and first ASF release was made on 2024-05-03 - [X] (fury) Yu Li Comments: Good to see the first ASF release accomplished and community built up in a healthy way. - [ ] (fury) Xin Wang Comments: - [ ] (fury) Enrico Olivelli Comments: ### IPMC/Shepherd notes:
A blazing fast multi-language serialization framework powered by jit and zero-copy Fury has been incubating since 2023-12-15. ### Three most important unfinished issues to address before graduating: 1. Grow the community(attracting more committers, contributors, and users) 2. Publish Apache releases 3. Improve project documentation and align the implementation of Java/Python/JavaScript/C++/Golang/Rust. ### 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? 1. We started the community vote of the first release. 2. We received 7 new issues and closed 6 issues. 3. Community development wasn't grown too much in last month. The main reason is probably due to core committers were engaged in the first release and the standardization of fury serialization protocol. But there were some new developers continuing contributing to fury in recent months. ### How has the project developed since the last report? 1. Created 28 PR in last month 2. Standardized the fury cross-language serialization protocol, which will make the project develop ### 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: ### Date of last release: We haven't make a release since Fury joined Apache incubator. ### When were the last committers or PPMC members elected? We haven't elected new committers or PPMC members. Currently all the committers and PPMC members are the initial committers. ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No ### Signed-off-by: - [X] (fury) tison Comments: - [X] (fury) PJ Fanning Comments: - [X] (fury) Yu Li Comments: Good to see the first apache release on the way. - [ ] (fury) Xin Wang Comments: - [ ] (fury) Enrico Olivelli Comments: ### IPMC/Shepherd notes:
A blazing fast multi-language serialization framework powered by jit and zero-copy Fury has been incubating since 2023-12-15. ### Three most important unfinished issues to address before graduating: 1. Standardize cross-language serialization protocol of Fury. 2. Align the serialization implementation of Java/Python/JavaScript/C++/Golang/Rust to the cross-language serialization protocol. 3. Grow the community (attracting more committers, contributors, users) ### 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? This is the first report for Fury. We attracted about 10 new contributors since Fury started incubating in 2023-12-15. ### How has the project developed since the last report? This is the first report for Fury. The main progress are: 1. Standardized Fury java serialization protocol. 2. Optimized Fury JavaScript performance. ### 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: ### Date of last release: We haven't made a release since Fury joined the Apache incubator. ### When were the last committers or PPMC members elected? We haven't elected new committers or PPMC members. Currently all the committers and PPMC members are the initial committers. ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? No. ### Signed-off-by: - [X] (fury) tison Comments: Let's try to make the first release in the following two months. - [X] (fury) PJ Fanning Comments: All looking good - [X] (fury) Yu Li Comments: Good to see all necessary infra are set for the project and the team is working towards the first release as an incubator project. - [X] (fury) Xin Wang Comments: The team is working towards the first Apache release. - [X] (fury) Enrico Olivelli Comments: LGTM, Probably points 1 and 2 are not strictly needed for graduation (they look more nice-to-have) ### IPMC/Shepherd notes: jmclean: Points 1 and 2 don't have anything to do with graduation. Try not to focus on functionality in the next report.
