Flyspray - The bug killer!

People might like to know exactly how to use Flyspray. Some documentation and help files might be nice.

For version 1.0 we need a nice new layout for Flyspray.

Some ideas so far:

• The theme should be bright, clean, modern and colourful.
  • I personally think it should look a bit like http://www.oswd.org, "Web 2.0"
  • Also nice look and feel: http://fisheye1.cenqua.com/changelog/matheclipse/ (not a BTS)
  • A good attempt is Paul's "Clean theme", but it's not very colourful/modern (dark grey parts are ugly) and there should be more significant layout changes. http://tasks.pureco...

A list what could/should be done for 1.0

• get rid of modify.inc.php (make do-modes pluggable)
• database transactions
• new templating engine (eval free)
• user area (summed up notifications, own notes)
• remove the usage of $_REQUEST and the Req class (only reduce)
• add two checkboxes SSL and TLS to the SMTP configuration section in order to permit usage on servers that requires them (f.e gmail)
• Find no longer used functions in the code and remove them
• Add an option for SSL login
• permit multiple flyspray installations with a single codebase.
• Add support for both sqlite and mssql - not needed.
• Make threaded mail really work.
• Localize the Installer/Upgrader
• cleanup messy code like includes/events.inc.php, scripts/depends.php and Notifications::GenerateMsg(), class.database.php
• Upgrade to SwiftMailer v3 (when released for PHP4)
• IRC bot (?)
• simplify task changes ( FS#1203 )? quick-edit is enough
• link to dokuwiki syntax
• replace FS prefix
• conversion scripts for most popular BTs
• improve voting and comments
• lock password capability?
• auto-close tasks...
• http://forum.flyspray.org/viewtopic.php?pid=731 ?
• restrict assignees (group permission → "show for assignees", default 1)
• last-edited-by column, others,  FS#1330  (redundancy table?)
• hide not editable fields
• allow ordering of fields
• for upgrading, to not make all fields project level?
• e-mail language depends on sender not recipient
• Provide functionality similar to bugzilla 3.0 "whining" (Custom scheduled notifications)

With all informations on flyspray, it’s possible to generate a gantt chart.\\
For this, some php code exists :\\
- http://www.aditus.nu/jpgraph/
- http://www.graphviz.org/
- http://www.phpclasses.org/browse/package/2737.html

Everything is currently hard-coded. Create a plugin system that allows a module to be simply “dropped into” a plugins/ directory, enabled in the options, and have the plugin just work.

Possibilities might include alternative methods of notification, perhaps a documentation subsystem, or even simple things like voting for tasks.

The user should NOT have to edit existing Flyspray source code to make a plugin work.

Currently, only one owner can be applied per category (at least, that's what the tooltip implies). The ability to add more than one user, a user group, or a mix of the two to a category would be ideal.

Often times, more than one programmer will work on and maintain a feature that cannot be divided into subcategories with the various programmers dispersed accordingly. In such cases, setting all such programmers as owners of the category is beneficial in that they will all receive notifications...