Todo

Do you have some time to Coefficient? If so, we are looking for people to do the following:

  • Unit testing! We need test cases.
  • rework the coefficient security model. We need a flexable security model that does not tie the system to any hard-coded roles.
  • create an events module so that a project can track time based events. This should have a graphical calendar representation.
  • add a CVS/subversion viewing module (plus support to create the repositories)
  • create a links module to allow a user to add links to their project page
  • add support for JSF and other presentation frameworks.
  • make it so that the password on login is sent through a secure protocol
  • add a GUI based workflow creation module to the system
  • email server (like on sourceforge, each user gets a sourceforge email address that forwards to their real email address so that a users email won't be swamped)
  • help screens
  • developers Guide extensions, Users Guide extentions
  • Add better support for different project types - e.g. research projects.
  • Add better project management features - e.g. project planning and task tracking, GANTT charts, timesheets, etc.
  • Add better bug management features to issue tracker, including support for test phases and management style reporting
  • I18N support. Remove hard-coded english from the system, use resource files
  • deploy the system in a second application server (Websphere or Weblogic), modify the Xdoclet metadata and build to support this
  • chat module (gabber server)
  • Shorten database table names (so that Oracle doesn't freak out)
  • Add password reset facility (for admins)
  • Integrate a wiki engine
  • Add JDK1.5 and Tomcat5.5 support
  • Add RSS publishing and blogging faciltities
  • Add bulk mail facilities: e.g. all-site-subscribers, all-project-subscribers, etc
  • General issues needing attention:
    • Cursor does not change to hand when hovering over some links
    • Create default project mailing lists and forums when project is created. People automatically join these lists when becoming members of the project.
    • UserAdmin: when registering with incorrect information, user is registered anyway.
  • Issues needing attention in Issue Tracker:
    • Issue comments don't like weird chars (e.g.#)
    • Issue description cannot be edited
    • Don't use session for storing currently selected issue. It breaks when viewing > 1 simultaneously
    • Fix searching for issues (it is buggy, and very slow).
    • Show issue comments on same page as issue details
    • Use <pre> tags to display descriptions and comments, to preserve formatting
    • Show substatus as well for closed issues (e.g. Fixed, Can't Reproduce, etc.)
    • Add ability to jump directly to a bug, given it's number
    • Add concept of release/version to issue tracker, so that bugs can be tracked per version.
    • Add graphing (e.g. pie-chart) of open vs closed bugs
    • Keep and show issue history (i.e. history of state changes, with person making changes and date changed)
    • Use wioki-style formatting for issue comments and descriptions (safer than inline HTML)
    • Add email notification of Issue tracker activity
    • Add link to "claim" an issue as yours (shortcut to assigning it to yourself)
    • Show issue details on page when closing an issue.
    • Allow issue type (bug, improvement, etc) to be edited
    • Allow searhcing and browsing for an issue to link/refer to (currently, the issue number must be known)
    • Would be good to be able to link to other issues while adding a comment to an issue. Conceptually, the link is "softer" than when linking one issue to another. i.e. is is not used to indicate that one duplicates another, etc, but rather to simply refer to another issue.

Things for the future:

  • Rearchitect Coefficient:
    • modules are split into 2 parts, namely a Service part (with the logic) and a Module part (with the presentation). Modules are exclusively processed in the web tier, Services in the business logic tier.