THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code | Description | Status | Comments |
|---|---|---|---|
| CO10 | The project has a well-known homepage that points to all the information required to operate according to this maturity model. |  | https://hudi.apache.org/ is very comprehensive |
| CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | | The project homepage/website makes it clear that contributions are most welcome. The project has never refused any contributions. |
| 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. | | The project welcomes and recognizes all contributions that add value to the project. Not just code. e.g: wiki documentation, documentation improvement. |
| CO40 | The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. | | 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 documentedand 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. | | Information on how to become a committer is documented here http://hudi.apache.org/community.html. |
| 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. | | The number of DISCUSS threads on the dev mailing list bear testimony to this. |
| CO70 | The project strives to answer user questions in a timely manner. | | 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 |
|---|---|---|---|
| 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. | | All committers and PMC members are documented at http://hudi.apache.org/community.html |
| CS20 | Decisions are made by consensus among PMC members 9 and are documented on the project's main communications channel. | | The project has voted on new committers, PPMC members, and releases using the appropriate channels and mailing lists. |
| CS30 | Documented voting rules are used to build consensus when a discussion is not sufficient. 10 | | Hudi uses the Apache rules laid down at http://www.apache.org/foundation/voting.html |
| 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.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. | | All decisions are made on the mailing lists. |
...