[Kde-scm-interest] KOffice moving to gitorious

[Dmitry Suzdalev]

On Friday 12 February 2010 17:33:23 Esben Mose Hansen wrote:
> Could someone spell out to me why moving parts like KOffice to git hinders
> (or  helps) anything? The only argument I've heard is that using 2 tools
> raises the bat for developers, but since KOffice development is unlikely
> to need changes to kdelibs, I don't see this is applicable here.
It does indirectly. As I've said I think this man power could be spent on 
helping whole KDE SC switch to git and after that switching KOffice would be a 
breeze (theoretically).

Instead we'll have people's initiative spent on moving individual components 
while the core part is kept where it is with no (or little) progress 
happening.

Another thing to think about is that the workflow for working with git+KDE is 
not steady yet, discussion is in progress. So some work might be needed anyway 
after KDE switches to git in its wholeness. So why spread the forces to do the 
double work later and not helping the whole project in any way?

OK, I don't want to continue ranting. That's how I see what happens.
I may be completely wrong, but that's my opinion :)
Also I myself done nothing to help KDE SC git migration, so don't feel I have 
much right to crituque someone's desicions (well, only once maybe ;-)), but 
just wanted to express what i think about this.

Cheers,
Dmitry.