[Kde-scm-interest] Re: kdegraphics libs migration

[Marcel Wiesweg]

> The same question applies to SVN, why should one want to download gwenview
> code to code in libksane? The answer was because we were supposed to help
> eachother and more people downloading and compiling your code meant more
> people possibly being ready to help. But people helping eachother is an old
> fashioned way of thinking amonsgt KDE younglings it seems.

With SVN, you could check out only parts of a repository. I have never checked 
out full kdegraphics for development.
With git, the entity "repository" should be decoupled from the "release 
tarball" or "KDE submodule". I was told so by sysadmins when requesting the 
digikam repo - there is supposed to be a bundling mechanism on 
projects.kde.org, like having a number of git repos making up the whole of 
kdegraphics. 
For digikam, we plan to have a compilation repository with some magic to pull 
in our 7 repositories (no, not git submodules. The projects.kde solution? dont 
know), three of which being discussed here.

See the repository layout as a technical detail. 
There can be technical factor vetoeing a split. It's discussed elsewhere. 
There is no such technical bond between the applications in kdegraphics.
Splitting a KDE module in separate repos does not mean to split the KDE 
module. It's technical, not social.