Notes on what is still to do. These are also WISHLIST type of features, so 
if you feel like implementing stuff, please feel free, just make sure that 
you let the developers on the Turbine and Jyve mailing lists know so that 
we are not duplicating effort. All contributions are extremely appreciated.


[LOOK/FEEL]

  o add the ability to change the look and feel of the application
    fairly easily.


[FUNCTIONALITY] 

  o add the ability to move items around in the system. right now,
    it is pretty hard to do this. you have to delete the item and then
    re-add it in.
    
  o allow someone to be able to add a new question without having to
    select the topic heading first. this would be done by adding a
    link at the bottom of the DisplayTopics screen. when the link is
    clicked, it would show the NewQuestion screen, and on that screen
    would be a popdown menu of all the topics. one would then select a
    topic when they add their new question and this is how the
    association would be defined.

    
[COLLABORATION]

  o email all the people associated to the question when a new
    answer has been added.  this will help foster a system where only
    correct answers are posted.

  o bug/email authors of questions that have no answers to see if
    they have found their answer in another way and encourage them to
    post their answer to the board. this should be implemented using
    Turbine's Cron functionality.

  o email all the addresses in the system once a month asking people
    to validate their address by clicking on a link in the email.
    maybe if people don't validate after another month or so, then do
    not show their questions/answers in the gui?  or at least make it
    an option to show/hide based on that criteria.

    
[SECURITY]

  o add the ability to filter the content that is accepted from the
    user and put into the database as well as whatever comes out of
    the database (for most security).  this is to address the recent
    CERT advisory where sites can be hijacked as a result of data that
    may be displayed. one issue with this is making sure to filter
    *everything* that needs to be filtered. the easy way to do this is
    to define a set of Html Elements that are allowed. anything else
    is rejected to /dev/null.  this functionality really should be
    integrated into Turbine directly as a service so that others can
    take advantage of this feature.
