On Sunday, 2012-12-09, Shantanu Tushar Jha wrote: > Hi Yogesh, > > On Sun, Dec 9, 2012 at 10:51 PM, Yogesh Marwaha <yogeshm....@gmail.com>wrote: > > Hi, > > > > I have incorporated parts of source code from KDE software in my software > > as > > per following: - > > KDE softwares' source code are usually licensed as GPL, which means that if > you copy KDE source code, you must license your software as GPL as well. > Read http://www.gnu.org/licenses/gpl-2.0.html for more info.
Depends. Each file usually says which licence it is under in its header. For example libraries are often not licenced under GPL but LGPL, MIT or BSD. > > i) I've copied one function (5-6 lines) which is used as it was. > > ii) I've copied one class from old release (KDE3) and made few changes; > > mostly > > port to Qt4. > > The question is, how do I give due credit to the developers and mention > > details like license? > > Is mentioning copyright-year-developer name enough? > > As I mentioned above, you have to make your source code released as GPL (or > as some people say, Open Source it). So as long as you adhere to the > license, you don't have to give credit as such. As mentioned above it is not required to release your code under GPL licence, but your licence needs to be compatible with the terms of the licence of the code you are using (which could be GPL but could be any of a couple of others). As far as attribution goes, a lot of those licences require appropriate attribution. Which is usually satisfied by copying the Copyright line(s) of the original authors, but could require copying the licence header if your licence is different (but compatible) the one being used by the original code. Cheers, Kevin Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
