Page History

...

Metron provides instructions on how to validate and test as a part of every voting email.  Further more, there is a integration and unit test framework that runs during every Maven build to catch bugs at build time.  

Instructions on how to verify builds are provided here: Verifying Builds

An email template annoucing the build and providing a link to verification instructions can be found here: Build Vote Template[TODO] We need to establish documentation about these frameworks 

QU20The project puts a very high priority on producing secure software. 7

[TODO] We need to document our security guidelines As documented in our release instructions if a JIRA comes in that has security implications on Metron it is prioritized and a new build may be issued immediately upon it's resolution.  This process is documented here: Release Process [DRAFT]

QU30The project provides a well-documented channel to report security issues, along with a documented way of responding to them. 8

[TODO] Add Metron has a security board where security issues can be identified addressed.  The board as well as the instructions on how to the incubator status websitepost are documented in the Metron's incubation status page located here: Metron Incubation Status

QU40The 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.

...

CO10The project has a well-known homepage that points to all the information required to operate according to this maturity model.

[TODO] Align our website to better correspond to the items in this entryMetron's website is http://metron.incubator.apache.org/ and Metron's wiki has additional information that can be found here: Metron Wiki

CO20The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.

...

CO50The 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.

[TODO] We need to produce this documentation This process is outlined in the Metron Bylaws and can be found here: Apache Metron Bylaws

CO60The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects.

...

CS30Documented voting rules are used to build consensus when discussion is not sufficient. 10

[TODO] Need to produce this documentation Voting rules are documented in the Metron Bylaws located here: Apache Metron Bylaws

CS40In 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.

...