[kde-edu]: kde4 - URGENT - Please read

Peter Hedlund peter at peterandlinda.com
Mon Jun 6 20:31:22 CEST 2005

Albert Astals Cid wrote:
> I disagree, annma asked the module to be there, why should we remove it now? 
> Moreover i've put some work to make libkdeedu almost link, that work should 
> be done later or sooner, so i did it, removing it now is a bad thing to do to 
> that people that started working (like Pino on Kig)
> More examples, kmplot builds and almost works perfectly, me and Laurent put 
> some work on doing the conversion too, why throw away our work? Just ignore 
> it until it is need and then use it.
> And yes, i know nobody asked me to do the work so if it gets trashed i can not 
> say anything.

I just recalled the discussion from last week (I think it was KStars) 
were people were contributing to different branches without coordination.

I also don't see the hurry with kde4. KDE 3.5 is supposed to be the 
great applications release and what we should focus on. Is it not better 
for us to let the kdelibs people get everything ported and stable and 
then we start porting our programs?

I don't even have the kde4 branch checked out. Do I need to do that just 
   to then be able to delete KVocTrain and KWordQuiz?

My other option at this point is probably to stop development and like 
everyone else jump on the KDE 4 bandwagon. But that defeats the purpose 
of a 3.5 release. My limited time cannot be split between two branches.

I guess kdepim is more coordinated, and it is easier for them to make 
the IMHO right decision.


> Albert
> A Dilluns 06 Juny 2005 19:57, Peter Hedlund va escriure:
>>Anne-Marie Mahfouf wrote:
>>>Hi all,
>>>It seems my latest mail was a bit confusing about merging in kde4. Sorry
>>>about that, I did not understand exactly what was asked from us.
>>>I have the latest from coolo himself:
>>>- if you want to keep your app in the kde4 branch, you have to merge your
>>>changes by yourself from now on
>>>- if you develop too fast in 3.5 (like kalzium does for example), you
>>>must remove your app from kde4/kdeedu and you'll readd it when 3.5 is
>>>separated from 4.0 for example or when you feel it's OK. kdepim people
>>>for example don't want to work on kde4 before september.
>>>So either you keep your app in branches/work/kde4/kdeedu and you keep it
>>>synch with 3.5 or you remove it until you can develop on it maybe
>>>separately from 3.5.
>>>I would say to adopt the latest solution for Kalzium, KStars and
>>>KVocTrain for example. I'll probably remove KHangMan as well.
>>I propose that we remove the entire kdeedu module from the kde4 branch.
>>That will give us two major advantages:
>>1. Actively developed applications do not need to worry about merging
>>and contributions to the wrong branch.
>>2. Less active or unmaintained applications can be reevaluated to
>>determine if they should even be put into KDE 4.

More information about the kde-edu mailing list