[Kde-imaging] Gwenview, kdegraphics and libkipiAl

[Seb Ruiz]

On 20/01/07, Angelo Naselli <anaselli at linux.it> wrote:
> Alle 14:19, venerdì 19 gennaio 2007, Caulier Gilles ha scritto:
> > Le jeudi 18 janvier 2007 10:20, Angelo Naselli a écrit:
> > > Alle 10:14, mercoledì 17 gennaio 2007, Caulier Gilles ha scritto:
> > > > Le mercredi 17 janvier 2007 10:03, Angelo Naselli a écrit:
> > > > > Alle 08:53, mercoledì 17 gennaio 2007, Valerio Fuoglio ha scritto:
> > > > > > Alle 00:07, mercoledì 17 gennaio 2007, Aurelien Gateau ha scritto:
> > > > > > > PS: Note that this change would "only" concerned libkipi. It would
> > > > > > > not impose any restriction on kipi-plugins.
> > > > > >
> > > > > > IMHO, the best solution for the future of kipi-plugins, is to be
> > > > > > included too.
> > > > > > Can't we do this?
> > > > >
> > > > > hmm, if not necessary why?
> > > > > We're not so good at releasing new plugins, but something is
> > > > > changing (new ideas, new developers, new maintainers and
> > > > > contributors,...) and i wouldn't like to see that going backwards again
> > > > > :(
> > > > >
> > > > > Just my 2 €cents
> > > > >         Angelo
> > > >
> > > > Look my previous mail. if libkipi is moved in KDE4, it will be ported to
> > > > Qt4. Only gwenview will use it until all others host will be ported to
> > > > Qt4...
> > > >
> > > > This sound like a fork of libkipi dedicaced to gwenview.
> > > >
> > > > In fact, I'm not favorable to do it.
> > >
> > > But we should evaulate a migration though sooner or later.....
> >
> > Angelo,
> >
> > You need to release kipi-plugins 0.1.3-final before to move/fork libkipi in
> > kdegraphics (:=)))...
> Of course, but I don't think the meant to have it tonight :p
>
> Since I haven't contacted i18n group yet, my fault, I believe i cannot do
> that before Wednesday, i believe. I will send a mail to them tonight.
> (If there isn't any volonteers for that first ;) )
>


I think it is really important to keep the project unified, forking is
bad. simultaneous development of qt3 / qt4 branches will make it much
more difficult to have an _excellent_ qt4 release. I would advise
moving to qt4 asap, but not neglecting the stable versions - that
means, bug fix releases often and when required, and features only if
they are mirrored in both branches and are maintained by the same
author.

I know its a lot of work, but I feel it would reap the most benefits
in the long term.

Seb


-- 
http://www.sebruiz.net/