diff --git a/Manuals/Docbook/repository-parts/Repository.docbook b/Manuals/Docbook/repository-parts/Repository.docbook
deleted file mode 100644
index f601bbd..0000000
--- a/Manuals/Docbook/repository-parts/Repository.docbook
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<part>
- <title>The Repository</title>
-
- &repo-history;
- &repo-copying;
- &repo-usage;
- &repo-directories;
-
-</part>
diff --git a/Manuals/Docbook/repository-parts/Repository/Copying.docbook b/Manuals/Docbook/repository-parts/Repository/Copying.docbook
deleted file mode 100644
index 1dfe080..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Copying.docbook
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repo-copying-chapter" xreflabel="Copying">
-
- <title>Copying conditions</title>
-
- <para>Copyright © 2009, 2010, 2011 The CentOS Project</para>
- <para>Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.</para>
-
- &repo-copying-preamble;
- &repo-copying-the-centos-brand;
-
-</chapter>
diff --git a/Manuals/Docbook/repository-parts/Repository/Copying/preamble.docbook b/Manuals/Docbook/repository-parts/Repository/Copying/preamble.docbook
deleted file mode 100644
index 4bd4737..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Copying/preamble.docbook
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-copying-section-1" xreflabel="Preamble" label="2.1">
-
- <title>Preamble</title>
-
- <para>The CentOS Artwork Repository organizes files in a very
- specific way to implement The CentOS Project corporate visual
- identity. This very specific organization of files must be
- considered part of <command>centos-art.sh</command> script, a bash
- script that automate most of the frequent tasks inside the
- repository.</para>
-
- <para>The <command>centos-art.sh</command> script and the
- organization of files it needs to work are not in the public
- domain; they are copyrighted and there are restrictions on their
- distribution, but these restrictions are designed to permit
- everything that a good cooperating citizen would want to do. What
- is not allowed is to try to prevent others from further sharing
- any version of this program that they might get from you.</para>
-
- <para>Specifically, we want to make sure that you have the right
- to give away copies of <command>centos-art.sh</command> script and
- the organization of files it needs to work, that you receive
- source code or else can get it if you want it, that you can change
- this program or use pieces of it in new free programs, and that
- you know you can do these things.</para>
-
- <para>To make sure that everyone has such rights, we have to
- forbid you to deprive anyone else of these rights. For example,
- if you distribute copies of the <command>centos-art.sh</command>
- script, you must give the recipients all the rights that you have.
- You must make sure that they, too, receive or can get the source
- code. And you must tell them their rights.</para>
-
- <para>Also, for our own protection, we must make certain that
- everyone finds out that there is no warranty for the
- <command>centos-art.sh</command> script. If this program is
- modified by someone else and passed on, we want their recipients
- to know that what they have is not what we distributed, so that
- any problems introduced by others will not reflect on our
- reputation.</para>
-
- <para>The <command>centos-art.sh</command> script is released as a
- GPL work. Individual packages used by
- <command>centos-art.sh</command> script include their own licenses
- and the <command>centos-art.sh</command> script license applies to
- all packages that it does not clash with. If there is a clash
- between the <command>centos-art.sh</command> script license and
- individual package licenses, the individual package license
- applies instead.</para>
-
- <para>The precise conditions of the license for the
- <command>centos-art.sh</command> script are found in the <xref
- linkend="licenses-gpl" />. This manual specifically is
- covered by the <xref linkend="licenses-gfdl" />.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Copying/the-centos-brand.docbook b/Manuals/Docbook/repository-parts/Repository/Copying/the-centos-brand.docbook
deleted file mode 100644
index 071b4f7..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Copying/the-centos-brand.docbook
+++ /dev/null
@@ -1,25 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-copying-section-2" xreflabel="The CentOS Brand" label="2.2">
-
- <title>The CentOS Brand</title>
-
- <para>The CentOS Brand () is the main visual manifestaion of The
- CentOS Project. The CentOS Project uses The CentOS Brand to
- connect all its visual manifestions (e.g., GNU/Linux
- Distributions, Websites, Stationery, etc.) and, this way, it
- provides recognition among other similar projects available on the
- Internet.</para>
-
- <para>Both The CentOS Brand and all the visual manifestations that
- derivate from it are available for you to study and propose
- improvement around a good citizen's will at The CentOS Community
- environment, but you are not allowed to redistribute them
- elsewhere, without the given permission of The CentOS
- Project.</para>
-
- <para>If you need to redistribute either The CentOS Brand or any
- visual manifestation derived from it, write your intentions to the
- The CentOS Developers mailing list
- (centos-devel@centos.org).</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Directories.docbook b/Manuals/Docbook/repository-parts/Repository/Directories.docbook
deleted file mode 100644
index c0bdc56..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Directories.docbook
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repo-dirs-chapter" xreflabel="Chapter 4. Directories">
-
- <title>Directories</title>
-
- <para>The CentOS Artwork Repository uses directories to organize
- files and describe conceptual idea about corporate identity. Such
- conceptual ideas are explained in each directory related
- documentation entry.</para>
-
- <para>In this chapter you'll learn what each directory inside The
- CentOS Artwork Repository is for and so, how you can make use of
- them. For that purpose, the following list of directories is
- available for you to explore:</para>
-
- &repo-dirs-trunk;
- &repo-dirs-trunk-identity;
- &repo-dirs-trunk-identity-models;
- &repo-dirs-trunk-identity-models-themes;
- &repo-dirs-trunk-identity-models-themes-default;
- &repo-dirs-trunk-manuals;
-
-</chapter>
diff --git a/Manuals/Docbook/repository-parts/Repository/History.docbook b/Manuals/Docbook/repository-parts/Repository/History.docbook
deleted file mode 100644
index 41cf7f9..0000000
--- a/Manuals/Docbook/repository-parts/Repository/History.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repo-history-chapter" xreflabel="History">
-
- <title>History</title>
-
- <para>This chapter describes, briefly, where we've been and where
- we're going to with the CentOS Artwork Repository.</para>
-
- &repo-history-2008;
- &repo-history-2009;
- &repo-history-2010;
- &repo-history-2011;
-
-</chapter>
diff --git a/Manuals/Docbook/repository-parts/Repository/History/2008.docbook b/Manuals/Docbook/repository-parts/Repository/History/2008.docbook
deleted file mode 100644
index 9cd57f2..0000000
--- a/Manuals/Docbook/repository-parts/Repository/History/2008.docbook
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-history-section-1" label="1.1">
-
- <title>2008</title>
-
- <para>The CentOS Artwork Repository started at <ulink
- url="mailto:centos-devel@centos.org">CentOS Developers mailing
- list</ulink> during a discussion about how to automate the slide
- images of Anaconda. In such discussion, Ralph Angenendt rose up
- his hand to ask: Do you have something to show?</para>
-
- <para>To answer the question, Alain Reguera Delgado suggested a
- bash script which combined SVG and SED files in order to produce
- PNG images in different languages —together with the
- proposition of creating a Subversion repository where translations
- and image production could be distributed inside The CentOS
- Community—.</para>
-
- <para>Karanbirn Sighn considered the idea intresting and provided
- the infrastructure necessary to support the effort. This way the
- <ulink url="https://projects.centos.org/trac/artwork/">CentOS
- Artwork SIG</ulink> and the <ulink
- url="https://projects.centos.org/svn/artwork/">CentOS Artwork
- Repository</ulink> were officially created.</para>
-
- <para>Once the CentOS Artwork Repository was available, Alain
- Reguera Delagdo uploaded the bash script for rendering Anaconda
- slides; Ralph Angenendt documented it very well; and people
- started to download working copies of CentOS Artwork Repository to
- produce slide images in their own languages.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/History/2009.docbook b/Manuals/Docbook/repository-parts/Repository/History/2009.docbook
deleted file mode 100644
index 9a3b493..0000000
--- a/Manuals/Docbook/repository-parts/Repository/History/2009.docbook
+++ /dev/null
@@ -1,47 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-history-section-2" label="1.2">
-
- <title>2009</title>
-
- <para>The rendition script was at a very rustic state where only
- slide images could be produced, so it was redesigned to extend the
- image production to other areas, not just slide images. In this
- configuration, one SVG file was used as input to produce a
- translated instance of it which, in turn, was used to produce one
- translated PNG image as output. The SVG translated instance was
- created through SED replacement commands. The translated PNG image
- was created from the SVG translated instance using Inkscape
- command-line interface.</para>
-
- <para>The rendition script was named
- <quote>render.sh</quote>.</para>
-
- <para>The repository directory structure was prepared to receive
- the rendition script using design templates and translation files
- in the same location. There was one directory structure for each
- artwork that needed to be produced. In this configuration, if you
- would want to produce the same artwork with a different visual
- style or structure, it was needed to create a new directory
- structure for it because both the image structure and the image
- visual style were together in the design template.</para>
-
- <para>The rendition script was moved to a common place and linked
- from different directory structures. There was no need to have the
- same code in different directory structures if it could be in just
- one place and then be linked from different locations.</para>
-
- <para>The concepts about corporate identity began to be
- considered. As referece, it was used the book <quote>Corporate
- Identity</quote> by Wally Olins (1989) and Wikipedia (<ulink
- url="http://en.wikipedia.org/Corporate_identity" />). This way,
- the rendition script main's goal becomes to: automate production
- of a monolithic corporate visual identity structure, based on the
- mission and the release schema of The CentOS Project.</para>
-
- <para>The directory structures started to be documented inside the
- repository using text files without markup. Later, documentation
- in flat text files was moved to LaTeX format and this way
- <quote>The CentOS Artwork Repository Manual</quote> started to
- take form.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/History/2010.docbook b/Manuals/Docbook/repository-parts/Repository/History/2010.docbook
deleted file mode 100644
index 0ff7031..0000000
--- a/Manuals/Docbook/repository-parts/Repository/History/2010.docbook
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-history-section-3" label="1.3">
-
- <title>2010</title>
-
- <para>The rendition script changed its name from
- <command>render.sh</command> to <command>centos-art.sh</command>
- and became a collection of functionalities where rendition was
- just one among others (e.g., documenting and localizing).</para>
-
- <para>The <command>centos-art.sh</command> was created to organize
- automation of most frequent tasks inside the repository. There
- was no need to have links all around the repository if a
- command-line interface could be created (through symbolic links,
- in the <filename class="directory">~/bin</filename> directory) and
- be called anywhere inside the repository as it would be a regular
- command.</para>
-
- <para>Inside <command>centos-art.sh</command>, functionalities
- started to get identified and separated one another. For example,
- when images were rendered, there was no need to load
- functionalities related to documentation manual. This layout moved
- us onto common functionalities and specific functionalities inside
- <command>centos-art.sh</command> script. Common functionalities
- are loaded when <command>centos-art.sh</command> script is
- initiated and are available to specific functionalities.</para>
-
- <para>The <command>centos-art.sh</command> script was redesigned
- to handle command-line options trough <command>getopt</command>
- option parser.</para>
-
- <para>The repository directory structure was updated to improve
- the implementation of concepts related to corporate visual
- identity. Specially in the area related to themes which were
- divided into <emphasis>design models</emphasis> and
- <emphasis>artistic motifs</emphasis> to eliminate the content
- duplication produced by having both image structure and image
- visual style in the same file. Now, themes are produced as result
- of arbitrary combinations of both design models (structures) and
- artistic motifs (visual styles).</para>
-
- <para>In the documentation area, the documentation files in LaTeX
- format were migrated to Texinfo format. In this configuration,
- each directory structure in the repository has a documentation
- entry associated in a Texinfo structure which can be read, edited
- and administered (e.g., renamed, deleted, copied) interactively
- throuch <command>centos-art.sh</command>. Additionally, the
- <command>texi2html</command> program was used to produced XHTML
- output customized by CSS from The CentOS Webenv.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/History/2011.docbook b/Manuals/Docbook/repository-parts/Repository/History/2011.docbook
deleted file mode 100644
index 3fe1641..0000000
--- a/Manuals/Docbook/repository-parts/Repository/History/2011.docbook
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-history-section-4" label="1.4">
-
- <title>2011</title>
-
- <para>The <command>centos-art.sh</command> script was redesigned
- to start translating SVG and other XML-based files (e.g., XHTML
- and Docbook files) through the <command>xml2po</command> program
- and shell scripts files (e.g., Bash scripts) through GNU
- <command>gettext</command> tools. This configuration provided a
- stronger interface for graphic designers, translators and
- programmers to produce localized content. The SED files are no
- longer used to handle translations.</para>
-
- <para>Improve option parsing through
- <command>getopt</command>.</para>
-
- <para>Consolidate the <code>render</code>, <code>help</code> and
- <code>locale</code> functionalities as the most frequent tasks
- performed inside the repository. Additionally, the
- <code>prepare</code> and <code>tuneup</code> functionalities are
- maintained as useful tasks.</para>
-
- <para>The <command>centos-art.sh</command> script is updated to
- organize functionalities in two groups: <quote>the administrative
- functionalities</quote> and <quote>the productive
- functionalities</quote>. The administrative functionalities cover
- actions like: copying, deleting and renaming directory structures
- inside the repository. Also, preparing your workstation for using
- <command>centos-art.sh</command> script, making backups of the
- distribution theme currently installed, installing themes created
- inside repository and restoring themes from backup. On the other
- hand, the productive functionalities cover actions like: content
- rendition, content localization, content documentation and content
- maintainance.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage.docbook b/Manuals/Docbook/repository-parts/Repository/Usage.docbook
deleted file mode 100644
index 13711aa..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage.docbook
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repo-usage-chapter">
-
- <title>Usage convenctions</title>
-
- <para>The CentOS Artwork Repository is supported by <ulink
- url="http://subversion.tigris.org/">Subversion</ulink>, a version
- control system which allows you to keep old versions of files and
- directories (usually source code), keep a log of who, when, and
- why changes occurred, etc., like CVS, RCS or SCCS.</para>
-
- <para>When using Subversion there is one "source repository" and
- many "working copies" of that source repository. The working
- copies are independent one another, can be distributed all around
- the world and provide a local place for designers, documentors,
- translators and programmers to perform their work in a
- descentralized way. The source repository, on the other hand,
- provides a central place for all independent working copies to
- interchange data and provides the information required to permit
- extracting previous versions of files at any time.</para>
-
- &repo-usage-policy;
- &repo-usage-organization;
- &repo-usage-filenames;
- &repo-usage-worklines;
- &repo-usage-connection-between-worklines;
- &repo-usage-syncronizing-paths;
- &repo-usage-extending-repository;
-
-</chapter>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/Worklines.docbook
deleted file mode 100644
index ba692e9..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines.docbook
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-usage-section-4" xreflabel="Graphic design" label="3.4">
-
- <title>Work lines</title>
-
- <para>Inside CentOS Artwork Repository there are four major work
- lines of production which are: graphic design, documentation,
- localization and automation. These work lines describe different
- areas of content production. Content production inside these
- specific areas may vary as much as persons be working on them.
- Producing content in too many different ways may result
- innapropriate in a collaborative environment like CentOS Artwork
- Repository where content produced in one area depends somehow from
- content produced in another different area. So, a content
- production standard is required for each available work
- line.</para>
-
- &repo-usage-worklines-graphic-design;
- &repo-usage-worklines-documentation;
- &repo-usage-worklines-localization;
- &repo-usage-worklines-automation;
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/automation.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/automation.docbook
deleted file mode 100644
index f6fb5a5..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/automation.docbook
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<sect2 id="repo-usage-section-4-4" xreflabel="Graphic design" label="3.4.4">
-
- <title>Automation</title>
-
- <para>The automation work line exists to standardize content
- production inside the working copies of CentOS Artwork Repository.
- Here is developed the <command>centos-art.sh</command> script, a
- bash script specially designed to automate most frequent tasks
- (e.g., rendition, documentation and localization) inside the
- repository. There is no need to type several tasks, time after
- time, if they can be programmed into just one executable
- script.</para>
-
- <para>The automation work line is organized in the <filename
- class="directory">trunk/Scripts</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/documentation.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/documentation.docbook
deleted file mode 100644
index 574458b..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/documentation.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<sect2 id="repo-usage-section-4-2" xreflabel="Graphic design" label="3.4.2">
-
- <title>Documentation</title>
-
- <para>The documentation work line exists to describe what each
- directory inside the CentOS Artwork Repository is for, the
- conceptual ideas behind them and, if possible, how automation
- scripts make use of them.</para>
-
- <para>The documentation work line is organized in the <filename
- class="directory">trunk/Manuals</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/graphic-design.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/graphic-design.docbook
deleted file mode 100644
index c3727d8..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/graphic-design.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml versio="1.0"?>
-<sect2 id="repo-usage-section-4-1" xreflabel="Graphic design" label="3.4.1">
-
- <title>Graphic design</title>
-
- <para>The graphic design work line exists to cover brand design,
- typography design and themes design mainly. Additionally, some
- auxiliar areas like icon design, illustration design, brushes
- design, patterns designs and palettes of colors are also included
- here for completeness.</para>
-
- <para>The graphic design work line is organized in the <filename
- class="directory">trunk/Identity</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/localization.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/localization.docbook
deleted file mode 100644
index 972a618..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/Worklines/localization.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<sect2 id="repo-usage-section-4-3" xreflabel="Graphic design" label="3.4.3">
-
- <title>Localization</title>
-
- <para>The localization work line exists to provide the translation
- messages required to produce content in different languages.
- Translation messages inside the repository are stored as portable
- objects (e.g., .po, .pot) and machine objects (.mo).</para>
-
- <para>The localization work line is organized in the <filename
- class="directory">trunk/Locales</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/connection-between-worklines.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/connection-between-worklines.docbook
deleted file mode 100644
index afe6e85..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/connection-between-worklines.docbook
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-usage-section-5" xreflabel="Connection between directories" label="3.5">
-
- <title>Connection between directories</title>
-
- <para>In order for automation scripts to produce content inside
- working copies of CentOS Artwork Repository, it is required that
- all work lines be connected somehow. Using this connection,
- automation scripts can know where to retrive the information they
- need to work with (e.g., design model, translation messages,
- output locations, etc.). This connection is built using two path
- constructions named <emphasis>master paths</emphasis> and
- <emphasis>auxiliar paths</emphasis>.</para>
-
- <para>The master path points only to directories that contain
- source files (e.g., SVG files) required to produce base content
- (e.g., PNG files) through automation scripts. Each master path
- inside the repository may have several auxiliar paths associated,
- but auxiliar paths can only have one master path associated.
- Master paths are organized under <filename
- class="directory">trunk/Identity/Models</filename> directory
- structure and auxiliar paths under <filename
- class="directory">trunk/Identity/Images</filename>, <filename
- class="directory">trunk/Locales</filename> and <filename
- class="directory">trunk/Manuals</filename> directory
- structures.</para>
-
- <para>The auxiliar paths can point either to directories or files.
- When an auxiliar path points to a directory, that directory
- contains information that modifies somehow the content produced
- from master paths (e.g., translation messages) or provides the
- output information required to know where to store the content
- produced from master path. When an auxiliar path points to a
- file, that file has no other purpose but to document the master
- path it refers to.</para>
-
- <para>The relationship between auxiliar paths and master paths is
- realized by combining the master path itself and the second level
- directory structures of the repository. The master path is
- considered the path identifier and the second level directory
- structure taken from the repository is considered the common part
- of the path where the path identifier is appended to.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/extending-repository.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/extending-repository.docbook
deleted file mode 100644
index 75ad32a..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/extending-repository.docbook
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-usage-section-7" xreflabel="Syncronizing path information" label="3.7">
-
- <title>Extending repository organization</title>
-
- <para>Occasionly, you may find that new components of The CentOS
- Project Corporate Identity need to be added to the repository in
- order to work them out. If that is the case, the first question we
- need to ask ourselves, before start to create directories blindly
- all over, is: @emph{What is the right place to store it?}</para>
-
- <para>The best place to find answers is in The CentOS Community
- (see page @url{http://wiki.centos.org/GettingHelp}), but going
- there with hands empty is not good idea. It may give the
- impression you don't really care about. Instead, consider the
- following suggestions to find your own comprehension in order to
- make your own propositions based on it.</para>
-
- <para>When extending respository structure it is very useful to
- bear in mind The CentOS Project Corporate Identity Structure
- (@pxref{Directories trunk Identity}) The CentOS Mission and The
- CentOS Release Schema. The rest is just matter of choosing
- appropriate names. It is also worth to know that each directory in
- the repository responds to a conceptual idea that justifies its
- existence.</para>
-
- <para>To build a directory structure, you need to define the
- conceptual idea first and later create the directory. There are
- some locations inside the repository that already define some
- concepts you probably want to reuse. For example,
- @file{trunk/Identity/Images/Themes} to store theme artistic
- motifs, @file{trunk/Identity/Models/Themes} to store theme design
- models, @file{trunk/Manual} to store documentation files,
- @file{trunk/Locales} to store translation messages,
- @file{trunk/Scripts} to store automation scripts and so on.</para>
-
- <para>To illustrate this desition process let's consider the
- @file{trunk/Identity/Images/Themes/TreeFlower/3} directory
- structure as example. This directory can be read as: the theme
- development line of version @file{3} of @file{TreeFlower} artistic
- motif. Additional, we can identify that artistic motifs are part
- of themes as well as themes are part of The CentOS Project
- Corporate Identity. These concepts are better described
- independently in each documentation entry related to the directory
- structure as it is respectively shown in the list of commands
- bellow.
-
- <itemizedlist>
- <listitem>
- <para><command>centos-art help --read turnk</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images/Themes</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3</command></para>
- </listitem>
- </itemizedlist>
-
- </para>
-
- <para>The concepts behind other location can be found in the same
- way described above, just change the path information used above
- to the one you are trying to know concepts for.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/filenames.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/filenames.docbook
deleted file mode 100644
index 74614b2..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/filenames.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-usage-section-3" xreflabel="File names" label="3.3">
-
- <title>File names</title>
-
- <para>Inside the CentOS Artwork Repository, file names are all
- written in lowercase (e.g., <filename>01-welcome.png</filename>,
- <filename>splash.png</filename>,
- <filename>anaconda_header.png</filename>, etc.) and directory
- names are all written capitalized (e.g., <filename
- role="directory">Identity</filename>, <filename
- role="directory">Themes</filename>, <filename
- role="directory">Motifs</filename>) and sometimes in cammel case
- (e.g., <filename role="directory">TreeFlower</filename>, etc.).
- </para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/organization.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/organization.docbook
deleted file mode 100644
index e04ebac..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/organization.docbook
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml verion="1.0"?>
-<sect1 id="repo-usage-section-2" xreflabel="Organization" label="3.2">
-
- <title>Organization</title>
-
- <para>The CentOS Artwork Repository organization is described in
- the chapter <xref linkend="repo-dirs-chapter"
- />.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/policy.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/policy.docbook
deleted file mode 100644
index c6acd7d..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/policy.docbook
+++ /dev/null
@@ -1,49 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-usage-section-1" xreflabel="Policy" label="3.1">
-
- <title>Policy</title>
-
- <para>The CentOS Artwork Repository is a collaborative tool that
- anyone can have access to. However, changing that tool in any form
- is something that should be requested in the <ulink
- url="mailto:centos-devel@centos.org">CentOS Developers mailing
- list</ulink>. Generally, people download working copies from
- CentOS Artwork Repository, study the repository organization, make
- some changes in their working copies, make some tests to verify
- such changes do work the way expected and finally request access
- to commit them up to the CentOS Artwork Repository (i.e., the
- source repository) for others to benefit from them.</para>
-
- <para>Once you've received access to commit your changes, there is
- no need for you to request permission again to commit other
- changes from your working copy to CentOS Artwork Repository as
- long as you behave as a <emphasis>good cooperating
- citizen</emphasis>. Otherwise, your rights to commit changes might
- be temporarly revoked or completly banished.</para>
-
- <para>As a good cooperating citizen one understand of a person who
- respects the work already done by others and share ideas with
- authors before changing relevant parts of their work, specially in
- situations when the access required to realize the changes has
- been granted already. Of course, there is a time when
- conversation has taken place, the paths has been traced and
- changing the work is so obvious that there is no need for you to
- talk about it; that's because you already did, you already built
- the trust to keep going. Anyway, the mailing list mentioned above
- is available for sharing ideas in a way that good relationship
- between community citizens could be constantly balanced.</para>
-
- <para>The relationship between community citizens is monitored by
- repository administrators. Repository administrators are
- responsible of granting everything goes the way it needs to go in
- order for the CentOS Artwork Repository to accomplish its mission
- which is: to provide a colaborative tool for The CentOS Community
- where The CentOS Project Corporate Identity is built and
- maintained by The CentOS Community itself.</para>
-
- <para>It is also important to remember that all source files
- inside CentOS Artwork Repository should comply the terms of <xref
- linkend="licenses-gpl" /> in order for them to remain
- inside the repository.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository-parts/Repository/Usage/syncronizing-paths.docbook b/Manuals/Docbook/repository-parts/Repository/Usage/syncronizing-paths.docbook
deleted file mode 100644
index 75b0e26..0000000
--- a/Manuals/Docbook/repository-parts/Repository/Usage/syncronizing-paths.docbook
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repo-usage-section-6" xreflabel="Syncronizing path information" label="3.6">
-
- <title>Syncronizing path information</title>
-
- <para>Syncronizing path information is the action of keeping all
- path information up to date in the repository. This action implies
- both file movement and replacement of content inside files already
- moved, in this very specific order. File movement is related to
- actions like duplicate, delete and rename files and directories in
- the repository. Replacement of content inside files is related to
- replace information, path information in this case, inside files
- in the repository.</para>
-
- <para>The order followed to syncronize path information is
- relevant because the versioned nature of the files we are working
- with. We don't perform file content replacement first because that
- would imply a repository change which will immediatly demmand a
- commit in order for actions like duplicate, delete or rename to
- take place. However, if we perform file movement first, it is
- possible to commit both file moved and file content replacements
- as if they were just one change. In this case the file content
- replacement takes palce in the target location that have been
- duplicated or renamed, not the one use as source location. This
- configuration is specially useful when files are renamed (i.e.,
- one file is copied from a source location to a target location and
- then the source location of it is removed from repository).</para>
-
- <warning><para>There is no support for URLs actions inside
- <command>centos-art.sh</command> script. The
- <command>centos-art.sh</command> script is designed to work with
- local files inside the working copy only. If you need to perform
- URL actions directly, use Subversion commands
- instead.</para></warning>
-
- <para>When one master path is changed it is required that all
- related auxiliar paths be changed, too. This is required in order
- for master paths to retain their relation with auxiliar paths.
- This way, automation scripts are able to know where to retrive
- translation messages from, where to store final output images to
- and where to look for documentation. If relation between master
- paths and auxiliar paths is lost, there is no way for automation
- scripts to know where to retrive the information they need.</para>
-
- <para>The auxiliar paths should never be modified under any reason
- but to satisfy the relationship with the master path. Liberal
- change of auxiliar paths may suppress the conceptual idea they
- were initially created for; and certainly, automation scripts may
- stop working as expected. The update direction to rename path
- information must be from master path to auxiliar path and never
- the opposite.</para>
-
- <para>The relation between master and auxiliar paths is useful to
- keep repository organized but introduce some complications when we
- work with files that use master path information as reference to
- build structural information. This is the case of repository
- documentation manual source files where inclusions, menus, nodes
- and cross references are built using master path information as
- reference. Now, to see what kind of complication we are talking
- about, consider what would happen to a structural definitions
- (i.e., inlusions, menus, nodes and cross refereces) already set in
- the manual from one master path that is suddenly renamed to
- something different. If the path information is not syncronized,
- at this point, we lose connection between the master path and the
- auxiliar path created to store the related documentation entry, as
- well as the related structural definitions that end up pointing to
- a master path that no longer exist.</para>
-
- <para>The syncronization of path information is aimed to solve
- these kind of issues.</para>
-
-</sect1>