...
ID |
Description |
Status |
CO10 |
The project has a well-known homepage that points to all the information required to operate according to this maturity model. |
YES. The OpenWhisk project homepage [OW-Web-Home] provides all the relevant information. This includes top-level pages containing:
- User Documentation for users (broken down into roles of Developer, Contributor and Operator). The Contributor section explains the components and GitHub repos. as well as links to our project Wiki's discussion of:
- Community page hat explains our various Media outlets and their purpose, Mailing list information, Project Wiki overview, and links (as req.'ed to Apache's event feed.
- Download Information describing our Apache Releases for all components with links to download and instructions on verifying compressed archives.
All pages include a footer with links to the ASF, license and copyright disclaimers, Apache Events, Security, as well as Apache Sponsorship and "Thanks". All pages include a header with media links to GitHub (OpenWhisk projects filter), Twitter, Medium, Slack, YouTube, SlideShare and StackOverflow. |
CO20 |
The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. |
YES. We endeavor to welcome all Contributors and encourage involvement on our community. This is clearly stated front-and-center on our project Wiki [OW-Confluence-Wiki], as well as on our Documentation page which includes a section specifically for Contributors. |
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. |
YES. The community welcomes contributions in all these forms and takes them gratefully with respect. |
CO40 |
The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. |
YES. This is stated prominently on our [OW-Confluence-Wiki] and linked from our website. |
CO50 |
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. |
YES. This is stated prominently on our [OW-Confluence-Wiki] and linked from our website. |
CO60 |
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. |
YES. We have people who have been long time contributors and have a good context on various design aspects. However all changes are done via consensus and not seen any case where any decision was forcefully taken |
CO70 |
The project strives to answer user questions in a timely manner. |
YES. Several channels are monitored for user and developer questions, including the "dev" list, Stack Overflow, Slack, and Twitter. |
Consensus Building
ID |
Description |
Status |
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. |
YES. The list of mentors and committers are accurate and maintained as part of the project's roster in Whimsy (https://whimsy.apache.org/roster/ppmc/openwhisk) and is also linked from the project incubation status page. |
CS20 |
Decisions are made by consensus among PMC members 9 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. |
YES. All significant project decisions are made on the project's mailing list (dev@openwhisk.incubator.apache.org); with votes that include results tallies that contain the number of votes from contributors and binding votes from mentors, committers and PMC members when applicable.
|
CS30 |
Documented voting rules are used to build consensus when discussion is not sufficient. 10 |
YES. The community attempts to achieve consensus based using discussions based in the project email list and seeks to positively resolved conflicts informally without a formal email list vote when possible. |
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. |
YES. Please note that community, so far, has had need not needed to exercise a veto. |
CS50 |
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. |
YES. All significant project-related discussions happen on and are directed to the project's mailing list. Alternate communication channels, such as Slack and GitHub issues, are at times used to quickly iterate on topics, but issues having wider impact are moved to '"dev' " list discussions. All community web conferences are posted and call minutes are documented on the wiki, as are longer term design discussions. |
... |
|
|
|