Future of teamwork plugin

Andreas Pakulat apaku at gmx.de
Wed Jul 4 15:18:41 UTC 2007

On 04.07.07 11:00:47, dukju ahn wrote:
> 2007/7/4, Kris Wong <wongk at seapine.com>:
> > Any code that is released as part of KDevelop needs to:
> >
> > 1. be maintainable
> Does the maintainability means that there should be maintainer for certain
> code? What if the developer cannot continue his development?

No, it means the code has to be clean and easily understandable,
including documentation. We don't have designated maintainers for each
part in KDevelop, even though mostly everybody has his pet peeve (is
that proper english?). However its important that all code base is not
overly complex/complicated and somewhat well structured so that anybody
can take over or do fixes when the person who maintained it doesn't have
time anymore.

> Honestly, I cannot promise that I can continue any development from
> august. In that case, I want to know the future of subversion plugin,
> which I wrote. I'll write documentation and some tutorials before
> I stop the development.

Good, also you could get rid of all the warning's because of unused
parameters, just put Q_UNUSED(<name>) at the top of the method. That way
its easier to find real warnings and errors when changing the code.


You're working under a slight handicap.  You happen to be human.

More information about the KDevelop-devel mailing list