On Sun, Dec 9, 2012 at 11:20 PM, Yogesh Marwaha <yogeshm....@gmail.com>wrote:

> Thanks for the reply.
> My software is licensed under gpl v3 and hosted at sourceforge, so that
> means I need not to mention orginal developer's or project's name?
>
Its not necessary to do that in the application itself, but you have to
maintain the names appearing in the source code license headers.

On Dec 9, 2012 11:09 PM, "Shantanu Tushar Jha" <shaan...@gmail.com> 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.
>>
>>
>>> 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.
>>
>>
>>> Regards,
>>>
>>> Yogesh M
>>>
>>>
>>> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
>>> unsubscribe <<
>>>
>>
>> Don't hesitate to ask if you still have questions,
>>
>>
>> --
>> Shantanu Tushar    (UTC +0530)
>> http://www.shantanutushar.com
>>
>>
>> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
>> unsubscribe <<
>>
>>
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
>


-- 
Shantanu Tushar    (UTC +0530)
http://www.shantanutushar.com
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to