Warning: Can't synchronize with the repository (Unsupported version control system "svn": "/usr/lib/libxml2.so.2: undefined symbol: gzopen64" ). Look in the Trac log for more information.

Dolmen/Roadmap

This page has come to life so we can collect ideas about further actions on Dolmen. Time goes top to bottom. Your notes do not need to be verbose -- just dump things here as you go by so they will not be forgotten and we can do a somewhat "collective brainstorming" as we move Dolmen forward.

Todo List:

Pending Tasks

  • Snappy (assigned to: all, trollfot main driving force for now, due date: July 24th, 2009)
  • i18n: for dolmen core packages, create per-package buildout.cfg files in case they need to have a translation domain (see listing below)
  • Content Versioning: (assigned to: pumazi)
    1. Move menhir.component.versioning to dolmen.versioning (complete)
    2. Move menhir.versioning to dolmen.app.versioning (complete)
    3. Write dolmen.app.versioning (due date: July 25th, 2009)
    4. Verify dolmen.versioning test coverage is 100% then release beta version to pypi (due date: ?)
    5. Verify dolmen.app.versioning test coverage is 100% then release alpha version to pypi (due date: ?)
  • Content Workflow: (assigned to: tentatively pumazi )
  • Tagging system: (assigned to: trollfot )
    • Needs to start the dolmen.tag package
    • Implementation will lies in dolmen.app.tagging
    • We need a global metadata policy (including a tab to edit them locally)
  • Commenting system: (assigned to: trollfot )
    • Started the menhir.simple.comments package
    • Tests written and working
    • Needs to work on UI mainly
  • Accessibility general work
    • We need to work on the w3c norms to make the site HTML/CSS code validate.
    • We need an accessibility policy
  • General adminitration Panel
    • This includes : additional packages configuration
    • Local installation / uninstallation
    • Global policies control (email, metadata, etc.)
  • Local security policy
    • Implementation of Groups is needed. (High priority)
    • Local roles UI (Joerg request, almost done)
  • Content framework
    • The basic dolmen.content package is globally ready but needs more tests Along with that, we need to extract the whole browser dependant elements from there. They now belong a dolmen.forms.x package.
    • We need to work on the FTP/JSON/DAV representation now
    • We need to release it.
  • Documentation (assigned to: Suno Ano, due date: August 24th, 2009)
    • Sphinx documentation
    • General API
  • monitoring/autostart/autorestart Dolmen Applications we should include  http://supervisord.org/ with the buildout in order to make dolmen applications automatically start at boot, restart them if necessary and monitor as well as log their behavior/actions for debuging and administrative purposes.  Here is a paster specific howto that shows howto set things up. (assigned to: ?, due date: ?)
  • Hosting - Bugtracking and Official Dolmen Website: now that we have  http://demo.dolmen-project.org/demo-site in place, the next task on the infrastructure part will be to put in place  http://bugtracking.dolmen-project.org which will point to the bugtracking section of a trac site.  http://www.dolmen-project.org will point to the wiki part of this trac site (yes, one trac instance for both; this is good, if only for reasons of linking back and forth among the two). This will be up and running by July 24th. Note that from there on, the source code management system will be GIT.  Here is why this is a good move. (assigned to: Suno Ano, due date: August 6th, 2009)
  • Email - indivdual Email accounts plus Mailinglist: On August 28th,  http://mail.dolmen-project.org will point to webmail accounts i.e. we will have for example <username>@dolmen-project.org available, both, via external MUA (Mail User Agent) like for example Thunderbird as well as we will be able to use Webmail at  http://mail.dolmen-project.org. This will be dovecot driven IMAP accounts. Also on August 28th, there will be mailinglist(s) at  http://lists.dolmen-project.org. Those lists will be driven by Mailman. Of course, there will be spam protective measures for both URLs in place.  http://mail.dolmen-project.org will also feature virtual email accounts i.e. a user does not need to have a UNIX system account on the machine in order to use his email address <username>@dolmen-project.org. This will allow us to easily add/remove new users i.e. provide them with a <new_user>@dolmen-project.org email address. (assigned to: Suno Ano, due date: August 28th, 2009)
  • UI design: The general idea is to consolidate actions into succinct menu items. Two menu items that are currently being thought of are 'Action' and 'View'. Example items in the 'Action' menu are 'Add to Folder', 'Edit', 'Delete', etc. Examples for the 'View' menu would be for default view, viewing a specific version, etc. (assigned to: ?, due date: postponed until future release)

Finished Tasks

  • Design Documents: Create so-called design documents for Snappy. At first we are going to create a wiki page in order to draft user requirements for Snappy. For more info on possible design documents go  here --> URD, SRD, ADD, DDD. (assigned to: Suno Ano, due date: June 19th, 2009)
  • Hosting: We are going on-line with a Dolmen site at June 12th. OS will be Debian with OpenVZ. Trac, buildbot, mailing list, etc. will follow later this summer -- all will get their own OpenVZ Virtual Environment and public IPv4 address. SSH access and root permissions for pumazi and trollfot will be available to those VEs concerned with Dolmen stuff e.g. trac, GIT, mailing list, etc.. (assigned to: Suno Ano, due date: June 12th, 2009)
  • Domain name: trollfot is going to take care about it; it will be dolmen-project.org. Domain owner (Registrant) will be trollfot. Maybe Admin and/or Tech contact should be the person doing the main sys admin work for the Dolmen project. (assigned to: trollfot, due date: June 10th)
  • with regards to a msgid norm, we might use action_<particular_action>, label_formfield or form_field_fieldname for example
    • we decided to use the default message for the msgid except for very long default messages in which case we use labels
    • see  here for how it might be done

Dolmen core packages that need translation domains

  • dolmen.app.authentication
  • dolmen.app.clipboard
  • dolmen.app.layout
  • dolmen.app.site
  • dolmen.file
  • dolmen.imaging
  • dolmen.relations
  • dolmen.translations

Dolmen packages that have been buildout'ified

including above packages

  • dolmen.app.content
  • dolmen.app.security
  • dolmen.content
  • dolmen.blob
  • dolmen.field
  • megrok.layout