Podling maturity evaluation of Apache DataFu based on the Apache project maturity model as of 2/27/2017.
Code
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| The project produces Open Source software, for distribution to the public at no charge. | The project has always been open source and distributed for free at no charge. | mhayes,eyal |
| The project's code is easily discoverable and publicly accessible. | A Google search https://www.google.com/search?q=datafu easily finds the project home page https://datafu.incubator.apache.org/ and source https://github.com/apache/incubator-datafu on the GitHub mirror. | mhayes,eyal |
| The code can be built in a reproducible way using widely available standard tools. | The code is built using Gradle, a widely used build tool. Instructions for building the code are documented: https://github.com/apache/incubator-datafu/blob/master/README.md | mhayes,eyal |
| The 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. | The full history of the project is available in git. Each release candidate is tagged in git in a consistent way (e.g. release-1.3.2-rc0). Each release has a distinct branch (e.g. 1.3.2). This makes it possible to reconstruct the release from source history. Instructions for releasing are clearly documented in https://github.com/apache/incubator-datafu/blob/master/RELEASE.md. | mhayes,eyal |
| The 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. | This is established by the git commit history: https://github.com/apache/incubator-datafu | mhayes,eyal |
Licenses and Copyright
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| The code is released under the Apache License, version 2.0. | https://github.com/apache/incubator-datafu/blob/master/LICENSE | mhayes,eyal |
| Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | The datafu-pig library bundles other libraries that are also Apache-2.0 licensed. datafu-hourglass does not bundle other libraries. The datafu-pig library has no further dependencies to use it. The datafu-hourglass library only depends on either Apache-2.0 licensed libraries or libraries that are no more restrictive than Apache 2.0. | mhayes,eyal |
| The libraries mentioned in LC20 are available as Open Source software. | All dependences mentioned in LC20 are open source. | mhayes,eyal |
| 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. | All committers have completed the ICLA. | mhayes,eyal |
| The copyright ownership of everything that the project produces is clearly defined and documented. | All necessary files have a header covering license ownership. This can be verified with the rat task in the build system. Any other copyright information is available in the LICENSE files. | mhayes,eyal |
Releases
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | http://ftp.wayne.edu/apache/incubator/datafu/apache-datafu-incubating-1.3.1 | samshah, mhayes,eyal |
| Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. | http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201511.mbox/%3CCAA4Vo8BR_-8whhNYr6jUdXTrE2ZYZWwJEx2XvgHDt22SRyr55w%40mail.gmail.com%3E | samshah, mhayes,eyal |
| Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. | http://ftp.wayne.edu/apache/incubator/datafu/apache-datafu-incubating-1.3.1/apache-datafu-incubating-sources-1.3.1.tgz.SHA-512 | samshah, mhayes,eyal |
| Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee. | Binary releases are available here: | samshah, mhayes,eyal |
| The release process is documented and repeatable to the extent that someone new to the project is able to independently generate the complete set of artifacts required for a release. | https://github.com/apache/incubator-datafu/blob/master/RELEASE.md | samshah, mhayes,eyal |
Quality
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| 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. | Yes. For example, there is a unit test for each PIG UDF and for Hourglass. And test cases are added and kept up to date, e.g., https://issues.apache.org/jira/browse/DATAFU-106 | mitultiwari, mhayes,eyal |
| The project puts a very high priority on producing secure software. | Yes. | mitultiwari, mhayes,eyal |
| The project provides a well-documented channel to report security issues, along with a documented way of responding to them. | Security issues are to be reported to the private mailing list, as explained here: http://datafu.incubator.apache.org/community/issues.html | mhayes, samshah, rjurney, eyal |
| 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. | Yes, through Jira and release notes. | mitultiwari, mhayes,eyal |
| The project strives to respond to documented bug reports in a timely manner. | Yes, through Jira and release notes. | mitultiwari, mhayes,eyal |
Community
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| The project has a well-known homepage that points to all the information required to operate according to this maturity model. | https://datafu.incubator.apache.org/ | mhayes,eyal, samshah |
| The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | No examples of unkind or rejecting behavior could be found in a search through the e-mail list. | mhayes,eyal, samshah |
| Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | Committers are evaluated on all these categories of contribution. | mhayes,eyal, samshah |
| The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. | New committers include: * Russell Jurney * Casey Stella * Eyal Allweil * Jian Wang | mhayes,eyal, samshah |
| 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. | Becoming a Committer | mhayes, samshah, eyal |
| 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. | mhayes, samshah, eyal | |
| The project strives to answer user questions in a timely manner. | mhayes, samshah, eyal |
Consensus Building
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors. | Public list of contributors with decision power are available here: http://incubator.apache.org/projects/datafu | mhayes, samshah, eyal |
| 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. | Decisions are documented in the dev mailing list documented at http://datafu.incubator.apache.org/community/mailing-lists.html and in JIRAs tracked in the Bugs link. | mhayes,eyal |
| Documented voting rules are used to build consensus when discussion is not sufficient. | The Apache DataFu community fully accepts standard ASF voting rules as detailed here: https://www.apache.org/foundation/voting.html | mhayes, samshah, eyal |
| 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. | Vetoes are only valid for code commits and are justified by a technical explanation | mhayes, samshah, eyal |
| All "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. | All important discussions happen in the documented communication channels, which is either the dev mailing list or in JIRAs. Any offline communication that happens is documented in those channels. | mhayes,eyal, samshah, eyal |
Independence
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| The project is independent from any corporate or organizational influence. | Committers come from at least the following organizations:
Having committers from a diverse set of companies means independence from the influence of any one company. Also committers are not paid by their organizations to work on DataFu specifically. | mhayes,eyal |
| Contributors act as themselves as opposed to representatives of a corporation or organization. | None of the contributors act as representatives of a corporation or organization and only act for themselves. | mhayes,eyal |