Changes between Version 4 and Version 5 of CityTrac


Ignore:
Timestamp:
Dec 16, 2007 4:35:11 PM (7 years ago)
Author:
Rottenchester
Comment:

Expanded entry a bit

Legend:

Unmodified
Added
Removed
Modified
  • CityTrac

    v4 v5  
    33== Description == 
    44 
    5 CityTrac has two goals: 
     5CityTrac is the informal name of a project to make Trac more useful to place-based wikis with a large number of users.  CityTrac arose from the desire of a small group of users of [http://projectsycamore.org Sycamore] to migrate to wiki software with a larger development community.  CityTrac has two goals: 
    66 
    7 1.  Create scripts to migrate wikis stored in [http://projectsycamore.org Sycamore] to trac. 
     7 1.  Create scripts to migrate wikis stored in Sycamore to trac. 
    88 
    9 2.  Create plugins to replicate Sycamore features missing from trac, and to add new features in trac which are tailored for use in city wikis. 
     9 2.  Create plugins to replicate Sycamore features missing from trac, and to add new features in trac which are tailored for use in city wikis. 
    1010 
    1111At this point, CityTrac makes the following assumptions, which needn't be cast in stone: 
    1212 
    13 1.  The target database is MySQL. 
     13 1.  The target database is MySQL. 
    1414 
    15 2.  The trac instance will use the acct_mgr plugin with the db backend.  In other words, user information is stored in the session_attribute table. 
     15 2.  The trac instance will use the acct_mgr plugin with the db backend.  In other words, user information is stored in the session_attribute table. 
    1616 
    17 At the moment, CityTrac is an alpha project.  Here's the current set of plugins: 
     17The code posted for CityTrac is all tagged as alpha.  Here's the current set of plugins: 
    1818 
    1919[[ListTagged(expression=plugin+citytrac)]] 
    2020 
    21 Here are the current scripts; 
     21Here are the current scripts: 
    2222 
    2323[[ListTagged(expression=script+citytrac)]]