Page History

.

Code

CD10The project produces Open Source software, for distribution to the public at no charge. 

...

1CD20The project's code is easily discoverable and publicly accessible.

All of Metron source code is staged in Github at the following URLgit: https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git  (mirrored on github at https://github.com/apache/incubator-metron).  Metron also has a website at the following URL: http://metron.incubator.apache.org/.  A Google search for "Apache Metron" brings up these links #4 and #1 on the list respectively. 

CD30The code can be built in a reproducible way using widely available standard tools.

All of Metron source code (not inclusive of build scripts and configuration files)  can be built via Maven from a top-level POM file

CD40The full history of the project's code is available via a source code control system, in a way that allows any released version to be recreated.

We maintain release branches per every Metron release in source control.  The list of release branches can be referenced here: https://github.com/apache/incubator-metron/releasesgit-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=heads

CD50The provenance of each line of code is established via the source code control system, in a reliable way based on strong authentication of the committer. When third-party contributions are committed, commit messages provide reliable information about the code provenance. 2

Full attribution to the committer is provided upon the merge of the pull request.  This is recorded in two places.  First, it is recorded when a pull request is committed.  Second, this is recorded in the JIRA workflow.

Licenses and Copyright

LC10The code is released under the Apache License, version 2.0.

All Metron code is released under the Apache 2.0 License.  We have had 4 sanctioned Apache releases that are staged here: https:as per http://distmetron.apache.org/repos/dist/release/incubator/metron/documentation/#releases

LC20Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. 3 4

...

We document copyrights of all included source code in compliance with Apache licensing standards.

Releases

RE10Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. 6

...

Our release process is documented here: Release Process

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.

...

We document bugs in the Metron JIRA as soon as we find them.  The Metron JIRA can be seen here: https://issues.apache.org/jira/browse/METRON/

Community

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

...

We strive to respond as quickly as we can to any question we see on the boards

Consensus Building

CS10The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors.

...

Metron uses lists as primary communication channels.  This communication is visible to all community.  If private conversations occur, they are documented on the boards to give visibility to all and no project decisions are ever made in private. 

Independence

IN10The project is independent from any corporate or organizational influence. 12

...