Page History

...

Zeppelin uses the standard apache distribution methods. Source and release packages are always be available at no charge on download page.

...

The project's code is easily discoverable and publicly accessible.

Yes

Source code are is available on git repository as well as on the mirror. Github mirror is provided for convenience.

...

Only Committers have write access to git repository. We guide recommend that every contribution contains enough informations in pull request description. When code mergesis merged, the merge script automatically include information of authorincludes author's informations, each commit hash and message as well as pull request description into commit message.

...

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

Yes 

LC30

The libraries mentioned in LC20 are available as Open Source software.

Yes 

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.

Yes 

LC50

The copyright ownership of everything that the project produces is clearly defined and documented.

Yes 

We provide LICENSE and NOTICE file for source release. As well as LICENSE and NOTICE for binary package

Releases

RE10

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

Yes 

Released source code is available through https://dist.apache.org/repos/dist/release/incubator/zeppelin in tgz format.

RE20

Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.

Yes 

Every release is approved by Incubator PMC. (while Zeppelin is in incubation, approval of PPMC is recommendation)

RE30

Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.

Yes 

Release are provided with KEYS and digests in download page for validation.

RE40

Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee.

...

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

No

We don't have communication channel dedicated to security issue.Yes 

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.

...

The project strives to respond to documented bug reports in a timely manner.

Yes  

Community

CO10

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

Yes 

Project has http://zeppelin.incubator.apache.org/ that points all informations.

...

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

Yes 

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.

Yes 

CO40

The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.

Yes 

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.

Yes 

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.

Yes 

CO70

The project strives to answer user questions in a timely manner.

Yes 

Consensus Building

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.

Yes 

We maintain the list of Committers in the project incubation status page.

CS20

Decisions are made by consensus among PMC members and are documented on the project's main communications channel. Community opinions are taken into account but the PMC has the final word if needed.

Yes 

CS30

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

Yes 

Documented voting rules are used for code commit.

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.

Yes 

CS50

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

Yes 

Independence

IN10

The project is independent from any corporate or organizational influence.

Yes 

IN20

Contributors act as themselves as opposed to representatives of a corporation or organization.

Yes