Recent changes to feature-requests

Speed up clients

Steve Willoughby — Fri, 05 Dec 2003 20:14:23 -0000

Don't download all the category codes and owners and
such for every client startup--this has been known to
take way too long at sites with large numbers of staff
and category lists. Instead, load only what you need
just when you need it.

Improve report generation GUI

Steve Willoughby — Tue, 28 Oct 2003 22:54:04 -0000

Reqadm-report was always supposed to have a full GUI
where you could query the data and get graphs on-
screen which you could zoom in on or fiddle with. Now
maybe when we move to MySQL we'll just have people
use other third-party reporting tools against the
database directly, but we really ought to update
reqadm-report too.

Migrate from AthenaDBMS to MySQL

Steve Willoughby — Tue, 28 Oct 2003 22:45:45 -0000

Change out the database access code from the Athena
DBMS to use MySQL instead. Then we need to move
the configuration and site/user info into the database,
allowing admins to use other tools to manage REQADM
as a part of their IT infrastructure without needing
layers of adapting scripts and so forth.

In the process, we will FINALLY* jettison the old ASCII
files where tickets are stored and put everything in the
SQL database.

*and there was much rejoicing.

Improve install process

Steve Willoughby — Tue, 28 Oct 2003 22:39:54 -0000

REQADM's install process is quite arguably one of its
weak points. Once you set it up, you're set to go but
getting there is a PITA. I'd like to see the following:

* Totally remove dependencies on localisms from the
environment where it was originally designed to be used

* Remove the need to "burn in" shared authentication
keys in the binary clients and server, and move to using
dynamic key exchange or user profiles so a generic
client can work anywhere.

* Replace the old means of getting local user
information with a MySQL database table(s) which
external site tools can maintain and REQADM can read.

Set up REQADM sources in CVS

Steve Willoughby — Tue, 28 Oct 2003 22:26:49 -0000

Go through the current source code set and clean it up
for distribution (try to remove the site dependencies
that have crept in), and upload into SourceForge's CVS
repository.