Product: mUzima
Website: www.muzima.org ⧉
Code repository: https://github.com/muzima/muzima-android ⧉
Current version: v2.6.0
License: MPL-2.0
Sources:
Description:
Statistics Very Active Repository
Stars

8

Watcher Count

20

Fork Count

39

Current Version

Created

06/04/2013

Last Updated

06/25/2020

Open Pull Requests

5

Merged Pull Requests

243

Organizations
Sectors
Building Blocks

We do not have any building blocks information for this product.

SDGs
Self-reported
Self-reported
Self-reported
Interoperable Products

We don't have any interoperating information for this product.

Included Products

We don't have any includes information for this product.

Product Maturity Scores
Overall Maturity Score: 64 / 100

Maturity Categories

Impact, Overall Score: 10.0 / 10.0

Indicator: IM20, Score: 5.0

Description: The project should be able to clearly make the case for its importance in the Development and/or Humanitarian sector(s).

Indicator: IM10, Score: 5.0

Description: The project should be used in real applications and not just in demos. Because not all real-world implementations may be inspected publicly, in such cases statements providing as much details as possible about these implementations should be made.

Independence, Overall Score: 3.3 / 10.0

Indicator: IN20, Score: 3.3

Description: Contributors act as themselves as opposed to representatives of a corporation or organization.

Consensus Building, Overall Score: 2.0 / 10.0

Indicator: CS20, Score: 2.0

Description: 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.

Community, Overall Score: 8.1 / 10.0

Indicator: CO80, Score: 0.9

Description: The project has an active and diverse set of contributing members representing various constituencies.

Indicator: CO73, Score: 0.9

Description: The community has a forum or other discussion platform for users to ask questions, with reasonable response times from the community.

Indicator: CO72, Score: 0.9

Description: The project's real-time communications are archived so that users can refer back to past conversations.

Indicator: CO71, Score: 0.9

Description: The project has a well-known real-time communication platform such as IRC.

Indicator: CO70, Score: 0.9

Description: The project strives to answer user questions in a timely manner.

Indicator: CO60, Score: 0.9

Description: 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.

Indicator: CO30, Score: 0.9

Description: Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project.

Indicator: CO20, Score: 0.9

Description: The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.

Indicator: CO10, Score: 0.9

Description: The project has a well-known homepage that points to all the information required to operate according to this maturity model.

Software Quality, Overall Score: 5.6 / 10.0

Indicator: QU71, Score: 0.7

Description: The project must include enough documentation for a software developer of moderate skill to set up their development environment to contribute to the software code.

Indicator: QU70, Score: 0.7

Description: The project must include enough documentation for anyone to test or deploy any of the software.

Indicator: QU51, Score: 0.7

Description: A list of outstanding bugs is open, easily discoverable, prioritized, and responsively triaged.

Indicator: QU50, Score: 0.7

Description: The project strives to respond to documented bug reports in a timely manner.

Indicator: QU20, Score: 0.7

Description: The project puts a very high priority on producing secure software.

Indicator: QU12, Score: 0.7

Description: In particular, there are no custom utility features that could be replaced with common open source tools, including:DatabasesWeb application servers/containersObject relational mappersDependency/package managementAuthenticationContinuous integrationPackaging/installation

Indicator: QU11, Score: 0.7

Description: In particular, there are either no "monoliths" or "god classes", or they are known and there is a roadmap to refactor them.

Indicator: QU10, Score: 0.7

Description: 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.

Software Releases, Overall Score: 7.0 / 10.0

Indicator: RE80, Score: 1.4

Description: The project has released at least one version.

Indicator: RE70, Score: 1.4

Description: The project should use the OSC standard release taxonomy, once that is agreed upon.

Indicator: RE50, Score: 1.4

Description: 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.

Indicator: RE30, Score: 1.4

Description: Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.

Indicator: RE10, Score: 1.4

Description: Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.

Licenses and Copyright, Overall Score: 6.8 / 10.0

Indicator: LC50, Score: 1.7

Description: The copyright ownership of everything that the project produces is clearly defined and documented.

Indicator: LC30, Score: 1.7

Description: The libraries mentioned in LC20 are available as Open Source software.

Indicator: LC20, Score: 1.7

Description: Libraries that are mandatory dependencies of the project's code do not create more restrictions than the project's license does.

Indicator: LC10, Score: 1.7

Description: The code is released under one of the preferred copyleft licenses explained in our Licensing Principles.

Software Code, Overall Score: 8.8 / 10.0

Indicator: CD60, Score: 1.1

Description: The code contains README, NOTICE, and CONTRIBUTING files (or README sections).

Indicator: CD50, Score: 1.1

Description: 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 provide reliable information about the code provenance.

Indicator: CD40, Score: 1.1

Description: 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.

Indicator: CD31, Score: 1.1

Description: Step-by-step instructions for setting up a developer environment is available for all appropriate platforms/operating systems, with a minimum of manual steps (e.g. running commands in a terminal/shell).

Indicator: CD30, Score: 1.1

Description: The code can be built in a reproducible way using widely available standard tools.

Indicator: CD21, Score: 1.1

Description: The project's code uses mainstream revision control software, such as git.

Indicator: CD20, Score: 1.1

Description: The project's code is easily discoverable and publicly accessible.

Indicator: CD10, Score: 1.1

Description: The project produces Open Source software, for distribution to the public at no charge.

Cost data for this product
Lines of Code

72177

Estimated effort (person months)

214

Automatic Launch

This product is not configured for auto-launch

Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more