Permalink
Browse files

2013-02-16: closure of the first feedback slot

  • Loading branch information...
1 parent 1f9e3ef commit 714d798e24c947d9bc23457568849ea9686b809b @kreincke kreincke committed Feb 16, 2013
View
@@ -1,3 +1,4 @@
+2012-02-16: closure of the integration of the results of the first call for reviews
2012-02-11: integrated the received feedback
2013-02-10: collection of
- refactoring the structure
View
@@ -56,7 +56,7 @@ dpdf: apdf
@ latex $<
@ latex $<
@ latex $<
- @ latex2rtf -o `basename $@ .rtf`-`cat release.tex`.rtf $<
+ @ latex2rtf -o `basename $@ .rtf`-`cat re-number.tex`.rtf $<
.dvi.ps:
@ echo "### `date +'%Y%m%dT%H%M%S'`"
@@ -67,11 +67,11 @@ dpdf: apdf
@ echo "### `date +'%Y%m%dT%H%M%S'`"
@ echo "### converting $< to $@"
@ ps2pdf $<
- @ mv $@ `basename $@ .pdf`-`cat release.tex`.pdf
+ @ mv $@ `basename $@ .pdf`-`cat rel-number.tex`.pdf
dist:
- tar -czvf ../${OSLICDIR}-`cat release.tex`.tar.gz --exclude=${OSLICDIR}/ecopies/* ../${OSLICDIR}
- zip -r ../${OSLICDIR}-`cat release.tex`.zip --exclude=../${OSLICDIR}/ecopies/* ../${OSLICDIR}
+ tar -czvf ../${OSLICDIR}-`cat rel-number.tex`.tar.gz --exclude=${OSLICDIR}/ecopies/* ../${OSLICDIR}
+ zip -r ../${OSLICDIR}-`cat rel-number.tex`.zip --exclude=../${OSLICDIR}/ecopies/* ../${OSLICDIR}
clearAuxFiles:
$(foreach EXT, ${AUX_EXTS}, if [ ! "x`ls *.${EXT} 2>/dev/null`" = "x" ]; then rm *.${EXT}; fi;)
@@ -27,22 +27,22 @@
% an 'and before last author explicetly written conjunction
% for authors in citations
-\renewcommand*{\jbbtasep}{ a. } % bta = between two authors sep
+\renewcommand*{\jbbtasep}{ a.\ } % bta = between two authors sep
\renewcommand*{\jbbfsasep}{, } % bfsa = between first and second author sep
-\renewcommand*{\jbbstasep}{, a. }% bsta = between second and third author sep
+\renewcommand*{\jbbstasep}{, a.\ }% bsta = between second and third author sep
% for editors in citations
-\renewcommand*{\jbbtesep}{ a. } % bta = between two authors sep
+\renewcommand*{\jbbtesep}{ a.\ } % bta = between two authors sep
\renewcommand*{\jbbfsesep}{, } % bfsa = between first and second author sep
-\renewcommand*{\jbbstesep}{, a. }% bsta = between second and third author sep
+\renewcommand*{\jbbstesep}{, a.\ }% bsta = between second and third author sep
% for authors in literature list
-\renewcommand*{\bibbtasep}{ a. } % bta = between two authors sep
+\renewcommand*{\bibbtasep}{ a.\ } % bta = between two authors sep
\renewcommand*{\bibbfsasep}{, } % bfsa = between first and second author sep
-\renewcommand*{\bibbstasep}{, a. }% bsta = between second and third author sep
+\renewcommand*{\bibbstasep}{, a.\ }% bsta = between second and third author sep
% for editors in literature list
-\renewcommand*{\bibbtesep}{ a. } % bte = between two editors sep
+\renewcommand*{\bibbtesep}{ a.\ } % bte = between two editors sep
\renewcommand*{\bibbfsesep}{, } % bfse = between first and second editor sep
-\renewcommand*{\bibbstesep}{, a. }% bste = between second and third editor sep
+\renewcommand*{\bibbstesep}{, a.\ }% bste = between second and third editor sep
% use: name, forname, forname lastname u. forname lastname
\jurabibsetup{authorformat=firstnotreversed}
@@ -31,8 +31,8 @@
manner, name their sponsor \textit{Deutsche Telekom AG} and link it to
\texttt{http://www.telekom.com}. In a paper-like reuse please insert a short
hint to \texttt{http://www.telekom.com}, to the initial authors, and to their
-sponsor \textit{Deutsche Telekom AG} into your preface. For normal quotations
-please use the scientific standard to cite.
+sponsor \textit{Deutsche Telekom AG} into your preface. For normal citations
+please use the scientific standard.
\newline
{ \tiny \itshape [derived from myCsrf (= 'mind your Scholar Research Framework')
\copyright K. Reincke CC BY 3.0 http://mycsrf.fodina.de/)] }}
@@ -33,4 +33,16 @@
\abbr[njear]{n.y.}{year not stated / no year}
\abbr[nlocation]{n.l.}{location not stated / no location}
\abbr[ub]{UB}{'Universitätsbibliothek' = library of university X}
-\abbr[ulb]{ULB}{'Universitäts- \& Landesbibliothek' = library of university and state X}
+\abbr[ulb]{ULB}{'Universitäts- \& Landesbibliothek' = library of university and state X}
+\abbr[apl]{ApL}{Apache License}
+\abbr[bsd]{BSD}{Berkeley Software Distrobution (License)}
+\abbr[mit]{MIT}{Massachusetts Institute of Technology (License)}
+\abbr[mspl]{Ms-PL}{Microsoft Public License}
+\abbr[pgl]{PgL}{Postgres License}
+\abbr[php]{PHP}{PHP (License)}
+\abbr[epl]{EPL}{Eclipse Public License}
+\abbr[eupl]{EUPL}{European Public License}
+\abbr[lgpl]{LGPL}{GNU Lesser General Public License}
+\abbr[mpl]{MPL}{Mozilla Public License}
+\abbr[gpl]{GPL}{GNU General Public License}
+\abbr[agpl]{AGPL}{GNU Affero General Public License}
View
@@ -130,6 +130,7 @@
\usepackage{nameref}
+
\counterwithout{footnote}{chapter}
\usepackage[intoc]{nomencl}
@@ -155,14 +156,21 @@
%% \nocite{*}
%%-- start(titlepage)
-\titlehead{Release \input{release}}
+\titlehead{Version \input{rel-number} % -- \input{rel-date}
+}
\subject{\small \itshape A Practical Guide for Developers, Managers, OS Experts,
and Companies}
\title{Open Source License Compendium}
-\subtitle{How to Achieve Open Source License Compliance}
-\author{K. Reincke, G. Sharpe \input{btexmat/oscLicenseFootnoteInc}}
+\subtitle{How to Achieve Open Source License Compliance\input{btexmat/oscLicenseFootnoteInc}}
+\author{
+Karsten Reincke\thanks{Deutsche Telekom AG, Products \& Innovation,
+T-Online-Allee 1, 64295 Darmstadt}
+\and
+Greg Sharpe\thanks{Deutsche Telekom AG, Telekom Deutschland GmbH,
+Landgrabenweg, Bonn}}
+
\maketitle
%%-- end(titlepage)
@@ -181,6 +189,7 @@
Eitan Adler,\\
John Dobson, \\
Steffen Härtlein, \\
+Ta'Id Holmes, \\
Michael Kern,\\
Michael Machado,\\
Thomas Quiehl,\\
@@ -258,15 +267,6 @@ \chapter{Appendices}
\input{snippets/en/09C-Appendices/0903-ProlegomenaInc}
-% \section{Prolegomena}
-% \input{snippets/en/09C-Appendices/0b03a-prolegomenaAbstractInc}
-% \input{snippets/en/09C-Appendices/0b03b-why01Inc}
-% \input{snippets/en/09C-Appendices/0b03c-APC-LicenseMissedInc}
-% \input{snippets/en/09C-Appendices/0b03d-ifrossWithoutGuideInc}
-% \input{snippets/en/09C-Appendices/0b03e-AnotherCompendiumTryInc}
-%
-% \input{snippets/en/09C-Appendices/0b03f-why02Inc}
-% \input{snippets/en/09C-Appendices/0b03g-whatInc}
\small
%\theendnotes
View
@@ -0,0 +1 @@
+February, 2013
File renamed without changes.
@@ -29,15 +29,15 @@ \chapter{Introduction}
% Abstract
\footnotesize \begin{quote}\itshape
This chapter briefly describes the idea behind the OSLiC, the way it should be
-used and the way it can be read - which is indeed not quite the same.
+used and the way it can be read -- which is indeed not quite the same.
\end{quote}
\normalsize{}
% Content
This book focuses on just one issue: \emph{What needs to be done in order to act
in accordance with the licenses of those \emph{open source software} we use?}
The \emph{Open Source License Compendium} aims at reliably answering this
-question - in a simple and easy to understand manner. However, it is not just
+question -- in a simple and easy to understand manner. However, it is not just
another book on \emph{open source} in ge\-ne\-ral\footnote{Meanwhile, there are
tons of literature dealing with open source. By expanding your knowledge by
means of books and articles you might get lost in literature: our list of
@@ -47,7 +47,7 @@ \chapter{Introduction}
the background information we did not directly cite in the OSLiC. If we were
forced to indicate two books for attaining a good overview on the topic of
\emph{open source (licenses)} we would name (a) the 'Rebel Code' (\cite[for a
-German version cf.][\nopage passim]{Moody2001a} - \cite[for an English version
+German version cf.][\nopage passim]{Moody2001a} -- \cite[for an English version
cf.][passim]{Moody2002a}) and (b) the 'legal basic conditions'
(\cite[cf.][\nopage passim]{JaeMet2011a}). But fortunately, we are not forced to
do so.}. The intention is, rather, for it to be a tool for simplifying the
@@ -60,13 +60,13 @@ \chapter{Introduction}
precisely must be done in order to comply with the license of that piece of open
source being used.
-As some of these co-workers in Telekom projects, even we - the initial authors
-of the OSLiC - did not want to become open source license experts only for being
+As some of these co-workers in Telekom projects, even we -- the initial authors
+of the OSLiC -- did not want to become open source license experts only for being
able to use open source software in accordance with the respective licenses. We
did not want to become lawyers. We just wanted to do more efficiently, what
in those days claimed much time and many resources. We were searching for clear
guidance instead of having to determine a correct way through the jungle of open
-source licenses - over and over again, project for project. We loved using the
+source licenses -- over and over again, project for project. We loved using the
high-quality open source software to improve our performance. We liked using it
legally. But we did not like to laboriously discuss the legal constraints of the
many and different open source licenses.
@@ -88,16 +88,16 @@ \chapter{Introduction}
are acting according to the corresponding open source licenses. The idea behind
this decision was simple. It would save cost and increase quality if one had one
central group of experts instead of being obliged to select (and to train)
-developers - over and over again, for every new project. So, the \emph{OSRB} -
-the \emph{Telekom Open Source Review Board} - was founded as an internal expert
-group - as a self-organizing, bottom-up driven community.
+developers -- over and over again, for every new project. So, the \emph{OSRB} --
+the \emph{Telekom Open Source Review Board} -- was founded as an internal expert
+group -- as a self-organizing, bottom-up driven community.
The second decision our company took, was to allow this \emph{Telekom OSRB} to
-collect their results systematically . The idea behind this decision was also
+collect their results systematically. The idea behind this decision was also
simple: The more the internal service becomes known, the more the workload will
increase: the more work, the more recources, the more costs. So, the idea was to
save costs and enable the requestors to find answers by themselves without
-becoming license experts - but simply without becoming licenses experts: For all
+becoming license experts -- but simply without becoming licenses experts: For all
default cases, they should find an answer in the compendium instead of having to
request that their work be analyzed by the OSRB. Thus, the planned \emph{Telekom
Open Source License Compendium} prevents Telekom from having to increase the
@@ -106,7 +106,7 @@ \chapter{Introduction}
The third decision our company reached, was to allow the \emph{Telekom OSRB} to
create the compendium in the same mode of cooperation, open source projects
usually use. Again, a simple reason evoked this ruling: If in the future
-- as a rule - not a reviewing OSRB, but a simple manual should assure the open
+-- as a rule -- not a reviewing OSRB, but a simple manual should assure the open
source license compliant behavior of projects, programmers and managers, this
book had of course to be particularily reliable. There is a known feature of the
open source working model: the ongoing review by the cooperating community
@@ -133,7 +133,7 @@ \chapter{Introduction}
sponsor \textit{Deutsche Telekom AG} into your preface. For normal citations
please use the scientific standard.}.
-But to publish the \emph{OSLiC} as a free book has another important connotation -
+But to publish the \emph{OSLiC} as a free book has another important connotation --
at least for the \emph{Telekom OSRB}: It is also intended to be an appreciative
\emph{giving back} to the \emph{open source community} which has enriched and
simplified the life of so many employees and companies over so many years.
@@ -154,30 +154,30 @@ \chapter{Introduction}
and why\footnote{For that purpose, we are using an 'old-fashioned'
bibliographic style with footnotes, instead of endnotes or inline-hints.
We want to enable the users to review or to ignore our comments and hints just
- as they prefer - but on all accounts without being disturbed by large inline
+ as they prefer -- but on all accounts without being disturbed by large inline
comments or frequent page turnings. We know that modern writer guides prefer
less 'noisy' styles (\cite[pars pro toto cf.][\nopage passim]{Mla2009a}). But
- for a reliable usage - challenged by the often modified internet sources -
+ for a reliable usage -- challenged by the often modified internet sources --
these methods are still a little imprecise (for details $\rightarrow$
- \enquote{sec:QuotationAppendix}, pp. \pageref{sec:QuotationAppendix} . For a
+ \enquote{sec:QuotationAppendix}, pp.\ \pageref{sec:QuotationAppendix}. For a
short motivation of the style used in the OSLiC \cite[cf.][\nopage
passim]{Reincke2012a}. For a more elaborated legitimizing version
\cite[cf.][\nopage passim]{Reincke2012b}) }.
\item[No clearing the forest, but cutting a swath]: The OSLiC
has to deal with licenses and their legal aspects, no doubt. But it shall not
discuss all details of every aspect. It shall focus on one possible way to act
- according to a license in a specific usecase - even it is known that there
+ according to a license in a specific usecase -- even it is known that there
might be alternatives\footnote{The OSLiC shall not counsel projects with
respect to their specific needs. This must remain the task for lawyers and
- legal experts. They can assess whether a project with its' specfic conditions
+ legal experts. They can assess whether a project with its specfic conditions
could also / better use another way to fulfill the open source license.}.
\item[Take the license text seriously]: The OSLiC shall not give general
lectures on legal discussions, much less shall it participate in them. It
shall only find one dependable way for each license and each usecase to comply
with the license. The main source for this analysis shall be the exact reading
- of the open source licenses themselves - based on and supported by the
+ of the open source licenses themselves -- based on and supported by the
interpretation of benevolent lawyers and rational argueing software
developers. The OSLiC shall respect that open source licenses are written for
software developers (and sometimes by developers).
@@ -191,7 +191,7 @@ \chapter{Introduction}
First and foremost the readers expect to simply and quickly find those to-do
lists fitting their needs. Here is the respective process\footnote{For the well
-known 'quick and dirty hackers' - as we tend to be, too - we have integrated a
+known 'quick and dirty hackers' -- as we tend to be, too -- we have integrated a
shortcut: If you already know the license of the open source package you want to
use and if you are very familiar with the meaning of the open source use cases
we defined, then you might directly jump to the corresponding license specific
@@ -201,7 +201,7 @@ \chapter{Introduction}
\textbf{O}pen \textbf{S}ource \textbf{U}se \textbf{C}ase page ($\rightarrow$
\pageref{OSUCList}ff.): Each of the open source license specficic chapters
starts with a license specific finder offering a set of license specific use
-cases - which according to the complexity of the license - in some cases could
+cases -- which according to the complexity of the license -- in some cases could
be stripped down. But the disdadvantage of this method is that you have to apply
your knowledge about the use cases and their side effects by yourself without
the systematic control of the full OSLiC process as presented here.}:
@@ -288,11 +288,11 @@ \chapter{Introduction}
behavior\footnote{$\rightarrow$ \enquote{\nameref{sec:LicenseTaxonomies}}, pp.
\pageref{sec:LicenseTaxonomies}}. We consider some side effects with
regard to act according to the open source licenses\footnote{$\rightarrow$
-\enquote{\nameref{sec:SideEffects}}, pp. \pageref{sec:SideEffects}}. And we
+\enquote{\nameref{sec:SideEffects}}, pp.\ \pageref{sec:SideEffects}}. And we
study the structure of open source use cases\footnote{$\rightarrow$
-\enquote{\nameref{sec:OSUCdeduction}}, pp. \pageref{sec:OSUCdeduction}}.
+\enquote{\nameref{sec:OSUCdeduction}}, pp.\ \pageref{sec:OSUCdeduction}}.
-So, let's close our introduction by using, modifying, and (re)distributing a well
+So, let us close our introduction by using, modifying, and (re)distributing a well
known wish of a well known man: Happy (Legally) Hacking.
%\bibliography{../../../bibfiles/oscResourcesEn}
Oops, something went wrong.

0 comments on commit 714d798

Please sign in to comment.