Graduation Checklist
A working maturity assessment for Apache Iggy as it prepares for eventual graduation from the Apache Incubator.
Overview
This checklist is based on the Apache Project Maturity Model and the Apache Incubator graduation guide. It is intended to help mentors, the PPMC and the community track the remaining work before proposing graduation.
Next Steps
- Create or link an umbrella graduation issue for open checklist items.
- Confirm podling status-file tasks are complete and signed off.
- Refresh dependency, license, security and release-process checks.
- Document community diversity and recent committer or PPMC growth.
- Review branding, trademark attribution and website readiness.
Maturity Model Assessment
Last Updated: July 31, 2026.
Code
| ID | Description | Status |
|---|---|---|
| CD10 | The project produces open source software for distribution to the public at no charge. | YES. Apache Iggy source code is distributed under the Apache License, Version 2.0. |
| CD20 | Anyone can easily discover and access the project's code. | YES. Source code is linked from the website and hosted in Apache repositories mirrored on GitHub. |
| CD30 | Anyone using standard, widely available tools can build the code in a reproducible way. | YES. All details and instructions are documented in the README.md file of Iggy's Git repo |
| CD40 | The full history of the project's code is available through source control. | YES. Apache Iggy uses Git, with release tags available for published source releases. |
| CD50 | The source control system establishes reliable code provenance. | YES. Apache-managed Git repositories and pull request history provide provenance for committed work. |
Licenses and Copyright
| ID | Description | Status |
|---|---|---|
| LC10 | The Apache License, Version 2.0, covers the released code. | YES. The project includes license files and Apache license headers. |
| LC20 | Mandatory dependencies do not create restrictions beyond the Apache License. | YES. All dependencies are listed. |
| LC30 | Mandatory dependencies are available as open source software. | YES. All dependencies are listed are available as Open Source software |
| LC40 | Committers are bound by an Apache Individual Contributor License Agreement. | YES. All committers have filed their respecrive ICLAs. |
| LC50 | Copyright ownership of project outputs is clearly defined and documented. | YES. And all source files are with APLv2 header |
Releases
| ID | Description | Status |
|---|---|---|
| RE10 | Releases consist of source code distributed using standard archive formats. | YES. Source release is distributed via dist.apache.org and linked from Downloads page on iggy.apache.org website. |
| RE20 | The PPMC and Incubator approve releases as acts of the Foundation. | YES. All releases have been voted at dev@iggy.apache.org and general@incubator.apache.org, and have at least 3 PPMC member votes. |
| RE30 | Releases are signed or distributed with digests for validation. | YES. Downloads include signatures, SHA-512 checksums and KEYS guidance. |
| RE40 | Convenience binaries are clearly distinguished from Apache releases. | YES. Users can easily build binaries from source code, and we do not provide binaries as Apache Releases. |
| RE50 | The release process is documented and repeatable by a new release manager. | YES. The How to Release page under Community section on iggy.apache.org website described the steps. |
Quality
| ID | Description | Status |
|---|---|---|
| QU10 | The project is open and honest about code quality and module maturity. | YES. We encourage users to report issues on GitHub. |
| QU20 | The project puts a high priority on secure software. | YES. Security-sensitive work should continue to be handled with high priority. |
| QU30 | The project provides a documented channel for reporting security issues. | YES. We encourage users to report issues on GitHub and Security page link provided under ASF menu on the website iggy.apache.org |
| QU40 | The project prioritizes backward compatibility and documents incompatible changes. | YES. We follow semantic versions. As long as it's within one major version, it's backward compatible. And when any breaking changes added, we provide clear communication and upgrade guides when applicable. |
| QU50 | The project strives to respond to documented bug reports in a timely manner. | YES. As of July 31, 2026, The project has resolved ~1000 issues and 2500+ pull requests so far, with very prompt response. The community is very active on the Discord channel as well. |
Community
| ID | Description | Status |
|---|---|---|
| CO10 | The project homepage points to the information required by the maturity model. | YES. The official website and README.md file in the Git repo includes all information that the users need to run Apache Iggy. |
| CO20 | The community welcomes good-faith contributions that add value. | YES. We have 100+ contributors. Contribution paths are documented and public discussion channels are available. |
| CO30 | Contributions include code, documentation, bug reports, discussions and other project value. | YES. All good contributions including code and non-code are welcomed. |
| CO40 | The community is meritocratic and grants more responsibility over time. | YES. The community has elected 5 new committers since joining Apache Incubator, with a total of 19 Committers. |
| CO50 | The project documents how contributors can earn commit access or decision power. | YES. The community has clear docs on nominating committers. |
| CO60 | The community operates by consensus among members with decision power. | YES. All decisions are made after vote by community members. |
| CO70 | The project strives to answer user questions promptly. | YES. We use dev@iggy.apache.org, GitHub issues and GitHub discussions to do this in a timely manner. We're also active on the Discord channel. |
Consensus Building
| ID | Description | Status |
|---|---|---|
| CS10 | The project maintains a public list of contributors with decision power. | YES. The Team page links to the canonical Apache roster and lists PPMC members, mentors and committers. |
| CS20 | Decisions are made by consensus and documented on the main communication channel. | YES. All decisions are made by votes on dev@iggy.apache.org, and with at least 3 +1 votes from PPMC. |
| CS30 | Documented voting rules are used when discussion is not sufficient. | YES. The project uses the standard ASF voting rules. |
| CS40 | Vetoes are limited to code commits and justified with technical explanations. | YES. Continue following ASF voting and veto expectations. |
| CS50 | Important discussions happen asynchronously in written form. | YES. All important discussions and conclusions are recorded in written form on GitHub issues and discussions. |
Independence
| ID | Description | Status |
|---|---|---|
| IN10 | The project is independent from corporate or organizational influence. | YES. The current PPMC includes long-time Apache committers and PMC members, along with engineers from LaserData, Inc., the company that donated Iggy to the Apache Software Foundation in February 2025. There are many Committers outside this company, who are on the path to become PPMC/PMC members. |
| IN20 | Contributors act as themselves, not as representatives of employers or organizations. | YES. Continue reinforcing individual participation in votes, reviews and decisions. |
Trademark and Branding
| ID | Description | Status |
|---|---|---|
| TB10 | The project uses the Apache project name consistently with trademark attribution. | YES. Continue using Apache Iggy (Incubating) in formal contexts until graduation. |
| TB20 | The primary homepage is at an apache.org domain and non-apache.org domains are ASF-owned when used. | YES. The public websites are served from iggy.apache.org and benchmarks.iggy.apache.org. No non-apache.org domain names are used. |
| TB30 | The ASF has trademark rights to the project name, logo and major branding elements. | YES. As an incubating project, Apache Iggy is not yet on the ASF page https://www.apache.org/foundation/marks/list/, but the ASF holds common law trademark rights through the incubation process. The project name, logo, and all branding assets are hosted exclusively on ASF infrastructure (iggy.apache.org). Formal trademark registration is typically pursued upon graduation. |
| TB40 | The project monitors major brand misuse and reports potential misuse to ASF Brand Management. | YES. No major misuses of the Apache Iggy brand have been identified to date. The PPMC should continue monitoring public use of Apache Iggy marks. |