Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

2012-07-05: committing release 0.4.0 which contains

- the defintion of the Open Source Use Case tokens
- the defintion of the Open Source Use Cases themselves
- the corresponding taxonomy
- the finder based on this general OSUC taxonomy
- the corresponding BSD to-do list
  • Loading branch information...
commit 30d71b12b12206a3eb2624352c1c118d6586bd2a 1 parent 832bc5d
Karsten Reincke authored
8 CHANGES
View
@@ -1,3 +1,11 @@
+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
30 bibfiles/oscResourcesDe.bib
View
@@ -1350,6 +1350,36 @@ @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},
28 bibfiles/oscResourcesEn.bib
View
@@ -1362,6 +1362,34 @@ @MISC{OSI2012a
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
3  btexmat/oscHyphenationEnInc.tex
View
@@ -20,4 +20,5 @@
%
-\hyphenation{ rein-cke }
+\hyphenation{rein-cke}
+
2  release.tex
View
@@ -1 +1 @@
-0.3.90
+0.4.0
11 snippets/en/06-osUseCases/0600-chapterAbstractInc.tex
View
@@ -24,11 +24,12 @@
\footnotesize
\begin{quote}\itshape
-This chapter establishes the concept of Open Source Use Cases
-as a sorting system for to-do lists, which fulfill specific licenses in the
-context of such an Open Source Use Case. Additionally it introduces a taxonomy
-for these Open Source Use Cases whose structure later on will organize the Open
-Sourse Use Case Finder.
+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{}
159 snippets/en/06-osUseCases/0601-chapterStartInc.tex
View
@@ -25,4 +25,163 @@
%[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}
249 snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc.tex
View
@@ -23,157 +23,11 @@
%% use all entries of the bibliography
%\nocite{*}
-After all these introducing remarks let us summarize the center of our idea: We
-know that the right to use Open Source Software depends on the doings required
-by the corresponding Open Source Licenses. In opposite to the commercial
-licenses, you can not buy the right to use a piece of Open Source software.
-Never! 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}.
-But nevertheless, it is not adequate to derive from this statement that you are
-automatically allowed to use Open Source Software without any service in return:
-generally you have to do something for getting the right to use the software. In
-other words: Open Source Software is specified by the idea of 'paying by doing'.
-
-Therefore these Open Source Licenses describe specific circumstances under
-which the user must execute some tasks. Such circumstances are often sets of
-conditions and may be viewed as triggers for a compliant behaviour. So, if we
-want to offer license fulfilling to-do lists, we have to consider these triggers.
-
-The real challenge is, that such circumstances are not linear and simple. They
-contain combinations of (sometimes) context sensitive conditions. These
-conditions refer to different class of tokens. Such a class of token might
-denote a feature of the software itself - like being an application or a
-library. Or it might denote the circumstances of using the software - like
-'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 - 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 fulfill the license
-in the context of this use case. In our discussion, such an \textit{Open Source
-Use Case} shall be a set of tokens describing the circumstances of a specific
-usage. So, in the beginning we have to specify the relevant classes of tokens.
-Then we build the valid combinations of tokens, our Open Source Use Cases. And
-finally - based on the specifying tokens - we generate a taxonomy. In the
-next chapter this taxonomy will become the base of the Open Source Use Case
-Finder which leads you to your specific OSUC by only a few questions and
-answers.
-
-In other words: this chapter defines the relevant tokens and derives the
-conceptual structures. The following chapter will use the results of this
-chapter - but without deeper discussions.
-
-So, let's now start with the classes of tokens by which the circumstances of
-using a piece of Open Source Software can be specified:
-
-\begin{itemize}
- \item Firstly we will consider the \textbf{type of the Open Source Software}.
- We will distinguish between code snippets, modules, libraries or plugins on
- the one hand, and autonomous, processable applications, programs or servers on
- the other hand. Let's name the first set the 'snimolis' and the second the
- 'proapses' for indicating, that we are not only talking about libraries or
- applications in the well known 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 'librabries',
- 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
- librabries in the strict sense of the words, but about clusters of similar
- entities. Finally we decided to generate our own words. Naturally, each
- improving proposal is welcome ;-) }. More detailedly spoken, we will ask you,
- whether the Open Source Software, you want to use, is a software library in
- the broadest sense (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 snimoli', in the second 'it's a proapse'.
- \item Secondly we will consider the \textbf{state of the of the Open Source
- Software}: It might be used, as one has got it. Or one can modify it, before
- using it. More detailedly spoken, we will ask you, whether you want to leave
- the evaluated 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 'unmodified', in the second 'modified'.
- \item Thirdly we will consider the \textbf{usage context of the of the Open
- Source Software}: On the hand you might use the received Open Source Software
- as one of your readily constructed applications. On the other hand you might
- construct a larger application based upon the received Open Source, because it
- is using it as one of its' components. More detailedly spoken, we will ask
- you, whether you are you using the evaluated Open Source Software as an
- autonomous piece of software, or whether you are using it in combination
- with other components for setting up a larger, more complex piece of software.
- \item Fourthly we will consider the \textbf{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 detailedly spoken, we will
- ask you, whether you are going to use the evaluated Open Source Software only
- for yourself, or whether you plan to (re)distribute it (also) to third
- parties,
- \item Fifthly and finally we will consider the \textbf{combining mode of the
- of the Open Source Software usage}: In this case, we will ask you, whether you
- are going to combine the evaluated 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.
-\end{itemize}
-
-In the beginning we defined an \emph{Open Source Use Case} as a set of
-classified tokens. No we have the following classified tokens:
-\begin{itemize}
- \item \texttt{type::snimoli} or \texttt{type::proapse}
- \item \texttt{state::unmodified} or \texttt{state::modified}
- \item \texttt{context::alone} or \texttt{context::combined}
- \item \texttt{recipient::4yourself} or \texttt{ecipient::4others}
- \item \texttt{mode::statically-linked} or \texttt{mode::dynamically-linked} or
- \\ \texttt{mode::textually-included}
-\end{itemize}
-
-If we now simply combine all the tokens of all these classes with all the tokens
-of the other classes\footnote{in the sense of the cross product
-TYPE x STATE x CONTEXT x RECIPIENT x MODE}, we get 2*2*2*3*2 = 48 sets of tokens
-or 48 \textit{Open Source Use Cases}. But some of these sets are invalid from
-an empirical or logical view. And some of these sets are context sensitive:
-
-Firstly, 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 \textit{proapse} or
-that it shall be used \textit{alone}: 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 \textit{proapse} or \textit{snimoli}
-\textit{alone} includes that it is used \textit{not in combination} with other
-units, simply because they are tokens of the same class.
-
-Secondly: If you already have specified that the used Open Source
-Software is a \textit{proapse} - hence an autonomous program, an application,
-or a server -, then your answer includes, that the software is used alone and is
-not used in combination. But if you have specified that the used Open Source
-Software is a \textit{snimoli} - hence a snippet of code, a module, a plugin, or a
-librabry -, then it can indeed be used in combination (if it becomes a
-component of a constructed larger unit) or be used alone (if it is
-'only' re-distributed to 3rd parties).
-
-And thirdly - just the other way round: If you already have specified that the
-used Open Source Software is a \textit{snimoli} - hence a snippet of code, a
-module, a plugin, or a library -, and that this \textit{snimoli} shall be used
-only by yourself (not distributed to other 3rd. parties), then your answer
-includes pratically, that this \textit{snimoli} is used in combination. This
-conclusion is valid, because if you want to use it in the state \textit{alone},
-then you would have a software library on your disc (your are 'using' it for
-yourself) without combining it to any other software: hence in this case this
-librabry would lie on your disc and nothing more: a senseless use case.
+\section{The OS Use Case Dimensions: Classes and Tokens}
-Do you think, this is complicate? So we do. We spent a couple of time to
-explain ourselves these constraints. Only when we had transposed all the
-combinations and rules into a tree, we got the real insight into situation.
-So let us summarize these specifications by two little pictures before we
-will specify the real Open Source Use Case Finder:
-\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?}}}{
@@ -185,8 +39,8 @@ \section{The OS Use Case Dimensions: Classes and Tokens}
\Toval{modified}
}
\pstree[]{\Tr{\fbox{context?}}}{
- \Toval{alone}
- \pstree[]{\Toval{combined}}{
+ \Toval{independent}
+ \pstree[]{\Toval{embedded}}{
\pstree[]{\Tr{\fbox{mode?}}}{
\Toval{statically linked}
\Toval{dynamically linked}
@@ -199,11 +53,22 @@ \section{The OS Use Case Dimensions: Classes and Tokens}
\Toval{4others}
}
}
-
+
+\end{footnotesize}
\section{The OS Use Case Taxonomy}
-\tiny
+
+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}\}}}}}{
@@ -215,7 +80,7 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{proapse,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}\underline{alone}\}}}}}{
+ \hspace*{0.5em}\underline{independent}\}}}}}{
\pstree[]{\Tr{\fbox{recipient?}}}{
\pstree[]{\Toval{\bfseries{OSUC-01}}}{
@@ -223,7 +88,7 @@ \section{The OS Use Case Taxonomy}
\Tr{\parbox{5.2em}{
\texttt{\{proapse,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4yourself}\}}}}
}
\pstree[]{\Toval{\bfseries{OSUC-02}}}{
@@ -231,7 +96,7 @@ \section{The OS Use Case Taxonomy}
\Tr{\parbox{5.2em}{
\texttt{\{proapse,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4others}\}}}}
}
}
@@ -239,7 +104,7 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.4em}{
\texttt{\{proapse,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}\underline{combined}
+ \hspace*{0.5em}\underline{embedded}
\bfseries{\lightning}\}}}}}{
\Tr{$\varnothing$}
}
@@ -252,20 +117,20 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{proapse,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}\underline{alone}\}}}}}{
+ \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}alone,\\
+ \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}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4others}\}}}}
}
}
@@ -273,7 +138,7 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.4em}{
\texttt{\{proapse,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}\underline{combined}
+ \hspace*{0.5em}\underline{embedded}
\bfseries{\lightning}\}}}}}{
\Tr{$\varnothing$}
}
@@ -290,13 +155,13 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}\underline{alone}\}}}}}{
+ \hspace*{0.5em}\underline{independent}\}}}}}{
\pstree[]{\Tr{\fbox{recipient?}}}{
\pstree[]{
\Tr{\parbox{5.8em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4yourself}
\bfseries{\lightning}\}}}}
}{\Tr{$\varnothing$}}
@@ -306,7 +171,7 @@ \section{The OS Use Case Taxonomy}
\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4others}\}}}}
}
}
@@ -316,22 +181,22 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}\underline{combined}\}}}}}{
+ \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}combined,\\
+ \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-06a}}\\
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-06b}}\\
\texttt{\{dynamically\\
\hspace*{0.5em}linked\}}}}
- \Tr{\parbox{5.6em}{\underline{\textit{OSUC-06a}}\\
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-06c}}\\
\texttt{\{textually\\
\hspace*{0.5em}included\}}}}
}
@@ -341,16 +206,16 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}unmodified,\\
- \hspace*{0.5em}combined,\\
+ \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-07a}}\\
+ \Tr{\parbox{5.26em}{\underline{\textit{OSUC-07b}}\\
\texttt{\{dynamically\\
\hspace*{0.5em}linked\}}}}
- \Tr{\parbox{5.6em}{\underline{\textit{OSUC-07a}}\\
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-07c}}\\
\texttt{\{textually\\
\hspace*{0.5em}included\}}}}
}
@@ -370,13 +235,13 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}\underline{alone}\}}}}}{
+ \hspace*{0.5em}\underline{independent}\}}}}}{
\pstree[]{\Tr{\fbox{recipient?}}}{
\pstree[]{
\Tr{\parbox{5.8em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4yourself}
\bfseries{\lightning}\}}}}
}{\Tr{$\varnothing$}}
@@ -385,7 +250,7 @@ \section{The OS Use Case Taxonomy}
\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}alone,\\
+ \hspace*{0.5em}independent,\\
\hspace*{0.5em}\underline{4others}\}}}}
}
}
@@ -394,22 +259,22 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}\underline{combined}\}}}}}{
+ \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}combined,\\
+ \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-09a}}\\
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-09b}}\\
\texttt{\{dynamically\\
\hspace*{0.5em}linked\}}}}
- \Tr{\parbox{5.6em}{\underline{\textit{OSUC-09a}}\\
+ \Tr{\parbox{5.6em}{\underline{\textit{OSUC-09c}}\\
\texttt{\{textually\\
\hspace*{0.5em}included\}}}}
}
@@ -419,7 +284,7 @@ \section{The OS Use Case Taxonomy}
\pstree[]{\Tr{\parbox{5.2em}{
\texttt{\{snimoli,\\
\hspace*{0.5em}modified,\\
- \hspace*{0.5em}combined,\\
+ \hspace*{0.5em}embedded,\\
\hspace*{0.5em}\underline{4others}\}}}}}{
\pstree[]{\Tr{\fbox{$\cup$ mode?}}}{
\Tr{\parbox{5.6em}{\underline{\textit{OSUC-10a}}\\
@@ -435,36 +300,12 @@ \section{The OS Use Case Taxonomy}
}
}
}
- }
-
-
-
- %%
-% \pstree[]{\Tr{\parbox{5.2em}{
-% \texttt{\{snimoli!,\\
-% \hspace*{0.5em}modified,\\
-% \hspace*{0.5em}\underline{combined}\}}}}}{
-% \pstree[]{\Tr{\fbox{recipient?}}}{
-% \Tr{\parbox{5.2em}{
-% \texttt{\{snimoli,\\
-% \hspace*{0.5em}modified,\\
-% \hspace*{0.5em}combined,\\
-% \hspace*{0.5em}\underline{4yourself}\}}}}
-% \Tr{\parbox{5.2em}{
-% \texttt{\{snimoli,\\
-% \hspace*{0.5em}modified,\\
-% \hspace*{0.5em}combined,\\
-% \hspace*{0.5em}\underline{4others}\}}}}
-% }
-% }
-
-
+ }
}
}
}
}
}
}
-
-\normalsize{}
+\end{tiny}
%\bibliography{../../../bibfiles/oscResourcesEn}
12 snippets/en/07-osToDoListFinder/0700-chapterAbstractInc.tex
View
@@ -24,12 +24,12 @@
\footnotesize
\begin{quote}\itshape
-This chapter offers the Open Source Use Case Finder: Firstly it presents
-of form to gather the information. Secondly it offers a tree which easily
-can be transversed by the gathered information. Each leaf of the tree leads to
-one Open Source Use Case. These Open Source Use Cases are listed as third
-section of this chapter and are finally referring to the specific license
-fulfill to-do list.
+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{}
510 snippets/en/07-osToDoListFinder/0701-chapterStartInc.tex
View
@@ -24,50 +24,55 @@
%\nocite{*}
\section{A standard form for gathering the relevant information}
-
-
+
+\begin{small}
\begin{tabular}[h]{|l|l|l|l|}
\hline
-Class & Question & Answers\\
+Class & Questions & Answers\\
\hline
- Type &
- \parbox[c][4cm][c]{8cm}{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 application or server
- which can be executed or processed [=propase]?} &
- \parbox{10em}{
- $\square$\hspace{1em}proapse\\
- $\square$\hspace{1em}snimoli}\\
+ 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][2.5cm][c]{8cm}{Do you want to leave the evaluated 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[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][3cm][c]{8cm}{Are you using the evaluated Open Source Software as
- an autonomous piece of software [=alone], or are you using it in combination with other components
- for setting up a larger, more complex piece of software?} &
- \parbox{10em}{
- $\square$\hspace{1em}alone\\
- $\square$\hspace{1em}combined}\\
+ \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][3cm][c]{8cm}{Are you are going to use the evaluated Open Source
- Software only for yourself [=4yourself], or do you plan to (re)distribute it (also) to third
- parties [=4others]?}
+ \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][3.4cm][c]{8cm}{Are you going to combine the evaluated Open Source
- Software with other software components by linking all together statically, by linking them
+ \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?} &
+ into your larger unit?}} &
\parbox{10em}{
$\square$\hspace{1em}statically linked\\
$\square$\hspace{1em}dynamically linked\\
@@ -75,9 +80,462 @@ \section{A standard form for gathering the relevant information}
\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}
7 snippets/en/08-osFulfillmentByToDoLists/0800-chapterAbstractInc.tex
View
@@ -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{}
40 snippets/en/08-osFulfillmentByToDoLists/0802-apacheFulfillToDoList.tex
View
@@ -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}
+
+\label{OSUC-02-Apache20} \label{OSUC-04-Apache20} \label{OSUC-05-Apache20}
+\label{OSUC-07-Apache20} \label{OSUC-08-Apache20} \label{OSUC-10-Apache20}
+
+\subsection{Apache specific mini finder}
+
+\subsection{Apache specific use case 1}
+(covers OSUC-X - OSUC-Z)
+
+\subsection{Apache specific use case n}
+(covers OSUC-x - OSUC-z)
+
+
%\bibliography{../../../bibfiles/oscResourcesEn}
425 snippets/en/08-osFulfillmentByToDoLists/0803-bsdFulfillToDoList.tex
View
@@ -23,26 +23,411 @@
%% use all entries of the bibliography
%\nocite{*}
-\section{BSD 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{BSD Licensed Software \ldots}
+\subsection{The BSD specific mini finder}
+
+As an approved Open Source license, the BSD license exists in two
+versions\footcite[Following the Open Source Initiative, initially a not approved
+BSD license contained a fourth clause also known as advertising clause which
+\glqq{}(\ldots) officially was rescinded by the Director of the Office of
+Technology Licensing of the University of California on July 22nd, 1999\grqq{}.
+ Cf.][\nopage wp. Because of the cancellation you can simply act according the
+ \textit{BSD 3-Clause license} if you have to fulfill the eldest BSD
+ license]{BsdLicense3Clause}. The latest, most modern release is the \textit{BSD
+ 2-Clause license}\footcite[cf.][\nopage wp]{BsdLicense2Clause}, the elder
+ release is the \textit{BSD 3-Clause license}\footcite[cf.][\nopage
+ wp]{BsdLicense3Clause}. Nevertheless, the little differences between the
+ two versions have to be respected.
+
+All BSD Open Source Licenses explicitly focuses 'only' on the (re-)distribution
+\textit{Open Source Use Cases}, which we have specified by our token
+\textit{4others}. Conditions for the use cases specified by the token
+\textit{4yourself} can be derived\footnote{For details of the \textit{Open
+Source Use Cases tokens} see p. \pageref{OsucTokens}. For Details of the
+\textit{Open Source Use Cases} based on these token see p.
+\pageref{OsucDefinitionTree} }. Additionally the BSD license considers the form
+of the distribution, e.g. whether the work is distributed as a (set of) source
+code file(s) or as a (set of) the binary file(s). Use the following tree to find
+the license fulfilling to-do lists\footcite[The BSD license requires, that a
+re-distributed software package must contain the (package specific) copyright
+notice, the (license specific) conditions and the BSD discaimer. (cf.][\nopage
+wp.) You might ask what you should do, if these elements are missed in the
+package you got. If so, the package you got had not been licensed adequately.
+Hence, you do not know reliably whether you have received it under a BSD
+license. In other words: If you have received a BSD licensed software package,
+it must contain sufficient license fulfilling elements, or it is not a BSD
+licensed software]{BsdLicense2Clause}.
+
+\begin{center}
+\begin{footnotesize}
+\pstree[levelsep=*1,treesep=0.2]{\Toval{BSD}}{
+ \pstree[levelsep=*0.2,treesep=1]{
+ \Toval{2 Clause License}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{recipient: \textit{4yourself}\\
+ \textbf{\textit{used by yourself}}}}}
+ }{
+% \Toval{\parbox{7em}{\begin{center}BSD-1: using the BSD software only for
+% yourself\end{center}}}
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-1}:}\\
+ \tiny{\textit{using the}}\\\tiny{\textit{software}}\\
+ \tiny{\textit{only for}}\\\tiny{\textit{yourself}} }}}
+ }
+ \pstree[levelsep=*0.2,treesep=0.2]{
+ \Tr{\Ovalbox{\shortstack{recipient: \textit{4others}\\
+ \textbf{\textit{distributed to 3rd. parties}}}}}
+ }{
+ \pstree[levelsep=*0.2,treesep=0.2]{
+ \Tr{\Ovalbox{\shortstack{state:\\\textbf{\textit{unmodified}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{source}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-2}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{unmodified}}\\
+ \tiny{\textit{software as}}\\\tiny{\textit{source code}} }}}
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{binary}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-3}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{unmodified}}\\
+ \tiny{\textit{software as}}\\\tiny{\textit{binary pkg}} }}}
+ }
+
+ }
+
+ \pstree[levelsep=*0.2,treesep=0.2]{
+ \Tr{\Ovalbox{\shortstack{state:\\\textbf{\textit{modified}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{type:\\\textbf{\textit{proapse}}}}}
+ }{
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{source}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-4}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{a modified}}\\
+ \tiny{\textit{program as}}\\\tiny{\textit{source code}} }}}
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{binary}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-5}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{a modified}}\\
+ \tiny{\textit{program as}}\\\tiny{\textit{binary pkg}} }}}
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{type:\\\textbf{\textit{snimoli}}}}}
+ }{
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{independent}}}}}
+ }{
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{source}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-6}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{a modified}}\\
+ \tiny{\textit{library as}}\\\tiny{\textit{independent}}\\
+ \tiny{\textit{source pkg}} }}}
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{binary}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-7}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{a modified}}\\
+ \tiny{\textit{library as}}\\\tiny{\textit{independent}}\\
+ \tiny{\textit{binary pkg}} }}}
+ }
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{context:\\\textbf{\textit{embedded}}}}}
+ }{
+
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{source}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-8}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{a modified}}\\
+ \tiny{\textit{library as}}\\\tiny{\textit{embedded}}\\
+ \tiny{\textit{source pkg}} }}}
+ }
+ \pstree{
+ \Tr{\Ovalbox{\shortstack{form:\\\textbf{\textit{binary}}}}}
+ }{
+ \Tr{\doublebox{\shortstack{\tiny{\textbf{BSD-9}:}\\
+ \tiny{\textit{distributing}}\\\tiny{\textit{a modified}}\\
+ \tiny{\textit{library as}}\\\tiny{\textit{embedded}}\\
+ \tiny{\textit{binary pkg}} }}}
+ }
+ }
+
+
+ }
+
+ }
+ }
+
+ }
+ \pstree[levelsep=*0.2,treesep=0.2]{
+ \Toval{3 Clause License}
+ }{
+ \Ttri{}
+ }
+}
+\end{footnotesize}
+\end{center}
+
+\subsection{Software licensed by the \emph{BSD 2-Clause License}}
+
+\subsubsection{BSD-1: using the software only for yourself}
+\label{OSUC-01-BSD}
+\label{OSUC-03-BSD}
+\label{OSUC-06-BSD}
+\label{OSUC-09-BSD}
+
+\begin{description}
+\item[means] that you are going to use a received BSD software only for yourself
+and that you do not handover it to any 3rd. party in any sense.
+\item[covers] OSUC-01, OSUC-03, OSUC-06, and OSUC-09\footnote{For details see pp.
+ \pageref{OSUC-01-DEF} - \pageref{OSUC-09-DEF}}
+\item[requires] the tasks in order to fulfill the conditions
+ of the BSD license:
+ \begin{itemize}
+ \item You are allowed to use any kind of BSD software in any sense and in
+ any context without any obligations if you do not handover the software to
+ 3rd parties.
+ \end{itemize}
+\end{description}
+
+
+\subsubsection{BSD-2: Passing the unmodified software as a source code package}
+\label{OSUC-02-BSD} \label{OSUC-05-BSD} \label{OSUC-07-BSD}
+
+\begin{description}
+\item[means] that you are going distribute an unmodified version of the received
+BSD software to 3rd. parties in form of a set of source code files or an
+integrated source code package\footnote{In this case it doesn't matter whether
+you distribute a program, an application, a server, a snippet, a module, a
+library, or a plugin as an independent or an embedded unit}
+
+\item[covers] OSUC-02, OSUC-05, OSUC-07\footnote{For details see pp.
+\pageref{OSUC-02-DEF} - \pageref{OSUC-07-DEF}}
+
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that the licensing elements - e.g.
+ the BSD license text, the specific copyright notice of the original author(s),
+ and the BSD disclaimer - are retained in your package in the form you have got
+ them.
+ \item \textbf{[-b voluntary:]} Let the documentation of your distribution
+ and/or your additional material also contain the original copyright notice, the
+ BSD conditions, and the BSD disclaimer.
+\end{itemize}
+\end{description}
+
+\subsubsection{BSD-3: Passing the unmodified software as a binary package}
+
+\begin{description}
+\item[means] that you are going distribute an unmodified version of the BSD
+received software to 3rd. parties in form of a set of binary files or an
+integrated binary package\footnote{In this case it doesn't matter whether you
+distribute a program, an application, a server, a snippet, a module, a library,
+or a plugin as an independent or an embedded unit}
+\item[covers] OSUC-02, OSUC-05, OSUC-07\footnote{For details see pp.
+\pageref{OSUC-02-DEF} - \pageref{OSUC-07-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that your distribution contains the
+ original copyright notice, the BSD license, and the BSD disclaimer in the form
+ you have got them. If you compile the binary file on the base of the source
+ code package and if this compilation does not also generate and integrate the
+ licensing files, then create the copyright notice, the BSD conditions, and the
+ BSD disclaimer according to the form of the source code package and insert
+ these files into your distribution manually.
+ \item \textbf{[+b mandatory:]} Ensure, that the documentation of your
+ distribution and/or your additional material also contain the author specific
+ copyright notice, the BSD conditions, and the BSD disclaimer.
+\end{itemize}
+\end{description}
+
+\subsubsection{BSD-4: Passing a modified program as a source code package}
+\label{OSUC-04-BSD}
+
+\begin{description}
+\item[means] that you are going distribute a modified version of the received
+BSD program, application, or server (proapse) to 3rd. parties in form of a set
+of source code files or an integrated source code package.
+\item[covers] OSUC-04\footnote{For details see pp. \pageref{OSUC-04-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that the licensing elements - e.g.
+ the BSD license text, the specific copyright notice of the original author(s),
+ and the BSD disclaimer - are retained in your package in the form you have got
+ them.
+ \item \textbf{[-b voluntary:]} Let the documentation of your distribution
+ and/or your additional material also contain the original copyright notice, the
+ BSD conditions, and the BSD disclaimer.
+
+ \item \textbf{[-c voluntary:]} It is a good practice of the Open Source
+ community, to let the copyright notice which is shown by the running program
+ also state that the program is licensed under the BSD license. Because you are
+ already modifying the program, you can also add such a hint, if the presented
+ original copyright notice lacks such a statement.
+\end{itemize}
+\end{description}
+
+\subsubsection{BSD-5: Passing a modified program as a binary package}
+
+\begin{description}
+\item[means] that you are going distribute a modified version of the received
+BSD pro\-gram, application, or server (proapse) to 3rd. parties in form of a set
+of binary files or an integrated binary package.
+\item[covers] OSUC-04\footnote{For details see pp. \pageref{OSUC-04-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+
+ \item \textbf{[+a mandatory:]} Ensure, that your distribution contains the
+ original copyright notice, the BSD license, and the BSD disclaimer in the form
+ you have got them. If you compile the binary file on the base of the source
+ code package and if this compilation does not also generate and integrate the
+ licensing files, then create the copyright notice, the BSD conditions, and the
+ BSD disclaimer according to the form of the source code package and insert
+ these files into your distribution manually.
+
+ \item \textbf{[+b mandatory:]} Ensure, that the documentation of your
+ distribution and/or your additional material also contain the author specific
+ copyright notice, the BSD conditions, and the BSD disclaimer.
+
+ \item \textbf{[-c voluntary:]} It is a good practice of the Open Source
+ community, to let the copyright notice which is shown by the running program
+ also state that the program is licensed under the BSD license. Because you are
+ already modifying the program, you can also add such a hint, if the presented
+ original copyright notice lacks such a statement.
+\end{itemize}
+\end{description}
+
+\subsubsection{BSD-6: Passing a modified library as independent source code
+package}
+\label{OSUC-08-BSD}
+\begin{description}
+\item[means] that you are going distribute a modified version of the received
+BSD code snippet, module, library, or plugin (snimoli) to 3rd. parties in form
+of a set of source code files or an integrated source code package, but without
+embedding it into another larger software unit.
+\item[covers] OSUC-08\footnote{For details see pp. \pageref{OSUC-08-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that the licensing elements - e.g.
+ the BSD license text, the specific copyright notice of the original author(s),
+ and the BSD disclaimer - are retained in your package in the form you have got
+ them.
+ \item \textbf{[-b voluntary:]} Let the documentation of your distribution
+ and/or your additional material also contain the original copyright notice, the
+ BSD conditions, and the BSD disclaimer.
+\end{itemize}
+\end{description}
+
+
+\subsubsection{BSD-7: Passing a modified library as independent binary
+package}
+
+\begin{description}
+\item[means] that you are going distribute a modified version of the received
+BSD code snippet, module, library, or plugin (snimoli) to 3rd. parties in form
+of a set of binary files or an integrated binary package, but without embedding
+it into another larger software unit.
+\item[covers] OSUC-08\footnote{For details see pp. \pageref{OSUC-08-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that your distribution contains the
+ original copyright notice, the BSD license, and the BSD disclaimer in the form
+ you have got them. If you compile the binary file on the base of the source
+ code package and if this compilation does not also generate and integrate the
+ licensing files, then create the copyright notice, the BSD conditions, and the
+ BSD disclaimer according to the form of the source code package and insert
+ these files into your distribution manually.
+ \item \textbf{[+b mandatory:]} Ensure, that the documentation of your
+ distribution and/or your additional material also contain the author specific
+ copyright notice, the BSD conditions, and the BSD disclaimer.
+\end{itemize}
+\end{description}
+
+\subsubsection{BSD-8: Passing a modified library as an embedded source code
+package}
+\label{OSUC-10-BSD}
+\begin{description}
+\item[means] that you are going distribute a modified version of the received
+BSD code snippet, module, library, or plugin (snimoli) to 3rd. parties in form
+of a set of source code files or an integrated source code package together with
+another larger software unit, which contains this code snippet, module, library,
+or plugin as an embedded component.
+\item[covers] OSUC-10\footnote{For details see pp. \pageref{OSUC-10-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that the licensing elements - e.g.
+ the BSD license text, the specific copyright notice of the original author(s),
+ and the BSD disclaimer - are retained in your package in the form you have got
+ them.
+ \item \textbf{[-b voluntary:]} Let the documentation of your distribution
+ and/or your additional material also contain the original copyright notice, the
+ BSD conditions, and the BSD disclaimer.
+ \item \textbf{[-c voluntary:]} It is a good practice of the Open Source
+ community, to let the copyright notice which is shown by the running program
+ also state that it contains components licensed under the BSD license. Because
+ you are embedding this snimoli into a larger software unit, you are
+ developing this larger unit. Hence, you can also expand the copyright notice
+ of this larger unit by such a hint to its BSD components.
+\end{itemize}
+\end{description}
+
+
+\subsubsection{BSD-9: Passing a modified library as an embedded binary
+package}
+
+\begin{description}
+\item[means] that you are going distribute a modified version of the received
+BSD code snippet, module, library, or plugin to 3rd. parties in form of a set of
+binary files or an integrated binary package together with another larger
+software unit, which contains this code snippet, module, library, or plugin as
+an embedded component.
+\item[covers] OSUC-10\footnote{For details see pp. \pageref{OSUC-10-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions
+\begin{itemize}
+ \item \textbf{[+a mandatory:]} Ensure, that your distribution contains the
+ original copyright notice, the BSD license, and the BSD disclaimer in the form
+ you have got them. If you compile the binary file on the base of the source
+ code package and if this compilation does not also generate and integrate the
+ licensing files, then create the copyright notice, the BSD conditions, and the
+ BSD disclaimer according to the form of the source code package and insert
+ these files into your distribution manually.
+ \item \textbf{[+b mandatory:]} Ensure, that the documentation of your
+ distribution and/or your additional material also contain the author specific
+ copyright notice, the BSD conditions, and the BSD disclaimer.
+ \item \textbf{[-c voluntary:]} It is a good practice of the Open Source
+ community, to let the copyright notice which is shown by the running program
+ also state that it contains components licensed under the BSD license. Because
+ you are embedding this snimoli into a larger software unit, you are
+ developing this larger unit. Hence, you can also expand the copyright notice
+ of this larger unit by such a hint to its BSD components.
+\end{itemize}
+\end{description}
+
+\subsection{Software licensed by the \emph{BSD 3-Clause License}}
+
+Compared with the \textit{BSD 2-Clause license}, the \textit{BSD 3-Clause
+license} only contains one additional 3rd. clause, the rest is the same. So, for
+acting according the \textit{BSD 3-Clause license}, do that, what you would have
+to do for fulfilling the 2 clause license. And additionally do not use the name
+of licensing organization or the names of the licensing distributors to promote
+your own work.
+
+\subsection{Discussions and Explanations}
+[\ldots to be done]
%\bibliography{../../../bibfiles/oscResourcesEn}
34 snippets/en/08-osFulfillmentByToDoLists/0804-gplv2FulfillToDoList.tex
View
@@ -24,27 +24,19 @@
%\nocite{*}
\section{GPL V2 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.}
+\label{OSUC-01-GPL2X} \label{OSUC-03-GPL2X}
+\label{OSUC-06-GPL2X} \label{OSUC-09-GPL2X}
+
+\label{OSUC-02-GPL2X} \label{OSUC-04-GPL2X} \label{OSUC-05-GPL2X}
+\label{OSUC-07-GPL2X} \label{OSUC-08-GPL2X} \label{OSUC-10-GPL2X}
+
+\subsection{GPL-2 specific mini finder}
+
+\subsection{GPL-2 specific use case 1}
+(covers OSUC-X - OSUC-Z)
+
+\subsection{GPL-2 specific use case n}
+(covers OSUC-x - OSUC-z)
%\bibliography{../../../bibfiles/oscResourcesEn}
32 snippets/en/08-osFulfillmentByToDoLists/0805-mitFulfillToDoList.tex
View
@@ -24,24 +24,18 @@
%\nocite{*}
\section{MIT 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
+\label{OSUC-01-MIT} \label{OSUC-03-MIT}
+\label{OSUC-06-MIT} \label{OSUC-09-MIT}
+
+\label{OSUC-02-MIT} \label{OSUC-04-MIT} \label{OSUC-05-MIT}
+\label{OSUC-07-MIT} \label{OSUC-08-MIT} \label{OSUC-10-MIT}
+
+\subsection{MIT specific mini finder}
+
+\subsection{MIT specific use case 1}
+(covers OSUC-X - OSUC-Z)
+
+\subsection{MIT specific use case n}
+(covers OSUC-x - OSUC-z)
%\bibliography{../../../bibfiles/oscResourcesEn}
Please sign in to comment.
Something went wrong with that request. Please try again.