blob: 4e63da8532658fc3c3413b62b7de989ed6a3c116 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
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
|
