Version 2 (modified by wallento, 5 years ago) (diff)



The central idea of LISTrac can be described in a few points by the requirements we put on our project management system:

  • Use Trac and SVN, with a Trac environment and a repository for each project
  • One authorization for all projects, no anonymous access (although possible with current project status)
  • Centralization of user information (name, e-mail-adress)
  • Fine grained authorization for Trac and SVN with consistent groups, controlled by project administrators
  • Beside this no further functionality for the project administrators (i.e., plugin management etc. by the system administrators)
  • Global groups, that are kept in sync with the project group files
  • Repository hooks, that in special can be opted by users
  • Use as much as possible from existing plugins
  • No significant invasive changes to the Trac core and the plugins. When changes necessary try to bring them to the mainline development

Apparently those criteria conflict with the standard Trac setup, so that we current work on necessary steps, that are

  • Management scripts and plugin for global management (done)
  • Centralize management of groups and synchronization of them (done)
  • Evaluate how to keep session information and centralized user information in sync (current work in progress)
  • Extend hook system

Bugs/Feature Requests

Existing bugs and feature requests for LisTracScript are here.

If you have any issues, create a new ticket.


Download the zipped source from here.


You can check out LisTracScript from here using Subversion, or browse the source with Trac.


We use it at our university network, where all users are known. They authenticate globally for all projects and the project administrators can grant fine grained access to Trac and SVN, but have no further rights beyond this.

Recent Changes

[7643] by wallento on 2010-02-18 18:52:03
New hack LisTracScript, created by wallento


Author: wallento
Maintainer: wallento