DRAFT : Evaluation of Django

CMS Platform

  • State the CMS version number that is audited against the requrements Django 0.95

  • Platform (i.e. what does it run on--e.g. PHP, Python, etc) Python

  • Backends (e.g. files (custom XML in CVS, etc), DB (MySQL, Postgres, etc) Django works with PostgreSQL (recommended), MySQL and SQLite.

  • Architecture
    • "Gateway Interface" (e.g runs in mod_php / Zope app server connected to on port 8080, etc) Django follows the WSGI spec, which allows it to run on a variety of server platforms. mod_python is recommended. For other platform, see http://code.djangoproject.com/wiki/ServerArrangements

    • Short description of software architecture or link to such document (major components (such as auth, editing, caching, etc), important data flows, bottle necks (esp. database hammering))

TODO

  • List of required CMS modules to fulfill these requirements

All modules described here in basic distribution (unless I indicate otherwise). Just go to admin>feature and activate.

  • Resource usage
    • External runtime dependencies (mod_php / database / 3rd party libs)
      • State minimum required version number if appropriate
    • Anticipated system requrements for current known work load (best effort guess is fine)
      • http://www.gnome.org/stats/usage_200606.html

      • For now this is just informative, we'll try to come up with better numbers based on expected future work load expected after the revamp
      • CPU / Mem
      • Perhaps requred disk space for installation (not content)

TODO

Security

robust against attack attempts TODO

some features protected by authentication TODO

option to communicate over a secure channel (SSL) TODO

upstream is active releasing security updates Yes

URLs

TODO

I18N

  • ways to translate standard CMS strings

Yes

  • Use PO files here as well

Yes, via

  • ways to translate content
    • How far is Tiki from using/importing/exporting PO files for publishing content in several languages?

    TODO

    • preferably show translators what changed and what needs updating

TODO

  • This is a must for me. Translation is impossible without it, and out-of-date translations are worse than no translations. For others, translation via .po files might be a must. MurrayCumming

TODO

  • How far is Tiki from having a revision control system showing to translators what changed in the original English pages and what needs updating in the translations?
    • I need to check. This would be a most welcome feature to Tiki. We need it as well for our documentation.

  • preferably get language settings from browser (Accept-Language) and session (cookies)

TODO

  • have URLs to translated pages, so they can be directly referenced

TODO

  • == Authoring ==
  • a comfortable framework for editing content
    • can be wiki style, but does not have to

TTODO

  • "draft" content, which is already managed in the system, but not yet published
    • translators can do their job before content appears to the public
    • pre-edit text to be published at a specific date and time

TODO

* perhaps automatically publish on a specific date and time

TODO

  • track who has rights to edit a page

TODO

  • track who did edit a page
    • I think we should default to anyone being able to edit a page. Logging in is already an obstacle. MurrayCumming.

TODO

  • track exactly what was changed. For instance, like a diff.

TODO

  • can display when a page was last updated

TODO

  • perhaps change management, so older version of a page can be recalled

TODO

  • copyright and licensing information can be displayed on the pages

TODO

  • == Markup ==
  • the served html should be accessible
    • with a wide range of browsers (desktop and mobile)

TODO

  • for people with disabilities

TODO

  • the markup should primarily capture content structure not representation
    • (i.e. "heading" versus "big bold font")

TODO

  • support hierarchical URLs (subdirs)

TODO

  • support hierarchical navigation (submenus)

TODO

  • preferably have a site map

TODO

Feeds

  • shall provide feeds (RSS, Atom, etc)
    • news (for visitors)
    • site updates (for content authors)
  • peferably shall integrate external feeds (e.g. from gnomefiles.org)

TODO

There are RSS feeds for all major features: calendar, wiki, articles, forums, blogs, etc

Theming

  • shall be themeable to adopt the gnome look

TODO

Expertise

There should be enough expertise in our community to:

  • select (know the CMS enough to assert it meets our reqs)

TODO

  • install (the whole stack, includng RDBMS)

TODO

  • manage (keep updated and secure, without breaking it)

TODO

  • fix (add missing features or critical updates not yet released by upstream)

TODO

  • full text search TODO

  • perhaps keywords assigned to pages? TODO

  • something else?

Backup

  • it should be easy to make backups
  • it should be easy to restore backups
  • perhaps a replicate server in case the main one goes down?
    • perhaps clustering?

TODO

GnomeWeb/CmsRequirements/DjangoEval (last edited 2008-02-03 14:45:26 by localhost)