[Kolab-devel] Code revision for kolab

[Gunnar Wrobel]

Zitat von Christoph Wickert <wickert at kolabsys.com>:

> Hallo world,
>
> recently some changes have gone into the repo that confused some  
> contributors.
> Therefor it was suggested to introduce code reviews before  
> committing changes.

Feels like an unnecessary overhead to me. There was an intense  
discussion concerning these commits which actually tells me that we do  
have an active code review process which is alive and kicking.

I do believe we are all aware that with the start of Kolab Systems the  
Kolab development sees some new activities, also new people and in  
general gets a decent shot of new energy.

It is also obvious that this will not always be without some pain in  
the one or the other corner. Sometimes old ways will have to be  
abolished and sometimes new ideas will have to be ignored in favor of  
the old ways. I consider this process to be "learning" even if it may  
hurt a little.

So we are all able to talk with each other and I really would like to  
avoid adding additional structure, rules or anything that can impede  
our current progress.

Cheers,

Gunnar

> The question is: Do we need to go that way? And if so, is there a nice
> workflow that will not slow down development too much? I think of a tool like
> 'gerrit' [1] but I wonder if something similar is available for mercurial.
>
> Regards,
> Christoph
>
> [1] http://code.google.com/p/gerrit/
>
> --
> Christoph Wickert
> Senior Engineer
>
> Kolab Systems AG
> Zürich, Switzerland
>
> e: wickert at kolabsys.com
> t: +49 251 871 369 77
> w: http://kolabsys.com
>
> pgp: 85DACC63 Christoph Wickert
>



--
Gunnar Wrobel
Developer, Kolab Systems AG

e: wrobel at kolabsys.com
t: +49 700 6245 0000
w: http://www.kolabsys.com

pgp: 9703 43BE

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.