Page History

...

Our release process is documented here: Release Process [DRAFT]

Quality

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

...

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

...

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.

[TODO] We need to clearly state this in our bylaws A specific provision for this was recently added into the Metron Bylaws and was voted on and approved by the Metron community.  The document is located here: Apache Metron Bylaws

CS50All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions 11 that affect the project are also documented on that channel.

...