Page History

...

Code	Description	Comments
CD10	The project produces Open Source software, for distribution to the public at no charge.	Available from download page with Apache license http://hudi.incubator.apache.org/docs/downloads
CD20	The project's code is easily discoverable and publicly accessible.	See CD10
CD30	The code can be built in a reproducible way using widely available standard tools.	Maven build process documented in README.md
CD40	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 source is available here and release is tagged.
CD50	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 to provide reliable information about the code provenance.

Licenses and Copyright

Code	Description	Comments
LC10	The code is released under the Apache License, version 2.0.	see CD10
LC20	Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.	All dependencies included in release bundles have licenses compatible with the Apache License and are documented in the LICENSES file in the bundle
LC30	The libraries mentioned in LC20 are available as Open Source software.	All libraries are available as Open Source software and documented in the LICENSES file
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.	All committers have signed ICLA's
LC50	The copyright ownership of everything that the project produces is clearly defined and documented.	The release bundle LICENSE and NOTICE files are accurate and complete

...

Code	Description	Comments
RE10	Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.	See https://hudi.apache.org/docs/downloads
RE20	Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.
RE30	Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.
RE40	Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee.
RE50	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.	See See Release Manager's Guide

Code	Description	Comments
QU10	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	Known issues are tracked in JIRA for public viewing
QU20	The project puts a very high priority on producing secure software.
QU30	The project provides a well-documented channel to report security issues, along with a documented way of responding to them.	TODO: Add a page to the website with this information. Suggestion: Issues should be reported to the ppmc,(pmc once we graduate) and a pubic JIRA created when a resolution is available.
QU40	The project puts a high priority on backward compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features.	Hudi provides documentation on our website and will take care to preserve backward compatibility and announce any changes in behavior that are necessary because of security or other concerns.
QU50	The project strives to respond to documented bug reports in a timely manner.	That is the goal and the results so far have generally been good.

...