Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Merge branch 'kreincke' into integration

  • Loading branch information...
commit 6414909c74eddf1bf437018905fd8e6078b8ddcf 2 parents 727339f + 0e245ed
Karsten Reincke authored
Showing with 2,439 additions and 278 deletions.
  1. +10 −0 CHANGES
  2. +98 −125 bibfiles/oscCopiedButNotRead.bib
  3. +11 −1 bibfiles/oscNextActions.bib
  4. +187 −23 bibfiles/oscResourcesDe.bib
  5. +183 −23 bibfiles/oscResourcesEn.bib
  6. +2 −1  btexmat/oscHyphenationEnInc.tex
  7. +2 −1  btexmat/oscNclAbbreviationsEnInc.tex
  8. +3 −0  btexmat/oscNclJournalsInc.tex
  9. +227 −0 extracts/ifross2005a.tex
  10. +133 −0 extracts/vwdjDebVEee2003a.tex
  11. +10 −5 oslic-en.tex
  12. +1 −1  release.tex
  13. +6 −2 snippets/en/06-osUseCases/0600-chapterAbstractInc.tex
  14. +160 −1 snippets/en/06-osUseCases/0601-chapterStartInc.tex
  15. +311 −0 snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc.tex
  16. +6 −2 snippets/en/07-osToDoListFinder/0700-chapterAbstractInc.tex
  17. +514 −1 snippets/en/07-osToDoListFinder/0701-chapterStartInc.tex
  18. +3 −4 snippets/en/08-osFulfillmentByToDoLists/0800-chapterAbstractInc.tex
  19. +17 −23 snippets/en/08-osFulfillmentByToDoLists/0802-apacheFulfillToDoList.tex
  20. +501 −20 snippets/en/08-osFulfillmentByToDoLists/0803-bsdFulfillToDoList.tex
  21. +13 −21 snippets/en/08-osFulfillmentByToDoLists/0804-gplv2FulfillToDoList.tex
  22. +13 −19 snippets/en/08-osFulfillmentByToDoLists/0805-mitFulfillToDoList.tex
  23. +10 −4 snippets/en/0b-Appendices/0b02-MythsOfOsEn.tex
  24. +18 −1 snippets/en/20110928-Changes.tex
  25. BIN  xtras/oslicFinderDefs-2012-06-24-rel-0.92.xmind
  26. BIN  xtras/oslicFinderDefs-2012-0619-rel-0.91.xmind
View
10 CHANGES
@@ -1,3 +1,13 @@
+2012-07-05: release 0.4.0
+- textual improvements
+2012-07-03: release 0.3.99
+- completed the break through version containing the
+ finder, the definitions, and the corresponding
+ BSD to-do lists.
+- Integrated Greg's proposals for adding a license
+ specific finder additionally.
+2012-06-24: release 0.3.90
+- completed the OS UC finder introducing chapter
2012-03-22: released 0.2.1
- generalization of bin/gendist.sh (thanks to Eitan Adler [grimreaper])
- upgrade of bin/gendist.sh according to changings 0.1.6->0.2.0
View
223 bibfiles/oscCopiedButNotRead.bib
@@ -1,4 +1,4 @@
-% This file was created with JabRef 2.6.
+% This file was created with JabRef 2.8.
% Encoding: UTF8
@INPROCEEDINGS{AlsAsuSca2009a,
@@ -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
@@ -776,6 +758,26 @@ @ARTICLE{Azzi2010a
timestamp = {2012.02.13}
}
+@INCOLLECTION{Boeckler2006a,
+ author = {Lina B\"{o}ckler},
+ title = {Mit Freier Software gegen den Wettbewerb},
+ year = {2006},
+ pages = {69 - 76},
+ shorttitle = {Mit Freier Software gegen den Wettbewerb, 2006},
+ booktitle = {Variationen im Recht: Beiträge zum Arbeits-, Immaterialgüter-, Infrastruktur-,
+ Lauterkeits-, Unternehmens-, Wettbewerbs- und Zivilrecht},
+ booktitleaddon = {Festbeigabe für Fanz Jürgen Säcker zum 65. Geburstag},
+ editor = {Katharina Vera Boesche},
+ address = {Berlin},
+ publisher = {BWV},
+ isbn = {3-8305-1234-1},
+ annote = {[eval copy]},
+ language = {german},
+ note = {BibWeb/Copy},
+ owner = {reincke},
+ timestamp = {2012.06.20}
+}
+
@ARTICLE{bacCar2010a,
author = {Paula M. Bach and John M. Carroll},
title = {Characterizing the Dynamics of Open User Experience Design: The Cases
@@ -1026,22 +1028,6 @@ @INPROCEEDINGS{BerPri2001a
urldate = {2011-12-29}
}
-@BOOK{Berry2008a,
- author = {David M. Berry},
- title = {Copy, Rip, Burn},
- address = {London},
- year = {2008},
- shorttitle = {Copy, Rip, Burn, 2008a},
- titleaddon = {The Politics of Copyleft and Open Source},
- publisher = {Pluto Press},
- isbn = {978-0-7453-2414-2},
- annote = {Fernlehibuch},
- language = {english},
- note = {Print},
- owner = {reincke},
- timestamp = {2012.02.28}
-}
-
@INPROCEEDINGS{BhaSum2007a,
author = {Jaijit Bhattacharya and Sourabh Suman},
title = {Analysis of popular open source licenses and their applicability
@@ -1880,30 +1866,6 @@ @ARTICLE{DemWeiJonGre2002a
urldate = {2011-12-28}
}
-@INPROCEEDINGS{DipGerGueAnt2010a,
- author = {Di Penta, Massimiliano and German, Daniel M. and Gu{\'e}h{\'e}neuc,
- Yann-Ga\"{e}l and Antoniol, Giuliano},
- title = {An Exploratory Study of the Evolution of Software Licensing},
- year = {2010},
- pages = {145-154},
- shorttitle = {An Exploratory Study of the Evolution of Software Licensing, 2010},
- booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software
- Engineering},
- volume = {1},
- series = {ICSE '10},
- address = {New York, NY, USA},
- publisher = {ACM},
- isbn = {978-1-60558-719-6},
- annote = {[to be evaluated]},
- keywords = {empirical study, evolution, mining software repositories, open source
- systems, software licenses},
- note = {BibWeb/PDF},
- owner = {reincke},
- timestamp = {2012.01.11},
- url = {http://doi.acm.org/10.1145/1806799.1806824},
- urldate = {2011-12-28}
-}
-
@MISC{Diedrich2011a,
author = {Oliver Diedrich},
title = {Die Geschichte von Linux},
@@ -1943,6 +1905,30 @@ @ARTICLE{DioDicAugDorToa2007a
urldate = {2011-12-29}
}
+@INPROCEEDINGS{DipGerGueAnt2010a,
+ author = {Di Penta, Massimiliano and German, Daniel M. and Gu{\'e}h{\'e}neuc,
+ Yann-Ga\"{e}l and Antoniol, Giuliano},
+ title = {An Exploratory Study of the Evolution of Software Licensing},
+ year = {2010},
+ pages = {145-154},
+ shorttitle = {An Exploratory Study of the Evolution of Software Licensing, 2010},
+ booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software
+ Engineering},
+ volume = {1},
+ series = {ICSE '10},
+ address = {New York, NY, USA},
+ publisher = {ACM},
+ isbn = {978-1-60558-719-6},
+ annote = {[to be evaluated]},
+ keywords = {empirical study, evolution, mining software repositories, open source
+ systems, software licenses},
+ note = {BibWeb/PDF},
+ owner = {reincke},
+ timestamp = {2012.01.11},
+ url = {http://doi.acm.org/10.1145/1806799.1806824},
+ urldate = {2011-12-28}
+}
+
@ARTICLE{Dobb2009a,
author = {Dr. Dobb},
title = {It All About The License},
@@ -2392,6 +2378,22 @@ @INPROCEEDINGS{FujTsu2010a
urldate = {2011-12-29}
}
+@ARTICLE{FunZei2007a,
+ author = {Axel Funk and Gregor Zeitfang},
+ title = {Die GNU General Public License, Version 3},
+ journal = {Computer und Recht},
+ year = {2007},
+ volume = {23},
+ pages = {617-624},
+ shorttitle = {Die GNU General Public License, Version 3, 2007},
+ number = {10},
+ annote = {[evaluate copy]},
+ language = {german},
+ note = {BibWeb/Copy},
+ owner = {reincke},
+ timestamp = {2012.06.20}
+}
+
@MISC{FuseSource2010a,
author = {The {Fuse Source Team}},
title = {How to Use Open Source Integration Software Safely in the Enterprise.
@@ -4286,6 +4288,27 @@ @INPROCEEDINGS{MtsBie2008a
urldate = {2012-02-01}
}
+@ARTICLE{MueReg2009a,
+ author = {Müller-Seitz, Gordon and Reger, Guido},
+ title = {Is open source software living up to its promises? Insights for open
+ innovation management from two open source software-inspired projects},
+ journal = {R\&D Management},
+ year = {2009},
+ volume = {39},
+ pages = {372-381},
+ shorttitle = {Is open source software living up to its promises?, 2009},
+ number = {4},
+ annote = {[to be evaluated]},
+ doi = {10.1111/j.1467-9310.2009.00565.x},
+ language = {english},
+ note = {BibWeb/PDF},
+ owner = {reincke},
+ publisher = {Blackwell Publishing Ltd},
+ timestamp = {2012.02.13},
+ url = {http://dx.doi.org/10.1111/j.1467-9310.2009.00565.x},
+ urldate = {2012-02-09}
+}
+
@INPROCEEDINGS{MunFogWil2009a,
author = {Munga, Neeshal and Fogwill, Thomas and Williams, Quentin},
title = {The Adoption of Open Source Software in Business Models: A Red Hat
@@ -4354,27 +4377,6 @@ @ARTICLE{Mustonen2003a
urldate = {2012-02-09}
}
-@ARTICLE{MueReg2009a,
- author = {Müller-Seitz, Gordon and Reger, Guido},
- title = {Is open source software living up to its promises? Insights for open
- innovation management from two open source software-inspired projects},
- journal = {R\&D Management},
- year = {2009},
- volume = {39},
- pages = {372-381},
- shorttitle = {Is open source software living up to its promises?, 2009},
- number = {4},
- annote = {[to be evaluated]},
- doi = {10.1111/j.1467-9310.2009.00565.x},
- language = {english},
- note = {BibWeb/PDF},
- owner = {reincke},
- publisher = {Blackwell Publishing Ltd},
- timestamp = {2012.02.13},
- url = {http://dx.doi.org/10.1111/j.1467-9310.2009.00565.x},
- urldate = {2012-02-09}
-}
-
@INPROCEEDINGS{NadDerBac2007a,
author = {Nadah, Nadia and {Dulong de Rosnay}, M\'{e}lanie and Bachimont, Bruno},
title = {Licensing Digital Content With A Generic Ontology: Escaping From
@@ -4708,20 +4710,6 @@ @ARTICLE{Petreley2007a
urldate = {2011-12-28}
}
-@BOOK{Phillips2009a,
- author = {Douglas E. Phillips},
- title = {The Software License Unveiled. How Legislation by License Controls
- Software Access},
- address = {Oxford, New York, Auckland [etc. ...]},
- year = {2009},
- shorttitle = {The Software License Unveiled, 2009},
- publisher = {Oxford University Press},
- isbn = {978-0-19-534187-4},
- annote = {[to be evaluated]},
- owner = {reincke},
- timestamp = {2012.02.28}
-}
-
@ARTICLE{Polanski2007a,
author = {Arnold Polanski},
title = {Is the General Public Licence a Rational Choice?},
@@ -5450,6 +5438,22 @@ @INPROCEEDINGS{Scacchi2007a
urldate = {2011-12-29}
}
+@BOOK{Schaefer2007a,
+ author = {Fabian Schäfer},
+ title = {Der virale Effekt. Entwicklungsrisiken im Umfeld von Open Source
+ Software},
+ address = {Karlsruhe},
+ year = {2007},
+ shorttitle = {Der virale Effekt, 2007},
+ publisher = {Universitätsverlag Karlsruhe},
+ isbn = {978-3-86644-141-5},
+ annote = {[tbd: evaluate copy]},
+ language = {german},
+ note = {BibWeb/PDF},
+ owner = {reincke},
+ timestamp = {2011.08.03}
+}
+
@ARTICLE{Schlesinger2007a,
author = {Schlesinger, David},
title = {Working with Open Source: A Practical Guide},
@@ -5508,22 +5512,6 @@ @INPROCEEDINGS{SchKad2009a
urldate = {2012-01-06}
}
-@BOOK{Schaefer2007a,
- author = {Fabian Schäfer},
- title = {Der virale Effekt. Entwicklungsrisiken im Umfeld von Open Source
- Software},
- address = {Karlsruhe},
- year = {2007},
- shorttitle = {Der virale Effekt, 2007},
- publisher = {Universitätsverlag Karlsruhe},
- isbn = {978-3-86644-141-5},
- annote = {[tbd: evaluate copy]},
- language = {german},
- note = {BibWeb/PDF},
- owner = {reincke},
- timestamp = {2011.08.03}
-}
-
@ARTICLE{Searls2009a,
author = {Searls, Doc},
title = {Eof[:] The Power of Definitions},
@@ -6810,21 +6798,6 @@ @PROCEEDINGS{LutBaeGeh2006a
urldate = {2011-10-17}
}
-@PROCEEDINGS{VdBCouJae2011a,
- title = {The International Free and Open Source Software Law Book},
- year = {2011},
- shorttitle = {The International Free and Open Source Software Law Book, 2011},
- editor = {Ywain {Van den Brande} and Shane Coughlan and Till Jaeger},
- address = {Munich (Germany)},
- publisher = {Open Source Press},
- isbn = {978-3-941841-49-9},
- annote = {Fernleihauswertung: Articles listed particularily},
- language = {english},
- note = {Print},
- owner = {reincke},
- timestamp = {2012.02.22}
-}
-
@PROCEEDINGS{FLOSS10-2010a,
title = {Proceedings of the 3rd International Workshop on Emerging Trends
in Free/Libre/Open Source Software Research and Development},
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
210 bibfiles/oscResourcesDe.bib
@@ -1,4 +1,4 @@
-% This file was created with JabRef 2.6.
+% This file was created with JabRef 2.8.
% 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 = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.20}
+}
+
@MISC{AsfApacheLicense20a,
author = {{Apache Software Foundation}},
title = {Apache License, Version 2.0},
@@ -691,6 +714,24 @@ @ARTICLE{Babcock2006a
timestamp = {2012.03.09}
}
+@BOOK{Berry2008a,
+ author = {David M. Berry},
+ title = {Copy, Rip, Burn},
+ address = {London},
+ year = {2008},
+ shorttitle = {Copy, Rip, Burn, 2008a},
+ titleaddon = {The Politics of Copyleft and Open Source},
+ publisher = {Pluto Press},
+ isbn = {978-0-7453-2414-2},
+ annote = {Dies soziologische Buch enthält zumindest eine Hinweise zur Geschichte
+ von Open Source - bezogen auf die internen 'Schlachten' ('from software
+ to open source?') und deren Diskursformen ('the contestation of code').},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.28}
+}
+
@BOOK{Booth2010a,
author = {David R. Booth},
title = {Peer Production and Software. What Mozilla Has To Teach Government},
@@ -901,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},
@@ -985,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},
@@ -1079,6 +1159,28 @@ @BOOK{JaeMet2002a
timestamp = {2011.07.27}
}
+@BOOK{Kaes2008a,
+ author = {Simone Käs},
+ title = {Rethinking industry practice. The emergence of openness in the embedded
+ component industry},
+ address = {München},
+ year = {2008},
+ shorttitle = {Rethinking industry practice; The emergence of openness, 2008},
+ publisher = {Pro BUSINESS},
+ isbn = {978-3-86805-256-5},
+ annote = {Untersucht den Wandel hin zur Offenheit in der Softwareentwicklung
+ über Interviews innerhalb von 'Embedded-Linux'-Firmen. Das Ergebnis
+ ist, dass die Offenheit kundengetrieben sei und zugleich einen Lernprozess
+ innerhalb der Firmen bedinge. Das Buch enthält eine kurze, aber präzise
+ Darstellung dessen, was OSS auch aus Lizenzsicht ist; eine systematische
+ Darstellung der eingegangenen Verpflichtungen liefert es nicht.},
+ comment = {FaM Bibliothek Recht und Wirtschaft 05/QP 210 K11},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2011.08.01}
+}
+
@BOOK{Kersken2009a,
author = {Sasche Kersken},
title = {Apache 2.2. Das umfassende Handbuch},
@@ -1140,28 +1242,6 @@ @BOOK{Kugler2005a
timestamp = {2011.08.04}
}
-@BOOK{Kaes2008a,
- author = {Simone Käs},
- title = {Rethinking industry practice. The emergence of openness in the embedded
- component industry},
- address = {München},
- year = {2008},
- shorttitle = {Rethinking industry practice; The emergence of openness, 2008},
- publisher = {Pro BUSINESS},
- isbn = {978-3-86805-256-5},
- annote = {Untersucht den Wandel hin zur Offenheit in der Softwareentwicklung
- über Interviews innerhalb von 'Embedded-Linux'-Firmen. Das Ergebnis
- ist, dass die Offenheit kundengetrieben sei und zugleich einen Lernprozess
- innerhalb der Firmen bedinge. Das Buch enthält eine kurze, aber präzise
- Darstellung dessen, was OSS auch aus Lizenzsicht ist; eine systematische
- Darstellung der eingegangenen Verpflichtungen liefert es nicht.},
- comment = {FaM Bibliothek Recht und Wirtschaft 05/QP 210 K11},
- language = {english},
- note = {Print},
- owner = {reincke},
- timestamp = {2011.08.01}
-}
-
@ARTICLE{McAllister2003a,
author = {Neil McAllister},
title = {Licence to Profit [. Hybrid Open Source Licensing]},
@@ -1270,6 +1350,73 @@ @BOOK{Oberhem2008a
timestamp = {2011.08.01}
}
+@MISC{BsdLicense2Clause,
+ author = {{Open Source Initiative}},
+ title = {The BSD 2-Clause License},
+ year = {2012 [Jahr o.A.]},
+ shorttitle = {The BSD 2-Clause License, 2012},
+ annote = {Die aktuellste BSD Lizenz, die auch als 2 Klausel BSD Lizenz bekannt
+ ist.},
+ language = {english},
+ note = {FreeWeb/HTML},
+ owner = {reincke},
+ timestamp = {2012.07.03},
+ url = {http://www.opensource.org/licenses/BSD-2-Clause},
+ urldate = {2012-07-03}
+}
+
+@MISC{BsdLicense3Clause,
+ author = {{Open Source Initiative}},
+ title = {The BSD 3-Clause License},
+ year = {2012 [Jahr o.A.]},
+ shorttitle = {The BSD 3-Clause License, 2012},
+ annote = {Die ältere BSD Lizenz, die auch als 3 Klausel BSD Lizenz bekannt
+ ist.},
+ language = {english},
+ note = {FreeWeb/HTML},
+ owner = {reincke},
+ timestamp = {2012.07.03},
+ url = {http://www.opensource.org/licenses/BSD-3-Clause},
+ urldate = {2012-07-04}
+}
+
+@MISC{OSI2012a,
+ author = {{Open Source Initiative}},
+ title = {The Open Source Definition},
+ year = {2012 [Jahr o.A.]},
+ shorttitle = {The Open Source Definition, 2012},
+ annote = {Diese Seite listet die 10 Regeln auf, die zusammen bestimmen, wann
+ eine bestimmte Lizenz als Open Source Lizenz klassifiziert werden
+ kann. Sie präsentiert die Open Source Definition. Das bedeutet auch,
+ dass Software tatsächlich nur dann Open Source Software ist, wenn
+ ihre Lizenz als Open Source Lizenz durch die Open Source Initiative
+ bestätigt worden ist.},
+ language = {english},
+ note = {FreeWeb},
+ owner = {reincke},
+ timestamp = {2012.06.21},
+ url = {http://www.opensource.org/docs/osd},
+ urldate = {2012-06-21}
+}
+
+@BOOK{Phillips2009a,
+ author = {Douglas E. Phillips},
+ title = {The Software License Unveiled. How Legislation by License Controls
+ Software Access},
+ address = {Oxford, New York, Auckland [etc. ...]},
+ year = {2009},
+ shorttitle = {The Software License Unveiled, 2009},
+ publisher = {Oxford University Press},
+ isbn = {978-0-19-534187-4},
+ annote = {Stellt die proprietären Lizenzen den Freien oder Open Source Alternativen
+ gegenüber. Das Fazit ist mutig: Proprietär lizenzierte Software sei
+ Nutzbarkeits orientiert (und vernachlässige die Nutzungsrechte).
+ Open Source Software dagegen sei Entwickler orientiert (und vernachlässige
+ die Nutzbarkeit).},
+ owner = {reincke},
+ timestamp = {2012.02.28}
+}
+
@BOOK{RenVetRexKet2005a,
author = {Thomas Renner and Michael Vetter and Sascha Rex and Holger Kett},
title = {Open Source Software. Einsatzpotentiale und Wirtschaftlichkeit},
@@ -1644,6 +1791,23 @@ @PROCEEDINGS{GehLut2004a
urldate = {2011-08-29}
}
+@PROCEEDINGS{VdBCouJae2011a,
+ title = {The International Free and Open Source Software Law Book},
+ year = {2011},
+ shorttitle = {The International Free and Open Source Software Law Book, 2011},
+ editor = {Ywain {Van den Brande} and Shane Coughlan and Till Jaeger},
+ address = {Munich (Germany)},
+ publisher = {Open Source Press},
+ isbn = {978-3-941841-49-9},
+ annote = {Neben einer sehr kurzen Einführung enthält dieses Buch juristisch
+ oriwntierte Beschreibungen des Open Source Kontextes und der Open
+ Source Interpretation in verschiedenen europäischen Ländern.},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.22}
+}
+
@comment{jabref-meta: selector_publisher:}
@comment{jabref-meta: selector_author:}
View
206 bibfiles/oscResourcesEn.bib
@@ -1,4 +1,4 @@
-% This file was created with JabRef 2.6.
+% This file was created with JabRef 2.8.
% 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 = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.20}
+}
+
@MISC{AsfApacheLicense20a,
author = {{Apache Software Foundation}},
title = {Apache License, Version 2.0},
@@ -690,6 +713,24 @@ @ARTICLE{Babcock2006a
timestamp = {2012.03.09}
}
+@BOOK{Berry2008a,
+ author = {David M. Berry},
+ title = {Copy, Rip, Burn},
+ address = {London},
+ year = {2008},
+ shorttitle = {Copy, Rip, Burn, 2008a},
+ titleaddon = {The Politics of Copyleft and Open Source},
+ publisher = {Pluto Press},
+ isbn = {978-0-7453-2414-2},
+ annote = {This sociological book contains at least some remarks on the open
+ source history - focusing on the internal 'battles' ('from software
+ to open source?') and its discources ('the contestation of code').},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.28}
+}
+
@BOOK{Booth2010a,
author = {David R. Booth},
title = {Peer Production and Software. What Mozilla Has To Teach Government},
@@ -895,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},
@@ -980,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},
@@ -1075,6 +1154,28 @@ @BOOK{JaeMet2002a
timestamp = {2011.07.27}
}
+@BOOK{Kaes2008a,
+ author = {Simone Käs},
+ title = {Rethinking industry practice. The emergence of openness in the embedded
+ component industry},
+ address = {München},
+ year = {2008},
+ shorttitle = {Rethinking industry practice; The emergence of openness, 2008},
+ publisher = {Pro BUSINESS},
+ isbn = {978-3-86805-256-5},
+ annote = {This book analyzes the change to open software developement by interviewing
+ 'embedded-linux'-companies. The result is that openness is required
+ by the customers and that practicing openness evokes a process of
+ learning. The book offers a short but tellingly survey of OSS and
+ their licenses, although it doesn't offer a systematical review of
+ the obligations established by the different licenses.},
+ comment = {FaM Bibliothek Recht und Wirtschaft 05/QP 210 K11},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2011.08.01}
+}
+
@BOOK{Kersken2009a,
author = {Sasche Kersken},
title = {Apache 2.2. Das umfassende Handbuch},
@@ -1136,28 +1237,6 @@ @BOOK{Kugler2005a
timestamp = {2011.08.04}
}
-@BOOK{Kaes2008a,
- author = {Simone Käs},
- title = {Rethinking industry practice. The emergence of openness in the embedded
- component industry},
- address = {München},
- year = {2008},
- shorttitle = {Rethinking industry practice; The emergence of openness, 2008},
- publisher = {Pro BUSINESS},
- isbn = {978-3-86805-256-5},
- annote = {This book analyzes the change to open software developement by interviewing
- 'embedded-linux'-companies. The result is that openness is required
- by the customers and that practicing openness evokes a process of
- learning. The book offers a short but tellingly survey of OSS and
- their licenses, although it doesn't offer a systematical review of
- the obligations established by the different licenses.},
- comment = {FaM Bibliothek Recht und Wirtschaft 05/QP 210 K11},
- language = {english},
- note = {Print},
- owner = {reincke},
- timestamp = {2011.08.01}
-}
-
@ARTICLE{McAllister2003a,
author = {Neil McAllister},
title = {Licence to Profit [. Hybrid Open Source Licensing]},
@@ -1265,6 +1344,70 @@ @BOOK{Oberhem2008a
timestamp = {2011.08.01}
}
+@MISC{OSI2012a,
+ author = {{Open Source Initiative}},
+ title = {The Open Source Definition},
+ year = {2012 [Year n.st]},
+ shorttitle = {The Open Source Definition, 2012},
+ annote = {This page lists the ten rules which together specify under which
+ conditions a specific license can be classified as Open Source license.
+ It presents the Open Source Definition. So, a piece of software is
+ only then Open Source Software, if its license has been approved
+ as an Open Source License by the Open Source Initiative.},
+ language = {english},
+ note = {FreeWeb},
+ owner = {reincke},
+ timestamp = {2012.06.21},
+ url = {http://www.opensource.org/docs/osd},
+ urldate = {2012-06-21}
+}
+
+@MISC{BsdLicense2Clause,
+ author = {{Open Source Initiative}},
+ title = {The BSD 2-Clause License},
+ year = {2012 [Year n.st.]},
+ shorttitle = {The BSD 2-Clause License, 2012},
+ annote = {The latest current BSD license, known as 2 clause BSD license.},
+ language = {english},
+ note = {FreeWeb/HTML},
+ owner = {reincke},
+ timestamp = {2012.07.03},
+ url = {http://www.opensource.org/licenses/BSD-2-Clause},
+ urldate = {2012-07-03}
+}
+
+@MISC{BsdLicense3Clause,
+ author = {{Open Source Initiative}},
+ title = {The BSD 3-Clause License},
+ year = {2012 [Year n.st.]},
+ shorttitle = {The BSD 3-Clause License, 2012},
+ annote = {The elder BSD license, known as 3 clause BSD license.},
+ language = {english},
+ note = {FreeWeb/HTML},
+ owner = {reincke},
+ timestamp = {2012.07.03},
+ url = {http://www.opensource.org/licenses/BSD-3-Clause},
+ urldate = {2012-07-04}
+}
+
+@BOOK{Phillips2009a,
+ author = {Douglas E. Phillips},
+ title = {The Software License Unveiled. How Legislation by License Controls
+ Software Access},
+ address = {Oxford, New York, Auckland [etc. ...]},
+ year = {2009},
+ shorttitle = {The Software License Unveiled, 2009},
+ publisher = {Oxford University Press},
+ isbn = {978-0-19-534187-4},
+ annote = {This book contrasts the proprietary licenses and their Free and/or
+ Open Source alternatives. The conclusion is daring: Proprietary software
+ is described as being focused on the usability (and disregarding
+ the rights of the user), Open Source Software as being focused on
+ the developer (and neglecting the usability).},
+ owner = {reincke},
+ timestamp = {2012.02.28}
+}
+
@BOOK{RenVetRexKet2005a,
author = {Thomas Renner and Michael Vetter and Sascha Rex and Holger Kett},
title = {Open Source Software. Einsatzpotentiale und Wirtschaftlichkeit},
@@ -1639,6 +1782,23 @@ @PROCEEDINGS{GehLut2004a
urldate = {2011-08-29}
}
+@PROCEEDINGS{VdBCouJae2011a,
+ title = {The International Free and Open Source Software Law Book},
+ year = {2011},
+ shorttitle = {The International Free and Open Source Software Law Book, 2011},
+ editor = {Ywain {Van den Brande} and Shane Coughlan and Till Jaeger},
+ address = {Munich (Germany)},
+ publisher = {Open Source Press},
+ isbn = {978-3-941841-49-9},
+ annote = {Beside a very short historical introduction this book contains legal
+ descriptions of the Open Source context and interpretation in different
+ European countries.},
+ language = {english},
+ note = {Print},
+ owner = {reincke},
+ timestamp = {2012.02.22}
+}
+
@comment{jabref-meta: selector_publisher:}
@comment{jabref-meta: selector_author:}
View
3  btexmat/oscHyphenationEnInc.tex
@@ -20,4 +20,5 @@
%
-\hyphenation{ rein-cke }
+\hyphenation{rein-cke}
+
View
3  btexmat/oscNclAbbreviationsEnInc.tex
@@ -28,4 +28,5 @@
Software}
\abbr[lc]{l.c.}{loco citato = latin for 'in the place cited'}
\abbr[np]{np.}{no page numbering}
-\abbr[wp]{wp.}{webpage / webdocument without any internal (page)numbering}
+\abbr[wp]{wp.}{webpage / webdocument without any internal (page)numbering}
+\abbr[nst]{n.st.}{not stated}
View
3  btexmat/oscNclJournalsInc.tex
@@ -77,4 +77,7 @@
\abbr[sigbul]{SIGCSE Bulletin}{SIGCSE Bulletin [ISSN: 0097-8418]}
\abbr[ubiquity]{Ubiquity}{Ubiquity - The ACM IT Magazine and Forum [ISSN:
1530-2180]}
+\abbr[bwv]{BWV}{Berliner Wissenschafts-Verlag GmbH}
+\abbr[cr]{CR}{Computer und Recht. Zeitschrift für die Praxis des Rechts der
+Informationstechnologien}
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
15 oslic-en.tex
@@ -102,6 +102,10 @@
% - additional packages
\usepackage{amssymb}
+\usepackage{wasysym}
+\usepackage{pstricks, pst-node, pst-tree}
+\usepackage{chngcntr}
+\counterwithout{footnote}{chapter}
\usepackage[intoc]{nomencl}
\let\abbr\nomenclature
@@ -131,8 +135,7 @@
and OS Experts}
\title{Open Source License Compendium}
\subtitle{How to to Use Open Source Software in a Regular Manner}
-\author{K. Reincke, J. Dobson, G. Sharpe, P. Schichl,
- M. Kern\input{btexmat/oscLicenseFootnoteInc}}
+\author{K. Reincke, J. Dobson, G. Sharpe, M. Kern\input{btexmat/oscLicenseFootnoteInc}}
\maketitle
%%-- end(titlepage)
@@ -150,6 +153,7 @@
\begin{flushright}
Eitan Adler,\\
Thomas Quiehl,\\
+Peter Schichl,\\
Helene Tamer,\\
and all the \\
other\ldots
@@ -213,12 +217,13 @@ \chapter{Open Source: Important Minor Points}
\input{snippets/en/05-osImportantMinorPoints/0505-oslicAndPatents}
%%%%%%%%%%%%%%%
-\chapter{Open Source: Use Cases As Principle of Classification}
+\chapter{Open Source Use Cases: Concept and Taxonomy}
\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}
+\chapter{Open Source Use Cases: Find the License Fulfilling To-do Lists}
\input{snippets/en/07-osToDoListFinder/0700-chapterAbstractInc}
\input{snippets/en/07-osToDoListFinder/0701-chapterStartInc}
@@ -257,7 +262,7 @@ \chapter{Appendices}
\input{btexmat/oscNclJournalsInc}
\printnomenclature
-\bibliography{bibfiles/oscResourcesDe}
+\bibliography{bibfiles/oscResourcesEn}
\end{document}
View
2  release.tex
@@ -1 +1 @@
-0.2.1
+0.4.0
View
8 snippets/en/06-osUseCases/0600-chapterAbstractInc.tex
@@ -24,8 +24,12 @@
\footnotesize
\begin{quote}\itshape
-This chapter offers our taxonomie of use cases which lateron will structure each
-license specific chapter.
+This chapter establishes our concept of \emph{Open Source Use Cases} as a
+classification system for to-do lists. The conditions of a specific license, in
+the context of a par\-ti\-cu\-lar \emph{Open Source Use Case}, will be fulfilled
+by following the corresponding to-do list. Additionally this chapter introduces a
+taxonomy for these \emph{Open Source Use Cases}. Later on, this taxonomy will
+organize the \emph{Open Sourse Use Case Finder}.
\end{quote}
\normalsize{}
View
161 snippets/en/06-osUseCases/0601-chapterStartInc.tex
@@ -23,6 +23,165 @@
%% use all entries of the bibliography
%\nocite{*}
-[TDB \ldots]
+%[todo: \ldots (insert all contexts concerning the idea of use cases)]
+
+After all these introductory remarks, we can summarize our idea. We know that
+the right to use Open Source Software depends on the tasks required by the Open
+Source Licenses. As opposed to commercial licenses, you can not buy the right to
+use a piece of Open Source Software using money. It is embedded into the Open
+Source Definition that the right to use the software may not be sold. The OSD
+states firstly that an Open Source License may \glqq{}[\ldots] not restrict any
+party from selling or giving away the software as a component of (any) aggregate
+software distribution\grqq{}, and adds secondly in the same context that an Open
+Source License \glqq{}[\ldots] shall not require a royalty or other fee for such
+sale\grqq{}\footcite[cf.][\nopage wp. §1]{OSI2012a}.
+
+However, it would be wrong to conclude that you are automatically allowed to use
+Open Source Software without any service in return: generally you have to do
+something to gain the right to use the software. In other words: Open Source
+Software is covered by the idea of ’paying by doing’. As such, Open Source
+Li\-cen\-ses describe specific circumstances under which the user must execute
+some tasks in order to be compliant with the licenses. So, if we want to offer
+to-do lists for fulfilling license conditions, we must consider these tasks and
+circumstances.
+
+In practice, such circumstances are not linear and simple. They contain
+combinations of (sometimes context sensitive) conditions, which can be grouped
+together into classes of tokens. Such a class of tokens might denote a feature
+of the software itself - such as being an application or a library. Or it can
+refer to the circumstances of using the software, such as 'using the software
+only for yourself' or 'distributing the software also to third parties'.
+
+At the end, we want to determine a set of specific OSUCs - the \emph{Open Source
+Use Cases}. And we want to deliver for each of these OSUCs and for each of the
+considered Open Source Licenses one list of actions, which fulfills the license
+in that context\footnote{Fortunately, sometimes one task list fulfills the
+conditions of more than one use case - a welcome reduction of complexity}.
+
+Such an \emph{Open Source Use Case} shall be considered as a set of tokens
+describing the circumstances of a specific usage. Hence, to begin, we must
+specify the relevant classes of tokens, before we can determine the valid
+combinations of these tokens - our \emph{Open Source Use Cases}. Finally, based
+on the tokens, we generate a taxonomy in form of a tree. This tree will become
+the base of the \emph{Open Source Use Case Finder} which will be offered by the
+next chapter, and which leads you to your specific OSUC by evaluating just a few
+questions and answers.
+
+There are only a handful of tokens which are relevant to the circumstances of
+Open Source Software Licenses:
+
+\label{OsucTokens}
+\begin{itemize}
+ \item The \textbf{\underline{type} of the Open Source Software}: On one hand
+ there are code snippets, modules, libraries and plugins, and on the other
+ hand, autonomous applications, programs and servers. We’ll coin the word
+ ’snimolis’ for the first set, and ’proapses’ for the second. This is
+ necessary, as we are not only talking about libraries and applications in the
+ everyday sense, but rather in the broadest sense\footnote{Of course, our newly
+ introduced concepts 'snimoli' and 'proapse' are not absolutely one of the most
+ elegant words. So, initially we tried to talk about 'applications' and
+ 'libraries', although in our context these words should denote more, than they
+ traditionally do. But we couldn't minimize the irritations of our
+ interlocutors. Too often we had to amend that we were not only talking about
+ applications and libraries in the strict sense of the words. Finally we
+ decided to find our own words - and to stay open for better proposals ;-) }.
+ More specifially, we will ask you, whether the Open Source Software, you
+ want to use, is an includable code snippet, a linkable module or library, or a
+ loadable plugin, or whether it is an autonomous application or server which
+ can be executed or processed. In the first case, the answer should be 'it's a
+ \underline{snimoli}', in the second 'it's a \underline{proapse}'.
+
+ \item The \textbf{\underline{state} of the of the Open Source Software}: It
+ might be used, as one has got it. Or it can be modified, before being used.
+ More specifially, we will ask you, whether you want to leave the Open Source
+ Software as you have got it, or whether you want to modify it before using
+ and/or distributing it to 3rd parties. In the first case, the answer should be
+ '\underline{unmodified}', in the second '\underline{modified}'.
+
+ \item The \textbf{usage \underline{context} of the of the Open Source
+ Software}: On the hand you might use the received Open Source Software as a
+ readily prepared application. On the other hand you might embed the received
+ Open Source into a larger application as one of its' components. More
+ specifially, we will ask you, whether you are you using the Open Source
+ Software as an autonomous piece of software, or whether you are using it as an
+ embbeded part of a larger, more complex piece of software. In the first case,
+ the answer should be '\underline{independent}', in the second
+ '\underline{embedded}'.
+
+ \item The \textbf{\underline{recipient} of the of the Open Source Software}:
+ Sometimes you might wish to use the received Open Source Software only for
+ yourself. In other cases you might intend to hand over the software (also) to
+ other people. More specifially, we will ask you, whether you are going to use
+ the Open Source Software only for yourself, or whether you plan to
+ (re)distribute it (also) to third parties. In the first case, the answer
+ should be '\underline{4yourself}', in the second '\underline{4others}'.
+
+ \item The \textbf{\underline{mode} of combination}: In this case, we will ask
+ you, whether you are going to combine or to embed the Open Source Software
+ with other software components by linking them statically, by linking them
+ dynamically, or by textually including (parts of) the Open Source Software
+ into your larger product. In the first case, the answer should be
+ '\underline{statically linked}', in the second '\underline{dynamically
+ linked}', in the third '\underline{textually included}'
+
+\end{itemize}
+
+From a more programmatic point-of-view, we can summarise these tokens as follows:
+
+\begin{itemize}
+ \item \texttt{type::snimoli} \emph{or} \texttt{type::proapse}
+ \item \texttt{state::unmodified} \emph{or} \texttt{state::modified}
+ \item \texttt{context::independent} \emph{or} \texttt{context::embedded}
+ \item \texttt{recipient::4yourself} \emph{or} \texttt{ecipient::4others}
+ \item \texttt{mode::statically-linked} \emph{or} \texttt{mode::dynamically-linked}
+ \emph{or} \\ \texttt{mode::textually-included}
+\end{itemize}
+
+We already defined an Open Source Use Case as a combination of these tokens. If
+we simply combine all these tokens of all these classes with all the tokens of
+the other classes\footnote{in the sense of the cross product TYPE $\times$ STATE
+$\times$ CONTEXT $\times$ RECIPIENT $\times$ MODE}, we get 2*2*2*2*3 = 48 sets
+of tokens - or 48 \emph{Open Source Use Cases}. Fortunately, some of the
+generated sets are invalid from an empirical or logical view, and some of these
+sets are context sensitive:
+
+\begin{enumerate}
+
+ \item \label{InvalidFinderTokenCombinations}It makes no sense to ask you
+ whether you are going to combine the received software with other software
+ components by linking them statically or dynamically, or by including it
+ textually into a larger unit, if you already have answered, that the received
+ Open Source Software is a \emph{proapse} or that it shall be used
+ \emph{independently}: A readily prepared application or server can't be linked
+ to another application or server, which also contains a
+ \texttt{main}-function. And using a \emph{proapse} or \emph{snimoli}
+ \emph{independently} includes that it is used \emph{not in combination} with
+ other units, simply because they are tokens of the same class.
+
+ \item If you already have specified that the used Open Source Software is a
+ \emph{proapse} - hence an autonomous program, an application, or a server -,
+ then your answer includes, that the software is used independently and is not
+ embedded with other components into a larger unit - simply because of the
+ nature of all \emph{proapses}. But if you have specified that the used Open
+ Source Software is a \emph{snimoli} - hence a snippet of code, a module, a
+ plugin, or a library -, then it can indeed be used as an embedded component of
+ a constructed larger application or server, or it can be used independently in
+ case you 'only' re-distribute it to 3rd parties.
+
+ \item If you already have specified that the used Open Source Software is a
+ \emph{snimoli} - hence a snippet of code, a module, a plugin, or a library -,
+ and that this \emph{snimoli} shall be used only by yourself (not distributed
+ to other 3rd. parties), then your answer must also imply that this
+ \emph{snimoli} is used in combination, as an embedded part of a larger unit.
+ It makes no sense to 'try' to use a library autonomously, without using it
+ as component of another application. In this case, it would simply sit on the
+ disk and would do nothing more than occupying space.
+
+\end{enumerate}
+
+Does this sound complex? We thought so too. We spent much
+time explaining these constraints to ourselves, and only when we had transposed
+all the combinations and rules into a tree, did the situation become clearer.
+The following diagrams shall summarise this way of clarification:
%\bibliography{../../../bibfiles/oscResourcesEn}
View
311 snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc.tex
@@ -0,0 +1,311 @@
+% 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{*}
+
+
+\section{The OS Use Case Dimensions: Classes and Tokens}
+
+
+\begin{footnotesize}
+
+\pstree[treemode=R, levelsep=*0.2, treesep=0.6]{\Toval{tokens}}{
+ \pstree[]{\Tr{\fbox{type?}}}{
+ \Toval{proapse}
+ \Toval{snimoli}
+ }
+ \pstree[]{\Tr{\fbox{state?}}}{
+ \Toval{unmodified}
+ \Toval{modified}
+ }
+ \pstree[]{\Tr{\fbox{context?}}}{
+ \Toval{independent}
+ \pstree[]{\Toval{embedded}}{
+ \pstree[]{\Tr{\fbox{mode?}}}{
+ \Toval{statically linked}
+ \Toval{dynamically linked}
+ \Toval{textually included}
+ }
+ }
+ }
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+ \Toval{4yourself}
+ \Toval{4others}
+ }
+ }
+
+\end{footnotesize}
+
+
+\section{The OS Use Case Taxonomy}
+
+This is one tree, 'collecting' the tokens and offering the \emph{Open Source Use
+Cases} as their leafs\footnote{ Each of the invalid use cases (= sets of tokens)
+[for details s. p. \pageref{InvalidFinderTokenCombinations}] is marked by an
+\lightning{} and leads to an empty set (= $\varnothing$): A proapse can not be
+embedded with another software unit, also containing a main-function. Using
+a software library only for yourself and independent (not in combination with larger
+software unit), is like having an unused heap of bytes on your disc.}:
+
+\label{OsucDefinitionTree}
+\begin{tiny}
+\pstree[treemode=R,levelsep=*0.2, treesep=0.2]{\Toval{OSS}}{
+ \pstree[]{\Tr{\fbox{type?}}}{
+ \pstree[]{\Tr{\parbox{4em}{\texttt{\{\underline{proapse}\}}}}}{
+ \pstree[]{\Tr{\fbox{state?}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}\underline{unmodified}\}}}}}{
+ \pstree[]{\Tr{\fbox{context?}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}\underline{independent}\}}}}}{
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+
+ \pstree[]{\Toval{\bfseries{OSUC-01}}}{
+
+ \Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4yourself}\}}}}
+ }
+ \pstree[]{\Toval{\bfseries{OSUC-02}}}{
+
+ \Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4others}\}}}}
+ }
+ }
+ }
+ \pstree[]{\Tr{\parbox{5.4em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}\underline{embedded}
+ \bfseries{\lightning}\}}}}}{
+ \Tr{$\varnothing$}
+ }
+ }
+ }
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}\underline{modified}\}}}}}{
+ \pstree[]{\Tr{\fbox{context?}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}\underline{independent}\}}}}}{
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+ \pstree[]{\Toval{\bfseries{OSUC-03}}}{
+ \Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4yourself}\}}}}
+ }
+ \pstree[]{\Toval{\bfseries{OSUC-04}}}{
+ \Tr{\parbox{5.2em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4others}\}}}}
+ }
+ }
+ }
+ \pstree[]{\Tr{\parbox{5.4em}{
+ \texttt{\{proapse,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}\underline{embedded}
+ \bfseries{\lightning}\}}}}}{
+ \Tr{$\varnothing$}
+ }
+ }
+ }
+ }
+ }
+ \pstree[]{\Tr{\parbox{4em}{\texttt{\{\underline{snimoli}\}}}}}{
+ \pstree[]{\Tr{\fbox{state?}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}\underline{unmodified}\}}}}}{
+ \pstree[]{\Tr{\fbox{context?}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}\underline{independent}\}}}}}{
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+ \pstree[]{
+ \Tr{\parbox{5.8em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4yourself}
+ \bfseries{\lightning}\}}}}
+ }{\Tr{$\varnothing$}}
+
+
+ \pstree[]{\Toval{\bfseries{OSUC-05}}}{
+ \Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4others}\}}}}
+ }
+ }
+ }
+
+
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}\underline{embedded}\}}}}}{
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+ \pstree[]{\Toval{\bfseries{OSUC-06}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}embedded,\\
+ \hspace*{0.5em}\underline{4yourself}\}}}}}{
+ \pstree[]{\Tr{\fbox{$\cup$ mode?}}}{
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-06a}}\\
+ \texttt{\{statically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-06b}}\\
+ \texttt{\{dynamically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-06c}}\\
+ \texttt{\{textually\\
+ \hspace*{0.5em}included\}}}}
+ }
+ }
+ }
+ \pstree[]{\Toval{\bfseries{OSUC-07}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}unmodified,\\
+ \hspace*{0.5em}embedded,\\
+ \hspace*{0.5em}\underline{4others}\}}}}}{
+ \pstree[]{\Tr{\fbox{$\cup$ mode?}}}{
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-07a}}\\
+ \texttt{\{statically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.26em}{\underline{\textit{OSUC-07b}}\\
+ \texttt{\{dynamically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-07c}}\\
+ \texttt{\{textually\\
+ \hspace*{0.5em}included\}}}}
+ }
+ }
+ }
+ }
+ }
+
+
+ }
+ }
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}\underline{modified}\}}}}}{
+ \pstree[]{\Tr{\fbox{context?}}}{
+
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}\underline{independent}\}}}}}{
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+ \pstree[]{
+ \Tr{\parbox{5.8em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4yourself}
+ \bfseries{\lightning}\}}}}
+ }{\Tr{$\varnothing$}}
+
+ \pstree[]{\Toval{\bfseries{OSUC-08}}}{
+ \Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}independent,\\
+ \hspace*{0.5em}\underline{4others}\}}}}
+ }
+ }
+ }
+
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}\underline{embedded}\}}}}}{
+ \pstree[]{\Tr{\fbox{recipient?}}}{
+ \pstree[]{\Toval{\bfseries{OSUC-09}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}embedded,\\
+ \hspace*{0.5em}\underline{4yourself}\}}}}}{
+ \pstree[]{\Tr{\fbox{$\cup$ mode?}}}{
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-09a}}\\
+ \texttt{\{statically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-09b}}\\
+ \texttt{\{dynamically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-09c}}\\
+ \texttt{\{textually\\
+ \hspace*{0.5em}included\}}}}
+ }
+ }
+ }
+ \pstree[]{\Toval{\bfseries{OSUC-10}}}{
+ \pstree[]{\Tr{\parbox{5.2em}{
+ \texttt{\{snimoli,\\
+ \hspace*{0.5em}modified,\\
+ \hspace*{0.5em}embedded,\\
+ \hspace*{0.5em}\underline{4others}\}}}}}{
+ \pstree[]{\Tr{\fbox{$\cup$ mode?}}}{
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-10a}}\\
+ \texttt{\{statically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-10b}}\\
+ \texttt{\{dynamically\\
+ \hspace*{0.5em}linked\}}}}
+ \Tr{\parbox{5.2em}{\underline{\textit{OSUC-10c}}\\
+ \texttt{\{textually\\
+ \hspace*{0.5em}included\}}}}
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+\end{tiny}
+%\bibliography{../../../bibfiles/oscResourcesEn}
View
8 snippets/en/07-osToDoListFinder/0700-chapterAbstractInc.tex
@@ -24,8 +24,12 @@
\footnotesize
\begin{quote}\itshape
-This chapter shall offer the finder in form of a process / deciding chart based
-on leading questions. The main part should be a simple picture!
+This chapter offers the \emph{Open Source Use Case Finder}: Firstly, it presents
+a form to gather the specifying information. Secondly it offers a tree, which
+can easily be transversed by the gathered information. And finally it contains
+the list of \emph{Open Source Use Cases}. Each leaf of the tree leads to one
+\emph{Open Source Use Case} which itself then refers to the specific license
+fulfilling to-do lists.
\end{quote}
\normalsize{}
View
515 snippets/en/07-osToDoListFinder/0701-chapterStartInc.tex
@@ -23,6 +23,519 @@
%% use all entries of the bibliography
%\nocite{*}
-[TDB \ldots]
+\section{A standard form for gathering the relevant information}
+
+\begin{small}
+\begin{tabular}[h]{|l|l|l|l|}
+\hline
+Class & Questions & Answers\\
+\hline
+ Type
+ & \parbox[c][2.6cm][c]{9.4cm}{
+ \textit{Is the Open Source Software you want to use a software library
+ in the broadest sense (an includable code snippet, a linkable module or
+ library, or a loadable plugin) [=snimoli], or is it an autonomous
+ program, application or server which can be executed or processed
+ [=proapse]?}} & \parbox{10em}{
+ $\square$\hspace{1em}proapse\\
+ $\square$\hspace{1em}snimoli}
+ \\
+\hline
+ State &
+ \parbox[c][1.6cm][c]{9.4cm}{
+ \textit{Do you want to leave your Open Source Software as you have
+ got it, or do you want to modify it before using and/or distributing it to 3rd
+ parties?}} &
+ \parbox{10em}{
+ $\square$\hspace{1em}unmodified\\
+ $\square$\hspace{1em}modified} \\
+\hline
+ Context &
+ \parbox[c][2cm][c]{9.4cm}{
+ \textit{Are you using your Open Source Software as an au\-to\-no\-mous piece
+ of software [=independent], or are you using it as an embedded part or component
+ of a larger, more complex piece of software [=embedded]?}} &
+ \parbox{10em}{ $\square$\hspace{1em}independent\\
+ $\square$\hspace{1em}embedded}\\
+\hline
+ Recipient &
+ \parbox[c][1.6cm][c]{9.4cm}{
+ \textit{Are you are going to use the received Open Source Software only for
+ yourself [=4yourself], or do you plan to (re)distribute it (also) to third
+ parties [=4others]?}}
+ & \parbox{10em}{
+ $\square$\hspace{1em}4yourself\\
+ $\square$\hspace{1em}4others}\\
+\hline
+ Mode &
+ \parbox[c][2.6cm][c]{9.4cm}{
+ \textit{Are you going to combine the received Open Source Software with other
+ software components by linking all together statically, by linking them
+ dynamically, or by textually including (parts of) the Open Source Software
+ into your larger unit?}} &
+ \parbox{10em}{
+ $\square$\hspace{1em}statically linked\\
+ $\square$\hspace{1em}dynamically linked\\
+ $\square$\hspace{1em}textually included}\\
+\hline
+\hline
+\end{tabular}
+\end{small}
+
+As discussed earlier, there are of course some invalid
+combinations\footnote{type::proapse excludes state::embedded;
+recipient::4yourself excludes the combination with state::independent and
+type::snimoli; any value of class 'mode' implies state::embedded [for details
+see page \pageref{InvalidFinderTokenCombinations}]. If you have gathered one of
+these invalid combinations, please check the corresponding explanations}. Here
+are some extra explanations about each class:
+
+\begin{description}
+\item[Type:] A piece of (Open Source) Software shall be viewed as a program, an
+application, or a server, if you can start its binary form with your normal
+program launcher, or (in case of an text file which still must be interpreted by
+an interpreter like php, perl, bash etc.) if you can start an interpreter taking
+the file as one of its' arguments. \item[State:] You modify Open Source Software
+if you expand, reduce or modify at least one of the received software files, and
+- in case of dealing woth binary object code - if you (re)compile and (re)link
+the modified software to a new binary file. If you only modify configuration
+files, you do not modify the Open Source Software.
+\item[Context:] You use Open Source Software embedded into a larger unit, if one
+of your files of the larger unit contains a verbatim or modified copy (i.e. a
+snippet) of the received Open Source Software, or if the larger unit contains an
+include statement referring to a file of the received Open Source Software, or
+if your development environment contains a compiler or linker directive
+referring to the received Open Source Software.
+\item[Recipient] You use the received Open Source Software only for yourself, if
+you as person do not pass it to other persons, or if you as a member of a
+specific development group pass it only to the other members of your
+development group. But if you store Open Source Software on any device such as a
+mobile phone, an USB stick, etc. or if you attach it to any transport
+medium like email etc. and if you then sell, give away, or simply send this
+device or transport medium to anyone (other than a direct member
+of your development group), then you indeed handover the Open Source Software to
+third parties\footnote{Please remember that - at least in Germany - there are
+opinions that even handing over software to another legal enity or department
+of the same company is also a kind of distribution. It is always safest
+to take the broadest possible meaning of distributing or handing over.}.
+\item[Mode] This follows the standard terminology of software development.
+this question.
+\end{description}
+
+\section{The taxonomic Open Source Use Case Finder}
+
+Now, after having gathered the necessary information, determine your specific
+Open Source Use Case by traversing the following tree and its corresponding
+branches:
+
+\begin{footnotesize}
+
+\pstree[treemode=R,levelsep=*0.2,treesep=0.2]{\Toval{OSS}}{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{type:\\\textbf{\textit{proapse}}\\
+ \tiny (= Program,\\\tiny Application,\\\tiny Server)
+ }
+ }}
+
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{state:\\\textbf{\textit{unmodified}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{independent}}}}}
+ }{
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4yourself}}}}}
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{6em}
+ $\Rightarrow$ OSUC-01\\
+ \textit{(see p. \pageref{OSUC-01-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4others}}}}}
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{6em}
+ $\Rightarrow$ OSUC-02\\
+ \textit{(see p. \pageref{OSUC-02-DEF})}\end{minipage} }
+ }
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{state:\\\textbf{\textit{modified}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{independent}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4yourself}}}}}
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{6em}
+ $\Rightarrow$ OSUC-03\\
+ \textit{(see p. \pageref{OSUC-03-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4others}}}}}
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{6em}
+ $\Rightarrow$ OSUC-04\\
+ \textit{(see p. \pageref{OSUC-04-DEF})}\end{minipage} }
+ }
+ }
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{
+ \shortstack{type:\\\textbf{\textit{snimoli}}\\
+ \tiny (= Snippet,\\\tiny Module,\\\tiny Plugin,\\\tiny Library)
+ }
+ }}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{state:\\\textbf{\textit{unmodified}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{independent}}}}}
+ }{
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4others}}}}}
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{6em}
+ $\Rightarrow$ OSUC-05\\
+ \textit{(see p. \pageref{OSUC-05-DEF})}\end{minipage} }
+ }
+
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{embedded}}}}}
+ }{
+ \pstree{
+ \Tr{
+ \Ovalbox{\shortstack{recipient:\\\textbf{\textit{4yourself}}}}
+ }
+ }{
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{statically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-06a\\
+ \textit{(see p. \pageref{OSUC-06-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{dynamically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-06b\\
+ \textit{(see p. \pageref{OSUC-06-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{textually included}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-06c\\
+ \textit{(see p. \pageref{OSUC-06-DEF})}\end{minipage} }
+ }
+
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4others}}}}}
+ }{
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{statically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-07a\\
+ \textit{(see p. \pageref{OSUC-07-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{dynamically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-07b\\
+ \textit{(see p. \pageref{OSUC-07-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{textually included}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-07c\\
+ \textit{(see p. \pageref{OSUC-07-DEF})}\end{minipage} }
+ }
+ }
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{state:\\\textbf{\textit{modified}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{independent}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4others}}}}}
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{6em}
+ $\Rightarrow$ OSUC-08\\
+ \textit{(see p. \pageref{OSUC-08-DEF})}\end{minipage} }
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{embedded}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4yourself}}}}}
+ }{
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{statically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-09a\\
+ \textit{(see p. \pageref{OSUC-09-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{dynamically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-09b\\
+ \textit{(see p. \pageref{OSUC-09-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{textually included}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-09c\\
+ \textit{(see p. \pageref{OSUC-09-DEF})}\end{minipage} }
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient:\\\textbf{\textit{4others}}}}}
+ }{
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{\tiny statically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-10a\\
+ \textit{(see p. \pageref{OSUC-10-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{dynamically linked}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-10b\\
+ \textit{(see p. \pageref{OSUC-10-DEF})}\end{minipage} }
+ }
+
+ \pstree{
+ \Tr{
+ \begin{tiny}
+ \Ovalbox{\shortstack{mode:\\\textit{textually included}}}
+ \end{tiny}
+ }
+ }{
+ \Tr[edge=none]{\begin{minipage}[b][2em][c]{7em}
+ $\Rightarrow$ OSUC-10c\\
+ \textit{(see p. \pageref{OSUC-10-DEF})}\end{minipage} }
+ }
+ }
+ }
+ }
+ }
+}
+\end{footnotesize}
+
+
+
+\section{The Open Source Use Cases and their links to the to-do lists}
+
+\begin{description}
+
+\item[OSUC-01:]\label{OSUC-01-DEF}
+Only for yourself, you are using an unmodified Open Source program, application,
+or server - just as you received it. You are not going to combine it with other
+components in the sense of software development (= \textit{proapse, unmodified,
+independent, 4yourself}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-01-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-01-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-01-GPL2X} for license \textbf{GPL 2.x}
+ \item p. \pageref{OSUC-01-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-02:]\label{OSUC-02-DEF} Just as you received it, you are going to
+distribute an unmodified Open Source program, application, or server to 3rd
+parties. In this act of distribution, you do not combine this program,
+application, or server with other software components in the sense of software
+development (= \textit{proapse, unmodified, independent, 4others}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-02-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-02-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-02-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-02-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-03:]\label{OSUC-03-DEF} Only for yourself, you are modifying a
+received Open Source program, application, or server, before you are using it.
+But you do not combine it with other components in the sense of software
+development (= \textit{proapse, modified, independent, 4yourself}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-03-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-03-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-03-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-03-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-04:]\label{OSUC-04-DEF} You are going to modify a received Open
+Source program, application, or server, before you distribute it to 3rd parties.
+But you do not combine this modified program, application, or server with other
+software components in the sense of software development (= \textit{proapse,
+modified, independent, 4others}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-04-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-04-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-04-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-04-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-05:]\label{OSUC-05-DEF} Just as you received it, you are going to
+distribute an unmodified Open Source library, code snippet, module, or plugin to
+3rd parties. In this act of distribution, you do not combine this library, code
+snippet, module, or plugin with other software components in the sense of
+software development (= \textit{snimoli, unmodified, independent, 4others}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-05-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-05-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-05-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-05-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-06:]\label{OSUC-06-DEF} Only for yourself and just as you received
+it, you are going to combine an unmodified Open Source library, code snippet,
+module, or plugin into a larger software unit as one of its parts. (=
+\textit{snimoli, unmodified, embedded, 4yourself}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-06-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-06-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-06-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-06-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-07:]\label{OSUC-07-DEF} Just as you received it and before you will
+distribute it to 3rd parties together with the larger software unit, you
+combine an unmodified Open Source library, code snippet, module, or plugin into
+a larger software unit in the sense of software development (= \textit{snimoli,
+unmodified, embedded, 4others}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-07-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-07-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-07-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-07-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-08:]\label{OSUC-08-DEF} Before you will distribute it, you are going
+to modify an Open Source library, code snippet, module, or plugin to 3rd
+parties, but you do not combine it with other software components in the sense of
+software development (= \textit{snimoli, modified, independent, 4others}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-08-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-08-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-08-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-08-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-09:]\label{OSUC-09-DEF} Only for yourself, you are going to modify an
+Open Source library, code snippet, module, or plugin, before you will combine it
+- in the sense of software development - into a larger software unit as one of
+its parts . (= \textit{snimoli, modified, embedded, 4yourself}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-09-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-09-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-09-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-09-MIT} for license \textbf{MIT}
+ \end{itemize}
+
+\item[OSUC-10:]\label{OSUC-10-DEF} Before you will distribute it to 3rd parties,
+you are going to modify an Open Source library, code snippet, module, or plugin,
+and to combine it with other software components in the sense of
+software development (= \textit{snimoli, modified, independent, 4others}).
+To see the \textit{specific, license fulfilling to-do lists} jump to the
+following pages:
+ \begin{itemize}
+ \item p. \pageref{OSUC-10-Apache20} for license \textbf{Apache 2.0}
+ \item p. \pageref{OSUC-10-BSD} for license \textbf{BSD}
+ \item p. \pageref{OSUC-10-GPL2X} for license \textbf{GPL}, release 2
+ \item p. \pageref{OSUC-10-MIT} for license \textbf{MIT}
+ \end{itemize}
+\end{description}
%\bibliography{../../../bibfiles/oscResourcesEn}
View
7 snippets/en/08-osFulfillmentByToDoLists/0800-chapterAbstractInc.tex
@@ -24,11 +24,10 @@
\footnotesize
\begin{quote}\itshape
-This chapter lists for the main Open Source Licenses and for the main use cases
-what one has to do for fulfilling a specific license. And it explains in which
-cases the combination with another Open Source License must be avoided. You
+With respect to the defined Open Source Use Cases, this chapter lists for the
+Open Source Licenses what one has to do for fulfilling a specific license. You
should be able to jump into the license specific chapter and find all relevant
-information - though without proving details,
+information - though without proving details.
\end{quote}
\normalsize{}
View
40 snippets/en/08-osFulfillmentByToDoLists/0802-apacheFulfillToDoList.tex
@@ -23,29 +23,23 @@
%% use all entries of the bibliography
%\nocite{*}
-\section{Apache Licensed Software in the usage context of \ldots}
-\subsection{Without Redistribution and \ldots}
-\subsubsection{As-It-Is-Usage}
-\ldots
-\subsubsection{With-Code-Modification}
-\ldots
-\subsubsection{As-Isolated-Initial-Development}
-\ldots
-\subsubsection{As-On-Top-Development}
-\ldots
-
-\subsection{With Redistribution and \ldots}
-\subsubsection{As-It-Is-Usage}
-\ldots
-\subsubsection{With-Code-Modification}
-\ldots
-\subsubsection{As-Isolated-Initial-Development}
-\ldots
-\subsubsection{As-On-Top-Development}
-\ldots
-
-\section{etc.}
-\ldots
+\section{Apache Licensed Software \ldots}
+
+\label{OSUC-01-Apache20} \label{OSUC-03-Apache20}
+\label{OSUC-06-Apache20} \label{OSUC-09-Apache20}
+