Proposal: KDE CVS Commit Policy

[Stephan Binner]

On Sunday 30 March 2003 14:24, Cornelius Schumacher wrote:

>  2. Never commit code that doesn't compile.

With --disable-final? With --enable-final?

>  6. Make sure that the maintainer of the code you are changing knows
>     about your plans before committing.

Do you want to describe the current situation (above has nothing to do with 
reality) or do you want to change and slow down the development? Most of my 
commits would be illegal by this definition. What about dead maintainers?

 11. Consider {security,BIC,i18n,usability,HIG,[API] documentation, ...}

Bye,
   Steve