[Kde-scm-interest] Have we arrived to a dead end?

Michael Jansen kde at michael-jansen.biz
Wed Feb 17 13:45:28 CET 2010


On Wednesday 17 February 2010 10:09:17 Lydia Pintscher wrote:
> Let's stop this BS discussion and name-calling now and actually get
> the conversion done, please.
> We could go on with this for another year and not get the conversion
> done. Let's stop it and get work done.
> 
> What is the progress on the conversion rules for edu, games and
> accessability? Afaik Tomaz, Marcus and Jeremy were working on them.

Not all all technical issues solved, Noone has proven git can really support all requirement kde 
development has, because noone really asked and analysed what that is. There is opposition to the 
move which affects everyone in kde development if done for all kde modules.

But nevertheless there is a movement to just do the thing.

I'm opposed to the move in the current form. I prefer no move to a botched one like ossi. But i 
consider any resistance or discussion futile because it will result in nothing but people calling 
you out for "stalling the move", "stealing the energy" or whatever it was called.

This move is not a natural like going from cvs to svn.

So i will repeat one last time. "He who does the work decides" should not apply in a situation where 
the end result affect absolutely everyone in their work on kde. 

What if two years from now someone is fed up with git and starts a movement to something else. Does 
the work, pays developer. Does that rule suddenly stop to apply  because we move away from git?

You want to move the core of kde. Make a real plan. Describe how modules will be split. Analyse how 
that affects the workflow of all devs, explain how a move from kdebase to kdelibs or so will be done 
after the move. Will history get lost? And i don't want to hear another "i don't think that happens 
that often from a certain guy". Predict and explain how big repositories will get using git, Explain 
how that affects and applies to kdesupport-oxygen. Show us how it affects the work of the release-
team. Get input from the distributions.

Then present that on kde-core-devel.

But i'm sure that will not happen. 

Mike


More information about the Kde-scm-interest mailing list