Very large, active development team
Over the past twelve months, 58 developers contributed new code to TikiWiki CMS/Groupware.
This is one of the largest open-source teams in the world, and is in the top 2% of all project teams on Ohloh.
For this measurement, Ohloh considered only recent changes to the code. Over the entire history of the project, 176 developers have contributed.
Mature, well-established codebase
The first lines of source code were added to TikiWiki CMS/Groupware in 2002. This is a relatively long time for an open source project to stay active, and can be a very good sign.
A long source control history like this one shows that the project has enough merit to hold contributors's interest for a long time. It might indicate a mature and relatively bug-free code base, and can be a sign of an organized, dedicated development team.
Note: The source code for TikiWiki CMS/Groupware might actually be older than the source control history can reveal. Many projects begin by duplicating a large amount of source code from an existing, older project. You can usually tell whether this is the case by looking for a rapid rise in the amount of code early in the project's history.
Increasing year-over-year development activity
Over the last twelve months, TikiWiki CMS/Groupware has seen a substantial increase in activity. This is probably good sign that interest in this project is rising, and that the open source community has embraced this project.
Ohloh makes this determination by comparing total number of commits made by all developers during the most recent twelve months with the same figure for the twelve months before that. The number of developers and total lines of code are not considered.
Well-commented source code
TikiWiki CMS/Groupware is written mostly in PHP.
Across all PHP projects on Ohloh, 30% of all source code lines are comments. For TikiWiki CMS/Groupware, this figure is 40%.
This high number of comments puts TikiWiki CMS/Groupware among the highest one-third of all PHP projects on Ohloh.
A high number of comments might indicate that the code is well-documented and organized, and could be a sign of a helpful and disciplined development team.
Mozilla Public License 1.0 may conflict with GPL
The source code for TikiWiki CMS/Groupware contains references to both the GNU General Public License 2.0 (GPL) and to the Mozilla Public License 1.0 (MPL). These two licenses include some contradictory restrictions.
The Ohloh source code parser is exhaustive, and can reveal licensing requirements which the developers themselves may have overlooked or forgotten.
This message is merely a warning. There may not actually be any conflict, because the two licenses may not apply to the exact same sections of code or the code in question may be available under multiple licenses. You should review the license requirements for this project carefully, especially if you are using this code for commercial purposes.
The GNU Project maintains a guide to GPL compatibility at their web site.
PHP License may conflict with GPL
The source code for TikiWiki CMS/Groupware contains references to both the GNU General Public License 2.0 (GPL) and to the PHP License. These two licenses include some contradictory restrictions.
The Ohloh source code parser is exhaustive, and can reveal licensing requirements which the developers themselves may have overlooked or forgotten.
This message is merely a warning. There may not actually be any conflict, because the two licenses may not apply to the exact same sections of code or the code in question may be available under multiple licenses. You should review the license requirements for this project carefully, especially if you are using this code for commercial purposes.
The GNU Project maintains a guide to GPL compatibility at their web site.
Apache Software License may conflict with GPL
The source code for TikiWiki CMS/Groupware contains references to both the GNU General Public License 2.0 (GPL) and to the Apache Software License (ASL). These two licenses include some contradictory restrictions.
The Ohloh source code parser is exhaustive, and can reveal licensing requirements which the developers themselves may have overlooked or forgotten.
This message is merely a warning. There may not actually be any conflict, because the two licenses may not apply to the exact same sections of code or the code in question may be available under multiple licenses. You should review the license requirements for this project carefully, especially if you are using this code for commercial purposes.
You can read more about Apache license compatibility at the Apache web site.
The GNU Project maintains a guide to GPL compatibility at their web site.