Future of teamwork plugin

David Nolden david.nolden.kdevelop at art-master.de
Tue Jul 3 19:58:43 UTC 2007

Am Dienstag, 3. Juli 2007 18:56:36 schrieb Alexander Dymo:
> On 7/3/07, Andras Mantia <amantia at kde.org> wrote:
> > Even if we abstract from the code content itself, if you admit that you
> > have no time to work on and as it was not really tested for the simple
> > case that KDevelop4 is pretty much in unusable state, and as KDevelop4
> > will continue to move forward, this is enough to say that your code
> > shouldn't stay *now* in kdevplatform.
> I'd like to stress the "now" part here. Once you have some time
> working on it and polishing its code we can move it back because
> basically everybody agrees teamwork is cool.

Teamwork is in a mainly working, and even stable(whereby I mean not crashing) 
state now. It mainly lacks integration into kdevelop(which was not possible 
when creating it, kdevelop has the ability to show context-menus since only a 
few months), some polishing of the user-interface, and disabling a few parts.

That's all not too big issues.

The question is: Why is it important to remove a plugin that nothing is going 
to depend on NOW?

Why not wait until before the kdevelop-4.0 release, and then decide whether 
teamwork is mature to be left there, or should be moved by side? 

It is quite probable that I will find time to fix the issues in a few months, 
as long as the plugin stays in a working state.
It is a lot less probable when kdevelop-teamwork is resting in some 
playground-corner and kdevplatform is evolving without it.

Personally I've got the feeling that to some people there's nothing more 
important than the count of krazy-issues, which imo is a little ridiculous. 
Of course you can reduce that count by removing 30tsloc.

greetings, David

More information about the KDevelop-devel mailing list