Minor style fix
Some minor fixes

- remove some old .gitignore rules and add some new ones
- fix authors, email and url in setup.py
- fix a typo in a comment in CWS
Updated the README
Version 0.9.0

https://github.com/cms-dev/cms/wiki/CMS-0.9.0-RELEASE-NOTES
Start development of version 1.0.0
Add *.mo files to .gitignore
Fix the way primary statements are stored in the DB

Use a JSON encoded dict to store the preferred statements for a user
(now called "primary"). The keys are task names and their corresponding
value is a list of language codes.

For symmetry, allow a task to specify multiple primary statements, too.
Export token_gen_time as the number of seconds, not minutes

The only reason to do it is to uniform the code.
Remove some useless single_parent arguments from DB relationships

The single_parent argument for relationships is needed to make
many-to-one or many-to-many relationships become one-to-one or
one-to-many. It has no effect on relationships that already are of the
latter types. Yet, it was used on many backrefs which, usually, were
one-to-many relationships. These occurences have been removed.

The only remaining use is for tokens: it is needed to prevent
submissions from being associated with more than one token.
Clean up the cascade argument of relationships in the DB model

The "delete" option can be removed since it's implied by "all".
Add passive deletes

Since we have set a ondelete="CASCADE" option on all foreign keys we
don't need SQLAlchemy to *load* and explictly delete all children when a
parent is deleted (because the database will do that automatically).
The passive_delete option does exactly this.

The passive_update option is the same but fot updates. Yet, it's True by
default, so we don't need to set it explicitly.
Use a uniform coding style for relationships in cms.db

That is, use a hanging indentation.
Clean up some imports in cms.db
Various fixes
Use hanging indent for column properties in cms.db

Like we did for relationships.
Add some CheckConstraints in cms.db

We don't allow these values to be zero because setting a min_*_interval
to zero is the same as setting it to None and setting a max_*_number to
zero would disable submissions or usertest. While I think that someone
may want to disable them (well, at least the usertests...) I don't think
that the correct way to do that is to set the max_*_number to zero.
There should be a more explicit way to do that, to also allow the
interface (i.e. CWS) to know it and properly display this behavior.
Fix bug on auto-updating submission rows
Some small fixes to RWS client
Fix UserTest exportation (and reimportation)
Improve internationalization of CWS

By marking more string for translation and using the browser locale
instead of a hardcoded "en_US".