[kforge-dev] Personal backlog of tasks

[Rufus Pollock]

Our primary Backlog and planning page at:

	http://www.okfn.org/kforge/wiki/KforgeRoadmap

However I have accumalated the following items in a text file and
thought I should dump prior to today's planning meeting in Cambridge (at
which we can integrate them into the main list ;)).

Regards,

Rufus

--------

1. KFORGEHOME -> to a better name? (e.g. KFORGE_HOME)
   * Date: 2005-06-20
   * Priority: Low

2. Create environment variable KFORGE_ETC which points to KFORGE config
   * Date: 2005-06-20
   * Priority: Medium
   * Motivation: will allow us to run 'live' off repository rather than
having to install but will still allow install to work
   * Comments: internally etcdir defaults to KFORGEHOME/etc/kforge

3. Norm path configuration paths
   * Date: 2005-06-20
   * Priority: Low
   * Motivation: currently because of the way config file must work when
prefix is just '/' end up with '//' at front of many paths

4. Apache configuration helpers
   * Date: 2005-06-20
   * Priority: High

5. web/dav plugin
   * Date: 2005-06-20
   * Priority High

6. Sort out test system to be able to run individual tests
   * Date: 2005-06-20
   * Priority: High
   * Comments: Since some tests read and write directories etc the test
harness should check that not on an ordinary live system by checking
that KFORGEHOME is set and to put up a confirmation dialogue if it is
not set.

7. Update Paths and Config to use SystemDictionary
   * Date: 2005-06-20
   * Priority: High
   * Comments: disable kforge-config-rebuild script at same time since
won't be working any longer

8. Move logging config into python file
   * Date: 2005-06-20
   * Priority: Medium
   * Motivation: reduce dependency on external files (particularly when
most of config is not to be configured by users of the system)
   * Comments: would still need some config of the logging to be
settable (e.g. log level, log file name and location ...) so maybe not
worth bothering with

9. Factor out gforge config stuff from kforge.conf
   * Date: 2005-06-20

10. Investigate Apache config files to check whether you can have
relative as well as absolute url pathes
   * Date: 2005-07-10
   * Priority: High
   * Motivation: Needed before writing apache config generation as
affects whether we have to have different outputs depending where
various config will go relative to VirtualHosts etc
   * Comments: For example can we have:
       ScriptAlias wiki "...."
     as opposed to
       ScriptAlias /wiki "..."
     The benefit of the first option is that if we move it inside a
<Location> section (e.g. inside /private) it would still work