KDE 4 modules structure (again) (was: structure of kde cvs modules, was Re: libkipi in kdesupport)

Simon Hausmann hausmann at kde.org
Sun Mar 14 21:48:37 GMT 2004

On Sunday 14 March 2004 21:36, Benjamin Meyer wrote:
> > I'm sure you can see the problems of our current way of doing. Apps
> > inside a module are easily gaining different levels of
> > completeness/functionality/popularity. Dumping many apps together in a
> > CVS module creates: a) a mean leveling of the perceived quality of all
> > the apps in the module; b) an artificial barrier to the developer that
> > would like to start anew some app that would compete with the app in the
> > "official" module.
> Actually I think that works for KDE.  Developers still do create new apps
> that reproduce the functionality of ones that exists in the modules, but
> most of the time a developer is much more likely to help out the existing
> project then to start his own (seeing as how 99% of the time they just had
> a small itch against the existing app).  Just my 2 cents on that small part
> of the larger issue.

I agree with Benjamin. Looking at kde-apps.org I see a fair amount of 3rd 
party applications, quite a few of them 'duplicating' functionality. Some of 
them have a long history of excellence. Take kvirc for example.


More information about the kde-core-devel mailing list