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

List:       koffice-devel
Subject:    Re: libkdchart api stability?
From:       Inge Wallin <inge () lysator ! liu ! se>
Date:       2010-03-23 11:37:07
Message-ID: 201003231237.07535.inge () lysator ! liu ! se
[Download RAW message or body]

On Tuesday 23 March 2010 08:55:56 Thomas Zander wrote:
> On Tuesday 23. March 2010 05.39.01 Carlos Licea wrote:
> > I would vote for keeping the copy in KOffice for the time being.
> > Otherwise we  could jeopardize responsiveness in bug fixing.
> 
> I'm sorry to say, but for that reason I think the exact opposite should
> happen.
> From experience it shows that if its easy to get your fix in your local
>  tree then the incentive to do the right thing and push it upstream becomes
>  an afterthought that in my experience is dropped too often.

In general I would say that you are right, but in this case the people 
actually doing the fixing is the same people who own and maintain kdchart: 
kdab.

> If Nokia needs a fix that didn't make it into a release yet then there are
> several options available for it to include the patch in the actual build
>  it ships. All of them suboptimal, but thats the point; it should go
>  upstream.
> 
> Please, if possible setup the open source environment in such a way that
>  the right thing to do is the easiest solution. That way you avoid a lot of
>  management and end up with a more sustainable long term ecology.

In the long term, I think it's already decided that kdab will maintain a 
separate package.  In the short term (until 2.3?) I think we should keep it as 
it is, possibly moving it somewhere within koffice.
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]