-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, I'm *really* sorry for disappearing very suddenly, but I'm back, and I'm now using Savane in production use (though not 100% for it's intended purpose). Anyway, I have a few things I'd like to suggest, and point out.

First off, I noticed a GPL violation -

* in backend/darwin, I included scripts from the OSXGnu project and credited them as well (the scripts were unmodified). The copyright notice has been changed to just say Savane project, and says nothing about the originating code is from. (The credit to them still exists in the readme file though).

Anyway, Feature Requests (that I would like to code if no one minds):

* Support for project MySQL creation through the backend
SourceForge has the ability to allow users to create and manulate MySQL databases for there projects. While I don't think Savannah/GNA are going to use this function, I am going to code into my local Savane copy because my projects do require it. This feature will be toggliable via savannah.conf, and managed as a separate crontab item. The frontend can control a projects right to use MySQL, and how many DBs they can create and name limitations, etc.

* PHP5 Fixes
It seems Savane still has a few minor issues with PHP5 which I've noticed. I'm comparing the sections that are bugging out with PHP4 and hopefully should have patches soon.

* Wiki
I remember this being purposed back when I was active on these lists, and I've been expanding my PHP coding skills since I left, and I think I can actually code one at this point, although it will take awhile cause it is a non-trivial thing to write

* Optimize Forum code
There are times where forums are more useful them wiki's or mailing lists, and since the code already exists, it should prob. be fixed and cleaned up

* Custom Tracker Creation
Another SF style feature - this will allow projects to create there own trackers. A good way to handle this in the DB is required though (creating tables on the fly doesn't sound like a great idea)

* Portability to non-GNU/Linux systems.
I have Savane running nicely on OpenBSD but getting the install to get that far isn't fun. Make chokes in a few places when on not using GNU/Linux (hostname being the biggest problem). I used GNU Linux because I also tried to install Savane on a machine that is using busybox instead of coreutils and it blew up wonderfully.

* Creation of a frontend only package
I'm not sure about the rest of you but the frontend of Savane is also quite useful by itself such as a support tracker/mini-forums section. It might be worthwhile to get Savane fairly easy to install without the backend. (Basically it just needs premade css templates, a wrapper function to allow Savane to work without gettext (should be very easy to write), and features that use the backend disabled, as well as a web-based installer

* Polls
While Matheui has an item on the task tracker about this, I am talking polls for projects to check on new features as a general survey (aka should project x do feature y) with comment code (kinda like Slashdot).

* Better documentation, esp for Apache 2
I had to go find my notes on what I did to get Savane setup on Darwin to properly get parts to install. The section on getting Apache 2 to properly work doesn't work with the lastest A2.

I have other feature ideas but I wanted to pitch these first in terms of ease of use/feature improvements, etc. I also didn't want to submit these to the tasks tracker without talking about them first on the lists, mostly because I've been inactive for so long.
M. Casadevall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFCmpCT0Q/LDcgAdNURAi2UAJ9COcmKF2HKz3M4JNQUj02axgoRhwCgizR+
BquyQIUOqMCtW3+yqcpBBh0=
=MQvQ
-----END PGP SIGNATURE-----

_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev

Reply via email to