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

Alexander Neundorf neundorf at kde.org
Sun Mar 14 21:13:30 GMT 2004

On Sunday 14 March 2004 21:36, Benjamin Meyer wrote:
> [snip]
> > 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.
> -Benjamin Meyer

I completely agree with Christian. KDE/Qt apps which are not in kde cvs are 
much less known (Scribus, karamba, sim, any others ?) and this is not a good 
thing. KDE has become too big for the current structure IMO.

Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org                - http://www.kde.org
      alex at neundorf.net               - http://www.neundorf.net

More information about the kde-core-devel mailing list