Maturity
The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
More details can be found Apache Project Maturity Model.
Status of this assessment
This self-assessment was prepared during the incubation of Apache Fesod.
Maturity model assessment
The following table is filled according to the Apache Maturity Model. Mentors and community members are welcome to comment and modify it.
Code
| ID | Description | Status | Remark |
|---|---|---|---|
| CD10 | The project produces Open Source software for distribution to the public, at no charge. | YES ✅ | The project source code is licensed under the Apache License 2.0. |
| CD20 | Anyone can easily discover and access the project's code. | YES ✅ | The official website includes GitHub link which can access the project's repository on GitHub directly. |
| CD30 | Anyone using standard, widely-available tools, can build the code in a reproducible way. | YES ✅ | The code contribution guide explains how to build Apache Fesod (Incubating) using Java and Maven. |
| CD40 | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version. | YES ✅ | It depends on git, and anyone can view the full history of the project via commit logs. |
| CD50 | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance. | YES ✅ | The project uses GitHub, managed by Apache Infra. Git history and pull requests record authorship and review, and third-party contributions follow the contributing guidelines. |
Licenses and Copyright
| ID | Description | Status | Remark |
|---|---|---|---|
| LC10 | The Apache License, version 2.0, covers the released code. | YES ✅ | The project is licensed under the Apache License 2.0. Bundled third-party code retains its applicable license and attribution notices. |
| LC20 | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | YES ✅ | All dependencies are listed. |
| LC30 | The libraries mentioned in LC20 are available as Open Source software. | YES ✅ | All dependencies are listed are available as Open Source software. |
| LC40 | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | YES ✅ | All the committers have submitted and signed the Apache iCLA. |
| LC50 | The project clearly defines and documents the copyright ownership of everything that the project produces. | YES ✅ | Copyright and third-party attribution are documented in NOTICE and license notices. The treatment of inherited copyright headers is being clarified in LEGAL-737. |
Releases
| ID | Description | Status | Remark |
|---|---|---|---|
| RE10 | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | YES ✅ | Source releases are distributed via dist.apache.org and linked from the download page. |
| RE20 | The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation. | YES ✅ | Releases are voted on via dev@fesod.apache.org and approved by the IPMC via general@incubator.apache.org. Each stage requires at least three binding +1 votes and more binding +1 than -1 votes; only IPMC votes are binding for ASF release approval. See the 2.1.0 RC7 IPMC vote. |
| RE30 | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives. | YES ✅ | All releases are signed, and the KEYS are available. |
| RE40 | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee. | YES ✅ | User can easily build binaries from source code, and we do not provide binaries as Apache Releases. |
| RE50 | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | YES ✅ | The release guide documents how to prepare, vote on, and publish an Apache Fesod (Incubating) release. |
Quality
| ID | Description | Status | Remark |
|---|---|---|---|
| QU10 | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. | YES ✅ | We encourage user to report issues. |
| QU20 | The project puts a very high priority on producing secure software. | YES ✅ | Security reports are handled privately according to the security policy, with fixes and advisories coordinated through the ASF security process. |
| QU30 | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | YES ✅ | The official website provides a security page |
| QU40 | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. | YES ✅ | The project prioritizes backwards compatibility and documents incompatible changes in release notes and migration guides, including changes required for security fixes. |
| QU50 | The project strives to respond to documented bug reports in a timely manner. | YES ✅ | The community responds to bug reports and follows through on fixes. For example, issue #828 received a reproduction response on the day it was reported, followed by an update on the 2.0.1-incubating fix. |
Community
| ID | Description | Status | Remark |
|---|---|---|---|
| CO10 | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | YES ✅ | The official website includes all information user need to run Apache Fesod (Incubating). |
| CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project. | YES ✅ | We provide contributing guides for every component. And we also have a general contributing guide |
| CO30 | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | YES ✅ | All good contributions including code and non-code are welcomed. |
| CO40 | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project. | YES ✅ | During incubation, the community has added 3 new committers, including 1 who subsequently joined the PPMC, as recorded in the incubation status as of 2026-11-04. |
| CO50 | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently. | YES ✅ | The community has clear documents on nominating committers and PPMC members. |
| CO60 | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects. | YES ✅ | Decisions are made through community discussion and consensus, using formal votes where required. The CI approval discussion and issue #1009 show discussion, agreement, and follow-through. |
| CO70 | The project strives to answer user questions in a timely manner. | YES ✅ | The community answers questions through dev@fesod.apache.org, GitHub issues, and discussions. For example, issue #828 received an initial response within minutes and subsequent updates. |
Consensus Building
| ID | Description | Status | Remark |
|---|---|---|---|
| CS10 | The project maintains a public list of its contributors who have decision power. The project's PMC (Project Management Committee) consists of those contributors. | YES ✅ | See members with all PPMC members and committers. |
| CS20 | Decisions require a consensus among PMC members and are documented on the project's main communications channel. The PMC takes community opinions into account, but the PMC has the final word. | YES ✅ | The PPMC builds consensus while considering community input, and records decisions on the mailing lists. See the CI approval discussion and conclusion. Voting requirements depend on the type of decision. |
| CS30 | The project uses documented voting rules to build consensus when discussion is not sufficient. | YES ✅ | The project follows the ASF voting rules and its documented release process. The 2.0.0 RC3 vote result records binding and non-binding votes separately. |
| CS40 | In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30. | YES ✅ | Under the ASF voting rules, a code-commit veto requires technical justification and cannot be overridden by a majority vote. Release votes are not subject to veto. |
| CS50 | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | YES ✅ | Important discussions and conclusions are recorded asynchronously on dev@fesod.apache.org. For example, issue #1009 directs a proposed CI policy change to the mailing list for consensus before implementation. Personnel and undisclosed security matters use the appropriate private channels. |
Independence
| ID | Description | Status | Remark |
|---|---|---|---|
| IN10 | The project is independent from any corporate or organizational influence. | YES ✅ | Apache Fesod (Incubating) is governed by its community. Project decisions are made through community consensus, and no company has unilateral decision-making authority. |
| IN20 | Contributors act as themselves, not as representatives of a corporation or organization. | YES ✅ | The contributors act on their own initiative without representing a corporation or organization. |
Trademark and Branding
| ID | Description | Status | Remark |
|---|---|---|---|
| TB10 | The project uses "Apache Fesod™" as the project and software product name consistently, with appropriate trademark attributions. | YES ✅ | The project uses appropriately the trademark symbol. |
| TB20 | The project's primary homepage is at projectname.apache.org. When exceptions exist to use alternate domains for any purpose, any non-apache.org domain names are owned by the ASF. | YES ✅ | The project's homepage is at fesod.apache.org. |
| TB30 | The ASF has trademark rights, including any registrations, to the project name, logo, and any other major branding elements. | YES ✅ | ASF has the trademark rights. |
| TB40 | The project monitors for any major misuses of their project's brand by others, and reports any potential misuses to Brand Management. | YES ✅ | The PPMC monitors potential misuse of the project brand and follows the ASF reporting process. |