Work in progress

We need to spend this time on ROR. Have we got an estimate of how long it will take to get ROR production ready?

I've just resolved the problem with it not sending mail, it was simply that webbrick wasn't dying when told to (a simple kill wouldn't work, it needed a kill -9). After a restart it re-read the config file and is now sending mail fine.

Since Tim fixed up (at least in a basic way enough for it to be usable) the CSS issue and I fixed up the intro text display the things holding us back now are: (in comparison to the current rhubarb system)

(note: I have left out lots of things which could come in a future release but are not required now)

MUST HAVES:
* finishing the test suite
* passing said tests
* finding a production server to house it
* installing it and testing it on production (including setting it up on Apache, not webbrick)
* any kind of reporting OR access to the access logs and rendering of those into a graph or something
* the ability to send to more than one target address in a single action
* HTTPS for admin pages
* Error handling (not just hiding) when sending mail
* HTTPS for front end???

THINGS OLD RHUBARB DOES THAT RHUBARB ON RAILS DOES NOT:
* report number of participants on the participate and/or any other page the admin wants
* linking of multiple actions into a single report/participant count
* tell-a-friend
* Switch to make the subject line read only
* Collection of the visitors country

TO IMPROVE THE CURRENT SITUATION:
* Implement confirmation email containing clickable link to confirm the send.

BASIC MISSING FUNCTIONALITY:
* Delete user account
* Change user account password
* Forgotten password handling
* Delete CSS file when deleting an action

AND..
* Collection of email addresses
* Ability to export said email addresses
* Hide the bounces column since bounce handling is missing

FINALLY, THINGS TO CONFORM WITH THE NON-FUNCTIONAL REQUIREMENTS:
* Handle/prevent double submission
* Handle bounces
* Admin audit trail
* Mark sent emails so we have what we need to investigate if an email including headers is handed to us as wrongfully delivered or otherwise a reason for complaint???
* Limiting of mail send speed?

FINALLY...
* Add twill/selenium tests
* Test with BrowserCam
* Test against W3C XHTML/CSS compliance testers
* Test the generated mails for RFC compliance.

Any more anybody?