en 1.7 revision-control-system 1.0

Generic criteria from QSOS version 1.6 Intrinsic durability Maturity less than 3 months if between 3 months and 3 years after 3 years Unstable software with numerous releases or patches generating side effects Stabilized production release existing but old. Difficulties to stabilize development releases Stabilized software. Releases provide bug fixes corrections but mainly new functionalities Software knows several problems which can be prohibitive No know major problem or crisis History of good management of crisis situations 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 Adoption by community and industry Very few users identified Detectable use on Internet Numerous users, numerous references None Few refences, non critical usages Often implemented for critical applications 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 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 Organisation and leadership of developments 1 to 2 individuals involved, not clearly identified Between 2 and 5 independent people More than 5 people Complete dictatorship Enlightened despotism Council of architects with identified leader (e.g: KDE) 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 Slow reactivity in forum or on mailing list, or nothing regarding bug fixes in releases note Detectable activity but without process clearly exposed, long reaction/resolution time Strong reactivity based on roles and tasks assignment 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 Very weak activity on both production and development releases Activity on production and development releases. Frequent minor releases (bug fixes) Important activity with frequent minor releases (bugs fixes) and planned major releases relating to the roadmap forcast Industrialization level of the project Developments realized at 100% by employees of a single company 60% maximum 20% maximum 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 several languages and split into modules of gradual levels 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) 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 several languages 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, ...) 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 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 Packaging for various operating systems 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 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 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 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 The software is not packaged for MacOSX A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 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 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 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 The software is not packaged for RedHat/Fedora A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 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 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 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: Windows2000 and WindowsXP) Windows is full supported and a package is provided 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 No administrative or monitoring functionalities Existing, functionalities but incomplete and or need improvement Complete and easy-to-use administration and monitoring functionalities. Possible integration with external tools (e.g: SNMP, syslog, ...) 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 Everything by hand Recompilation possible but complex without any tools or documentation Recompilation with tools (e.g: make, ANT, ...) and documentation provided Any modification requires code recompilation Architecture designed for static extension but requires recompilation Principle of plugin, architecture designed for dynamic extension without recompilation Project's strategy License 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 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 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) No practical 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 No published roadmap Existing roadmap without planning Versionned roadmap, with planning and measure of delays 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 No detectable strategy or strong dependency on one unique actor(person, company,sponsor) Strategic 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

Commits and chackout features If an operation on the repository is interrupted in the middle, the repository will not be left in an inconsistant state No atomic commits Limlited support of atomic commits Atomic commits fully supported Are local uncommited changes tracked? Local uncommited changes are not tracked Local uncommited changes are partially tracked Local uncommited changes are tracked Commit messages are not on a per-files basis Per-files commit messages are available but limited Commit messages are not a per-files basis Ability to work only on one directory of the repository The whole directory must be checkout Multiple directories must be checkout even if the whole repository must not A single directory can be checkout Ability to tag or label a set of versionned files Tags are not supported Tags are partially supported Tags are fully supported History and logging features History/log on the global repository No repository log or history Limited repository history/log is available Repository history/log is available History/log on individual files No file log or history Limited file history/log is available File history/log is available History/log on individual lines in a file No per-line history Limited line history is available Per-line history is available Possibility to visualize deifferences between different versions of a file (diff) No possibility to visualize differences Different lines between files are identified Different caracters of a same line are identified Branching and Merging features No branching or merging features Limited branching or merging features (example: no tracks are kept of merges) Merge tracking, automatic conflict resolution during merges Triggers and notifications Availability of triggers Availability of triggers to hook customs actions on system events No triggers available Triggers on a small part of the commandset Triggers on most part of the commandset No triggers available Triggers on a small part of the commandset Triggers on most part of the commandset Automatic notifications generated on system events No notifications available Limited notification features (small part of the commandset or limited notification channels) Comprehensive notification features on several channels Changesets are a way to group a number of modifications that are relevant to each other in one atomic package, that can be cancelled or propagated as needed. Changesets are not supported Limited changeset support Full changeset support

Features on the repository level Supported method of managing concurrent access Only one user at a time has write access to a file No file locking Limited file locking File locking is the main storage model Multiple users can edit the same file at the same time, the system provides facilities to merge changes into the central repository No version merging features Limited version merging features Version merging is the main storage model Every user has a working copy that includes the complete repository, all changes are distributed by merging (pushing/pulling) between repositories. No distributed version control Limited distributed version control Distributed version control is the main storage model Available operations on files and directories Files or directories can't be deleted Only files or only directories can be deleted Files and directories can be deleted Files or directories can't be moved nor renamed Only files or only directories can be moved or renamed Files and directories can be moved and renamed Files or directories can't be copied in the repository Only files or only directories can be copied in the repository Files and directories can be copied in the repository Possibility to define permissions on different parts of the repository Access is open for the whole repository Permissions can be set on the directory level Permissions can be set on the file level Multi-tree (or nested trees) project support No metaproject features Limited metaproject features Project tree can contain nested trees

Possibility to clone a remote repository to get a functionally equivalent copy No replication/cloning between remote repositories Limited replication/cloning between remote repositories Replication/cloning between remote repositories is supported Propagation of changes from one repository to another No online synchronization between remote repositories Limited synchronization between remote repositories Synchronization between remote repositories is supported Possibility to work offline (with local history) and synchronize with central repository later No local history is kept when disconnected Limited local history is kept when disconnected Full disconnected mode Supported authentication backends Lightweight Directory Access Protocol No LDAP authentication support Limited LDAP authentication support Full LDAP and Active Directory authentication support Relational database management systems No RDBMS authentication support Authentication possible through few RDBMS RDBMS authentication possible through standards API (like JDBC, ...) Authentication based on user file No file-based authentication is possible Limited file-based authentication File-based authentication is fully supported Other supported authentication backends Integration with development tools Integration with Integrated Development Environments (IDE) No IDE integration Integration limited to few IDE Integration possible with most known IDE Integration with bugtracking systems No bugtracker integration Integration limited to few bugtrackers Integration possible with most known bugtrackers Intregration with forge solutions No forge integration Integration limited to few forges Integration possible with most known forges Integration in office suites to provide document versionning No intregration possible with office suites Limited integration with office suites (few features or very few suites are supported) Full integration with most known office suites Integration in operating systems' file managers No intregration possible with OS file managers Limited integration with OS file managers (few features or very few OS are supported) Full integration with most known OS file managers Available APIs to integrate revision system with other applications No API is available Poorly features API or very few languages are supported Full APIs available in several languages

Remote Procedure Call RPC is not supported Limited RPC support (some features are not available via RPC) RPC is fully supported TCP/IP sockets are not supported Limited TCP/IP socket support (some features are not available via sockets) TCP/IP sockets are fully supported Proprietary protocol provided by the system No C/S proprietary protocol is provided Limited C/S proprietary protocol is provided (some features are not available) System implements a C/S proprietary protocol HTTP is not supported Limited HTTP support (some features are not available via HTTP) HTTP is fully supported WebDAV is not supported Limited WebDAV support (some features are not available via HTTP) WebDAV is fully supported FTP is not supported Limited FTP support (some features are not available via FTP) FTP is fully supported SMTP is not supported Limited SMTP support (some features are not available via SMTP) SMTP is fully supported Remote filesystem protocols (NFS, SMB, ...) No remote filesystem protocol is supported Limited remote filesystem support (some features are not available) Remote filesystem protocols are fully supported Network security features SSL is not supported Limited SSL support SSL is fully supported SSH is not supported Limited SSH support SSH is fully supported

No web interface is available Limited web interface is available Full web interface is available No graphical clients are available Graphical clients are available on few operating systems Full featured graphical clients are available on most operating systems No command line interface is available Limited command line interface is available or few OS are supported Full featured command line interface is available No visual console is available Limited visual console is available or few OS are supported Full featured visual console is available Find Who did What When No audit fonctionality Limited audit fonctionalities are available Comprehensive audit fonctionalities are available Approval and notification No change management policies can be implemented Limited change management features are available Comprehensive change management features (policies, monitoring, approval processes)