THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| id | description | evaluation | committers who agree with evaluation |
|---|---|---|---|
| Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/browser | myrle, sander, vishwasbabu, nazeer1100126 |
| Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. | http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201612.mbox/browser | myrle, sander, vishwasbabu, nazeer1100126 |
| Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. | http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/browser | myrle, sander, vishwasbabu, nazeer1100126 |
| Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee. | https://dist.apache.org/repos/dist/release/incubator/fineract/0.5.0-incubating/ | myrle, sander, vishwasbabu, nazeer1100126 |
| 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. |
| myrle, sander, vishwasbabu, nazeer1100126 |
Quality
| id | description | evaluation | committers who agree with evaluation | |
|---|---|---|---|---|
| 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. | Insufficient, at least I'm unaware any public documentation supporting this. We should add to http://fineract.incubator.apache.org/ IN PROGRESS: Nazeer is implementing FindBugs | sander, vishwasbabu, myrle | |
| The project puts a very high priority on producing secure software. | This will always be an ongoing process. | myrle | |
| The project provides a well-documented channel to report security issues, along with a documented way of responding to them. | Insufficient, I think we need to communicate this more clearly on http://fineract.incubator.apache.org/ IN PROGRESS: communicating our standards and readiness for responding to issues/threats. | sander, vishwasbabu, myrle | |
| The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. | Insufficient, while While we have structures in place that would support versioning of API's etc this has not been done at all, and as such backwards compatibility is not great, this is also not helped by not clearly stating which breaking changes are part of a given release. IN PROGRESS: ongoing discussion on the developer mailing list. | sander, vishwasbabu, myrle | |
| The project strives to respond to documented bug reports in a timely manner. | We have mailing lists to discuss the issues fineract and JIRA to report any issues. All the committers/contributors responds in timely manner | nazeer1100126, myrle |
Community
| id | description | evaluation | committers who agree with evaluation |
|---|---|---|---|
| The project has a well-known homepage that points to all the information required to operate according to this maturity model. | Insufficient. http://fineract.incubator.apache.org/ does not link the latest Fineract release.IN PROGRESS: Changes have been merged to GitHub repo for the Apache Fineract site but nothing has been reflected on the page. | myrle, sander, vishwasbabu, nazeer1100126 |
| The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | No examples of unkind or rejecting behavior could be found in a search through the e-mail list. | myrle, sander, vishwasbabu, nazeer1100126 |
| Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | insufficient.Only one committer has been added since the project began. IN PROGRESS: Several additional committers are being discussed. | myrle, sander, vishwasbabu, nazeer1100126 |
| The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. | insufficient.Only one committer has been added since the project began. | myrle, sander, vishwasbabu, nazeer1100126 |
| 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. | Becoming a Committer | myrle, sander, vishwasbabu, nazeer1100126 |
| 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. | myrle, sander, vishwasbabu, nazeer1100126 | |
| The project strives to answer user questions in a timely manner. | myrle, sander, vishwasbabu, nazeer1100126 |
...
| id | description | evaluation | committers who agree with evaluation |
|---|---|---|---|
| The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors. | List of contributors are maintained in http://incubator.apache.org/projects/fineract | myrle, sander, vishwasbabu, nazeer1100126 |
| Decisions are made by consensus among PMC members 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. | myrle, sander, vishwasbabu, nazeer1100126 | |
| Documented voting rules are used to build consensus when discussion is not sufficient. | How we change processes is documented here: There is no mention of voting however. At the request of our mentors, all mentions of voting were removed. | myrle, sander, vishwasbabu, nazeer1100126 |
| 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. | We follow general Apache voting process. | myrle, sander, vishwasbabu, nazeer1100126 |
| All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | See IN10 below for an important caveat. | myrle, sander, vishwasbabu |
...
| id | description | evaluation | committers who agree with evaluation | |
|---|---|---|---|---|
| The project is independent from any corporate or organizational influence. | The committers come mostly from three organizations:
In each of these organizations committers are paid for their work on the project. All of these are smaller organizations. The Mifos Initiative is a non-profit. The project is not completely independent of outside influence, but most Apache projects are not completely independent. This criteria is more about finding a threshold and a project's relation to that threshold. The main risk to the independence of the project is that the UI (aka the community app) was not contributed to Apache, and still belongs to the Mifos Initiative. The discussions for that part of the project still occur on Mifos Initiative infrastructure. Other UIs can be and are programmed against the backend. Unfortunately though, the splitting of the original Mifos community causes confusion about where to communicate about which issues. | Communication which continues on the Mifos infrastructure creates dependencies on the Mifos Initiative beyond what the author believes to be Apache's threshold.myrle, sander, vishwasbabu, nazeer1100126Progress has been made on clarifying which kinds of communication occur where. The current state is imperfect, but in the view of the author good enough. | myrle |
| Contributors act as themselves as opposed to representatives of a corporation or organization. | The author of the evaluation for IN10 is a Mifos Initiative employee demonstrating her independence. | myrle |