summaryrefslogtreecommitdiff
path: root/2005/gpl-ec2005/red-line
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2015-10-25 21:00:20 +0100
committerHarald Welte <laforge@gnumonks.org>2015-10-25 21:00:20 +0100
commitfca59bea770346cf1c1f9b0e00cb48a61b44a8f3 (patch)
treea2011270df48d3501892ac1a56015c8be57e8a7d /2005/gpl-ec2005/red-line
import of old now defunct presentation slides svn repo
Diffstat (limited to '2005/gpl-ec2005/red-line')
-rw-r--r--2005/gpl-ec2005/red-line67
1 files changed, 67 insertions, 0 deletions
diff --git a/2005/gpl-ec2005/red-line b/2005/gpl-ec2005/red-line
new file mode 100644
index 0000000..4e63da8
--- /dev/null
+++ b/2005/gpl-ec2005/red-line
@@ -0,0 +1,67 @@
+thanks for invitation
+
+introduction about the speaker
+
+legal disclaimer
+
+free software and it's role in computing
+ increased use
+ not only server market
+ not only desktop market
+ but _large_ quantities in the embedded market
+ router / gateway / firewall
+ wireless acces points / bridges
+ network attached storagee
+
+free software development model
+ distributed developers throughout the world
+ contributions from anyone with required skills
+ as a result, distributed copyright in many projects
+
+free software and it's licenses
+ free software != public domain
+ free as in freedom, not as in beer
+ significant part covered by gpl license
+
+gpl revisited
+ terminology
+ revisiting
+ complete source code
+ derivative works
+ collective works
+ non-public modifications
+
+gpl violations
+ when do i violate the license
+ what do i risk
+
+past (until 2003) gpl enforcement
+ most of it quietly
+ in many cases handled by the FSF
+
+the linksys case
+
+typical enforcement timeline
+
+success so far
+
+
+summary / what we've learnt
+ a lot of companies don't take free software licenses seriously
+ even companies with large legal deprartments have problems
+ why is that? lack of information? financial risk not hard enough?
+ it's not different to any other software license of 3rd party components
+
+ the FUD spread by certain corporations 'can the gpl be enforced' has vanished
+
+problems of gpl enforcmeent
+ distributed copyright is a safeguard, but can make enforcement difficult
+ the need to do reverse engineering to proof the violation
+ infringing companies obfuscating or encrypting free software
+ legally difficult to claim your rights as customer of gpl infringing product
+ damages claims can be difficult due to distribution problem
+
+gpl enforcment future
+ I just wanted to set some examples
+ so many cases, further enforcement has to be done by organization
+
personal git repositories of Harald Welte. Your mileage may vary