All Projects

ID Project Category Task Type Severity Summary Status Opened by Opened Progress
 1506 FlysprayBackend/CoreBug ReportLow Test ClosedFloele06.07.2009
100%
Task Description

Test

 1174 FlysprayBackend/CoreTODOMedium TODO List for 1.0 ClosedFloele27.01.2007
100%
34219 Task Description

A list what could/should be done for 1.0

  • language for email/jabber notification currently depends on sender(user who changes something), not the recipients preferences - needs loading translation everytime to the recipients prefered language changes in the sending loop. done.
  • Provide functionality similar to bugzilla 3.0 “whining” (Custom scheduled notifications) reminder (schedule.php) is working again . Setup a cronjob for that.
  • 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)
  • permit multiple flyspray installations with a single codebase.
  • Make threaded mail really work.
  • Localize the Installer/Upgrader
  • Upgrade to SwiftMailer v3 (when released for PHP4)
  • simplify task changes ( FS#1203 )? quick-edit is enough
  • link to dokuwiki syntax
  • replace FS prefix
  • lock password capability?
  • auto-close tasks...
  • restrict assignees (group permission → “show for assignees”, default 1)
  • last-edited-by column, others,  FS#1330  (redundancy table?)
  • for upgrading, to not make all fields project level?
  • remove all usage of split() and ereg_* functions, this include sending patches to external libraries.
  • Social networking authentification (Google, OpenID, Oauth, Facebook, Yahoo)

Things that will not be done in 1.0:

  • conversion scripts for most popular BTS - All of Flyspray data is stored in database. It should not be too hard to create a conversion script, at least from the Flyspray side. Do you need a conversion script to or from Flyspray? Tell us.
  • allow personal ordering of fields (FS 1.1 or later), see FS#2013
  • Add an option for SSL login - If you want a secure Flyspray, configure your webserver to only talk TLS/SSL, not unencrypted HTTP. Flyspray can help by hardening its source for TLS/SSL only sending, ask peterdd if it’s a requirement for you.

Things planned for 1.1:

  • Find no longer used functions in the code and remove them

Not planned yet:

  • Add support for both sqlite and mssql. But you can try your own experiments, we use adodb that supports a wide range of databases.
 937 FlysprayUser InterfaceTODOLow New fancy layout for 1.0 ClosedFloele29.05.2006
100%
57202 Task Description

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.
  • Comments could be displayed like messages on Google groups (complies to the mentioned requirements), see attachments
  • The menu needs to be changed. It probably has to be vertical in future, but in any case (the only point that matters) it should be possible to add more menu items without requiring a higher screen resolution (width)
  • the new theme should use unstyled input elements
  • the layout of all forms should be unified. I like the layout of phpbb for example (see attachment)

Layout bugs/problems that should be fixed:

Currently we don’t have anyone who is able to do this (I would like to, but I am not very good at it), so if anyone is skilled at making things look good (without creating an image-heavy layout like some at css Zen Garden) he can let us know.

More ideas are welcome and will be added to the description.

 748 FlysprayBackend/CoreBug ReportLow xfcgvd ClosedFloele23.11.2005
100%
Task Description

gdfgdfgfd

Showing tasks 1 - 4 of 4 Page 1 of 1

Available keyboard shortcuts

Tasklist

Task Details

Task Editing