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

[Benjamin Meyer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[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

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAVMI21rZ3LTw38vIRAul/AJ4+mPQr2b9P+n+sRcpFjC1cInFURgCgn458
ce+Yl8WtgdFly4lMI0W1uOo=
=YYM9
-----END PGP SIGNATURE-----