Re: GPL/LGPL licensing issues
2008/11/14 Aaron J. Seigo [EMAIL PROTECTED] On Friday 14 November 2008, Davide Bettio wrote: why we used LGPL for all our runners/dataengines? no particular reason. probably because i was working on libplasma a lot and just copied over the license headers between files as i was working on examples, such as the time engine. and like mono (the kissing disease, not the oss project) it just spread from there ... =P Are you saying that the LGPL/GPL is a viral license? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: GPL/LGPL licensing issues
On Fri, Nov 14, 2008 at 3:40 PM, Davide Bettio [EMAIL PROTECTED] wrote: Hi, I think that these files need to be relicensed to LGPL: Are dataengines really considered libraries? Theres no actual linking that occurs.. right? GPL should be just fine for them. favicons filebrowserengine sensoragent.h sensorclient.h sensorshellagent sensormanager sensorsocketagent (These files are located in kdebase/workspace/plasma/dataengines/) Bye, Davide Bettio. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: GPL/LGPL licensing issues
On Friday 14 November 2008, Dan Meltzer wrote: On Fri, Nov 14, 2008 at 3:40 PM, Davide Bettio [EMAIL PROTECTED] wrote: Hi, I think that these files need to be relicensed to LGPL: Are dataengines really considered libraries? Theres no actual linking that occurs.. right? GPL should be just fine for them. yes, i don't see any need to change the license on them. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: GPL/LGPL licensing issues
Hi, We need to relicense to LGPL these files too: * kdebase/workspace/plasma/runners/ PowerDevilRunner shell_config *kdebase/workspace/libs/libplasmaclock clocknumber (I think that we can kill this one, it seems almost unuseful) clockapplet Bye, Davide Bettio. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: GPL/LGPL licensing issues
Hi, Il Friday 14 November 2008 22:01:23 Aaron J. Seigo ha scritto: yes, i don't see any need to change the license on them. why we used LGPL for all our runners/dataengines? Bye, Davide Bettio. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: GPL/LGPL licensing issues
On Friday 14 November 2008, Davide Bettio wrote: Hi, We need to relicense to LGPL these files too: they don't need to be LGPL *kdebase/workspace/libs/libplasmaclock this should be LGPL is at all possible, yes. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: GPL/LGPL licensing issues
On Friday 14 November 2008, Davide Bettio wrote: why we used LGPL for all our runners/dataengines? no particular reason. probably because i was working on libplasma a lot and just copied over the license headers between files as i was working on examples, such as the time engine. and like mono (the kissing disease, not the oss project) it just spread from there ... =P -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
