2 files changed, 301 insertions, 0 deletions
diff --git a/management/foss_basics/Makefile b/management/foss_basics/Makefile
new file mode 100644
index 0000000..e343f40
--- /dev/null
+++ b/management/foss_basics/Makefile
@@ -0,0 +1 @@
+obj-$(CONFIG_FOSS_BASICS) += pres_foss_basics_en.pdf
diff --git a/management/foss_basics/pres_foss_basics_en.tex b/management/foss_basics/pres_foss_basics_en.tex
new file mode 100644
index 0000000..3c446a1
--- /dev/null
+++ b/management/foss_basics/pres_foss_basics_en.tex
@@ -0,0 +1,300 @@
+\input{configpres}
+
+\title{\lq FOSS Basics\rq}
+\maketitle
+
+\subsection{The history of Open-Source}
+
+\begin{frame}
+\frametitle{Understanding the history}
+\begin{figure}[h]
+\centering
+\includegraphics[width=8cm]{images/Thompson-sitting-Richie-standing-PDP11-1972.jpg}
+\end{figure}
+\end{frame}
+
+\begin{frame}
+\frametitle{Understanding the history}
+\begin{itemize}
+\item Open-Source is not a new idea
+\item In the early days of big server systems it was common to deliver the source
+\item The HW manufacturers only did the HW
+\item Customers basically had to do bugfixing on their own
+\item There was no business model behind the Operating System Software
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\begin{figure}[h]
+\centering
+\includegraphics[width=7cm]{images/800px-IBM_PC_5150.jpg}
+\end{figure}
+The computer market changed and components became exchangable. So did
+Operating Systems.
+\end{frame}
+
+\begin{frame}
+\frametitle{Change of the business model}
+\begin{itemize}
+\item Companies changed their business model and Operating Systems turned into
+products
+\item Also the most common UNIX Systems became proprietary
+\item So, people using UNIX now had to pay just to use their
+existing software
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{The FSF}
+\begin{itemize}
+\item In 1983 Richard Stallman founded the Free Software Foundation
+\item He announced to implement a Free UNIX and to give it for free to anyone who wants to use it
+\item So, he also implemented a licensing model
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{The FSF}
+\begin{itemize}
+\item The FSF was quite successful in implementing a lot of tools
+\item But they didn't finish (even not until today) their operating system (GNU HURD)
+\end{itemize}
+\end{frame}
+
+\subsection{The story of Linux}
+
+\begin{frame}[fragile]
+\frametitle{Linux enters the scene}
+\begin{verbatim}
+Hello everybody out there using minix -
+
+I'm doing a (free) operating system (just a hobby,
+won't be big andprofessional like gnu) for
+386(486) AT clones.  This has been brewing 
+since april, and is starting to get ready.
+\end{verbatim}
+Linus Torvalds (1991 / Minix newsgroup)
+\end{frame}
+
+\begin{frame}
+\frametitle{Linux}
+\begin{itemize}
+\item Linux was implemented as a UNIX derivative / clone
+\item In 1992 Linux was relicensed under GPLv2 (the license designed by the FSF)
+\item Now, the Linux Kernel and the available tools from the FSF resulted
+in a completely free UNIX!!
+\item That was the start of a big success story
+\end{itemize}
+\end{frame}
+
+\subsection{Free Software}
+
+\begin{frame}
+\frametitle{Misunderstandings about Free Software}
+One of the main questions asked about Free Software is: How can I earn
+money with a software if it's free?
+\end{frame}
+
+\begin{frame}
+\frametitle{Misunderstandings about Free Software}
+\begin{itemize}
+\item The most popular explanation of Free Software is: ''Free as in FREEdom
+and not as in free beer...''
+\item It gives you the FREEDOM to use, study and re-distribute it.
+\item You can charge for the re-distribution!
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{More misunderstandings about Free Software}
+Another common misunderstanding is, that software which is published as
+Open-Source is not copyrighted:
+\begin{itemize}
+\item Licensing and Copyright are two different things!
+\item For sure: Also Open-Source software is copyrighted!!!
+\item It's just licensed under a Open-Source license!
+\end{itemize}
+\end{frame}
+
+\subsection{Why using Open-Source}
+
+\begin{frame}
+\frametitle{Focus on your knowledge}
+\begin{itemize}
+\item Concentrate on the things which are "unique" to your product
+\item For the ''rest'' co-operate with others
+\item We call this Open-Innovation (which is neither a new idea)
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{What makes your product unique?}
+You have to define the level of your specific know-how:
+\begin{figure}[h]
+\centering
+\includegraphics[width=7cm]{images/knowhow.jpg}
+\end{figure}
+\end{frame}
+
+\begin{frame}
+\frametitle{Faster time to market}
+\begin{itemize}
+\item Focussing on your knowledge results in a faster ''time to market''
+\item Sharing common things with others results in faster innovations
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Open Innovation also results in:}
+\begin{itemize}
+\item Lower costs
+\item Faster development
+\item Better products
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Flexibility}
+\begin{itemize}
+\item Huge choice of ex-changable componentes
+\item You can do adjustments on your own
+\item You can build the know-how on your own
+\item You can work with MANY contractors and you're not bound to one manufacturer
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{How Open-Source changed business}
+\begin{itemize}
+\item Over the years companies more and more took advantage of Open-Source
+\item Companies adjusted to the benefits of Open-Source
+\item Many modern business models just won't work without OSS (just think
+about Social Media and Web Services)
+\item So, Open-Source became also commercially driven
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Free Software vs. Open-Source}
+...or the shift in terminology.
+\end{frame}
+
+\begin{frame}
+\frametitle{Free Software vs. Open-Source}
+\begin{itemize}
+\item The idea of Free Software was originally based on the FREEDOM of using
+software
+\item A lot of explanation was needed for the term ''Free Software''
+\item During the 90s the term Open-Source was created
+\item This shift in the terminology also reflects the commercial success
+\end{itemize}
+\end{frame}
+
+\subsection{A different mindset}
+
+\begin{frame}
+\frametitle{But, ...}
+Open-Source also adds some complexity!
+\end{frame}
+
+\begin{frame}
+\frametitle{Formerly you had...}
+\begin{figure}[h]
+\centering
+\includegraphics[width=7cm]{images/contract_work.jpg}
+\end{figure}
+\end{frame}
+
+\begin{frame}
+\frametitle{With Open-Source you have...}
+\begin{figure}[h]
+\centering
+\includegraphics[width=7cm]{images/oss_integration.jpg}
+\end{figure}
+\end{frame}
+
+\begin{frame}
+\frametitle{It's faster, it's cheaper, it's more flexible...}
+...but it doesn't come for free!
+\end{frame}
+
+\subsection{How to use Open-Source}
+\begin{frame}
+
+\frametitle{Adopt to this mindset!}
+Working with Open-Source is mostly "integration work":
+\begin{itemize}
+\item So, you need a common process for integrating OSS software
+\item You need to understand which quality assurance is done by the
+community and what needs to be done on your own
+\item You need a concept for maintaining the software
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Setting up an Open-Source program in your company}
+\begin{itemize}
+\item License compliance
+\item Selecting components
+\item Maintaining components 
+\item Community Participation
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Selecting and packaging components}
+\begin{itemize}
+\item Define a responsible team / person for selecting new OSS components
+\item Define clear criterias for acceptable OSS components
+\item Build a database for existing components in your company
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Maintaining components}
+\begin{itemize}
+\item Define a responsible team / person for maintaining existing components
+\item Setup processes for bugfixes, security updates and change requests
+\item The ideal case is having some kind of ''internal linux distribution''
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{How will these processes help}
+\begin{itemize}
+\item Share bugfixing amongst projects (do not underestimate this advantage!!!)
+\item Speed-up estimations for new projects
+\item Speed-up license compliance topics
+\item Reduce the overhead of maintaining the components
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{What can you do to participate}
+\begin{itemize}
+\item Well, ''participate'' ;-)
+\item Sponsoring
+\item Hiring
+\item Conferences (presentations, ...)
+\end{itemize}
+It's always good to be known and accepted by the community / communities.
+\end{frame}
+
+\begin{frame}
+\frametitle{Why should I participate?}
+It's always good to be known and accepted by the community / communities!
+\begin{itemize}
+\item Bring in your own interests
+\item Getting support from the community
+\item Push back changes and bugfixes to hand-over maintainance to the community
+\end{itemize}
+\end{frame}
+
+\begin{frame}
+\frametitle{Now, ...}
+...let's get the hands dirty and implement the processes...\\
+But, don't forget: Before implementing processes you have to
+define a strategy and derive adequate policies.
+\end{frame}
+
+\input{tailpres}