Generic criteria from QSOS version 1.6 Intrinsic durability Maturity less than 3 months if between 3 months and 3 years after 3 years 2 Old proprietary software edited by Netline, became Open Source in december 2004. Unstable software with numerous releases or patches generating side effects Stabilized production release existing but old. Difficulties to stabilize developpement releases Stabilized software. Releases provide bug fixes corrections but mainly new functionalities 2 Version 0.8.2 is stable. Software knows several problems which can be prohibitive No know major problem or crisis History of good management of crisis situations 1 Software is very likely to be forked in the future Software comes from a fork but has very few chances of being forked in the future Software has very little chance of being forked. It does not come from a fork either 2 Adoption by community and industry Very few users identified Detectable use on Internet Numerous users, numerous references 2 Recognized as the best mature solution for replacing Microsoft Exchange. None Few refences, non critical usages Often implemented for critical applications 1 Some references listed on this page : http://www.openexchange.com/EN/product/references.html No community or without real activity (forum, mailing list, ...) Existing community with a notable activity Strong community: big activity on forums, numerous contributors and advocates 1 Growing and active community, one of the more active project on SourceForge. No book about the software Less than 5 books about the software are available More than 5 books about software are available, in several languages 0 As we know, no book has been edited about OX. Organisation and leadership of developments 1 to 2 individuals involved, not clearly identified Between 2 and 5 independent people More than 5 people 2 No leader, but a core team with an identied role for each member. Complete dictatorship Enlightened despotism Council of architects with identified leader (e.g: KDE) 2 Activity of the project and around the software Less than 3 developers, not clearly identified Between 4 and 7 developers, or more unidentified developers with important turnover More than 7 developers, very stable team 2 11 identified developers for each modules of OX. Slow reactivity in forum or on mailing list, or nothing regarding bug fixes in releases note Detectable activity but without process clearly exposed, loing reaction/resolution time Strong reactivity based on roles and tasks assignment 2 No or few new functionalities Evolution of the product driven by the core team or by user's request without any clearly explained process Tool(s) to manage feature requests, strong interaction with roadmap 2 Community is very sensible about the request of the users. Very weak activity on both production and development releases Activity on production and developmenet releases. Frequent minor releases (bug fixes) Important activity with frequent minor releases (bugs fixes) and planned major releases relating to the roadmap forcast 1 Since 2004, frequency of the release is increasing. Industrialization level of the project Developments realized at 100% by employees of a single company 60% maximum 20% maximum 0 All the core team is employed by Netline. Services offering No offer of training identified Offer exists but is restricted geographically and to one language or is provided by a single contractor Rich offers provided by several contractors, in serveral languages and split into modules of gradual levels 2 Many companies provide training in France and in others countries. For example, Openxchange Ink or, in France, IdealX, Hermitage Solutions, Cyberlogic, Adelux, Linagora and many more No offer of support except via public forums and mailing lists Offer exists but is provided by a single contractor without strong commitment quality of services Multiple service providers with strong commitment (e.g: guaranteed resolution time) 2 Many companies provide training in France and in others countries. For example, Openxchange Ink or, in France, IdealX, Hermitage Solutions, Cyberlogic, Adelux, Linagora and many more No offer of consulting service Offer exists but is restricted geographically and to one language or is provided by a single contractor Consulting services provided by different contractors in serveral languages 2 Many companies provide training in France and in others countries. For example, Openxchange Ink or, in France, IdealX, Hermitage Solutions, Cyberlogic, Adelux, Linagora and many more No user documentation Documentation exists but shifted in time, is restricted to one language or is poorly detailed Documentation always up to date, translated and possibly adapted to different target readers (end user, sysadmin, manager, ...) 2 Official documentation and very helpful wiki available on the web site. http://mirror.open-xchange.org/ox/EN/community/documentation.htm http://www.open-xchange.org/oxwiki/Open_2dXchange_20Wiki Quality assurance process No QA process Identifies QA process but not much formalized and with no tool Automatic testing process included in code's life-cycle with publication of results 0 No processus has been identified No bug or feature request management tool Standard tools provided (for instance by a hosting forge) but poorly used Very active use of tools for roles/tasks allocation and progress monitoring 2 The project used BugZilla for the bug monitoring and the forum is used to discuss about the new functionalities. Packaging for various operating systems BSD The software is not packaged for FreeBSD A port exists but it has important issues or it doesn't have official support A official port exists in FreeBSD 0 Documentation available on the official wiki The software is not packaged for Mac OS X A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for NetBSD A port exists but it has important issues or it doesn't have official support A official port exists in NetBSD 0 The software is not packaged for OpenBSD A port exists but it has important issues or it doesn't have official support A official port exists in OpenBSD 0 Linux The software is not packaged for Debian A Debian package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 1 Package in development. Documentation availabe on the wiki. The software is not packaged for Mandriva A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for Red Hat/Fedora A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 A package is provided with the commercial version. The software is not packaged for SuSE A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 Novell supports and contributes to the OX project. A package is provided with the commercial version. An open source installer is under development : http://sourceforge.net/projects/ava-sbs Software can't be installed from source without lot of work Installation from source is limited and depends on very strict conditions (OS, arch, lib, ...) Installation from source is easy 2 Documentation available for installing OX on many Linux distributions on the official wiki. Unix The software is not packaged for AIX A package exists but it has important issues or it doesn't have official support A stable package is provided for AIX The software is not packaged for HP-UX A package exists but it has important issues or it doesn't have official support A stable package is provided for HP-UX 0 No documentation The software is not packaged for Solaris A package exists but it has important issues or it doesn't have official support (e.g: SunFreeware.com ) The software is supported by Sun for Solaris 0 The project can't be installed on Windows A package exists but it is limited or has important issues or just cover some specific Windows release (e.g: Windows 2000 and Windows XP) Windows is full supported and a package is provided 0 No installation has been identified on Windows OS. Exploitability level Difficult to use, requires an in depth knowledge of the software functionality Austere and very technical ergonomics GUI including help functions and elaborated ergonomics 2 Utilization is very intuitive and interface is user friendly. No administrative or monitoring functionalities Existing, functionalities but uncomplete and or need improvement Complete and easy-to-use administration and monitoring functionalities. Possible integration with external tools (e.g: SNMP, syslog, ...) 1 ATFrog is an administration tool provided by the OX community. Commercial version provides an administration interface. Technical adaptability Monolithic software Presence of hight level modules allowing a first level of software adaptation Modular conception, allowing easy adaptation of the software by selecting or creating modules 2 Code is in Java et C Everything by hand Recompilation possible but complex without any tools or documentation Recompilation with tools (e.g: make, ANT, ...) and documentation provided 2 Compilation is managed by a make file. The source architecture is not documented. Any modification requires code recompilation Architecture designed for static extension but requires recompilation Principle of plugin, architecture designed for dynamic extension without recompilation 0 You need to recompile the source after a code modification. Project's strategy License, only if user wants to become owner of code Very strict license, like GPL Moderate permissive license located between both extremes (GPL and BSD) dual-licensing depending on the type of user (person, company, ...) or their activities Very permissive like BSD or Apache licenses 0 Very permissive like BSD or Apache licenses Moderate permissive license located between both extremes (GPL and BSD), dual-licensing depending on the type of user (person, company, ...) or their activies Very strict license, like GPL 2 Rights held by a few individuals or entities, making it easier to change the license Rights held by numerous individuals owning the code in a homogeneous way, making relicense very difficult Rights held by a legal entity in whom the community trusts (e.g: FSF or ASF) 0 All the source code is helded by Netline. No pratical way to propose code modification Tools provided to access and modify code (like CVS or SVN) but not really used to develop the software The code modification process is well defined, exposed and respected, based on roles assignment 0 There is no tool for code modification. No published roadmap Existing roadmap without planning Versionned roadmap, with planning and measure of delays 1 A roadmap is available on the web site, but no delay are given. http://mirror.open-xchange.org/ox/EN/community/roadmap.htm Software has no sponsor, the core team is not paid Software has an unique sponsor who might determine its strategy Software is sponsored by industry 2 OpenEchange Ink, Novell and some other companies sponsored the project. No detectable strategy or strong dependency on one unique actor (person, company, sponsor) Strategical vision shared with several other free and open source projects but without strong commitment from copyrights owners Strong independence of the code team, legal entity holding rights, strong involvement in the standardization process 2 The association with Novell has no impact of the Netline strategy.