FusionDirectory - Mature level check-list

Technical criteria

Source code

The project must have means of separating active development from versioning and bug-fixing in the source repository. It must be documented on the web site	ok
The source code of the project must be available on the OW2 infrastructure. Either the OW2 forge is used as the main source code repository, or the source code is synced from external repositories to the OW2 forge, automatically and on regular basis (at least once per release)	ok - reference
For each release, the project must publish an archive file containing the source code corresponding to the release.	ok - reference
The project must follow a code convention guideline, which has to be documented on the web site. This guideline should be enforced by using tools such as Checkstyle	ok - Coding convention guidelines enforced by codesniffer + phpunit

Continuous integration

The way to build the project has to be documented on the web site (required environment and step by step process to be followed)	ok - Documentation on how to build and release sotfware
The project code base must compile successfully on the target platforms.	ok - reference: repository of software builds by CI
The project must contain automated test suites executing successfully	codesniffer + phpunit - git of automated test suite
A continuous integration platform must be set up (either within the OW2 forge with Bamboo currently, or an external CI platform)	ok - reference (Jenkins)

Binaries

The project binaries must be synced to the OW2 platform, at least once per release

N/A: no binaries, only interpreted languages

Documentation

A user and a developer documentation must be available	ok - User documentation , Developer documentation
The documentation must be synced to the OW2 forge, at least once per release	ok - reference (v1.0.15): Install / user manual FAQ Developer manual Plugins documentation: Addons plugin Admin plugin Mail plugin Services plugin User plugin

Quality assessment

Transversal maturity assessment by filling in and maintaining on a regular basis the Open-source Maturity Model form	ok - reference
Source code static analysis with a tool such as SonarQube	Done at sonar.fusiondirectory.org Documentation / examples: PHP Plugin php-sonar-runner example SonarQube documentation
IP and license analysis with a tool such as FOSSology	ok - reference
Source code originality analysis with a tool such as Antepedia Reporter	ok - reference
Activiy metrics eg via OpenHub	ok - OpenHub page

Activeness

Existence of discussions around the project on one or several communication channel(s) such as mailing-lists or IRC channels	ok - contacts for Fusiondirectory
Existence of recent source code commits	ok - git repos of FusionDirectory
Availability of technical support must be (not necessarily commercial)	ok - community and preofessional support

Usage

Download statistics	ok - download stats are available from the OW2 forge (complementary stats is a work in progress at OpenSides)
Availability of public case studies	ok - see dashboard
References to business users	ok - references: companies, public sector, NGO

Committers

The project must have at least two code committers.

Dashboard

SPDX license(s) reference	ok
Forge link	ok - see dashboard
Mailing-list(s) information	ok - see dashboard
Case study(ies)	ok - see dashboard
Quality assessment reports covering static analysis, IP/License analysis, originality analysis	in progress
Implemented standards	LDAP