[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qsos-commits] qsos/sheet/cms/Alfresco Alfresco-1.3.qsos
From: |
Raphaël Semeteys |
Subject: |
[Qsos-commits] qsos/sheet/cms/Alfresco Alfresco-1.3.qsos |
Date: |
Tue, 07 Nov 2006 09:13:08 +0000 |
CVSROOT: /sources/qsos
Module name: qsos
Changes by: Raphaël Semeteys <rsemeteys> 06/11/07 09:13:08
Added files:
sheet/cms/Alfresco: Alfresco-1.3.qsos
Log message:
Moved
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qsos/sheet/cms/Alfresco/Alfresco-1.3.qsos?cvsroot=qsos&rev=1.1
Patches:
Index: Alfresco-1.3.qsos
===================================================================
RCS file: Alfresco-1.3.qsos
diff -N Alfresco-1.3.qsos
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ Alfresco-1.3.qsos 7 Nov 2006 09:13:08 -0000 1.1
@@ -0,0 +1,889 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <header>
+ <authors>
+ </authors>
+ <dates>
+ <creation></creation>
+ <validation></validation>
+ </dates>
+ <language>en</language>
+ <appname>Alfresco</appname>
+ <release>1.3</release>
+ <licenseid>32</licenseid>
+ <licensedesc>GNU LGPL</licensedesc>
+ <url>www.alfresco.com</url>
+ <desc></desc>
+ <demourl>www.alfresco.com</demourl>
+ <qsosformat>1.6</qsosformat>
+ <qsosappfamily>cms</qsosappfamily>
+ <qsosspecificformat></qsosspecificformat>
+ </header>
+ <section name="generic" title="Generic section">
+ <desc>Generic criteria from QSOS version 1.6</desc>
+ <element name="intrinsicdurability" title="Intrinsic durability">
+ <desc>Intrinsic durability</desc>
+ <element name="maturity" title="Maturity">
+ <desc>Maturity</desc>
+ <element name="age" title="Age">
+ <desc0>less than 3 months</desc0>
+ <desc1>if between 3 months and 3 years</desc1>
+ <desc2>after 3 years</desc2>
+ <score>1</score>
+ <comment>Young Product .</comment>
+ </element>
+ <element name="stability" title="Stability">
+ <desc0>Unstable software with numerous releases or patches
generating side effects</desc0>
+ <desc1>Stabilized production release existing but old.
Difficulties to stabilize developpement releases</desc1>
+ <desc2>Stabilized software. Releases provide bug fixes
corrections but mainly new functionalities</desc2>
+ <score>2</score>
+ <comment>Very active project . A lot of new functionnalities
are implemented in each release . </comment>
+ </element>
+ <element name="historyknowproblems" title="History, know problems">
+ <desc0>Software knows several problems which can be
prohibitive</desc0>
+ <desc1>No know major problem or crisis</desc1>
+ <desc2>History of good management of crisis situations</desc2>
+ <score>1</score>
+ <comment></comment>
+ </element>
+ <element name="forkprobability" title="Fork probability, source of
Forking">
+ <desc0>Software is very likely to be forked in the
future</desc0>
+ <desc1>Software comes from a fork but has very few chances of
being forked in the future</desc1>
+ <desc2>Software has very little chance of being forked. It does
not come from a fork either</desc2>
+ <score>2</score>
+ <comment>Company founded by former managers of Documentum and
Business Objects</comment>
+ </element>
+ </element>
+ <element name="adoption" title="Adoption">
+ <desc>Adoption by community and industry</desc>
+ <element name="popularity" title="Popularity (related to: general
public, niche, ...)">
+ <desc0>Very few users identified</desc0>
+ <desc1>Detectable use on Internet</desc1>
+ <desc2>Numerous users, numerous references</desc2>
+ <score>1</score>
+ <comment></comment>
+ </element>
+ <element name="references" title="References">
+ <desc0>None</desc0>
+ <desc1>Few refences, non critical usages</desc1>
+ <desc2>Often implemented for critical applications</desc2>
+ <score>1</score>
+ <comment>http://www.alfresco.com/customers/</comment>
+ </element>
+ <element name="contributingcommunity" title="Contributing
Community">
+ <desc0>No community or without real activity (forum, mailing
list, ...)</desc0>
+ <desc1>Existing community with a notable activity</desc1>
+ <desc2>Strong community: big activity on forums, numerous
contributors and advocates</desc2>
+ <score>2</score>
+ <comment>Strong activity on the forums . Core developers often
respond to messages . A "forge" centralizes the various extensions contributed
by the community</comment>
+ </element>
+ <element name="books" title="books">
+ <desc0>No book about the software</desc0>
+ <desc1>Less than 5 books about the software are
available</desc1>
+ <desc2>More than 5 books about software are available, in
several languages</desc2>
+ <score>1</score>
+ <comment></comment>
+ </element>
+ </element>
+ <element name="developmentleadership" title="Development leadership">
+ <desc>Organisation and leadership of developments</desc>
+ <element name="leadingteam" title="Leading team">
+ <desc0>1 to 2 individuals involved, not clearly
identified</desc0>
+ <desc1>Between 2 and 5 independent people</desc1>
+ <desc2>More than 5 people</desc2>
+ <score>2</score>
+ <comment>Founders are former managers of Business Objects and
Documentum . Core developers are identifiable on the forums . </comment>
+ </element>
+ <element name="managementstyle" title="Management style">
+ <desc0>Complete dictatorship</desc0>
+ <desc1>Enlightened despotism</desc1>
+ <desc2>Council of architects with identified leader (e.g:
KDE)</desc2>
+ <score></score>
+ <comment></comment>
+ </element>
+ </element>
+ <element name="activity" title="Activity">
+ <desc>Activity of the project and around the software</desc>
+ <element name="developersidentificationturnover"
title="Developers, identification, turnover">
+ <desc0>Less than 3 developers, not clearly identified</desc0>
+ <desc1>Between 4 and 7 developers, or more unidentified
developers with important turnover</desc1>
+ <desc2>More than 7 developers, very stable team</desc2>
+ <score>2</score>
+ <comment>Approximately 10 are regularly posting on the forums .
</comment>
+ </element>
+ <element name="activityonbugs" title="Activity on bugs">
+ <desc0>Slow reactivity in forum or on mailing list, or nothing
regarding bug fixes in releases note</desc0>
+ <desc1>Detectable activity but without process clearly exposed,
loing reaction/resolution time</desc1>
+ <desc2>Strong reactivity based on roles and tasks
assignment</desc2>
+ <score>2</score>
+ <comment>Active JIRA . Anybody can raise bugs or feature
improvement . However , bugfix releases are reserved for the enterprise version
. </comment>
+ </element>
+ <element name="activityonfunctionalities" title="Activity on
functionalities">
+ <desc0>No or few new functionalities</desc0>
+ <desc1>Evolution of the product driven by the core team or by
user's request without any clearly explained process</desc1>
+ <desc2>Tool(s) to manage feature requests, strong interaction
with roadmap</desc2>
+ <score>2</score>
+ <comment>JIRA allows external users to ask for feature
improvements . Numerous discussions on the forums regarding functionnalities
.</comment>
+ </element>
+ <element name="activityonreleases" title="Activity on releases">
+ <desc0>Very weak activity on both production and development
releases</desc0>
+ <desc1>Activity on production and developmenet releases.
Frequent minor releases (bug fixes)</desc1>
+ <desc2>Important activity with frequent minor releases (bugs
fixes) and planned major releases relating to the roadmap forcast</desc2>
+ <score>2</score>
+ <comment>Major releases planned and displayed on the roadmap .
Minor releases reserved for enterprise version</comment>
+ </element>
+ </element>
+ </element>
+ <element name="industrializedsolution" title="Industrialized solution">
+ <desc>Industrialization level of the project</desc>
+ <element name="independenceofdevelopments" title="Independence of
developments">
+ <desc0>Developments realized at 100% by employees of a single
company</desc0>
+ <desc1>60% maximum</desc1>
+ <desc2>20% maximum</desc2>
+ <score>0</score>
+ <comment>All developers are from Alfresco . Some extensions can be
integrated into the core product . </comment>
+ </element>
+ <element name="services" title="Services">
+ <desc>Services offering</desc>
+ <element name="training" title="Training">
+ <desc0>No offer of training identified</desc0>
+ <desc1>Offer exists but is restricted geographically and to one
language or is provided by a single contractor</desc1>
+ <desc2>Rich offers provided by several contractors, in serveral
languages and split into modules of gradual levels</desc2>
+ <score>2</score>
+ <comment>http://www.alfresco.com/services/training/ : several
languages, several end-user profile ( users , developpers , administrators )
</comment>
+ </element>
+ <element name="support" title="Support">
+ <desc0>No offer of support except via public forums and mailing
lists</desc0>
+ <desc1>Offer exists but is provided by a single contractor
without strong commitment quality of services</desc1>
+ <desc2>Multiple service providers with strong commitment (e.g:
guaranteed resolution time)</desc2>
+ <score>1</score>
+ <comment>Bugs raised by the community are fixed by the dev team
, according to their priority , (no guaranteed resolution time ) .
+Minor releases reserved for the Enterprise version . </comment>
+ </element>
+ <element name="consulting" title="Consulting">
+ <desc0>No offer of consulting service</desc0>
+ <desc1>Offer exists but is restricted geographically and to one
language or is provided by a single contractor</desc1>
+ <desc2>Consulting services provided by different contractors in
serveral languages</desc2>
+ <score>1</score>
+ <comment>http://www.alfresco.com/services/consulting/</comment>
+ </element>
+ </element>
+ <element name="documentation" title="Documentation">
+ <desc0>No user documentation</desc0>
+ <desc1>Documentation exists but shifted in time, is restricted to
one language or is poorly detailed</desc1>
+ <desc2>Documentation always up to date, translated and possibly
adapted to different target readers (end user, sysadmin, manager, ...)</desc2>
+ <score>2</score>
+ <comment>Documentation nearly always up to date , correctly
detailed , and adapted to different target readers ( admin , end user ...
)</comment>
+ </element>
+ <element name="qualityassurance" title="Quality Assurance">
+ <desc>Quality assurance process</desc>
+ <element name="quality" title="Quality Assurance">
+ <desc0>No QA process</desc0>
+ <desc1>Identifies QA process but not much formalized and with
no tool</desc1>
+ <desc2>Automatic testing process included in code's life-cycle
with publication of results</desc2>
+ <score>1</score>
+ <comment>Identified QA Manager . tests results publication seem
to be absent . </comment>
+ </element>
+ <element name="tools" title="Tools">
+ <desc0>No bug or feature request management tool</desc0>
+ <desc1>Standard tools provided (for instance by a hosting
forge) but poorly used</desc1>
+ <desc2>Very active use of tools for roles/tasks allocation and
progress monitoring</desc2>
+ <score>2</score>
+ <comment>Active JIRA . Centralizes bug handling / improvements
/ feature requests ...</comment>
+ </element>
+ </element>
+ <element name="packaging" title="Packaging">
+ <desc>Packaging for various operating systems</desc>
+ <element name="packagingsource" title="Source">
+ <desc0>Software can't be installed from source without lot of
work</desc0>
+ <desc1>Installation from source is limited and depends on very
strict conditions (OS, arch, lib, ...)</desc1>
+ <desc2>Installation from source is easy</desc2>
+ <score>2</score>
+ <comment>Installation from source is easy . However , the
public SVN is not tagged , so it is not possible to access a particular version
of the software . This functionnality is reserved for users with an enterprise
account . </comment>
+ </element>
+ <element name="packagingdebian" title="Debian">
+ <desc0>The software is not packaged for Debian</desc0>
+ <desc1>A Debian package exists but it has important issues or
it doesn't have official support</desc1>
+ <desc2>The software is packaged in the distribution</desc2>
+ <score>2</score>
+ <comment></comment>
+ </element>
+ <element name="packagingfreebsd" title="FreeBSD">
+ <desc0>The software is not packaged for FreeBSD</desc0>
+ <desc1>A port exists but it has important issues or it doesn't
have official support</desc1>
+ <desc2>A official port exists in FreeBSD</desc2>
+ <score>0</score>
+ <comment></comment>
+ </element>
+ <element name="packaginghpux" title="HP-UX">
+ <desc0>The software is not packaged for HP-UX</desc0>
+ <desc1>A package exists but it has important issues or it
doesn't have official support</desc1>
+ <desc2>A stable package is provided for HP-UX</desc2>
+ <score>0</score>
+ <comment></comment>
+ </element>
+ <element name="packagingmacosx" title="MacOSX">
+ <desc0>The software is not packaged for MacOSX</desc0>
+ <desc1>A package exists but it has important issues or it
doesn't have official support</desc1>
+ <desc2>The software is packaged in the distribution</desc2>
+ <score>0</score>
+ <comment></comment>
+ </element>
+ <element name="packagingmandriva" title="Mandriva">
+ <desc0>The software is not packaged for Mandriva</desc0>
+ <desc1>A package exists but it has important issues or it
doesn't have official support</desc1>
+ <desc2>The software is packaged in the distribution</desc2>
+ <score>2</score>
+ <comment>Strange configuration defaults for MySQL on this
distribution</comment>
+ </element>
+ <element name="packagingnet" title="NetBSD">
+ <desc0>The software is not packaged for NetBSD</desc0>
+ <desc1>A port exists but it has important issues or it doesn't
have official support</desc1>
+ <desc2>A official port exists in NetBSD</desc2>
+ <score>0</score>
+ <comment></comment>
+ </element>
+ <element name="packagingopen" title="OpenBSD">
+ <desc0>The software is not packaged for OpenBSD</desc0>
+ <desc1>A port exists but it has important issues or it doesn't
have official support</desc1>
+ <desc2>A official port exists in OpenBSD</desc2>
+ <score>0</score>
+ <comment></comment>
+ </element>
+ <element name="packagingredhat" title="RedHat">
+ <desc0>The software is not packaged for RedHat/Fedora</desc0>
+ <desc1>A package exists but it has important issues or it
doesn't have official support</desc1>
+ <desc2>The software is packaged in the distribution</desc2>
+ <score>2</score>
+ <comment></comment>
+ </element>
+ <element name="packagingsolaris" title="Solaris">
+ <desc0>The software is not packaged for Solaris</desc0>
+ <desc1>A package exists but it has important issues or it
doesn't have official support (e.g: SunFreeware.com )</desc1>
+ <desc2>The software is supported by Sun for Solaris</desc2>
+ <score>0</score>
+ <comment></comment>
+ </element>
+ <element name="packagingsuse" title="SuSE">
+ <desc0>The software is not packaged for SuSE</desc0>
+ <desc1>A package exists but it has important issues or it
doesn't have official support</desc1>
+ <desc2>The software is packaged in the distribution</desc2>
+ <score>2</score>
+ <comment></comment>
+ </element>
+ <element name="packagingwindows" title="Windows">
+ <desc0>The project can't be installed on Windows</desc0>
+ <desc1>A package exists but it is limited or has important
issues or just cover some specific Windows release (e.g: Windows2000 and
WindowsXP)</desc1>
+ <desc2>Windows is full supported and a package is
provided</desc2>
+ <score>2</score>
+ <comment></comment>
+ </element>
+ </element>
+ </element>
+ <element name="exploitability" title="Exploitability">
+ <desc>Exploitability level</desc>
+ <element name="easeofuseergonomics" title="Ease of use, ergonomics">
+ <desc0>Difficult to use, requires an in depth knowledge of the
software functionality</desc0>
+ <desc1>Austere and very technical ergonomics</desc1>
+ <desc2>GUI including help functions and elaborated
ergonomics</desc2>
+ <score>2</score>
+ <comment></comment>
+ </element>
+ <element name="administrationmonitoring" title="Administration /
Monitoring">
+ <desc0>No administrative or monitoring functionalities</desc0>
+ <desc1>Existing, functionalities but uncomplete and or need
improvement</desc1>
+ <desc2>Complete and easy-to-use administration and monitoring
functionalities. Possible integration with external tools (e.g: SNMP, syslog,
...)</desc2>
+ <score>2</score>
+ <comment>Integrated user rights management , full repository
import / export , numerous API for integration with external tools . </comment>
+ </element>
+ </element>
+ <element name="technicaladaptability" title="Technical adaptability">
+ <desc>Technical adaptability</desc>
+ <element name="modularity" title="Modularity">
+ <desc0>Monolithic software</desc0>
+ <desc1>Presence of hight level modules allowing a first level of
software adaptation</desc1>
+ <desc2>Modular conception, allowing easy adaptation of the
software by selecting or creating modules</desc2>
+ <score>2</score>
+ <comment>Very modular solution , easily customizable and
extensible .</comment>
+ </element>
+ <element name="codemodification" title="Code modification">
+ <desc0>Everything by hand</desc0>
+ <desc1>Recompilation possible but complex without any tools or
documentation</desc1>
+ <desc2>Recompilation with tools (e.g: make, ANT, ...) and
documentation provided</desc2>
+ <score>2</score>
+ <comment> Ant scripts , supplied documentation . </comment>
+ </element>
+ <element name="codeextension" title="Code extention">
+ <desc0>Any modification requires code recompilation</desc0>
+ <desc1>Architecture designed for static extension but requires
recompilation</desc1>
+ <desc2>Principle of plugin, architecture designed for dynamic
extension without recompilation</desc2>
+ <score>2</score>
+ <comment>Most extensions can be done by modifying XML
configuration files . More extensive modifications will need recompilation .
</comment>
+ </element>
+ </element>
+ <element name="strategy" title="Strategy">
+ <desc>Project's strategy</desc>
+ <element name="license" title="License">
+ <desc>License</desc>
+ <element name="permissiveness" title="Permissiveness (only if user
wants to become owner of code)">
+ <desc0>Very strict license, like GPL</desc0>
+ <desc1>Moderate permissive license located between both
extremes (GPL and BSD) dual-licensing depending on the type of user (person,
company, ...) or their activities</desc1>
+ <desc2>Very permissive like BSD or Apache licenses</desc2>
+ <score>1</score>
+ <comment>Mozilla Public License v. 1.1</comment>
+ </element>
+ <element name="protectionagainstproprietaryforks"
title="Protection against proprietary forks">
+ <desc0>Very permissive like BSD or Apache licenses</desc0>
+ <desc1>Moderate permissive license located between both
extremes (GPL and BSD), dual-licensing depending on the type of user (person,
company, ...) or their activies</desc1>
+ <desc2>Very strict license, like GPL</desc2>
+ <score>1</score>
+ <comment></comment>
+ </element>
+ </element>
+ <element name="copyrightowners" title="Copyright owners">
+ <desc0>Rights held by a few individuals or entities, making it
easier to change the license</desc0>
+ <desc1>Rights held by numerous individuals owning the code in a
homogeneous way, making relicense very difficult</desc1>
+ <desc2>Rights held by a legal entity in whom the community trusts
(e.g: FSF or ASF)</desc2>
+ <score>0</score>
+ <comment>Rights belong to Alfresco.</comment>
+ </element>
+ <element name="modificationofsourcecode" title="Modification of
source code">
+ <desc0>No pratical way to propose code modification</desc0>
+ <desc1>Tools provided to access and modify code (like CVS or SVN)
but not really used to develop the software</desc1>
+ <desc2>The code modification process is well defined, exposed and
respected, based on roles assignment</desc2>
+ <score>2</score>
+ <comment>http://wiki.alfresco.com/wiki/Source_Code</comment>
+ </element>
+ <element name="roadmap" title="Roadmap">
+ <desc0>No published roadmap</desc0>
+ <desc1>Existing roadmap without planning</desc1>
+ <desc2>Versionned roadmap, with planning and measure of
delays</desc2>
+ <score>2</score>
+ <comment>Roadmap tres detaill� , avec des objectifs et delais
clairs
+detailed roadmap , with clear and detailed objectives</comment>
+ </element>
+ <element name="sponsor" title="Sponsor">
+ <desc0>Software has no sponsor, the core team is not paid</desc0>
+ <desc1>Software has an unique sponsor who might determine its
strategy</desc1>
+ <desc2>Software is sponsored by industry</desc2>
+ <score>1</score>
+ <comment>core team paid by Alfresco</comment>
+ </element>
+ <element name="strategicalindependence" title="Strategical
independence">
+ <desc0>No detectable strategy or strong dependency on one unique
actor (person, company, sponsor)</desc0>
+ <desc1>Strategical vision shared with several other free and open
source projects but without strong commitment from copyrights owners</desc1>
+ <desc2>Strong independence of the code team, legal entity holding
rights, strong involvement in the standardization process</desc2>
+ <score>1</score>
+ <comment>respect of multiple standards</comment>
+ </element>
+ </element>
+ </section>
+ <section name="contentimportation" title="Content importation">
+ <comment>This section describe the different way avaible to import
content in the system.</comment>
+ <element name="metadata" title="Meta data">
+ <comment>Meta data are infromation related to a document like
(author, copyright holder, ...)</comment>
+ <element name="keyword" title="Key word support">
+ <desc>Metadata are all the specific key work that can be attached
to a document (e.g: sun, holydays, summer for a picture from your last
holydays)</desc>
+ <desc0>Can't add specific key word</desc0>
+ <desc1>Key word can be add but with limitation: limited list, no
easy to way extend the list</desc1>
+ <desc2>Key word power are easy to add extend</desc2>
+ <comment>Possibility to add metadata dynamically via a rule engine
by attributing aspects to content . It is easy to extend rules / actions /
aspects , without heavy modifications . </comment>
+ <score>2</score>
+ </element>
+ <element name="hierarchicalclassification" title="Hierarchical
Classification">
+ <desc>Ability to do a classication in a predesigned
hierarchy</desc>
+ <desc0>This feature doesn't exist</desc0>
+ <desc1>The feature exist but is limited.</desc1>
+ <desc2>A new document can quickly be registered in the
hierarchy</desc2>
+ <comment>folders ( virtual ) , categorization , tagging
...</comment>
+ <score>2</score>
+ </element>
+ </element>
+ <element name="importformatsupported" title="File format supported
during importation">
+ <desc>Supported means that the internal engine is able to read or
parse file content to create preview file or find key words</desc>
+ <element name="importtext" title="text formats">
+ <element name="importformathtml" title="HTML files">
+ <desc></desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importformatrtf" title="RTF (Rich Text Format)">
+ <desc></desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importformatcsv" title="CSV">
+ <desc></desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importformatxml" title="XML files">
+ <desc></desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importformatopenoffice" title="OpenOffice files">
+ <desc>Staroffice and Openoffice document before release
2.0</desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ <element name="importformatopendocument" title="Opendocument
files">
+ <desc>Openoffice and others</desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importformatooo" title="MS Office files">
+ <desc></desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ </element>
+ <element name="importpicutre" title="picture formats">
+ <element name="importcommonpictureformat" title="common file
format">
+ <desc>Format are: jpg, gif, png, bmp, tiff, xpm, </desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importvectorialformat" title="common vectorial
format">
+ <desc>Format are: wmf, svg</desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="importcommercialpcitureformat" title="commercial
formats">
+ <desc>Format are: psp (PaintShopPro), psd (Photopshop)</desc>
+ <desc0>not supported</desc0>
+ <desc1>partialy (buggy or limited feature)</desc1>
+ <desc2>fully supported</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ </element>
+ </element>
+ </element>
+ </section>
+ <section name="internalprocessing" title="Internal processing">
+ <element name="internalcapability" title="Capability">
+ <element name="documentcrossreference" title="Cross reference">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="documentranking" title="Document ranking">
+ <desc>If a document have a good ranking it will be on the top of
the list during searchs. The ranking is determined by a list of parameter like
date of creation or amount of recent access to the file.</desc>
+ <desc0>Search are not ordered or the order</desc0>
+ <desc1>Limited, at best, just some documents are correctly sorted,
the rest is hidden in the mass (about 1/5 document correctly ordered).</desc1>
+ <desc2>Powerful ranking tool. Most important documents are on the
top of the list (4/5 documents correctly sorted).</desc2>
+ <comment>lucene indexation returns most pertinent first .
</comment>
+ <score>2</score>
+ </element>
+ <element name="filemanipulation" title="File manipulation">
+ <element name="previewcreation" title="Preview creation">
+ <desc>Please keep in mind that here we just evaluate the object
creation (does it work or not). We ignore how the results are published (e.g:
poor visiblity).</desc>
+ <element name="picturepreview" title="Picture preview">
+ <desc0>The software can't create picture preview</desc0>
+ <desc1>The software create picture preview for all the major
formats (jpg, png, bmp, gif)</desc1>
+ <desc2>The software can create preview for more than 10
picutres formats</desc2>
+ <comment></comment>
+ <score>1</score>
+ </element>
+ <element name="odtpreview" title="OpenOffice files preview">
+ <desc0>The feature doesn't exist</desc0>
+ <desc1>Work fine for at last odt files</desc1>
+ <desc2>Work fine for the majority of the formats</desc2>
+ <comment></comment>
+ <score>1</score>
+ </element>
+ <element name="mswordpreview" title="MS Office files preview">
+ <desc0>The feature doesn't exist</desc0>
+ <desc1>Work fine for at last doc files</desc1>
+ <desc2>Work fine for the majority of the formats</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ <element name="videopreview" title="Video preview">
+ <desc>Please keep in mind that DRM protected file can't be
load without official from its manifacturer. Because of this limitation, we
prefere to ignore these files in this evaluation. Preview could be a little
preview movie (e.g: in flash format) or just a picture.</desc>
+ <desc0>The feature doesn't exist</desc0>
+ <desc1>The software doesn't support the majority of the
files</desc1>
+ <desc2>The software can create preview for a large amount of
files</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ </element>
+ <element name="compressedfilesbrowing" title="Compressed files
browsing">
+ <element name="zipfilesprowsing" title="ZIP files">
+ <desc>zip files</desc>
+ <desc0>The engine see zip file as opaque binary</desc0>
+ <desc1>The engine can browse zip archive with limitation
(need of a specific action from the use, content not indexed, no keyword can by
attached to its content).</desc1>
+ <desc2>Zip archive are seen like common folder.</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ <element name="rarfilesprowsing" title="RAR files">
+ <desc>rar files</desc>
+ <desc0>The engine see rar file as opaque binary</desc0>
+ <desc1>The engine can browse rar archive with limitation
(need of a specific action from the use, content not indexed, no keyword can by
attached to its content).</desc1>
+ <desc2>Rar archive are seen like common folder.</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ <element name="tarfilesprowsing" title="TAR files">
+ <desc>tar.gz, tar.bz2 and tar.Z archives</desc>
+ <desc0>The engine see tar file as opaque binary</desc0>
+ <desc1>The engine can browse tar archive with limitation
(need of a specific action from the use, content not indexed, no keyword can by
attached to its content).</desc1>
+ <desc2>Tarball archive are seen like common folder.</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ </element>
+ </element>
+ </element>
+ <element name="publishing" title="Publishing">
+ <element name="editoriable" title="Editorialibilite!">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>Possibilit�de personnaliser sa page d'accueil .
</comment>
+ <score>1</score>
+ </element>
+ </element>
+ </section>
+ <section name="workprocess" title="Work Process">
+ <element name="editing" title="Edition tools">
+ <element name="journalisedchanges" title="Journalised Changes">
+ <desc0>No revision control system exist.</desc0>
+ <desc1>Every saved document are archived. Go back to an old
revision need an important amount of work.</desc1>
+ <desc2>Every change done with the internal editor are logged. It's
easy to come back to an old revision of the document from another user.</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="editwithstandalonetools" title="Standalone edition
tools">
+ <desc0>In oder to edit a document the user use the official
tool.</desc0>
+ <desc1>It's possible to use a remote stand alone tool to edit
documents.</desc1>
+ <desc2>All common feature are supported by a last one stand alone
tool.</desc2>
+ <comment></comment>
+ <score>1</score>
+ </element>
+ </element>
+ <element name="workflow" title="Workflow">
+ <element name="workflowlock" title="Lock">
+ <desc>Ability to lock file avoid data lost or synchronization
issues</desc>
+ <desc0>The feature doesn't exist</desc0>
+ <desc1>The feature just exist</desc1>
+ <desc2>The feature exist, administrator can quickly unlock a file
from an user. A time out system exists to unlock file after a certain amount of
time.</desc2>
+ <comment></comment>
+ <score>1</score>
+ </element>
+ <element name="workflowstep" title="step by step workflow">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>Configurable Worflow steps , granular rights . </comment>
+ <score>2</score>
+ </element>
+ <element name="workflowbpel" title="BPEL support">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>Basic . jBPM will be implemented in 1.4 , due for
september 2006</comment>
+ <score>1</score>
+ </element>
+ </element>
+ <element name="spellckecer" title="Groupware integration">
+ <desc0>no spell checker availble or it's just based on a too limited
dictionary that make it being a wast of time</desc0>
+ <desc1>working dictionnary but limited (e.g: grammar not included,
false positive, hard to extend)</desc1>
+ <desc2>Powerful dictionary</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ </section>
+ <section name="architecture" title="Architecture">
+ <element name="security" title="Security">
+ <element name="authentifaction" title="Authentification Backend">
+ <element name="authenbackendldap" title="LDAP">
+ <desc0>No LDAP based authentification availble</desc0>
+ <desc1>LDAP availble but limited (e.g: group mapping limited,
etc)</desc1>
+ <desc2>LDAP is one of the recommended authentification
backend</desc2>
+ <comment>native OpenLDAP, ActiveDirectory via JAAS/Kerberos
5</comment>
+ <score>2</score>
+ </element>
+ <element name="authenbackendad" title="Active Directory">
+ <desc0>No Active Directory based authentification
availble</desc0>
+ <desc1>Active Directory availble but limited (e.g: group
mapping limited, etc)</desc1>
+ <desc2>Active Directory is one of the recommended
authentification backend</desc2>
+ <comment>accessible using JAAS / Kerberos 5</comment>
+ <score>1</score>
+ </element>
+ <element name="authenbackenddb" title="data base">
+ <desc>Here we do not attach importance on supported data bases,
please see the storage section</desc>
+ <desc0>No data base base authentification availble</desc0>
+ <desc1>Data base availble but limited (e.g: group mapping
limited, etc)</desc1>
+ <desc2>Data base is one of the recommended authentification
backend</desc2>
+ <comment>alfresco can handle simple user / password
authentification</comment>
+ <score>2</score>
+ </element>
+ </element>
+ <element name="signaturemechansim" title="Signing">
+ <desc>Is possible to create digital cypher (e.g: GNU PGP)</desc>
+ <desc0>Feature not supported</desc0>
+ <desc1>Fetautre partialy supported</desc1>
+ <desc2>Feature fully supported</desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ <element name="digitalwatermarking" title="Digital watermarking">
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ <element name="DRM" title="DRM">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ <element name="SSL" title="SSL">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>possible to use Apache mod_ssl to access the web client
via https .</comment>
+ <score>0</score>
+ </element>
+ </element>
+ <element name="integration" title="Integration">
+ <element name="syndication" title="Syndication">
+ <desc></desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>RSS , Atom</comment>
+ <score>2</score>
+ </element>
+ <element name="soa" title="SOA">
+ <desc>SOA, SOAP, XML/RPC, (...) capability</desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>SOA Integration. Modern Architecture . Repository
accessible via Web Services , JSR170 , JSR168</comment>
+ <score>2</score>
+ </element>
+ </element>
+ <element name="storage" title="Storage">
+ <desc>Please keep in mind, that the score doesn't mean that an
element is good or bad. e.g: a solution that doesn't use the filesystem for the
data storage can be good. See: QSOS Method to get more details</desc>
+ <element name="filesystem" title="File System">
+ <desc>Can the solution use the file system to store data (files,
description, ...). Please, descript the recommended environment.</desc>
+ <comment>Stockage du contenu sur le filesystem . </comment>
+ <score>2</score>
+ </element>
+ <element name="database" title="Data Base">
+ <desc>No data storage available. Please, descript the recommended
environment.</desc>
+ <comment>MySQL is used by default . datasource is however
configurable to use SQL Server , Oracle ...</comment>
+ </element>
+ <element name="datawarehouse" title="Data Warehouse">
+ <desc>Can user create link to physical material like book or paper
document?</desc>
+ <desc0>This feature doesn't exist</desc0>
+ <desc1>The feature exists with limitation (TODO)</desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score>0</score>
+ </element>
+ </element>
+ <element name="multisite" title="Multisite architecure">
+ <desc>Is it possible to have a different decentralised site?</desc>
+ <desc0>Server is not designed to be decentralised</desc0>
+ <desc1>Some part of the service can be decentrralised but there is
still a bottleneck that limited the number of user (e.g: centralised data
base)</desc1>
+ <desc2>Thanks to a powerful synchronisation system every site can by
temporarly disconnected with just a service limitation interuption (e.g: read
only access)</desc2>
+ <comment></comment>
+ <score>1</score>
+ </element>
+ <element name="loadbalancing" title="Load balancing">
+ <desc>Load balancing capability of the server.</desc>
+ <desc0>The server is not designed to support load balancing</desc0>
+ <desc1>The server support load balancing but bottleneck still exist
(e.g: core software can be load balanced)</desc1>
+ <desc2>Load balancing is fully support</desc2>
+ <comment>Load balancing available with Apache Mod JK</comment>
+ <score>0</score>
+ </element>
+ <element name="failover" title="Fail over">
+ <desc0>Failover is at best limited</desc0>
+ <desc1>Failover works but important a lot of work (humain
intervention to set up the mechanim)</desc1>
+ <desc2>Failover works fine thanks a good designed</desc2>
+ <comment>recommanded to Apache Mod JK to provide fail over .
</comment>
+ <score>0</score>
+ </element>
+ </section>
+ <section name="administration" title="Administration">
+ <element name="rights" title="Rights">
+ <element name="usersrights" title="User's rights">
+ <desc0>Feature is not supported</desc0>
+ <desc1>Feature is partialy supported</desc1>
+ <desc2>Feature is supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="groupesrights" title="Group's rights">
+ <desc0>Feature is not supported</desc0>
+ <desc1>Feature is partialy supported</desc1>
+ <desc2>Feature is supported</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="role" title="Role">
+ <desc>Can we create a virtual user with specific rights and give
his rights to phyical people (e.g: the role "backup administrator" read access
on the data base)</desc>
+ <desc0>The feature doesn't exist</desc0>
+ <desc1>The feature exists but is limited</desc1>
+ <desc2>The Feature is available or can easily be simulated thanks
to a powerful group system</desc2>
+ <comment>Several predefined roles ( contributor , editor ,
coordinator ... ) defining a combination of rights : read , write , execute ,
create , delete .</comment>
+ <score>2</score>
+ </element>
+ </element>
+ </section>
+ <section name="webcompatibility" title="Web compatibility">
+ <element name="webstandards" title="Standards">
+ <element name="htmlstandard" title="HTML">
+ <desc>http://validator.w3.org</desc>
+ <desc0>Page not valid (parse errors)</desc0>
+ <desc1>Page not valid with important errors (encoding
mismatch)</desc1>
+ <desc2>Page not valid, but with minor errors (missing "alt"
attribute, use of unknow attribute)</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="xhtmlstandard" title="XHTML">
+ <desc>http://validator.w3.org</desc>
+ <desc0>Page not valid (parse errors)</desc0>
+ <desc1>Page not valid with important errors (encoding
mismatch)</desc1>
+ <desc2>Page not valid, but with minor errors (missing "alt"
attribute, use of unknow attribute)</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ <element name="cssstandard" title="CSS">
+ <desc>http://validator.w3.org</desc>
+ <desc0>CSS doesn't or no valid not valide (parse errors)</desc0>
+ <desc1>CSS not valid with important errors (encoding
mismatch)</desc1>
+ <desc2>CSS not valid, but with minor errors (missing "alt"
attribute, use of unknow attribute)</desc2>
+ <comment></comment>
+ <score>2</score>
+ </element>
+ </element>
+ <element name="webbestpractice" title="Best Practive">
+
<desc>http://developer.apple.com/internet/webcontent/bestwebdev.htmls</desc>
+ <element name="tablepsitioning" title="Table Positioning">
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>???</comment>
+ <score></score>
+ </element>
+ <element name="frameuse" title="Frame use">
+ <desc><frame> </desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment>???</comment>
+ <score></score>
+ </element>
+ <element name="firameuse" title="iFrame use">
+ <desc><iframe> </desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ <element name="cssdesignedforprintout" title="css designed for
printout">
+ <desc><iframe> </desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ <element name="cssdesignedforprintout" title="css designed for
printout">
+ <desc><iframe> </desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ </element>
+ <element supportedbrowser="supportedbrowser" title="Supported Browser">
+ <element name="browsermozillafirefox" title="Mozilla and Firefox">
+ <desc>Firefox > 1</desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ <element name="browserkonqueror" title="Konqueror">
+ <desc>Konqueror > 3</desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ <element name="browsermsie" title="MSIE">
+ <desc>MSIE > 5</desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ <element name="browsersafari" title="Safari">
+ <desc>Safarie</desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ <element name="browserlegacy" title="legacy browsers">
+ <desc>Legacy browser are browser outdated like MSIE4 and Netscape
4.* .</desc>
+ <desc0></desc0>
+ <desc1></desc1>
+ <desc2></desc2>
+ <comment></comment>
+ <score></score>
+ </element>
+ </element>
+ </section>
+</document>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qsos-commits] qsos/sheet/cms/Alfresco Alfresco-1.3.qsos,
Raphaël Semeteys <=