DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| 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 |  | Known issues are tracked in JIRA for public viewing | |
| 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. | TODO: Add a page to the website with this information. Suggestion: Issues should be reported to the ppmc,(pmc once we graduate) and a pubic JIRA created when a resolution is available. | ||
| 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. | | Edgent provides documentation on our website and will take care to preserve backward compatibility and announce any changes in behavior that are necessary because of security or other concerns. | |
| 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. |
...
| Code | Description | Status | Comments | |
|---|---|---|---|---|
| CO10 | 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. | | Information on how to become a committer is documented here http://edgent.incubator.apache.org/docs/committers. | |
| 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. | | In incubation Edgent has been successful in conducting open discussions, encouraging participation and reaching friendly consensus. | |
| 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. |
...
| 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 | | Edgent uses the Apache rules at http://www.apache.org/foundation/voting.html | |
| 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. | | All decisions are made on the list. |
Independence
| Code | Description | Status | Comments | |
|---|---|---|---|---|
| IN10 | The project is independent from any corporate or organizational influence. | | committers and participants that work for corporations appear to understand their Apache hat and make decisions based on the good of the project and appear to be independent. | |
| IN20 | Contributors act as themselves as opposed to representatives of a corporation or organization. | | See IN10 |
Related efforts, inspiration
- http://oss-watch.ac.uk/resources/ssmm
- http://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/
- https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
- http://rfc.zeromq.org/spec:16
- http://oss-watch.ac.uk/resources/reusereadinessrating
- http://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration
- https://www.apache.org/dev/project-requirements
Footnotes
- "For distribution to the public at no charge" is straight from the from the ASF Bylaws at http://apache.org/foundation/bylaws.html. (1)
- See also LC40. (2)
- It's ok for platforms (like a runtime used to execute our code) to have different licenses as long as they don't impose reciprocal licensing on what we are distributing. (3)
- http://apache.org/legal/resolved.html has information about acceptable licenses for third-party dependencies (4)
- In Apache projects, the ASF owns the copyright for the collective work, i.e. the project's releases. Contributors retain copyright on their contributions but grant the ASF a perpetual copyright license for them. (5)
- See http://www.apache.org/dev/release.html for more info on Apache releases (6)
- The required level of security depends on the software's intended uses, of course. Expectations should be clearly documented. (7)
- Apache projects can just point to http://www.apache.org/security/ or use their own security contacts page, which should also point to that. (8)
- In Apache projects, "consensus" means widespread agreement among people who have decision power. It does not necessarily mean "unanimity". (9)
- For Apache projects, http://www.apache.org/foundation/voting.html defines the voting rules. (10)
- Apache projects have a private mailing list that their PMC is expected to use only when really needed. The private list is typically used for discussions about people, for example to discuss and to vote on PMC candidates privately. (11)
- Independence can be understood as basing the project's decisions on the open discussions that happen on the project's main communications channel, with no hidden agendas. (12)
...