Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Merge branch 'kreincke' of https://github.com/dtag-dbu/oslic into kre…

…incke

Conflicts:
	bibfiles/oscCopiedButNotRead.bib
  • Loading branch information...
commit 0f67ede0f018cebdadad9c2195a44c0b9164fad5 2 parents baffe03 + d4f5238
Karsten Reincke authored
View
18 bibfiles/oscCopiedButNotRead.bib
@@ -542,24 +542,6 @@ @ARTICLE{DeLaat2005a
timestamp = {2011.08.01}
}
-@BOOK{VwdjDebVEee2003a,
- author = {R. {van Wendel de Joode} and J. A. {de Bruijn} and M. J. G. {van
- Eeten}},
- title = {Protecting the Virtual Commons. Self-Organizing Open Source and Free
- Software Communities and Innovative Intellectual Property Regimes},
- address = {The Hague},
- year = {2003},
- shorttitle = {Protecting the Virtual Commons, 2003},
- number = {3},
- series = {Information Technology \& Law Series},
- publisher = {T.M.C. Asser Press},
- isbn = {90-6704-159-9},
- annote = {Fernleihbuch lesen},
- note = {Print},
- owner = {reincke},
- timestamp = {2012.02.20}
-}
-
@INPROCEEDINGS{AhtSurRah2006a,
author = {Ahtiainen, Aleksi and Surakka, Sami and Rahikainen, Mikko},
title = {Plaggie: GNU-licensed Source Code Plagiarism Detection Engine for
View
12 bibfiles/oscNextActions.bib
@@ -1,4 +1,4 @@
-% This file was created with JabRef 2.6.
+% This file was created with JabRef 2.7b.
% Encoding: UTF8
@INPROCEEDINGS{Airlie2006a,
@@ -1654,6 +1654,16 @@ @ARTICLE{LerTir2002a
timestamp = {2011.07.29}
}
+@BOOK{Levy2001a,
+ author = {S. Levy},
+ title = {Hackers},
+ address = {USA},
+ year = {2001},
+ publisher = {Penguin},
+ owner = {reincke},
+ timestamp = {2012.05.17}
+}
+
@ARTICLE{LinKoChuLin2006a,
author = {YH Lin and TM Ko and TR Chuang and KJ Lin},
title = {Open source licenses and the creative commons framework: License
View
64 bibfiles/oscResourcesDe.bib
@@ -1,4 +1,4 @@
-% This file was created with JabRef 2.6.
+% This file was created with JabRef 2.7b.
% Encoding: UTF8
@INBOOK{ArlBriVol2004a,
@@ -657,6 +657,29 @@ @INPROCEEDINGS{SteHam2008a
timestamp = {2011.09.01}
}
+@BOOK{VwdjDebVEee2003a,
+ author = {R. {van Wendel de Joode} and J. A. {de Bruijn} and M. J. G. {van
+ Eeten}},
+ title = {Protecting the Virtual Commons. Self-Organizing Open Source and Free
+ Software Communities and Innovative Intellectual Property Regimes},
+ address = {The Hague},
+ year = {2003},
+ shorttitle = {Protecting the Virtual Commons, 2003},
+ number = {3},
+ series = {Information Technology \& Law Series},
+ publisher = {T.M.C. Asser Press},
+ isbn = {90-6704-159-9},
+ annote = {Neben anderen will dieser Bericht die Frage beantworten, warum die
+ Community so viele verschiedene FLOSS Lizenzen definiert hat. Die
+ Antwort ist vielleicht etwas dünn: der grösste Teil der Lizenzen
+ sei von der BSD oder der GPL abgeleitet, um die grundlegenden Prinzipien
+ der Community zu schützen.},
+ language = {emglish},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.20}
+}
+
@MISC{AsfApacheLicense20a,
author = {{Apache Software Foundation}},
title = {Apache License, Version 2.0},
@@ -919,6 +942,27 @@ @BOOK{Grassmuck2002a
timestamp = {2011.03.16}
}
+@BOOK{GuiOvd2006a,
+ author = {Lucie Guibault and Ot van Daalen},
+ title = {Unravelling the Myth around Open Source Licenses. An Anaysis from
+ A Dutch and European Law Perspective},
+ address = {The Hague},
+ year = {2006},
+ shorttitle = {Unravelling the Myth around Open Source Licenses, 2006},
+ number = {8},
+ series = {IT \& Law},
+ publisher = {T. M. C. Asser Press},
+ isbn = {978-90-6704-214-7},
+ annote = {Beschreibt die Open Source Idea aus dem Blickwinkel des holländischen
+ Rechtssystem. Es endet mit 5 Empfehlungen, die der OS Lizenzierung
+ zu mehr Klarheit verhelfen sollen. Abgesehen vom Titel wird der Mythos
+ von Open Source jedoch nicht explizit näher beleuchtet.},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.05.17}
+}
+
@BOOK{Heap1994a,
author = {Nicholas Heap},
title = {OSI-Referenzmodell ohne Geheimnis},
@@ -1003,6 +1047,24 @@ @MISC{ifross2011c
urldate = {2011-09-05}
}
+@BOOK{ifrOSS2005a,
+ author = {ifrOSS and Till Jaeger and Olaf Koglin and Till Kreutzer and Axel
+ Metzger and Carsten Schulz},
+ title = {Die GPL kommentiert und erklärt},
+ address = {Beijing, Cambridge, Farnham [etc ..]},
+ year = {2005},
+ shorttitle = {Die GPL kommentiert und erklärt, 2005},
+ publisher = {O'Reilly},
+ isbn = {3-89721-389-3},
+ annote = {Erläutert die jurstischen Implikationen und die Bedeutung der GPL
+ - Abschnitt für Abschnitt und einschließlich der Bedeutung des Begriffs
+ 'abgeleitetes Werk'},
+ language = {german},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.28}
+}
+
@BOOK{Imhorst2004a,
author = {Christian Imhorst},
title = {Die Anarchie der Hacker. Richard Stallman und die Freie-Software-Bewegung},
View
63 bibfiles/oscResourcesEn.bib
@@ -1,4 +1,4 @@
-% This file was created with JabRef 2.6.
+% This file was created with JabRef 2.7b.
% Encoding: UTF8
@INBOOK{ArlBriVol2004a,
@@ -656,6 +656,29 @@ @INPROCEEDINGS{SteHam2008a
timestamp = {2011.09.01}
}
+@BOOK{VwdjDebVEee2003a,
+ author = {R. {van Wendel de Joode} and J. A. {de Bruijn} and M. J. G. {van
+ Eeten}},
+ title = {Protecting the Virtual Commons. Self-Organizing Open Source and Free
+ Software Communities and Innovative Intellectual Property Regimes},
+ address = {The Hague},
+ year = {2003},
+ shorttitle = {Protecting the Virtual Commons, 2003},
+ number = {3},
+ series = {Information Technology \& Law Series},
+ publisher = {T.M.C. Asser Press},
+ isbn = {90-6704-159-9},
+ annote = {Beside other questions this report wants to answer the question why
+ the communities have created so many different Free / Open Source
+ Software licenses. The answer is perhaps a little thin: the most
+ part of the licenses are derived from BSD or GPL 'to protect the
+ fundamental principles of the communities'.},
+ language = {emglish},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.20}
+}
+
@MISC{AsfApacheLicense20a,
author = {{Apache Software Foundation}},
title = {Apache License, Version 2.0},
@@ -913,6 +936,27 @@ @BOOK{Grassmuck2002a
timestamp = {2011.03.16}
}
+@BOOK{GuiOvd2006a,
+ author = {Lucie Guibault and Ot van Daalen},
+ title = {Unravelling the Myth around Open Source Licenses. An Anaysis from
+ A Dutch and European Law Perspective},
+ address = {The Hague},
+ year = {2006},
+ shorttitle = {Unravelling the Myth around Open Source Licenses, 2006},
+ number = {8},
+ series = {IT \& Law},
+ publisher = {T. M. C. Asser Press},
+ isbn = {978-90-6704-214-7},
+ annote = {The book describes the Open Source idea from the viewpoint of the
+ Dutch legal system. It ends in five recommendations for enforcing
+ the clarity of OS licenses and their usage. Except for the title
+ the myth of Open Source is not explicitly mentioned or discussed.},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.05.17}
+}
+
@BOOK{Heap1994a,
author = {Nicholas Heap},
title = {OSI-Referenzmodell ohne Geheimnis},
@@ -998,6 +1042,23 @@ @MISC{ifross2011c
urldate = {2011-09-05}
}
+@BOOK{ifrOSS2005a,
+ author = {ifrOSS and Till Jaeger and Olaf Koglin and Till Kreutzer and Axel
+ Metzger and Carsten Schulz},
+ title = {Die GPL kommentiert und erklärt},
+ address = {Beijing, Cambridge, Farnham [etc ..]},
+ year = {2005},
+ shorttitle = {Die GPL kommentiert und erklärt, 2005},
+ publisher = {O'Reilly},
+ isbn = {3-89721-389-3},
+ annote = {This book explains the legal implications and meaning of each GPL
+ section - including the meaning of 'derivative work'},
+ language = {german},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.28}
+}
+
@BOOK{Imhorst2004a,
author = {Christian Imhorst},
title = {Die Anarchie der Hacker. Richard Stallman und die Freie-Software-Bewegung},
View
227 extracts/ifross2005a.tex
@@ -0,0 +1,227 @@
+% Telekom osCompendium extract template
+%
+% (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
+%
+% This LaTeX-File is licensed under the Creative Commons Attribution-ShareAlike
+% 3.0 Germany License (http://creativecommons.org/licenses/by-sa/3.0/de/): Feel
+% free 'to share (to copy, distribute and transmit)' or 'to remix (to adapt)'
+% it, if you '... distribute the resulting work under the same or similar
+% license to this one' and if you respect how 'you must attribute the work in
+% the manner specified by the author ...':
+%
+% In an internet based reuse please link the reused parts to www.telekom.com and
+% mention the original authors and Deutsche Telekom AG in a suitable manner. In
+% a paper-like reuse please insert a short hint to www.telekom.com and to the
+% original authors and Deutsche Telekom AG into your preface. For normal
+% quotations please use the scientific standard to cite.
+%
+% [ File structure derived from 'mind your Scholar Research Framework'
+% mycsrf (c) K. Reincke CC BY 3.0 http://mycsrf.fodina.de/ ]
+
+%
+% select the document class
+% S.26: [ 10pt|11pt|12pt onecolumn|twocolumn oneside|twoside notitlepage|titlepage final|draft
+% leqno fleqn openbib a4paper|a5paper|b5paper|letterpaper|legalpaper|executivepaper openrigth ]
+% S.25: { article|report|book|letter ... }
+%
+% oder koma-skript S.10 + 16
+\documentclass[DIV=calc,BCOR=5mm,11pt,headings=small,oneside,abstract=true, toc=bib]{scrartcl}
+
+%%% (1) general configurations %%%
+\usepackage[utf8]{inputenc}
+
+%%% (2) language specific configurations %%%
+\usepackage[]{a4,ngerman}
+\usepackage[english, ngerman]{babel}
+\selectlanguage{ngerman}
+
+% jurabib configuration
+\usepackage[see]{jurabib}
+\bibliographystyle{jurabib}
+\input{../btexmat/oscJbibCfgDeInc}
+
+% language specific hyphenation
+\input{../btexmat/oscHyphenationDeInc}
+
+%%% (3) layout page configuration %%%
+
+% select the visible parts of a page
+% S.31: { plain|empty|headings|myheadings }
+%\pagestyle{myheadings}
+\pagestyle{headings}
+
+% select the wished style of page-numbering
+% S.32: { arabic,roman,Roman,alph,Alph }
+\pagenumbering{arabic}
+\setcounter{page}{1}
+
+% select the wished distances using the general setlength order:
+% S.34 { baselineskip| parskip | parindent }
+% - general no indent for paragraphs
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{1.2ex plus 0.2ex minus 0.2ex}
+
+
+%%% (4) general package activation %%%
+%\usepackage{utopia}
+%\usepackage{courier}
+%\usepackage{avant}
+\usepackage[dvips]{epsfig}
+
+% graphic
+\usepackage{graphicx,color}
+\usepackage{array}
+\usepackage{shadow}
+\usepackage{fancybox}
+
+%- start(footnote-configuration)
+% flush the cite numbers out of the vertical line and let
+% the footnote text directly start in the left vertical line
+\usepackage[marginal]{footmisc}
+%- end(footnote-configuration)
+
+\begin{document}
+
+%% use all entries of the bliography
+
+%%-- start(titlepage)
+\titlehead{Literaturexzerpt}
+\subject{Autor(en): \ldots}
+\title{Titel: \ldots}
+\subtitle{Jahr: \ldots }
+\author{K. Reincke\input{../btexmat/oscLicenseFootnoteInc}}
+
+%\thanks{den Autoren von KOMA-Script und denen von Jurabib}
+\maketitle
+%%-- end(titlepage)
+%\nocite{*}
+
+\begin{abstract}
+\noindent
+
+\cite[(ist:)][]{ifross2005a} \\
+Das Werk / The work\footcite[cf.][]{ifross2005a} \\
+\noindent \itshape
+\ldots Erläutert die jurstischen Implikationen und die Bedeutung der GPL -
+Abschnitt für Abschnitt und einschließlich der Bedeutung des Begriffs
+'abgeleitetes Werk' \\
+\noindent
+\ldots This book explains the legal implications and meaning of each GPL section
+- including the meaning of 'derivative work'
+\end{abstract}
+\footnotesize
+%\tableofcontents
+\normalsize
+
+\section{Vertrieb gegen Entgeld}
+
+Die Autoren unterstreichen explizit, \glqq{}[\ldots] dass man die Software
+selbst zu jedem Preis anbieten und veräußern (dürfe)\grqq{} und dass es ein
+davon unabhängiger Aspoekt sei, \glqq{}oib es (gelinge), einen bestimmten Preis
+zu erzielen [\ldots], da ja jeder die Software weitergeben (könne) und es dehalb
+einen starken Wettbewerb (gäbe)\grqq\footcite[cf.][15]{ifross2005a}.
+
+\section{Entstehende Pflichten = Art der TO-DO-Liste}
+
+Sodann listen die Autoren in nuce auf, was ein NUtzer einer GPL lizenzierten
+Software zu beachten, will sagen: durch sein eigenes Tun sicherzustellen habe:
+So müsse der Lizenztext mitgeliefert werden, die Copyrightvermerke und der
+Haftungsausschluss beim Akt des Kopierens erhalten bleiben und nach außen
+durchgreicht werden, selbst wenn sie im deutschen Raum nur sehr eingteschränkt
+wirksam sind, und der Quelltext müsse zugänglich gemacht
+werden\footcite[cf.][16]{ifross2005a}. Außerdem gäbe es \glqq{}beim Vertrieb von
+Veränderungen eines GPL-Programms\grqq{} zusätzliche Pflichten: So müssen
+deutliche Änderungsvermerke aufgenommen werden, bei interaktiven Kommandos
+müssen (weiterhin) der Haftungsausschluss und die Copyrightvermerke sichtbar
+gemacht sein, und es gelte die zentrale Regel des 'derivative
+works'\footcite[cf.][17]{ifross2005a}:
+
+\begin{quote}
+\glqq{}Wiord ein unter GPL lizenziertes Programm so verändert, dass ein
+'derivative work' [\ldots] entsteht [\ldots], darf die so veränderte Software
+insgesamt nur unter den Lizenzbedingungen der GPKL an Dritte weitergegeben
+werden\grqq{}\footcite[cf.][17]{ifross2005a}
+\end{quote}
+
+Leider ist die Zusammenfassung als Handlungsanweisungen für Programmierer
+zumindets in einer Hinsicht irreführen: Wenn man eine GPL lizenzierte Bibliothek
+oder ein Modul oder ein Plugin oder ein inkludierbares File als Basis für eine
+darauf aufsetzende Entwicklung nimmt, hängt dieses darauf aufsetzende Werk
+sicher von der Bibliothek, dem Modul, dem Plugin oder dem inkludierbares File
+ab, ohne dass diese Bibliothek, dieses Modul, dieses Plugin oder dieses
+inkludierbares File dafür geändert worden sein müsste.
+
+\section{Derivative Work}
+
+Das zentrale Problem bei der GPL sei der \glqq{}virale
+Effekt\grqq{}\footcite[cf.][64]{ifross2005a}
+
+Initial unterstreichen die Autoren, dass \glqq{}[\ldots] in jedem Falle die
+Frage (entscheidend sei), wann ein 'derivative work', also ein 'abgeleitetes
+Werk' vorliege\grqq{} und dass glqq{}die Antwort auf die Frage (entscheide), ob
+der Rechtsinhaber sein Programm der GPL unterstellen (müsse), oder ob er frei in
+der Lizenzwahl (sei), also eine andere Open Sourcve-Lizenz oder eine proprietäre
+Lizenz verwenden (dürfe)\grqq{}\footcite[cf.][64]{ifross2005a}
+
+\subsection{klare nicht 'derived' Fälle}
+Als einen eindeutigen Fall, bei dem ein 'zugreifendes' Werk trotz technischer
+Verbindung nicht abgeleitet worden sei, stellen die Autoren sodann den
+Linuxkernel selbst dar: Durch eine spezielle Beudetungserklärung durch Linux
+Torvalds sei festgelegt, dass der Zugriff auf 'kernel services' das zugreifende
+Produkt gerade nicht zu einem vom Kernel abgeleiteten Werk mache. Deshalb wirke
+die GPL2 L;izenzierung des Kernels also nicht nach
+außen\footcite[cf.][66]{ifross2005a}.
+
+Des weiteren verweisen die Autoren darauf, dass die glibc, als eine derjenigen
+Bibliotheken, die die Zugriffe auf die Kernlservices kapselt, sozusagen
+sicherhateilshalber selbst nochmal der LGPL unterstellt sei, die ihrerseits
+gerade nicht erzwinge, dass auf sie aufsetzenden Programme ebenfalls GPL
+lizenztiert werden müssen\footcite[cf.][66]{ifross2005a}
+
+\subsection{klare 'derived' Fälle}
+
+Hier schreiben die Autoren klar, dass ein \glqq{}[\ldots] ein eigener Code
+eindeutig der GPL unterstellt werden (müsse), wenn das vorbestehende
+GPL-Programm in seiner bestehenden Form geändert werden[:] Erweiterungen,
+Kürzungen und Abänderungen des Codes führen stets dazu, dass das so geänderte
+Programm der GPL unterstellt werden müsse [\ldots]\grqq{}, vorausgesetzt, es
+werde vertrieben und nicht nur für sich selbst
+genutzt\footcite[cf.][66]{ifross2005a}.
+
+\subsection{unklare 'derived' Fälle}
+
+Hier sagen die Autoren, dass jene Fälle \glqq{}problematisch\grqq{} seien,
+\glqq{}[ldots] in denen nicht nur eine einfache Weiterentwicklung stattfinde,
+sondern ein GPL-Programm mit anderen Programmen oder Programmbestandenteilen
+kombiniert (werde)\grqq{}, und dass die GPL dazu nur \glqq{}Hinweise\grqq{}
+enthalte, die \glqq{}[ldots] alles andere als eindeutig
+(seien)\grqq{}\footcite[cf.][67]{ifross2005a}
+
+Nach einigen Bemerkungen fassen die Autoren folgende Regeln als Leitschnur
+zusammen
+
+\begin{quote}
+\begin{enumerate}
+ \item Programme oder Softwarebestandeteile, die (inhaltlich) nicht voneinander
+ abgeleitet sind, können unter unterschiedlichen Lizenzen verbreitet werden,
+ wenn sie auch formal getrennt vorliegen;
+ \item Programme oder Softwarebestandeteile, die (inhaltlich) nicht voneinder
+ abgeleitet sind, müssen aber dann insgesamt unter der GPL verbreitet werden,
+ wenn sie ein 'Ganzes' bilden, weil keine formalen Trennung besteht;
+ \item Programme oder Softwarebestandteile, die (inhaltlich) voneinander
+ abgeleitet sind, dürfen stets nur unter der GPL gemeinsam verbreitet werden.
+\end{enumerate}
+\end{quote}\footcite[cf.][69]{ifross2005a}
+
+Abgesehen, dass diese Regeln für sich genommen sprachlich viel zu scharf sind,
+weil sich nicht darauf verweisen, dass immer zumindest eines der kombinierten
+Teile unter GPL lizenziert sein muss, hängt die sonstige Klarheit an den
+selbst unscharfen Begriffen '(inhaltlich) [nicht] voneinander abgeleitet' und
+'formal getrennt'.
+
+Insofern kann man diese Regeln nicht an Entwickler weiterreichen.
+
+\small
+\bibliography{../bibfiles/oscResourcesDe}
+
+\end{document}
View
133 extracts/vwdjDebVEee2003a.tex
@@ -0,0 +1,133 @@
+% Telekom osCompendium extract template
+%
+% (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
+%
+% This LaTeX-File is licensed under the Creative Commons Attribution-ShareAlike
+% 3.0 Germany License (http://creativecommons.org/licenses/by-sa/3.0/de/): Feel
+% free 'to share (to copy, distribute and transmit)' or 'to remix (to adapt)'
+% it, if you '... distribute the resulting work under the same or similar
+% license to this one' and if you respect how 'you must attribute the work in
+% the manner specified by the author ...':
+%
+% In an internet based reuse please link the reused parts to www.telekom.com and
+% mention the original authors and Deutsche Telekom AG in a suitable manner. In
+% a paper-like reuse please insert a short hint to www.telekom.com and to the
+% original authors and Deutsche Telekom AG into your preface. For normal
+% quotations please use the scientific standard to cite.
+%
+% [ File structure derived from 'mind your Scholar Research Framework'
+% mycsrf (c) K. Reincke CC BY 3.0 http://mycsrf.fodina.de/ ]
+
+%
+% select the document class
+% S.26: [ 10pt|11pt|12pt onecolumn|twocolumn oneside|twoside notitlepage|titlepage final|draft
+% leqno fleqn openbib a4paper|a5paper|b5paper|letterpaper|legalpaper|executivepaper openrigth ]
+% S.25: { article|report|book|letter ... }
+%
+% oder koma-skript S.10 + 16
+\documentclass[DIV=calc,BCOR=5mm,11pt,headings=small,oneside,abstract=true, toc=bib]{scrartcl}
+
+%%% (1) general configurations %%%
+\usepackage[utf8]{inputenc}
+
+%%% (2) language specific configurations %%%
+\usepackage[]{a4,ngerman}
+\usepackage[ngerman, english]{babel}
+\selectlanguage{english}
+
+% jurabib configuration
+\usepackage[see]{jurabib}
+\bibliographystyle{jurabib}
+\input{../btexmat/oscJbibCfgEnInc}
+
+% language specific hyphenation
+\input{../btexmat/oscHyphenationEnInc}
+
+%%% (3) layout page configuration %%%
+
+% select the visible parts of a page
+% S.31: { plain|empty|headings|myheadings }
+%\pagestyle{myheadings}
+\pagestyle{headings}
+
+% select the wished style of page-numbering
+% S.32: { arabic,roman,Roman,alph,Alph }
+\pagenumbering{arabic}
+\setcounter{page}{1}
+
+% select the wished distances using the general setlength order:
+% S.34 { baselineskip| parskip | parindent }
+% - general no indent for paragraphs
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{1.2ex plus 0.2ex minus 0.2ex}
+
+
+%%% (4) general package activation %%%
+%\usepackage{utopia}
+%\usepackage{courier}
+%\usepackage{avant}
+\usepackage[dvips]{epsfig}
+
+% graphic
+\usepackage{graphicx,color}
+\usepackage{array}
+\usepackage{shadow}
+\usepackage{fancybox}
+
+%- start(footnote-configuration)
+% flush the cite numbers out of the vertical line and let
+% the footnote text directly start in the left vertical line
+\usepackage[marginal]{footmisc}
+%- end(footnote-configuration)
+
+\begin{document}
+
+%% use all entries of the bliography
+
+%%-- start(titlepage)
+\titlehead{Literaturexzerpt}
+\subject{Autor(en): R. van Wendel de Joode and J. A. de Bruijn and M. J. G. van
+Eeten}
+\title{Titel: Protecting the Virtual Commons. Self-Organizing Open Source
+and Free Software Communities and Innovative Intellectual Property Regimes}
+\subtitle{Jahr: 2003 }
+\author{K. Reincke\input{../btexmat/oscLicenseFootnoteInc}}
+
+%\thanks{den Autoren von KOMA-Script und denen von Jurabib}
+\maketitle
+%%-- end(titlepage)
+%\nocite{*}
+
+\begin{abstract}
+Das Werk / The work\footcite[][]{VwdjDebVEee2003a} \\
+\noindent \itshape
+\ldots Neben anderen will dieser Bericht die Frage beantworten, warum die
+Community so viele verschiedene FLOSS Lizenzen definiert hat. Die Antwort ist
+vielleicht etwas dünn: der grösste Teil der Lizenzen sei von der BSD oder der
+GPL abgeleitet, um die grundlegenden Prinzipien der Community zu schützen. \\
+\noindent
+\ldots Beside other questions this report wants to answer the question why the
+communities have created so many different Free / Open Source Software licenses.
+The answer is perhaps a little thin: the most part of the licenses are derived
+from BSD or GPL 'to protect the fundamental principles of the communities'.
+\end{abstract}
+\footnotesize
+%\tableofcontents
+\normalsize
+
+Beside other questions this report wants to answer the following question:
+\qlqq{}Why have open source and free software communities created so many
+differentlicenses to protect their intellectual
+property?\grqq{}\footcite[cf.][2]{VwdjDebVEee2003a}. The details are elaborated
+on some pages\footcite[cf.][72ff]{VwdjDebVEee2003a} and finally the authors
+themselves \glqq{}[\ldots] argued that many of the licenses derive from two
+licenses, namely the BSD license and the
+GPL\grqq{}\footcite[cf.][109]{VwdjDebVEee2003a} and that \glqq{} each open
+source and free softwarer license serves morew or less the same function, namely
+to protect the fundamental principles of the
+communities\grqq{}\footcite[cf.][11o]{VwdjDebVEee2003a}
+
+\small
+\bibliography{../bibfiles/oscResourcesEn}
+
+\end{document}
View
1  oslic-en.tex
@@ -216,6 +216,7 @@ \chapter{Open Source: Important Minor Points}
\chapter{Open Source: Use Cases As Principle of Classification}
\input{snippets/en/06-osUseCases/0600-chapterAbstractInc}
\input{snippets/en/06-osUseCases/0601-chapterStartInc}
+\input{snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc}
%%%%%%%%%%%%%%%
\chapter{Open Source Licenses: Find Your Specific To-do Lists}
View
2  snippets/en/06-osUseCases/0601-chapterStartInc.tex
@@ -23,6 +23,6 @@
%% use all entries of the bibliography
%\nocite{*}
-[TDB \ldots]
+[todo: \ldots (insert all contexts concerning the idea of use cases)]
%\bibliography{../../../bibfiles/oscResourcesEn}
View
73 snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc.tex
@@ -0,0 +1,73 @@
+% Telekom osCompendium 'for beeing included' snippet template
+%
+% (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
+%
+% This LaTeX-File is licensed under the Creative Commons Attribution-ShareAlike
+% 3.0 Germany License (http://creativecommons.org/licenses/by-sa/3.0/de/): Feel
+% free 'to share (to copy, distribute and transmit)' or 'to remix (to adapt)'
+% it, if you '... distribute the resulting work under the same or similar
+% license to this one' and if you respect how 'you must attribute the work in
+% the manner specified by the author ...':
+%
+% In an internet based reuse please link the reused parts to www.telekom.com and
+% mention the original authors and Deutsche Telekom AG in a suitable manner. In
+% a paper-like reuse please insert a short hint to www.telekom.com and to the
+% original authors and Deutsche Telekom AG into your preface. For normal
+% quotations please use the scientific standard to cite.
+%
+% [ Framework derived from 'mind your Scholar Research Framework'
+% mycsrf (c) K. Reincke 2012 CC BY 3.0 http://mycsrf.fodina.de/ ]
+%
+
+
+%% use all entries of the bibliography
+%\nocite{*}
+
+Based on this information we can no derive and define the use cases by which the
+OSLiC classifies its license fulfilling to-do lists:
+
+Firstly we have to discriminate the usage of Open Source software by the nature
+of the software itself:
+
+On the one side you can use an application intended to support the work of an
+end-user. It takes input data and generates output data, mostly by using a more
+or less elaborated end-user interface. On the other side you can use a computer
+librabry intended to support the work of a software developer. It mostly offers
+functions and/or objects and is embedded into an overarching work like an
+application.
+
+The use of an application is different from the use of a software library
+because the use of a software library implies the act of developing a new
+overarching piece of software.
+
+Secondly we have to discriminate the usage of Open Source software by the
+addressee:
+
+On the one side you can intend to use the software directly for your own
+purpose. On the other side you can intend to distribute the software to a third
+party.
+
+And thirdly we have to discriminate the usage of Open Source software by nature of
+the usage itself:
+
+One the one side you can intend to use the software as it is, respectively as
+you got it. On the other side you can intend to modify the software before using
+it.
+
+Let's form the corresponding dichotomies
+
+use-it-as-you-got-it <> modify-it
+use-it-for-yourself <> distribute-it
+application <> library
+
+Now we have 8 possibilities to combine these attributes:
+
+Use an application as you got it only for yourself
+Use a library as you got it only for your self
+Distribute an application as you got it to a third party
+Distribute a library as you got it to a third party
+
+
+
+
+%\bibliography{../../../bibfiles/oscResourcesEn}
View
14 snippets/en/0b-Appendices/0b02-MythsOfOsEn.tex
@@ -27,6 +27,15 @@
\section{Some Widespread Open Source Myths}
+From the viewpoint of an internet student we have to consider that the web
+offers a mass of rumors concerning the nature of Open Source Software
+(Licenses). Here are some of the myths\footcite[At least one time even a
+scientific legally discussing book is talking about the \glqq{}Myth around Open
+Source Licenses\grqq{} - although only as part of the title: cf][1ff,
+especially 209ff]{GuiOvd2006a}.
+we met:
+
+
\begin{description}
\item[Open Source tries to improve the world ethically] :- no, there's a clear
ban to exclude persons, groups, purposes
@@ -72,12 +81,10 @@ \section{Some Widespread Open Source Myths}
containg GNU software and the Linux kernel. But Ian Murdock states also, that
debian does not want to earn money. (clear details)
% TODO: check, wether OSD requires license fee free distribution
-
\item[Modifications of Open Source Software must be marked] :- No. This is not
a defining postulation of the OSD. The OSD allows licenses to require the mark
of modifacations. But it does not require from all licenses to rquire the mark
modifications for being an Open Source License.
-
\item[Modifications of Open Source Software must be marked by your personal
data] :- No, it's only required to mark modifications so that a reader could
distinguish the modifications from the original code. It's required for saving
@@ -86,8 +93,7 @@ \section{Some Widespread Open Source Myths}
requires your name. But's not featue of Open Source Software in general. And
at least the licenses discussed by us do not require to insert your name.
% TODO: check wether any of our licenses reuire that you mark modifications by
-% your personal data / real name
-
+% your personal data / real name
\item[The Open Source Definition determines the conditions to use Open Source
Software] :- No. The Open Source Definition determines which licenses are Open
Source Licenses, nothing more. The OSD is a set of necessary conditions to be
Please sign in to comment.
Something went wrong with that request. Please try again.