Bug Tracking

Chatterl

  • Distributed chat system
  • 2009-02-14T09:25:43Z
  • mit
  • 16

Mile Stones

  • Cleanup CWIGA & API

  • Secure, cleanup & add more functionality to CWIGA.
  • Add test cases

  • Is way overdue, down to sinan not running tests within a specific directory and me not understanding the process within Erlang. This will need to resolved ASAP to keep the project robust and functional.
  • Add storage mechanism

  • Need a storage mechanism to store group & admin data. Namely groups admins registered to the system & group data (messages,clients,etc).
  • Add registered user/groups functionality

  • Start to add futures features, with registered client & groups services as a priority.
  • General cleanup

  • General code review & bug fixing. We need the system clean enough for us to develop the frontend.
  • Implement AIML

  • Will be used to create chat bots.

CVMe

  • CV Management system
  • 2010-08-17T17:25:57Z
  • mit
  • 9

Mile Stones

  • Implement prototype

  • We want to be able to add the basic data needed to create a CV to the application. This includes the following features: Creating a user Adding a profile Adding experience Adding skills

Salad

  • Bridging the gap between clients and developers
  • 2010-04-08T19:22:42Z
  • mit
  • 43

Mile Stones

  • 0.8.0

  • General review of code and implementation of feature left over from the last iteration.
  • Clientside improvements

  • Salad needs needs some client side enhancements
  • Lighthouse Integration

  • We want to be able to integrate with Lighthouse. When using a specific tag (feature - tbc) Salad will be able to import these as feature headings and put the in a 'parked area' ready for adding stories (could possibly use tickets as a basic for stories here).
  • UX Improvements

  • We need to go through the application and improve the general layout and user experience.
  • 0.8.2

  • We have quite a bit of technical dept that needs to be paid up. The following will be of priority
    • Review of already implemented scenarios
    • Organisation of step definitions
    • General bug fixiing
  • 0.8.3

  • This milestone will focus on the implementation of new functionality, with a focus on Cucumber functionality yet to be implemented in Salad. The following will the main ones to focus on.
    • Backgrounds
    • Creating examples
    • Tagging
    • Comments
  • Github Integration

  • We'll want to be able to integrate Salad with github, allowing users to link it with there projects. In turn giving them the ability to import features from github
  • Improve homepage

  • Atm the home page is sparse. We need to improve the general layout and information that is displayed on it.
  • Move to Rails 3

  • We'll need to move over to Rails 3 eventually, so may as well plan for it now.
  • Refactor layout

  • To keep the application cutting edge we should take advantage of some of the functionality HTML5 gives us. This functionality will be purely Selenium based and should improve the general user experience of the application in general. As this application relies on JavaScript we will use jQuery to leverage our enhancements where HTML5 functionality is not available to the users browser. The first step will be to refactor the applications layouts and implement fallbacks for when HTML5 elements and features are not currently available. After this we can add some extra bell and whistle via HTML5 & jQuery.
  • User management

  • We want to optionally add user management functionality to the app. Allowing for collaboration work on a projects features and stories