...
Code | Description | Status | Comments | |
---|---|---|---|---|
LC10 | The code is released under the Apache License, version 2.0. | see CD10 | ||
LC20 | Libraries that are mandatory dependencies of the project's code do not create | All dependencies included in release bundles have licenses compatible with the Apache License and are documented in the LICENSES file in the bundle | ||
LC30 | The libraries mentioned in LC20 are available as Open Source software. | |||
LC40 | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they are allowed to commit and how they need to identify code that is not their own. | All committers have signed ICLA's | ||
LC50 | The copyright ownership of everything that the project produces is clearly defined and documented. | The release bundle LICENSE and NOTICE files are accurate and complete |
Releases
Code | Description | Status | Comments | |
---|---|---|---|---|
RE10 | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | See https://edgent.apache.org/docs/downloads | ||
RE20 | Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. | |||
RE30 | Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. | |||
RE40 | Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee. | |||
RE50 | The release process is documented and repeatable to the extent that someone new to the project is able to independently generate the complete set of artifacts required for a release. | See Release Manager's Guide |
Quality
Code | Description | Status | Comments | |
---|---|---|---|---|
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 | |||
QU20 | The project puts a very high priority on producing secure software. | |||
QU30 | The project provides a well-documented channel to report security issues, along with a documented way of responding to them. | |||
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. | |||
QU50 | The project strives to respond to documented bug reports in a timely manner. | That is the goal and the results so far have generally been good. |
Community
Code | Description | Status | Comments | |
---|---|---|---|---|
CO10 | he The project has a well-known homepage that points to all the information required to operate according to this maturity model. | https://edgent.apache.org/ | ||
CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | The project homepage/website makes it clear that contributions are most welcome. The project has never refused any contributions. | ||
CO30 | Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | The project welcomes and recognizes all contributions that add value to the project. | ||
CO40 | The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. | So far three individuals who have shown commitment to the project have been voted in as committers and PPMC members. | ||
CO50 | The way in which contributors can be granted more rights such as commit access or decision power is clearly documented and is the same for all contributors. 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. | |||
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. | |||
CO70 | The project strives to answer user questions in a timely manner. | That is the goal and the results so far have generally been good. |
Consensus Building
Code | Description | Status | Comments | |
---|---|---|---|---|
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. | All committers are PMC members and committers are documented at http://incubator.apache.org/projects/edgent.html | ||
CS20 | Decisions are made by consensus among PMC members 9 and are documented on the project's main communications channel. | The project has voted on new committers, PPMC members, and a release using the appropriate channels. | ||
CS30 | Documented voting rules are used to build consensus when discussion is not sufficient. 10 | |||
CS40 | In Apache projects, vetoes are only valid for code commits and are justified by a technical explanation, as per the Apache voting rules defined in CS30.CS50All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions 11 t hat affect the project are also documented on that channel. |
...