In order to facilitate the packaging of applications by providing successive steps to achieve, each package is assigned a quality level, from 0 to 9.
A package must meet a number of criteria to reach each level. In addition, to reach a level, the package must have previously reached the previous level.
This classification of applications by levels has 3 advantages:
The following summarizes the current definition of the levels.
The exact definitions are likely to shift over time and are heavily dependent on:
The application does not work at all.
The application can be installed/removed in at least one configuration.
The application can be installed/removed in all common configurations.
(Typically this corresponds to full domain vs. sub path installs, private/public installs, multi-instance installs)
The application supports upgrading.
The application supports backup/restore.
The application triggers no errors on the package linter
The application repository is part of the YunoHost-Apps organization, which allows the community to contribute to its maintainance.
The application triggers no warnings on the package linter.
The application is long-term good quality, meaning it's been at least level 5 in the application catalog for a certain amount of time (when writing this: level 5+ 90% of the time during the last year)
The application is considered "high-quality": it is well-integrated with YunoHost (in particular SSO/LDAP) and follows the recommended development workflow.
Using level 9 is being deprecated.
Found errors? Think you can improve this documentation? Simply click the Edit link at the top of the page, and then the icon on Github to suggest changes.