Development guidelines

[Jussi Arpalahti]

I thought we should take some time to draft some sort of development
guidelines for the project. I'm specifically talking about the
technical stuff, like how and what to commit, testing, documentation
and so on.

Since code is Peter's I thought he could say how he is used to
developing. For example, should I make a branch for my translation
work or just happily commit my changes to the trunk.

I have already changed the default database to the sqlite, but that
change is not committed. If you prefer, I could make a ticket for that
(albeit trivial) change. With sqlite one can start a site immediately.
With an RDBMS there is always the setting of the tables, rights and
such.


Best, Jussi

[Peter Krantz]

Hi!

Please note that the current code base was written basically over a
weekend this summer and should not be considered as some sort of
standard in any way:-)

I believe in trust so if you feel you have something to commit, please
do so:-) Branching only complicates things.

Using default db to sqlite sounds good and should make it easier to
get started with a local install. Please commit that.

What I would like to see in the future:

- A basic set of (at least) integration tests that verifies some of
the basic functionality.
- Valid HTML as much as possible.

Regards,

Peter