Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Merge branch 'integration'

  • Loading branch information...
commit a77b05213fde82d315f931186bda4a21274d5233 2 parents 5ee488f + 3c5ddfb
Karsten Reincke (on perceval) authored
View
15 snippets/en/02C-SameIdeaDifferentLicenseModelsInc.tex
@@ -888,16 +888,17 @@ \section{The protecting power of the Eclipse Public License (EPL)}
program, library, module, or plugin, then one has to publish the modified source
code, too. If one \enquote{adds} some own plugins or additional libraries which
are used by an EPL licensed program (which on behalf of this use must have been
-modified by adding [sic!] procedure calls) then one has publish the code of both
-parts: that of the program and that of the added elements. In this sense, the
-EPL clearly protects the binaries against re-closings like other weak copyleft
-using licenses. But if one distributes only an EPL licensed library which is
-used as a component by another not EPL licensed on-top program, then this
-library does not depend on the top development -- provided that the library
+modified by adding [sic!] procedure calls) then one has to publish the code of
+both parts: that of the program and that of the added elements. In this sense,
+the EPL clearly protects the binaries against re-closings like other weak
+copyleft using licenses. But if one distributes only an EPL licensed library
+which is used as a component by another not EPL licensed on-top program, then
+this library does not depend on the top development -- provided that the library
itself does not call any (program) functions or procedures delivered by the
overarching on-top development. Hence, nothing is added to the library; and
hence, no other code than that of the library must be published. Therefore, the
-EPL does not use the strong copyleft effect in the meaning of the GPL.
+EPL does not use the strong copyleft effect in the meaning of -- for example --
+the GPL.
\section{The protecting power of the European Union Public License (EUPL)}
\label{sec:ProtectingPowerOfEupl}
View
2  snippets/en/06C-osFulfillmentByToDoLists/0602-apacheFulfillToDoList.tex
@@ -146,7 +146,7 @@ \subsection{ApL-1: Using the software only for yourself}
license with respect to this use case:
\begin{itemize}
\item You are allowed to use any kind of Apache software in any sense and in
- any context without being obligied to do something as long as you do not
+ any context without being obliged to do something as long as you do not
give the software to 3rd parties.
\end{itemize}
View
586 snippets/en/06C-osFulfillmentByToDoLists/0604-eplFulfillToDoList.tex
@@ -23,12 +23,592 @@
%% use all entries of the bibliography
%\nocite{*}
-\section{Eclipse Licensed Software in the usage context of \ldots [tbd]}
+\section{EPL licensed software}
+
+The Eclipse Public License clearly distinguishes the distribution in the form of
+source code from that in the form of binaries: It allows to \enquote{distribute}
+Eclipse licensed programs \enquote{in source code and in object
+code}\footcite[cf.][\nopage wp\ §3]{Epl10OsiLicense2005a} before it specifies
+under which conditions one may distribute the program as a set of binaries.
+\footcite[cf.][\nopage wp\ §3 top area]{Epl10OsiLicense2005a}. One of these
+conditions is -- roughly spoken -- that the distributor makes the sources
+available too\footnote{\cite[cf.][\nopage wp\ §3 mid
+area]{Epl10OsiLicense2005a}. More precisely, the EPL has to be taken as a
+license with weak copyleft ($\rightarrow$ OSLiC, p.\
+\pageref{sec:ProtectingPowerOfEpl})}. The other conditions refer to the
+distribution in general -- no matter what form or state is
+used\footcite[cf.][\nopage wp\ §3 bottom area]{Epl10OsiLicense2005a}. So, taken
+as whole, the EPL mainly focusses on the distribution of a program. Thus, for
+finding the simply processable task lists, the following EPL specific open source
+use case structure\footnote{For details of the general OSUC finder $\rightarrow$
+OSLiC, pp.\ \pageref{OsucTokens} and \pageref{OsucDefinitionTree}} can be used:
+
+\tikzstyle{nodv} = [font=\small, ellipse, draw, fill=gray!10,
+ text width=2cm, text centered, minimum height=2em]
+
+\tikzstyle{nods} = [font=\footnotesize, rectangle, draw, fill=gray!20,
+ text width=1.2cm, text centered, rounded corners, minimum height=3em]
+
+\tikzstyle{nodb} = [font=\footnotesize, rectangle, draw, fill=gray!20,
+ text width=2.2cm, text centered, rounded corners, minimum height=3em]
+
+\tikzstyle{leaf} = [font=\tiny, rectangle, draw, fill=gray!30,
+ text width=1.2cm, text centered, minimum height=6em]
+
+\tikzstyle{edge} = [draw, -latex']
+
+\begin{tikzpicture}[]
+
+\node[nodv] (l71) at (4,10) {EPL};
+
+\node[nodb] (l61) at (0,8.6) {\textit{recipient:} \\ \textbf{4yourself}};
+\node[nodb] (l62) at (6.5,8.6) {\textit{recipient:} \\ \textbf{4others}};
+
+\node[nodb] (l51) at (2.5,7) {\textit{state:} \\ \textbf{unmodified}};
+\node[nodb] (l52) at (9.3,7) {\textit{state:} \\ \textbf{modified}};
+
+\node[nods] (l41) at (1.8,5.4) {\textit{form:} \textbf{source}};
+\node[nods] (l42) at (3.6,5.4) {\textit{form:} \textbf{binary}};
+\node[nodb] (l43) at (6.5,5.4) {\textit{type:} \\ \textbf{proapse}};
+\node[nodb] (l44) at (12,5.4) {\textit{type:} \\ \textbf{snimoli}};
+
+
+\node[nods] (l31) at (5.4,3.8) {\textit{form:} \textbf{source}};
+\node[nods] (l32) at (7.2,3.8) {\textit{form:} \textbf{binary}};
+\node[nodb] (l33) at (10,3.8) {\textit{context:} \\ \textbf{independent}};
+\node[nodb] (l34) at (13.5,3.8) {\textit{context:} \\ \textbf{embedded}};
+
+\node[nods] (l21) at (9,2.2) {\textit{form:} \textbf{source}};
+\node[nods] (l22) at (10.8,2.2) {\textit{form:} \textbf{binary}};
+\node[nods] (l23) at (12.6,2.2) {\textit{form:} \textbf{source}};
+\node[nods] (l24) at (14.4,2.2) {\textit{form:} \textbf{binary}};
+
+\node[leaf] (l11) at (0,0) {\textbf{EPL-1} \textit{using software only
+for yourself}};
+
+\node[leaf] (l12) at (1.8,0) { \textbf{EPL-2} \textit{ distributing unmodified
+software as sources}};
+
+\node[leaf] (l13) at (3.6,0) { \textbf{EPL-3} \textit{ distributing unmodified
+software as binaries}};
+
+\node[leaf] (l14) at (5.4,0) { \textbf{EPL-4} \textit{ distributing modified
+program as sources}};
+
+\node[leaf] (l15) at (7.2,0) { \textbf{EPL-5} \textit{ distributing modified
+program as binaries}};
+
+\node[leaf] (l16) at (9,0) { \textbf{EPL-6} \textit{ distributing modified
+library as independent sources}};
+
+\node[leaf] (l17) at (10.8,0) { \textbf{EPL-7} \textit{distributing modified
+library as independent binaries}};
+
+\node[leaf] (l18) at (12.6,0) { \textbf{EPL-8} \textit{distributing
+modified library as embedded sources}};
+
+\node[leaf] (l19) at (14.4,0) { \textbf{EPL-9} \textit{ distributing modified
+library as embedded binaries}};
+
+
+\path [edge] (l71) -- (l61);
+\path [edge] (l71) -- (l62);
+\path [edge] (l61) -- (l11);
+\path [edge] (l62) -- (l51);
+\path [edge] (l62) -- (l52);
+\path [edge] (l51) -- (l41);
+\path [edge] (l51) -- (l42);
+\path [edge] (l52) -- (l43);
+\path [edge] (l52) -- (l44);
+\path [edge] (l41) -- (l12);
+\path [edge] (l42) -- (l13);
+\path [edge] (l43) -- (l31);
+\path [edge] (l43) -- (l32);
+\path [edge] (l44) -- (l33);
+\path [edge] (l44) -- (l34);
+\path [edge] (l31) -- (l14);
+\path [edge] (l32) -- (l15);
+\path [edge] (l33) -- (l21);
+\path [edge] (l33) -- (l22);
+\path [edge] (l34) -- (l23);
+\path [edge] (l34) -- (l24);
+\path [edge] (l21) -- (l16);
+\path [edge] (l22) -- (l17);
+\path [edge] (l23) -- (l18);
+\path [edge] (l24) -- (l19);
+
+\end{tikzpicture}
+
+
+\subsection{EPL-1: Using the software only for yourself}
\label{OSUC-01-EPL} \label{OSUC-03-EPL}
\label{OSUC-06-EPL} \label{OSUC-09-EPL}
-\label{OSUC-02-EPL} \label{OSUC-04-EPL} \label{OSUC-05-EPL}
-\label{OSUC-07-EPL} \label{OSUC-08-EPL} \label{OSUC-10-EPL}
+\begin{description}
+
+\item[means] that you are going to use a received EPL licensed software only
+for yourself and that you do not hand it over to any 3rd party in any sense.
+
+\item[covers] OSUC-01, OSUC-03, OSUC-06, and OSUC-09\footnote{For details
+$\rightarrow$ OSLiC, pp.\ \pageref{OSUC-01-DEF} - \pageref{OSUC-09-DEF}}
+
+\item[requires] no tasks in order to fulfill the conditions of the EPL 1.0
+license with respect to this use case:
+ \begin{itemize}
+ \item You are allowed to use any kind of EPL software in any sense and in
+ any context without being obliged to do something as long as you do not
+ give the software to 3rd parties.
+ \end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+\subsection{EPL-2: Passing the unmodified software as source code}
+\label{OSUC-02-EPL} \label{OSUC-05-EPL} \label{OSUC-07-EPL}
+
+\begin{description}
+
+\item[means] that you are going to distribute an unmodified version of the
+received EPL software to 3rd parties in the 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 $\rightarrow$ OSLiC, pp.\
+\pageref{OSUC-02-DEF} - \pageref{OSUC-07-DEF}}
+
+\item[requires] the following tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them. If you compile the
+ binary from the sources, ensure that all these licensing elements are also
+ incorporated into the package.
+
+ \item \textbf{[mandatory:]} Give the recipient a copy of the EPL 1.0 license.
+ If it is not already present in the software package, add it\footnote{For
+ implementing the handover of files correctly $\rightarrow$ OSLiC, p.
+ \pageref{DistributingFilesHint}}. If the licensing statement in the licensing
+ file of the package does still not clearly state that the package is licensed
+ under the EPL, additionally insert your own correct EPL licensing file.
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EPL 1.0 license.
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+
+\subsection{EPL-3: Passing the unmodified software as binaries}
+
+\begin{description}
+\item[means] that you are going to distribute an unmodified version of the
+received EPL software to 3rd parties in the form of a set of binary files or an
+integrated bi\-na\-ry 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 $\rightarrow$ OSLiC, pp.\
+\pageref{OSUC-02-DEF} - \pageref{OSUC-07-DEF}}
+
+\item[requires] the following tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them. If you compile the
+ binary from the sources, ensure that all these licensing elements are also
+ incorporated into the package.
+
+ TODO: complete binary cases by weak copyleft hint ala EUPL\ldots
+
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+\subsection{EPL-4: Passing a modified program as source code}
+\label{OSUC-04-EPL}
+
+\begin{description}
+\item[means] that you are going to distribute a modified version of the received
+EPL licensed 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 $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-04-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them.
+
+ \item \textbf{[mandatory:]} Create a \emph{modification text file}, if such a
+ notice file still does not exist. \emph{Expand} the \emph{modification text
+ file} by a more general description of your modifications. Incorporate it into
+ your distribution package.
+
+ \item \textbf{[mandatory:]} Mark all modifications of the source code of the
+ program\footnote{or application or server} thoroughly -- namely within the
+ modfied source code.
+
+ \item \textbf{[mandatory:]} Give the recipient a copy of the EPL 1.0 license.
+ If it is not already present in the software package, add it\footnote{For
+ implementing the handover of files correctly $\rightarrow$ OSLiC, p.
+ \pageref{DistributingFilesHint}}. If the licensing statement in the licensing
+ file of the package does still not clearly state that the package is licensed
+ under the EPL, additionally insert your own correct EPL licensing file.
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EPL 1.0 license.
+
+ \end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+\subsection{EPL-5: Passing a modified program as binary}
+
+\begin{description}
+\item[means] that you are going to distribute a modified version of the received
+EPL licensed pro\-gram, application, or server (proapse) to 3rd parties in
+the form of a set of binary files or an integrated binary package.
+\item[covers] OSUC-04\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-04-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them. If you compile the
+ binary from the sources, ensure that all these licensing elements are also
+ incorporated into the package.
+
+ \item \textbf{[mandatory:]} Create a \emph{modification text file}, if such a
+ notice file still does not exist. \emph{Expand} the \emph{modification text
+ file} by a more general description of your modifications. Incorporate it into
+ your distribution package.
+
+ \item \textbf{[mandatory:]} Mark all modifications of the source code of the
+ program\footnote{or application or server} thoroughly -- namely within the
+ modfied source code.
+
+ TODO: complete binary cases by weak copyleft hint ala EUPL\ldots
+
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EPL 1.0 license -- especially as a subsection of
+ your own copyright notice.
+
+
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+\subsection{EPL-6: Passing a modified library as independent source code}
+\label{OSUC-08-EPL}
+
+\begin{description}
+\item[means] that you are going to distribute a modified version of the received
+EPL licensed code snippet, module, library, or plugin (snimoli) to 3rd
+parties in the 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 $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-08-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them.
+
+ \item \textbf{[mandatory:]} Create a \emph{modification text file}, if such a
+ notice file still does not exist. \emph{Expand} the \emph{modification text
+ file} by a more general description of your modifications. Incorporate it into
+ your distribution package.
+
+ \item \textbf{[mandatory:]} Mark all modifications of the source code of the
+ library\footnote{or snippet, or module, or plugin} thoroughly -- namely within
+ the modfied source code.
+
+ \item \textbf{[mandatory:]} Give the recipient a copy of the EPL 1.0 license.
+ If it is not already present in the software package, add it\footnote{For
+ implementing the handover of files correctly $\rightarrow$ OSLiC, p.
+ \pageref{DistributingFilesHint}}. If the licensing statement in the licensing
+ file of the package does still not clearly state that the package is licensed
+ under the EPL, additionally insert your own correct EPL licensing file.
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EPL 1.0 license.
+
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+
+\subsection{EPL-7: Passing a modified library as independent binary}
+
+\begin{description}
+\item[means] that you are going to distribute a modified version of the received
+Appache licensed code snippet, module, library, or plugin (snimoli) to 3rd
+parties in the 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 $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-08-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them. If you compile the
+ binary from the sources, ensure that all these licensing elements are also
+ incorporated into the package.
+
+ \item \textbf{[mandatory:]} Create a \emph{modification text file}, if such a
+ notice file still does not exist. \emph{Expand} the \emph{modification text
+ file} by a more general description of your modifications. Incorporate it into
+ your distribution package.
+
+ \item \textbf{[mandatory:]} Mark all modifications of the source code of the
+ library\footnote{or snippet, or module, or plugin} thoroughly -- namely within
+ the modfied source code.
+
+ TODO: complete binary cases by weak copyleft hint ala EUPL\ldots
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EPL 1.0 license -- especially as a subsection of
+ your own copyright notice.
+
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}
+
+\end{description}
+
+\subsection{EPL-8: Passing a modified library as embedded source code}
+\label{OSUC-10-EPL}
+
+\begin{description}
+\item[means] that you are going to distribute a modified version of the received
+EPL licensed code snippet, module, library, or plugin (snimoli) to 3rd
+parties in the 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 $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-10-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them.
+
+ \item \textbf{[mandatory:]} Create a \emph{modification text file}, if such a
+ notice file still does not exist. \emph{Expand} the \emph{modification text
+ file} by a more general description of your modifications. Incorporate it into
+ your distribution package.
+
+ \item \textbf{[mandatory:]} Mark all modifications of the source code of the
+ embedded libary\footnote{or snippet, or module, or plugin} thoroughly --
+ namely within the source code.
+
+ \item \textbf{[mandatory:]} Give the recipient a copy of the EPL 1.0 license.
+ If it is not already present in the software package, add it\footnote{For
+ implementing the handover of files correctly $\rightarrow$ OSLiC, p.
+ \pageref{DistributingFilesHint}}. If the licensing statement in the licensing
+ file of the package does still not clearly state that the embedded library is
+ licensed under the EPL, additionally insert your own correct EPL licensing file.
+
+ \item \textbf{[voluntary:]} Arrange your source code distribution so that the
+ integrated EPL and the \emph{licensing file} clearly refer only to the
+ embedded library and do not disturb the licensing of your own overarching
+ work. It's a good tradition to keep the embedded components like libraries,
+ modules, snippets, or plugins in specific directory which contains also all
+ additional licensing elements.
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the name of the used EPL
+ licensed component, a link to its homepage, and a link to the EPL 1.0 license
+ -- especially as subsection of your own copyright notice.
+
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+
+\subsection{EPL-9: Passing a modified library as embedded binary}
+
+\begin{description}
+\item[means] that you are going to distribute a modified version of the received
+EPL licensed 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 $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-10-DEF}}
+\item[requires] the tasks in order to fulfill the license conditions:
+\begin{itemize}
+
+ \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ all
+ copyright notices and the disclaimer of warranty and liability -- are retained
+ in your package in exact the form you have received them. If you compile the
+ binary from the sources, ensure that all these licensing elements are also
+ incorporated into the package.
+
+ \item \textbf{[mandatory:]} Create a \emph{modification text file}, if such a
+ notice file still does not exist. \emph{Expand} the \emph{modification text
+ file} by a more general description of your modifications. Incorporate it into
+ your distribution package.
+
+ \item \textbf{[mandatory:]} Mark all modifications of the source code of the
+ embedded libary\footnote{or snippet, or module, or plugin} thoroughly --
+ namely within the source code.
+
+ TODO: complete binary cases by weak copyleft hint ala EUPL\ldots
+
+
+ \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the name of the used EPL
+ licensed component, a link to its homepage, and a link to the EPL 1.0 license
+ -- especially as subsection of your own copyright notice.
+
+\end{itemize}
+
+\item[prohibits] \ldots
+\begin{itemize}
+ \item to remove or to alter any copyright notices contained within the
+ received software package.
+\end{itemize}.
+
+\end{description}
+
+\subsection{Discussions and Explanations}
+
+The EPL offers a simply structured section
+\enquote{Requirements}\footcite[cf.][\nopage wp\ §3]{Epl10OsiLicense2005a}
+completed by some definitions concerning a \enquote{Commercial
+Distribution}\footcite[cf.][\nopage wp\ §4]{Epl10OsiLicense2005a}: First it
+describes, what a distributor must do who wants to distribute an Eclipse
+licensed program as set of binaries. Then it describes, what must be done for
+compliantly distributing it as source code. Finally it lists two conditions
+which must be fulfilled in any case\footcite[cf.][\nopage wp\
+§3]{Epl10OsiLicense2005a}. With respect to this structure, we can detect the
+following tasks:
+
+\begin{itemize}
+
+ \item The EPL generally requires that \enquote{Contributors may not remove or
+ alter any copyright notices contained within the
+ Program}\footcite[cf.][\nopage wp\ §3]{Epl10OsiLicense2005a} whereas -- on the
+ one hand -- the word 'Contributor' has to be read as \enquote{any person or
+ entity that distributes the Program}, and -- on the other hand -- the word
+ 'Program' denotes the \enquote{initial contribution} and all its
+ modifications\footcite[cf.][\nopage wp\ §1]{Epl10OsiLicense2005a}. Similar to
+ the EUPL, also the EPL does not limit this requirement to the cases of
+ 'distributing' the software (\emph{4others}), at least in a very strict
+ reading. But -- in the cases of not distributing the software -- the control
+ of a license compliant use could be difficult without automatically switching
+ into the use case class 'distributing'. But in opposite to -- for example --
+ the EUPL, the EPL contains an interdiction. Nevertheless, the OSLiC not only
+ respects this interdiction, but also rewrites this negative condition as
+ positive assertion because it is important to actively control that the
+ existing copyright notes retain in exact the form one hase received them.
+ Thus, the OSLiC only inserts this activity as a mandatory clause for the
+ \emph{4others} use cases (EPL-2 - EPL-9).
+
+ \item Furthermore, the EPL requires that \enquote{each Contributor must
+ identify itself as the originator of its Contributions [\ldots] in a manner
+ that reasonably allows subsequent Recipients to identify the originator of the
+ Contribution}\footcite[cf.][\nopage wp\ §3]{Epl10OsiLicense2005a}, In this
+ case 'Contribution' has to be read as the \enquote{initial code and
+ documention} together with all subsequent modifications of these
+ parts\footcite[cf.][\nopage wp\ §1]{Epl10OsiLicense2005a}. For fulfilling this
+ condition faithfully, a developer must mark and describe his modifications of
+ a source code within this source code; and the distributor must describe these
+ modifications on the more general level of software features in a file
+ sometimes called CHANGES. On a first glance, the requirement to document the
+ source code modifications within the source code seems to be restricted to the
+ use cases which concern the distribution of a modified EPL software in the
+ form of source code. But the EPL allows the distribution in the form of
+ binaries only if the distributor also states where one can otain the
+ correspoding code\footcite[cf.][\nopage wp\ §3]{Epl10OsiLicense2005a}. So,
+ distributing the binaries implies the distribution of the source code.
+ Therefore the OSLiC inserts the two requirements as mandatory clauses into all
+ the use cases concerning the distribution of a modified EPL software (EPL-4 -
+ EPL-9).
+
+ \item For all distributions in the form of source code, the EPL requires that
+ the software \enquote{8\ldots] must be made available under this (Eclipse
+ Public License 1.0) Agreement} and that \enquote{[\ldots] a copy of this
+ Agreement must be included with each copy of the
+ Program}\footcite[cf.][\nopage wp\ §3]{Epl10OsiLicense2005a}. Thus, the OSLiC
+ inserts a respective mandatory clause into the use cases (EPL-4, EPL-6,
+ EPL-8). But the EPL is a license with a weak copyleft\footnote{($\rightarrow$
+ OSLiC, p.\ \pageref{sec:ProtectingPowerOfEpl})}. Therefore, this conditions
+ does not cover the overarching program which uses the embedded library (EPL-8)
+
+
+% TODO: unbedingt bei allen copyleft in binrar form auch die abarbeitung der
+
+
+
+\end{itemize}
+
+
+
+
+
+
%\bibliography{../../../bibfiles/oscResourcesEn}
View
66 snippets/en/06C-osFulfillmentByToDoLists/0605-euplFulfillToDoList.tex
@@ -25,7 +25,7 @@
\section{EUPL licensed software}
-The European Union Public License does explicitly distinguish the distribution
+The European Union Public License explicitly distinguishes the distribution
of the source code from that of the binaries: In the chapter
\enquote{Communication of the Source Code}, it allows to \enquote{provide the
Work either in its Source Code form, or as Executable
@@ -40,9 +40,10 @@ \section{EUPL licensed software}
respecting this conditions it is irrelevant whether the software has been
modified or not; and all the other \enquote{obligations of the licensee} refer
to both forms\footcite[cf.][\nopage wp\ §5]{EuplLicense2007en}. Thus, for
-getting simply processable task list, the following EUPL specific open source
-use case structure\footnote{For details of the general OSUC finder $\rightarrow$
-OSLiC, pp.\ \pageref{OsucTokens} and \pageref{OsucDefinitionTree}} can be used:
+finding the simply processable task lists, the following EUPL specific open
+source use case structure\footnote{For details of the general OSUC finder
+$\rightarrow$ OSLiC, pp.\ \pageref{OsucTokens} and \pageref{OsucDefinitionTree}}
+can be used:
\tikzstyle{nodv} = [font=\small, ellipse, draw, fill=gray!10,
text width=2cm, text centered, minimum height=2em]
@@ -157,7 +158,7 @@ \subsection{EUPL-1: Using the software only for yourself}
license with respect to this use case:
\begin{itemize}
\item You are allowed to use any kind of EUPL software in any sense and in
- any context without being obligied to do something as long as you do not
+ any context without being obliged to do something as long as you do not
give the software to 3rd parties.
\end{itemize}
@@ -290,8 +291,9 @@ \subsection{EUPL-4: Passing a modified program as source code}
notice file still does not exist. \emph{Expand} the \emph{modification text
file} by a description of your modifications.
- \item \textbf{[voluntary:]} Mark all modifications of source code of the
- embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
+ \item \textbf{[mandatory:]} Mark all modifications of source code of the
+ program\footnote{or application, or server} thoroughly -- namely within the
+ source code and including the date of the modification.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
your additional material also reproduce the content of the existing
@@ -342,8 +344,14 @@ \subsection{EUPL-5: Passing a modified program as binary}
explains how to the code can be received from where. Ensure, that this
repository is online for as long as you continue to distribute the software.
+ \item \textbf{[madatory:]} Execute the to-do list of use case EUPL-4\footnote{
+ Making the code accessible via a repository means distributing the software in
+ the form of source code. Hence, you must also fulfill all tasks of the
+ corresponding use case.}.
+
\item \textbf{[voluntary:]} Mark all modifications of source code of the
- embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
+ program\footnote{or application, or server} thoroughly -- namely within the
+ source code and including the date of the modification.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
your additional material also reproduce the content of the existing
@@ -390,8 +398,9 @@ \subsection{EUPL-6: Passing a modified library as independent source code}
notice file still does not exist. \emph{Expand} the \emph{modification text
file} by a description of your modifications.
- \item \textbf{[voluntary:]} Mark all modifications of source code of the
- embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
+ \item \textbf{[mandatory:]} Mark all modifications of source code of the
+ libary\footnote{or snippet, or module, or plugin} thoroughly -- namely within
+ the source code and including the date of the modification.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
your additional material also reproduce the content of the existing
@@ -443,10 +452,16 @@ \subsection{EUPL-7: Passing a modified library as independent binary}
integrate an easily to find descriptions into the distribution package which
explains how to the code can be received from where. Ensure, that this
repository is online for as long as you continue to distribute the software.
+
+ \item \textbf{[madatory:]} Execute the to-do list of use case EUPL-6\footnote{
+ Making the code accessible via a repository means distributing the software in
+ the form of source code. Hence, you must also fulfill all tasks of the
+ corresponding use case.}.
\item \textbf{[voluntary:]} Mark all modifications of source code of the
- embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
-
+ libary\footnote{or snippet, or module, or plugin} thoroughly -- namely within
+ the source code and including the date of the modification.
+
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
your additional material also reproduce the content of the existing
\emph{copyright notice text files}, a hint to the software name, a link to its
@@ -495,9 +510,10 @@ \subsection{EUPL-8: Passing a modified library as embedded source code}
\item \textbf{[mandatory:]} License your overarching program also under the
EUPL 1.1.
- \item \textbf{[voluntary:]} Mark all modifications of source code of the
- embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
-
+ \item \textbf{[mandatory:]} Mark all modifications of source code of the
+ embedded libary\footnote{or snippet, or module, or plugin} thoroughly --
+ namely within the source code and including the date of the modification.
+
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
your additional material also reproduce the content of the existing
\emph{copyright notice text files}, a hint to the name of the used EUPL
@@ -553,17 +569,25 @@ \subsection{EUPL-9: Passing a modified library as embedded binary}
you do not relicense the embedded library with respect to the list of
\enquote{compatible licenses accodring to article 5 EUPL} (\cite[cf.][\nopage
wp §5 and Appendix]{EuplLicense2007en}), you also have to publish the code of
- your overarching work.}: Push the source code package into a repository, make
- it downloadable via the internet, and integrate an easily to find descriptions
- into the distribution package which explains how to the code can be received
- from where. Ensure, that this repository is online for as long as you continue
- to distribute the software.
+ your overarching work.}: Push the source code package into a repository and
+ make it downloadable via the internet. Integrate an easily to find
+ descriptions into the distribution package which explains how to the code can
+ be received from where. Ensure, that this repository is online for as long as
+ you continue to distribute the software.
+
+ \item \textbf{[madatory:]} Execute the to-do list of use case EUPL-8\footnote{
+ Making the code accessible via a repository means distributing the software in
+ the form of source code. Hence, you must also fulfill all tasks of the
+ corresponding use case.}.
+
+
\item \textbf{[mandatory:]} License your overarching program also under the
EUPL 1.1.
\item \textbf{[voluntary:]} Mark all modifications of source code of the
- embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
+ embedded libary\footnote{or snippet, or module, or plugin} thoroughly --
+ namely within the source code and including the date of the modification.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
your additional material also reproduce the content of the existing
Please sign in to comment.
Something went wrong with that request. Please try again.