summaryrefslogtreecommitdiff
path: root/2016/open-compliance-jp
diff options
context:
space:
mode:
authorHolger Hans Peter Freyther <holger@moiji-mobile.com>2016-12-27 11:46:56 +0100
committerHolger Hans Peter Freyther <holger@moiji-mobile.com>2016-12-27 11:46:56 +0100
commit5ddbfb06084712ff69be8de2b7c6515702f4da07 (patch)
tree72632b38de84ed0fc53cd367d135e02fd0f812f1 /2016/open-compliance-jp
parent07e5c7d692ada060563b94884bed8c94e302a01b (diff)
parentbcc9e259fc0a6ef35549444755ddd1f3a84be8c1 (diff)
Merge remote-tracking branch 'origin/master'
Diffstat (limited to '2016/open-compliance-jp')
-rw-r--r--2016/open-compliance-jp/abstract.txt21
-rw-r--r--2016/open-compliance-jp/bio.txt23
2 files changed, 44 insertions, 0 deletions
diff --git a/2016/open-compliance-jp/abstract.txt b/2016/open-compliance-jp/abstract.txt
new file mode 100644
index 0000000..45178ed
--- /dev/null
+++ b/2016/open-compliance-jp/abstract.txt
@@ -0,0 +1,21 @@
+Strategies in practical GPL enforcement
+
+Enforcement of copyleft licenses like the GNU GPL has always been a
+somewhat controversial topic. Some people are not in favor of
+enforcement at all (but then, why choose the GPL and not a permissive
+license?). Other people have less inhibitions in enforcing the
+license. But then this raises the next questions? Enforcement using
+which strategy? Enforcement using which methods? The Linux Kernel
+developer community has recently re-fueled that debate on the
+ksummit-discuss mailing list.
+
+Ultimately, most projects and developers are looking for the
+downstream developers and companies to participate in a collaborative
+development model. The copyleft principle is just a legal "hack" to
+codify some part of that based on copyright. As a result, license
+compliance is not an end in itself, but the very bare legal minimum of
+what needs to be done when engaging in (particularly
+corporate/commercial) re-use of Free Software.
+
+This talk will look at the different (GPL) license enforcement
+approaches and present their advantages and disadvantages.
diff --git a/2016/open-compliance-jp/bio.txt b/2016/open-compliance-jp/bio.txt
new file mode 100644
index 0000000..0268a5f
--- /dev/null
+++ b/2016/open-compliance-jp/bio.txt
@@ -0,0 +1,23 @@
+Harald Welte is a data communications freelancer, enthusiast and hacker
+who is working with Free Software (and particularly GNU/Linux)
+since 1995 His major code contribution to the Linux kernel was as a
+core developer of the netfilter/iptables packet filter.
+
+He has co-started a number of other Free Software and Open Hardware
+projects, from RFID to telephony - including the worlds first 100% Open
+Free Software based mobile phone OpenMoko.
+
+Aside from his technical contributions, Harald has been pioneering the legal
+enforcement of the GNU GPL license as part of his gpl-violations.org project.
+More than 150 inappropriate use of GPL licensed code by commercial companies
+have been resolved as part of this effort, both in court and out of court. He
+has received the 2007 "FSF Award for the Advancement of Free Software" and the
+"2008 Google/O'Reilly Open Source award: Defender of Rights".
+
+In 2008, Harald started to work on Free Software on the GSM protocol side, both
+for passive sniffing and protocol analysis, as well as an actual network-side
+GSM stack implementation called OpenBSC, which later developed towards
+GPRS, EDGE and UMTS. In 2010, he expanded those efforts by creating
+OsmocomBB, a GSM telephony-side baseband processor firmware and
+protocol stack. Other projects include OsmocomTETRA, a receive-only
+implementation of the ETSI TETRA radio interface.
personal git repositories of Harald Welte. Your mileage may vary