Versions Compared

Old Version 12

changes.mady.by.user Suneel Marthi

Saved on

compared with

New Version Current

changes.mady.by.user Bhavani Sudha

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code

Description

Status

Comments

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

Available from download page with Apache license version 2.0

http://hudi.apache.org/releases.html

CD20The project's code is easily discoverable and publicly accessible.(tick)See CD10

Code can be found from the website in CD10

Code is hosted publicly on github 

https://github.com/apache/hudi

CD30The code can be built in a reproducible way using widely available standard tools.(tick)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.

(tick)The source history is available here and release is releases are tagged.
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 to provide reliable information about the code provenance.		(tick)

Code Only project committers have access to merge code contributions. Commit messages clearly detail the author & committer for each contribution, including 3rd party contributors. Code contributions and commit process documented 

at https://hudi.apache.org/contributing.html

...

Code

Description

Status

Comments

LC10The code is released under the Apache License, version 2.0.(tick)see CD10. LICENSE file is included in the release distributions.
LC20

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

(tick)All dependencies included in release bundles have licenses compatible with the Apache License and are documented in the LICENSES file in the bundle
LC30The libraries mentioned in LC20 are available as Open Source software.(tick)All libraries are available as Open Source software and documented in the LICENSES file
LC40Committers 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.		(tick)All committers have signed ICLA's. Write access to the project repo requires an Apache account, which requires an ICLA on file.
LC50The copyright ownership of everything that the project produces is clearly defined and documented.(tick)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.

(tick)See http://hudi.apache.org/releases.html, which distributes code as gzipped tarball archive
RE20Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.(tick)Yes, all releases so far have gone through PPMC's vetting and approvals.
RE30

Releases are signed and/or distributed along with digests that can be reliably

used to validate the downloaded archives.

(tick)Yes
RE40Convenience binaries can be distributed alongside source code but they are not Apache Releases
-- they are just a convenience provided with no guarantee.		(tick)Yes
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.

(tick)See Release Manager's Guide

...

Code

Description

Status

Comments

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		(tick)Known issues are tracked in JIRA for public viewing - HUDI Jira
QU20The project puts a very high priority on producing secure software.(tick)YES. Security issues are treated with the highest priority, according to the CVE/Security Advisory procedure.
QU30The project provides a well-documented channel to report security issues, along with a documented way of responding to them.TODO: Add a (tick)

Reporting security issues on the project has been documented at Reporting Security Issues

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

.

QU40The 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.		(tick)Hudi provides documentation on our website and will take care to preserve backward compatibility and announce any has thus far announced any breaking/important changes in behavior, that are necessary because of security or other concerns. Project will continue to uphold this.
QU50The project strives to respond to documented bug reports in a timely manner.(tick)That is the goal and the results so far have generally been good. 390+ issues closed since start of incubation.


Community

Code

Description

Status

Comments

CO10The project has a well-known homepage that points to all the information required to operate according to this
maturity model.		(tick)https://hudi.apache.org/ is very comprehensive
CO20The community welcomes contributions from anyone who acts in good faith and in a respectful manner and
adds value to the project.		(tick)The project homepage/website makes it clear that contributions are most welcome.  The project has never refused any contributions. 
CO30Contributions include not only source code, but also documentation, constructive bug reports, constructive
discussions, marketing and generally anything that adds value to the project.		(tick)The project welcomes and recognizes all contributions that add value to the project. Not just code. e.g:  wiki documentation, documentation improvement.
CO40The community is meritocratic and over time aims to give more rights and responsibilities to contributors
who add value to the project.		(tick)So far four individuals who have shown a commitment to the project have been voted in as committers and PPMC members. Project also recognizes promising contributors via an appreciation email
CO50

The way in which contributors can be granted more rights such as commit access or decision power is


clearly

documented and

documented and is the same for all contributors.

CO60 The community operates based on
the consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not
welcome in Apache projects.

 

(tick)Information on how to become a committer is documented here http://hudi.apache.org/community.html.  
CO60The community operates based on the consensus of its members (see CS10) who have decision power.
Dictators, benevolent or not, are not welcome in Apache projects.		(tick)The number of DISCUSS threads on the dev mailing list bear testimony to this.
CO70The project strives to answer user questions in a timely manner.(tick)The dev@ mailing lists, GitHub issues and Apache Hudi slack general# channel are the go-to places to pose questions and receive answers. 


Consensus Building


Code

Description

Status

Comments

CS10The project maintains a public list of its contributors who have decision power -- the project's PMC
(Project Management Committee) consists of those contributors.		(tick)All committers are and PMC members and committers are documented at http://hudi.apache.org/community.html
CS20Decisions are made by consensus among PMC members 9 and are documented on the project's main
communications channel.		(tick)The project has voted on new committers, PPMC members, and a release releases using the appropriate channels and mailing lists.
CS30Documented voting rules are used to build consensus when a discussion is not sufficient. 10(tick)Hudi uses the Apache rules laid down at http://www.apache.org/foundation/voting.html
CS40In 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.CS50All "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.		(tick)All decisions are made on the mailing lists. 

...