Page History

...

Code	Description	Status	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.apache.org/releases.html
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.		Code contributions and commit process documented  at https://hudi.apache.org/contributing.html

Licenses and Copyright

Code	Description	Status	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	Status	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 http://hudi.apache.org/releases.html
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 Release Manager's Guide

...

1. "For distribution to the public at no charge" is straight from the ASF Bylaws at http://apache.org/foundation/bylaws.html. (1)
2. See also LC40. (2)
3. It's ok for platforms (like a runtime used to execute our code) to have different licenses as long as they don't impose reciprocal licensing on what we are distributing. (3)
4. http://apache.org/legal/resolved.html has information about acceptable licenses for third-party dependencies (4)
5. In Apache projects, the ASF owns the copyright for the collective work, i.e. the project's releases. Contributors retain copyright on their contributions but grant the ASF a perpetual copyright license for them. (5)
6. See http://www.apache.org/dev/release.html for more info on Apache releases (6)
7. The required level of security depends on the software's intended uses, of course. Expectations should be clearly documented. (7)
8. Apache projects can just point to http://www.apache.org/security/ or use their own security contacts page, which should also point to that. (8)
9. In Apache projects, "consensus" means widespread agreement among people who have decision power. It does not necessarily mean "unanimity". (9)
10. For Apache projects, http://www.apache.org/foundation/voting.html defines the voting rules. (10)
11. Apache projects have a private mailing list that their PMC is expected to use only when really needed. The private list is typically used for discussions about people, for example, to discuss and to vote on PMC candidates privately. (11)
12. Independence can be understood as basing the project's decisions on the open discussions that happen on the project's main communications channel, with no hidden agendas. (12)

Copyright © 2013-2016 2020 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
Apache®, the names of Apache projects, and the feather logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.