Technical inclusion criteria - OrderOfTheBee/addons GitHub Wiki

This outlines the technical criteria concerning inclusion of addons into our managed list of Alfresco addons. Non-technical criteria are outlined in the corresponding wiki article.

As sure as development practices are ever changing, so are the requirements outlined on this page or any sub-page(s). Already accepted addons will retain their status even if they no longer fulfill all requirements. We will support and work with the author of an accepted addon to comply with updated rules when the next re-evaluation is due.

• An addon that provides extensions to the Repository-tier, Share-tier or both must be available in packaged form that can be installed via command line or build tooling (AMP / JAR), dropped into the application server hosting Alfresco (JAR) or uploaded into the data dictionary of a running Alfresco instance (ACP).
• An addon that provides tooling to work with an Alfresco installation must be available as an installable package (depending on the platform), an extractable archive or an automated installer.
• Users must not be required to build the addon themselves and should find a versioned release of the addon on the homepage of the addon or a site being linked to. Optional elements of the addon may be provided in separate artifacts.
• Installation and configuration of an extension addon must not require manual copying of individual files or editing existing configuration files in the Alfresco web application(s) other than alfresco-global.properties or share-config-custom.xml.

• Those parts of the addon that are available in source artifact form should have build tooling in place to allow re- or custom building.
• Build tooling must produce a result that matches the pre-built variant when no changes have been made to the source artifact form.
• The build tool should be based on community accepted standard technology, e.g. Maven for extension addons in JAR/AMP form.