KDE development with git

[Paolo Capriotti]

Hi,
since a few days, I've been experimenting with git for managing my KDE project 
(playground/games/kboard) and git-svn to interface back to the KDE svn 
repository.
Git encourages a development model where many branches are created, features 
are developed out of the main line, and then merged back to the master 
branch. This is something which is hardly possible with svn (and impossible, 
if one wants to keep some of the branches private), but IMHO highly 
desirable for many KDE projects.
Using git-svn when the git repository is used by more than one developer is 
quite hard, and I could not manage to make it work properly (i.e. without 
adding extraneous 'merge' commits to svn), so I've decided to switch 
development completely to git (at least for the moment) to try it out fully.
However, moving away from the KDE svn repository apparently means that the 
project is not anymore part of KDE, and will not be until moved back there. 
KDE reviews and translations are based on svn, as well as tagging for the 
releases.
What I would like is some kind of official support for projects that wish to 
use git (or maybe other distributed VCS's?). Generally speaking, it would be 
nice if a project could be part of KDE (for example, of the kde-games 
module), even if it is not developed in the svn repository.
I'm sure that the technical issues that would arise can be easily solved, but 
first I would like to know if there is some interest by other KDE developers 
in pursuing this. I hope it is clear that I'm not suggesting that the KDE 
project should change VCS, just that subprojects should be free to experiment 
with other development models and VCS's, without losing all the advantages 
that residing in the KDE svn provides.

Paolo Capriotti