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

List:       kde-devel
Subject:    Re: How does KDE deal with legal actions against it's developers?
From:       Hetz Ben Hamo <hetz () il ! linuxqa ! com>
Date:       2001-02-21 10:22:31
[Download RAW message or body]

Hmm, this is simple actually (and happend to me in the days of when I was
writing Assembly programs to the Amiga machines)..

As long as you say to the vendor that you are writing software under a GPL'd
license and show him or add to the agreement that you are not liable for any
damage whatsoever - you should be covered...

Note: IANAL :)

That, btw, helped me to get out of the lawsuit that they tried to sue me (not
GPL, but a pretty close license that was available back then)

Thanks,
-- 
Hetz Ben Hamo
Hardware Research dept.
Aduva Inc.


Rinse de Vries wrote:
> 
> Hi,
> I dunno if this is the proper group for this question, but I'll ask it
> anyway,
> How does KDE deal with legal actions against it's developers?
> 
> This question raised after a chat I had with a Dutch ISP. I asked their
> permission to use their account data in the Kppp wizard database. They
> first wanted to know if I would take the responsibility of possible legal
> claims against them if the data in the wizard is incorrect (e.g. wrong
> dial up phone number, resulting in higher phone bills for the clients of
> the isp, they had similar money claims in the past due to wrong
> information on their setup cd ROM)
> I pointed out the GPL, and that according to the GPL, KDE takes no
> responsibility for damage due to the use of it's software.
> Never heard of them since, so I didn't include their data in the wizard.
> 
> But it makes me wonder:
> If a company tries to sue a developer because of financial losses, due to
> the use of it's KDE-software, how should the developer deal with this?
> 
> Kind regards, Rinse
> 
> >> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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