thesis: introduction WIP

src/docs/parts/introduction/introduction.tex

@@ -1,36 +1,56 @@
 % // vim: set ft=tex:
 
 \chapter{Introduction}
-
 % Chapter 1, with a highly focused review of the literature, and is normally the “prospectus” that a committee approves before the “proposal” to start research is approved.  After the prospectus is approved, some of the review of literature may be moved into Chapter 2, which then becomes part of the proposal to do research.  
 % Chapter 1 is the engine that drives the rest of the document, and it must be a complete empirical argument as is found in courts of law.  It should be filled with proofs throughout.  It is not a creative writing project in a creative writing class; hence, once a word or phrase is established in Chapter 1, use the same word or phrase throughout the dissertation.  The content is normally stylized into five chapters, repetitive in some sections from dissertation to dissertation. A lengthy dissertation may have more than five chapters, but regardless, most universities limit the total number of pages to 350 due to microfilming and binding considerations in libraries in those institutions requiring hard copies.
 % Use plenty of transitional words and sentences from one section to another, as well as subheadings, which allow the reader to follow the writer’s train of thought.  Following is an outline of the content of the empirical argument of Chapter 1. Universities often arrange the content in a different order, but the subject matter is the same in all dissertations because it is an empirical “opening statement” as might be found in a court of law. (Note that a dissertation could also be five pages of text and 50 pages of pictures of dragonfly wings and qualify for a Doctor’s degree in entomology.)
 
 %State the general field of interest in one or two paragraphs, and end with a sentence that states what study will accomplish. Do not keep the reader waiting to find out the precise subject of the dissertation.
-This thesis is about building and packaging software applications specifically with the intention to distribute them in form of \glspl{apci}.
+This thesis is about building and packaging software applications specifically with the intention to distribute them in form of \glspl{apci} on systems running a \gls{Linux} based \gls{OS}.
 The primary concern is to find a viable method for declaring and assembling \glspl{apci} deterministically and ideally being able to reproducible these builds on different computers and different points in time.
 The secondary concern is to abstract enough of the method's complexity in order to make it attractive for application developers while still allowing them to specify the exact contents alongside their software within the resulting \gls{apci}.
 
 The choice for this topic was made due to my personal dissatisfaction with currently available methods for building \glspl{apci}, and seeing both the need and the potential of a scientifically substantiated approach.
-My hope that is that the abstraction makes it simple enough to be adopted by the community which has been forming around the technology of \glspl{apc} and its ever-growing popularity since \gls{Docker} was released.
 
+This chapter will cover the knowledge that is necessary to understand the problem and the development of technology and mindsets of technology users, leading to the current situation.
 
-\section{Background of the Problem}
+\section{The Advent of \glspl{apc}}
+% Background of the Problem 
 % This section is critically important as it must contain some mention of all the subject matter in the following Chapter 2 Review of the Literature 2 and the methodology in Chapter 3. Key words should abound that will subsequently be used again in Chapter 2. The section is a brief  two to four page summary of the major findings in the field of interest that cites the most current finding in the subject area. A minimum of two to three citations to the literature per paragraph is advisable. The paragraphs must be a summary of unresolved issues, conflicting findings, social concerns, or educational, national, or international issues, and lead to the next section, the statement of the problem. The problem is the gap in the knowledge. The focus of the Background of the Problem is where a gap in the knowledge is found in the current body of empirical (research) literature.
 
-\section{Statement of the Problem}
+% TODO: refer and limit scope to the FOSS/Linux, maybe Jails? Explain why not closed-source kernels (community, collaboration)
+% TODO: explain generically what APC is and compare to Hypervisors
+% TODO: explain performance and resource allocation overhead/flexibility
+% TODO: refer to Linux Namespaces and Cgroups
+
+\gls{Docker}, since with its release in 2013 (TODO reference), has brought \glspl{apc} to the attention and hands of the masses in the \gls{FOSS} community.
+From a psychological standpoint this is not surprising, as it has abstracted most of complexities of the technology, and has added ease of deployment with a platform for hosting the \gls{apci} in a Docker specific format, as well as a very convenient tool for building the like.
+Its popularity has come to a point where the term \textit{Docker} is being used interchangeably (TODO: do I need references for this?) with the \gls{apc} technology itself.
+
+One major issue I'm seeing that I want to discuss here is that, according to my subjective impression, there is a deficiency in education.
+
+What is referred to as \gls{apc} within the scope of this work has it's origins 
+
+The \gls{apc} technology that is openly available today, such as \gls{Docker},
+
+\section{No proved methods to declare, reproduce, and trust the builds of \glspl{apci}}
+% Statement of the Problem 
 % Arising from the background statement is this statement of the exact gap in the knowledge discussed in previous paragraphs that reviewed the most current literature found. A gap in the knowledge is the entire reason for the study, so state it specifically and exactly. Use the words “gap in the knowledge.” The problem statement will contain a definition of the general need for the study, and the specific problem that will be addressed.
 
 \section{Purpose of the Study}
+% Purpose of the Study
 %The Purpose of the Study is a statement contained within one or two paragraphs that identifies the research design, such as qualitative, quantitative, mixed methods, ethnographic, or another design. The research variables, if a quantitative study, are identified, for instance, independent, dependent, comparisons, relationships, or other variables. The population that will be used is identified, whether it will be randomly or purposively chosen, and the location of the study is summarized. Most of these factors will be discussed in detail in Chapter 3.
 
 \section{Significance of the Study}
+% Significance of the Study
 % The significance is a statement of why it is important to determine the answer to the gap in the knowledge, and is related to improving the human condition. The contribution to the body of knowledge is described, and summarizes who will be able to use the knowledge to make better decisions, improve policy, advance science, or other uses of the new information. The “new” data is the information used to fill the gap in the knowledge.
 
 \section{Primary Research Questions}
+% Primary Research Questions
 % The primary research question is the basis for data collection and arises from the Purpose of the Study. There may be one, or there may be several. When the research is finished, the contribution to the knowledge will be the answer to these questions. Do not confuse the primary research questions with interview questions in a qualitative study, or survey questions in a quantitative study. The research questions in a qualitative study are followed by both a null and an alternate hypothesis.
 
 \section{Hypotheses}
+% Hypotheses
 % A hypothesis is a testable prediction for an observed phenomenon, namely, the gap in the knowledge. Each research question will have both a null and an alternative hypothesis in a quantitative study. Qualitative studies do not have hypotheses. The two hypotheses should follow the research question upon which they are based. Hypotheses are testable predictions to the gap in the knowledge. In a qualitative study the hypotheses are replaced with the primary research questions.
 
 This should be possible with the help of a package manager that source-based packages, by specifying the container image content by referencing packages in a declarative manner.

src/docs/thesis.tex

@@ -60,6 +60,20 @@
                                      {\normalfont\normalsize\bfseries}}
 \makeatother
 
+\newglossaryentry{OS}{
+    name = Operating System,
+    description = {
+        TODO
+    },
+}
+
+\newglossaryentry{FOSS}{
+    name = Free and Open-Source Software,
+    description = {
+        TODO
+    },
+}
+
 \newglossaryentry{Linux}{
     name = Linux,
     description = {
@@ -79,27 +93,34 @@
 \newglossaryentry{apc}{
     name=Application Program Container,
     description={
-        The broad term for the technology used to build, package, distribute and run an application program in isolation from the underlying and co-existing systems, wherein the level or technique of isolation can be different depending on the \gls{apcr}
+        The broad term for the technology used to build, package, distribute and run an application program in isolation from the underlying and co-existing systems, wherein the level or technique of isolation can be different depending on the \gls{apcr}.
     }
 }
 \newglossaryentry{apci}{
     name=Application Program Container Image,
     description={
-        An archive file that contains all of the necessary binaries that are needed to execute an application and a manifest file that that contains metadata about the application. Alternatively to containing all the required binary files, the manifest file can declare dependencies to other application container images, which must then be available at runtime to execute the contained application
+        An archive file that contains all of the necessary binaries that are needed to execute an application and a manifest file that that contains metadata about the application. Alternatively to containing all the required binary files, the manifest file can declare dependencies to other application container images, which must then be available at runtime to execute the contained application.
     }
 }
 
 \newglossaryentry{apcr}{
     name=Application Program Container Runtime,
     description={
-        An application program or a collection thereof that understands how to run the software inside an \gls{apci}
+        An application program (suite) that understands how to run the software inside an \gls{apci}.
+    }
+}
+
+\newglossaryentry{LXC}{
+    name=LXC,
+    description={
+        TODO
     }
 }
 
 \newglossaryentry{Docker}{
     name=Docker,
     description={
-        is a an \gls{apc} platform, with an application program of the same name
+        A very popular \gls{apc} platform and application suite, providing functionality to build and deploy Docker specific \glspl{apci}.
     }
 }