[Kde-scm-interest] KDESDK to git migration: how many repos for the small developer utils?

[Friedrich W. H. Kossebau]

Hi,

[[cc: to kde-scm-interest just for heads-up,
  follow-ups _only_ on kde-sdk-devel please]]

so we are in Phase 1 of the process:
	"Decide which repos should be created from which submodules".

For the kind-of-standalone programs and the plugins it seems there is 
consensus how they should be split, a repo per program as well as a repo per 
plugin type.

But what about all those small developer utils?
There are some for developers using... 
... KDE libs/framework: 
* kpartloader - David Faure 
* scripts - Michael Pyne 

... Qt libs/framework: 
* kuiviewer - Benjamin C. Meyer 
* kprofilemethod - David Faure 

... X libs: 
* kstartperf - Geert Jansen 

... C++(/C?): 
* kmtrace - ? 

How should these submodules be split? 
a) One repo with all? 
b) "scripts" in a separate repo, rest in one? 
c) Each an own repo?
d) ?

(Above from http://community.kde.org/KDESDK/Git_Migration#Development_utils )

I currently would vote for b) or a). But I have no real hard rules besides the 
amount of files in the submodules.
What rules to base the decision on do you propose?
How would you split up these submodules?

Cheers
Friedrich