Initial CMS preview

1
Initial CMS preview
2
TIME SCHEDULE

• Prototypes 1 month
• Inmediate actions 6 months
• Milestones 18 months
• Deliverables none

3
STAGES

• Test problems analysis
• Initial test-cases will be used to drive the
  first content and tools service prototypes
• Web service prototypes with full web services
  definitions (meaningless??)
• Technology watch and recommendation
• Test problems deployment and evaluation
• Technology adoption and deployment

4
Identifying Users

• Pose the requisites to the system
• Having them satisfied, sucess is guaranteed.
• Workgroup, Administrators, Researcher, User,
  Partner, WP4.3

5
Identifying Requisites

• Functionalities for the system are part of them
• Test case submission, storage, publishing,
  tracking and versioning
• Helpdesk system
• FAQ
• Forum (or BB) -gt Polls (also?)
• Users and groups. Different roles, different
  permissions. Security issues.
• Workgroup features PM, TODOs, AB, Calendar,
  project logging reporting, sharing capabilities
  for project data or files
• CRM features marketing, keep the interest up,
  invitating to add test cases, customer care
• Requisites pinpointed in the presentation only
  included here. Do you want to add more???

6
CMSes

• Different views from different users. Multi user
  ease of use. Powerful administration features.
  EDITING CAPABILITIES.
• Security integration.
• Extensibility and modularity. Different formats
  supported.
• Usability, performance, cross browser support,
  accesibility, care of GUI.
• Training Documentation available
• Community resources support
• Number of installations, demo features

7
CMSes

• Basics XOOPS, MyPHPNuke, PHPNuke, Postnuke
• Enterprises Mambo, Typo3
• Others Nucleus, OpenCMS, Zope/-Plone, uPortal,
  SnipSnap
• More categories Groupware TUTOS, dotProject,
  phProject, phpGroupWare

8
Mambo

• Pros
• -Easy installation
• -Word processor editing.
• -Component aware
• -Widely accepted and priced
• -Large community support
• Cons
• -Kind of unfriendly editing. Too many features
  complexity.
• Hard to customize
• Lack of documentation http//www.netshinesoftware.
  com/mambo-tutorial.html

9
e107

• Pros
• -Ease of use and install
• -Big support and documentation.
• Cons
• -Unsecure.
• -Limited group support
• -Limited lang support and UTF-8
• Cannot comment editing features

10
Typo3

• Pros
• -Open source commercial level
• -Extremely powerful
• -Module awareness
• -Good documentation
• -Very good WYSIWYG-editor
• Cons
• -WYSIWYG-editor tag dependant
• -Extremely complicated to use and install to some
  extent
• -Step learning curve
• -Very little documentation for extensions
• -Lack of support to older versions

11
XOOPS

• Pros
• Easy extensible, module oriented (OO)
• Core code is minimal
• Ease of installation
• Big and active community
• Cons
• -Limited editor capabilities. Admin UI needs lots
  of work.
• -Very strict layout for GUI.
• -Limited code modification
• Not seen templates (none of them are good and
  clean?)

12
Other systems explored

• OpenCMS (no demo)
• Drupal
• Nucleus
• uPortal
• eGroupWare
• PHProjekt
• WebCalendar
• Some forum system should be looked phpBB

13

• Other issues

14
Php4 vs. Php5

• Packages of PHP 4 are available for Mac OS X
  10.3 and 10.2, but these are no longer actively
  maintained.
• http//www.entropy.ch/software/macosx/php/

15
PHP - Stability

• Not stable in versions 3.0.11 to 3.0.16.
• Problems on version 3.0.17
• Version 4.0.3pl1is okay
• Version 4.0.4 has problems.
• Not further versions reviewed
• Mac OS X installs version 4.3.10

16
Apache1 vs. Apache2

• Apache2
• Unix Threading, New Build System, Multiprotocol
  Support, Better support for non-Unix platforms,
  New Apache API, IPv6 Support, Filtering,
  Multilanguage Error Responses, Simplified
  configuration, Native Windows NT Unicode Support,
  Regular Expression Library Updated, Module
  Enhancements (mod_ssl,).
• If you intend to use Apache2 with one of the
  threaded multi-processing-modules (MPMs), you
  must ensure that the modules and libraries the
  MPMs depend on are thread-safe.

17
Apache2 - Stability

• If you intend to use Apache2 with one of the
  threaded MPMs, you must ensure that the modules
  and libraries the MPMs depend on are thread-safe.

18
Apache2 - Performance

• DSO is the only way PHP is supported now on
  Apache 2.
• Embedded modules vs. DSO
• Different MPMs
• Static content mmap sendfile (Apache2)
• References
• http//httpd.apache.org/docs/misc/perf-tuning.html
  
• http//httpd.apache.org/docs-2.0/misc/perf-tuning.
  html