commits to master

[Cyrille Berger]

I have started to put together a draft of a commit policy:

http://community.kde.org/Calligra/Policies/Commits

For now, it is essentially what I said in my emails.

For the git bisect part, maybe we could have some guideline on what to
commit in branch,
could be useful for beginners as well.

As for the changelog, we can already make use of the "BUG" keyword. But
what do you think of 
adding a FEATURE keyword, that would be followed by a description ? For
instance:

FEATURE: grammatical spell checking

Other comments ?

-- 
Cyrille Berger