[Kde-scm-interest] kdegraphics - a few technical questions

[Marcel Wiesweg]

Hi,

we are now internally discussing the kdegraphics git move with all interested 
and involved developers.
Some technical questions that arose, given we take the split repo approach:

1) Would it be suitable to have a shallow shell / umbrella repository 
including toplevel directory contents glue like CMake files, READMEs or AUTHOR 
files etc., with the submodules' repos copied inside this?
This would allow to a) dont have to edit CMake files right now to make 
everything compile standalone (would be a hurdle right now, could be achieved 
in the long run)
b) allow to cope with some cross-submodule source file dependencies for now
c) strengthen the coherence of the module
d) may contain a convenience script to pull all repos
e) leave it as a choice of individual submodules to build standalone, or 
require the umbrella.
f) if git-submodules or a different approach becomes usable for this purpose 
in the future, use it then

2) What happens with apps that have been in kdegraphics but are no more?
I see katalog, kcoloredit kdvi, kfax, kfaxview, kfract, kghostview, kiconedit, 
kooka, kpaint,kpixmap2bitmap, ksvg, kpovmodeler, kuickshow, kview, pixie, 
ligature, libkscan, libminimagick. A separate repo for each in kde-
unmaintained, or a "kdegraphics-history" repo?

3) There are strigi-analyzers and thumbnailers, both consisting of smaller 
submodules and with no explicit maintainer. Would you recommend to keep them 
separate or merge them into a kdegraphics-runtime module? Just an idea, no 
opinion from me here.

Thanks for recommendations
Marcel