KInfoCenter rewrite in Kdereview

David Hubner hubnerd at ntlworld.com
Thu Apr 8 23:26:20 BST 2010


On Thursday 08 April 2010 21:13:40 Raphael Kubo da Costa wrote:
> On Thursday 08 April 2010 19:06:56 David Hubner wrote:
> > On Thursday 08 April 2010 19:20:33 David Hubner wrote:
> > > On Tuesday 06 April 2010 22:41:56 David Hubner wrote:
> > > > On Tuesday 06 April 2010 02:19:32 Raphael Kubo da Costa wrote:
> > > > > On Monday 05 April 2010 20:07:23 David Hubner wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > I have mostly finished the new rewrite of kinfocenter. The rewrite
> > > > > > was due to a lot of legacy code in the old version, it was going
> > > > > > to be more trouble to modify the old code than write new code.
> > > > > > 
> > > > > > Some new features of the kinfocenter are:
> > > > > > 
> > > > > > - Getting some consistency between system settings.
> > > > > > - Summary page
> > > > > > - removes all legacy code and uses model/view
> > > > > > - new summary KCM
> > > > > > - Better organisation of the KCM's
> > > > > > - Export
> > > > > > 
> > > > > > There is still a few things to do at the moment, i need to redo
> > > > > > some of the documentation as well as write new parts and add
> > > > > > Whatsthis information to the KCM's
> > > > > > 
> > > > > > Some things to take note are:
> > > > > > 
> > > > > > - The network interfaces viewer is not complete yet, it will appear
> > > > > > blank. - You need trunk due to patches added to solid and KdeUI
> > > > > > - Only summary has export functionality at the moment. It will be
> > > > > > added to most of them. - The tooltips need a little more info.
> > > > > > 
> > > > > > Apart from that i feel it is complete. If possible could i get some
> > > > > > feedback on what people think? Its in kdereview under kinfocenter2.
> > > > > > 
> > > > > > Thanks
> > > > > 
> > > > > I just had a quick look at kinfocenter1's copyright issues pointed
> > > > > out by Krazy, and apparently they still haven't been fixed --
> > > > > furthermore, some small files, such as
> > > > > Modules/memory/memory_{fbsd,linux,netbsd,...}.{cpp,h} don't even
> > > > > have a copyright header at all.
> > > > > 
> > > > > I'll see if it works fine on FreeBSD later.
> > > > 
> > > > Thanks, i shall have to contact the authors of the old modules and see
> > > > if i can change the licensing on the old modules. Could be a sticky
> > > > problem if i cannot contact them :(
> > > 
> > > Yer, i had a good look at this.. nearly all code in the info, pci and
> > > memory directories have no licenses. I spent 3-4 hrs today going through
> > > it, looking in SVN log if there was no email in there. I e-mailed the
> > > authors but with code from 1999 i am already getting bounces.
> > > 
> > > Any idea what i do with code where i cannot contact the authors but has
> > > no license?
> > 
> > Lots of memory, info and base code - Nicolas Ternisien
> > Moving the licenses to LGPL 3
> > 
> > ---------------
> > Hi David,
> > 
> > Please relicense my source code as LGPL version 3.
> > 
> > Thank you and good luck with KInfoCenter maintenance.
> > 
> > Nicolas
> > -----------------
> 
> One has to be careful to check if the licenses don't end up being incompatible 
> with each other. For example, does the BSD-license code use LGPLv3-only code? 
> Is that ok?
> 

The LGPLv3 code uses BSD code, but i think it always has. I am not sure if this is OK. If someone from kde licensing could look at this i would be grateful.

Thanks
-- 
David Hubner
IRC: hubnerd
MSN: hubnerd at hubnerd.org
ICQ: 24308559




More information about the kde-core-devel mailing list