walid.nouh@atosorigin.com Walid Nouh nicolas.verite@atosorigin.com Nicolas Vérité en Psi 0.10 31 GNU GPL http://psi-im.org Psi is a Jabber client looking (by design) like licq. Besides basic instant messaging services, it provides support for features like groupchat and multiple accounts. For more information on jabber, see www.jabber.org (or the jabber package which contains the jabber server software). 1.7 jabber-client psi

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 The first packages have been released the 2002-07-11. 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 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 0 Psi have already been forked by Jabbin IMP and VoIP client Adoption by community and industry Very few users identified Detectable use on Internet Numerous users, numerous references 2 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 2 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 Organisation and leadership of developments 1 to 2 individuals involved, not clearly identified Between 2 and 5 independent people More than 5 people 1 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, loing 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 2 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 2 Industrialization level of the project Developments realized at 100% by employees of a single company 60% maximum 20% maximum 2 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 0 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) 1 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 0 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 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 2 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 1 Software is packaged for Mac Os X 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 2 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 2 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 2 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 2 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 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 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 1 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 1 Some part of the GUI are not easy to understand and need technical knowledge 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, ...) 0 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 0 A plugin mechanism is on the way for the next release 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 0 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 Justin Karneges is the owner of the source 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 2 The source repository use subversion. No published roadmap Existing roadmap without planning Versionned roadmap, with planning and measure of delays 2 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 0 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 1

No customizable skin Custumizable skin but needs complicated manipulation User friendly skin support List of other clients using the same skin constituent: No account creation is possible directly in the client Account creation is possible for part of the protocols supported Account creation is avalaible for all supported protocols 2 No link for account management provided by the client Link to the account management page for all or part of supported protocols A native interface exists to edit accounts (all or part of supported protocols) 2 Deleting an account is not possible via the client Link to the deletion page of an account is provided A native interface permits to delete an account without browsing the web 2 No plug-in system integrated to the client Limited plug-ins features Advanced plug-ins features 0 512KB/sec at least 256KB/sec at least 64KB/sec or less 2

Textual Instant Messaging Protocols Supported Core protocol of the Jabber Instant Messaging and Presence technology Multi User Chatroom features No MUC support Limited MUC support MUC is fully supported 1 Only groupchat is supported No Ressource priority support Limited support of Ressource priority Full support of Ressource priority 2 No vCard support Old vCard specification supported Flexible vCard support 2 No avatar system is provided by the client http-storage avatar system vCard-based avatar 2 Psi 0.10 does not display avatars in the roster. You can only publish or see avatars by watching the user information's page. Presence handling features No presence status features Basic presence status indicators only Customizable Status indicators 2 No auto-away system Basic auto-away system Advanced auto-away system 2 Presence status is the same for all contacts (one presence status even for more than one account) Presence status can be different from one account to another Presence status can be set for each contact 1 Tools provided to enlarge Instant Messaging possibilities No encryption support Encryption partially supported Advanced encryption suport 1 Psi 0.10 does not support SASL No peer to peer encryption support Basic peer to peer encryption support GPG based encryption 2 No smileys avalaible Basics smileys avalaible Ability to extend and share smileys list 1 No nudge support Nudge partially supported Nudge fully supported 0 No whiteboard support Partial support of whiteboard Full support of whiteboard 0 No game provided Limited choice of games with dependencies to the used protocol Large choice of games compatible with different protocols/clients 0 The IM module uses exclusively standard open protocols The IM module is based on costumized existing open protocole The IM module uses a Proprietary Protocol 2 Psi is a Jabber client Compatibility of the client with the different most popular proprietary protocols of Instant Messaging (throught gateways) Supported Protocol using Jabber gateways or native protocols

Not compatible Partially compatible Fully compatible 0 Not compatible Partially compatible Fully compatible 0 Not compatible Partially compatible Fully compatible 0 List of open or proprietary protocols compatible No compatibility Traditional telecom infrastructure is supported but bugs exists The system is entirely compatible with traditional telecom without important bugs 0 No billing system needed (no external call possible with the client) Limited billing system Adanced billing system 0 Additional features No AEC provided AEC system exists but doesn't work properly Full support of AEC 0 Interaction with call centers possibilities IVR and ASR are not supported IVR works but not ASR ASR and IVR works correctly 0 Voice Mails features No VMS support Limited VMS features Large Pannel of VMS possibilites 0 List of used protocols for Visio support Jingle, SIP, proprietary protocols, etc.) List of existing OS packaging Only one plateform supported Multi-plateform support but no inter-plateform connexion is possible Full multi-plateform support 0 Details about audio compression for videoconferencing Telephone quality (8KHz sampled sound) FM qualtity (16Khz sampled sound at least) Hi-fi quality (24Khz sampled sound at least) Lists of supported audio codecs Codecs and video format suitable for low rated networks Codecs and video format optimized for large band networks Video flows are customizable to fit the networks capacities List of codecs provided and details about patent issues List of proprietary codecs used No AEC provided AEC system exists but doesn't work properly Full support of AEC No data transfert is expected with VideoConferencing Data transfert works but hardly if behind a firewall or a NAT server Data transfert is fully supported Only peer to peer videoconferencing is supported Multi point Video conferencing is possible but no dedicated servers exists A dedicated architecture permits multi point videoconferencing List of Gateway and Media Gateways used/supported for VoIP module No calls possible due to Gatekeeper/Media Gateway controller inexistence Basic calls (call detection, analog/digital voice conversion and codec functions only) Calls and extra features (voice compression, echo cancelation, silence suppression..) No calls are possible due to Signaling Gateway problems Signaling Gateways problems may unable users to establish calls No reported bugs about Signaling Gateway Location possibilities Protocols used don't offer any location service Possibilities of location service under conditions Registrar servers exists and permits location services Not working behind a firewall using NAT Works behind a firewall with pain No difficult manipulations to negotiate with an NAT server

WengoPhone is a Voice and Video Over IP application based on standard protocols like SIP and RTP
Website: http://www.openwengo.com/ Not compatible Partially compatible Fully comlpatible 2 Not compatible Partially compatible Fully comlpatible 0 Not compatible Partially compatible Fully comlpatible 0 Ekiga is an open source VoIP and video conferencing application for GNOME.
Website: http://www.ekiga.org/ Not compatible Partially compatible Fully comlpatible 0 Ekiga does not use Jabber/XMPP for text messages Not compatible Partially compatible Fully comlpatible 0 Not compatible Partially compatible Fully comlpatible 0 Psi is a GPLed instant messaging client for the Jabber (XMPP) protocol which uses the Qt toolkit. It runs on Linux, Microsoft Windows, and Mac OS X. Ready-to-install RPM and deb packages are available for many Linux distributions. Successful ports of Psi were reported for FreeBSD and Sun Solaris operating systems.
website: http://psi-im.org/ Not compatible Partially compatible Fully comlpatible Not compatible Partially compatible Fully comlpatible Not compatible Partially compatible Fully comlpatible Kopete is an instant messenger supporting AIM, ICQ, MSN, Yahoo, Jabber, IRC, Gadu-Gadu, Novell GroupWise Messenger, and more. It is designed to be a flexible and extensible multi-protocol system suitable for personal and enterprise use.
Website: http://kopete.kde.org/ Not compatible Partially compatible Fully comlpatible 2 Not compatible Partially compatible Fully comlpatible 0 Gaim is a multi-protocol instant messaging (IM) client for Linux, BSD, MacOS X, and Windows. It is compatible with AIM and ICQ (Oscar protocol), MSN Messenger, Yahoo!, IRC, Jabber, Gadu-Gadu, SILC, Novell GroupWise Messenger, Lotus Sametime, and Zephyr networks.
Website: http://gaim.sourceforge.net/ Not compatible Partially compatible Fully comlpatible 2 Not compatible Partially compatible Fully comlpatible 0 Google Talk is a service offered by Google for Voice over IP and instant messaging
Website: http://talk.google.com/ Not compatible Partially compatible Fully comlpatible 1 Conversation works, but file transferts are not compatible Not compatible Partially compatible Fully comlpatible 0