[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kreateCD -> kdenonbeta
From:       Holger Freyther <freyther () gmx ! net>
Date:       2002-03-30 14:11:13
[Download RAW message or body]

Am Saturday 30 March 2002 13:35 schrieb Thomas Zander:
> On Sat, Mar 30, 2002 at 12:37:50PM +0100, Holger Freyther wrote:
> > Am Saturday 30 March 2002 15:25 schrieb Hetz Ben Hamo:
> > > Umm, there is at least 1 more "competitor" in the CD Create area -
> > > cdbakeoven...
> > >
> > > I think there should be some kind of decision which one of them will go
> > > into the KDE CVS. Both "competitors" are already ported to QT-3/KDE-3..
> > >
> > > I would vote for the cdbakeoven (http://cdbakeoven.sourceforge.net)
> > > since it's seems to me that its GUI design is the most easiest one for
> > > a Linux newbie and for some people who don't understand CD recording at
> > > Linux at all..
> >
> > Ok when the koncd discussion started I proposed the following.
> > Put all competitors into kdenonbeta. Let them evolve until let's say 2
> > Weeks before KDE3.1 then we will test them and decide which one to use.
> >
> > IMHO not only usability counts. For me it's important how the application
> > integrates into KDE and how the developer is intergrated into the
> > developer community.
>
> That can be done without importing as well.
> Just subscribe yourself to the various MLs and listent to the different
> applications-authors for yourself. Did you also consider that the author
> should actually want to put it in CVS ?  In other words; what do they say?
>
What do you think draws more attention a project resisting in kde itself or 
on sf?
So by importing the willing projects into KDE you'll first create a better 
possobility for the project to grow and you'll integrate the developers into 
kde.
Why do we've to do the same failure again?
We imported koncd. And the developer did not integrate into the community. He 
didn't reply to emails and now koncd is broken and dead.
So we can import cdbakeoven rely on it and then see they stopped developing 
it without any notification.
Where as we've kreatecd which is developed by a couple of people. Among of 
them is jowenn. Famouse for his work on kate.
We know that he integrates into the community. He uses KDE technology and KDE 
Look&Feel.

I'm for importing cd writer software where the developers want it. Create a 
kde-cd-writer mailinglist where they can coopearate maybe join their efforts 
in a common backend and then select one of the 2 programs for kde3.1


I'm for having a KDED Module with plugins for writing. The KDED Module will 
load plugins on demand keep track of "playlists" or whatever and these will 
be written to the cd.
Then we could have a KDED<->IO Slave bridge and have multiple frontends for it


just my 0.02Euro

zecke
> IMO cdbakeoven looks better then most others.  (But the name is terrible)
[prev in list] [next in list] [prev in thread] [next in thread]