Blame Manuals/Texinfo/Introduction/history.texinfo

eae056
This section records noteworthy changes of CentOS Artwork Repository
40dd51
through years.
c33909
c33909
@subheading 2008
c33909
c33909
The CentOS Artwork Repository started at CentOS Developers mailing
c33909
list (@email{centos-devel@@centos.org}) during a discussion about how
c33909
to automate the slide images of Anaconda. In such discussion, Ralph
c33909
Angenendt rose up his hand to ask: Do you have something to show? 
c33909
5c8537
To answer the question, Alain Reguera Delgado suggested a bash script
5c8537
which combined SVG and SED files in order to produce PNG images in
5c8537
different languages ---together with the proposition of creating a
5c8537
Subversion repository where translations and image production could be
5c8537
distributed inside The CentOS Community---.
c33909
5c8537
Karanbirn Sighn considered the idea intresting and provided the
40dd51
infrastructure necessary to support the effort. This way the CentOS
5c8537
Artwork SIG and the CentOS Artwork Repository were officially created
40dd51
and made available in the following urls:
c33909
c33909
@itemize
c33909
@item @url{https://projects.centos.org/trac/artwork/}
40dd51
@item @url{https://projects.centos.org/svn/artwork/}
c33909
@end itemize
c33909
c33909
Once the CentOS Artwork Repository was available, Alain Reguera
40dd51
Delagdo uploaded the bash script for rendering Anaconda slides; Ralph
40dd51
Angenendt documented it very well and The CentOS Translators started
40dd51
to download working copies of CentOS Artwork Repository to produce
40dd51
slide images in their own languages.
c33909
c33909
@subheading 2009
c33909
40dd51
The rendition script is at a very rustic state where only slide images
40dd51
can be produced. 
40dd51
5c8537
The rendition script was redesigned to extend image production to
5c8537
other areas, not just slide images.  In this configuration one
5c8537
translated SVG instance was created from the SVG file provided as
5c8537
input in order to produce one translated PNG image as output.  The
5c8537
translation of SVG files was made through SED replacement commands and
5c8537
the rendition of PNG images was realized through Inkscape command line
40dd51
internface.
40dd51
5c8537
The rendition script was named @command{render.sh}. The directory
5c8537
structures were prepared to receive the rendition script so images
5c8537
could be produced inside them. Each directory structure had design
40dd51
templates (.svg), translation files (.sed), and translated images
40dd51
(.png).
40dd51
5c8537
The rendition script was unified in a common place and linked from
5c8537
different directory structures. There was no need to have the same
5c8537
code in different directory structures if it could be in just one
5c8537
place and then be linked from different locations.
40dd51
5c8537
Concepts about corporate identity began to be considered. As referece,
5c8537
it was used the book @emph{Corporate Identity} by Wally Olins (1989)
5c8537
and Wikipedia (@url{http://en.wikipedia.org/Corporate_identity}).
40dd51
40dd51
The rendition script main's goal becomes to: automate production of a
5c8537
monolithic corporate visual identity structure, based on The CentOS
c33909
Mission and The CentOS Release Schema. 
c33909
5c8537
The documentation of CentOS Artwork Repository started to take form in
c33909
@LaTeX{} format.
c33909
c33909
@subheading 2010
c33909
40dd51
The rendition script @command{render.sh} is no longer a rendition
40dd51
script, but a collection of functionalities grouped into the
40dd51
@command{centos-art.sh} script where rendition is one functionality
40dd51
among others.  The @command{centos-art.sh} is created to automate most
40dd51
frequent tasks inside the repository.  There is no need to have links
40dd51
all around the repository if a command-line interface can be created
5c8537
(through symbolic links, in the @file{~/bin} directory) and be called
5c8537
anywhere inside the repository as it would be usually done with
40dd51
regular commands.   
c33909
40dd51
Inside @command{centos-art.sh}, functionalities started to get
5c8537
identified and separated one another. For example, when images were
5c8537
rendered, there was no need to load functionalities related to
5c8537
documentation manual. This moved us onto common functionalities and
5c8537
specific functionalities inside @command{centos-art.sh} script. Common
5c8537
functionalities are loaded when the script is initiated and are
5c8537
available to specific functionalities.
c33909
5c8537
The @command{centos-art.sh} script was redesigned to handle options
5c8537
trough @command{getopt} option parser.
c33909
5c8537
The repository directory structure was updated to improve the
5c8537
implementation of concepts related to corporate visual identity.
5c8537
Specially in the area related to themes which were divided into design
5c8537
models and artistic motifs.
c33909
c33909
@subheading 2011
c33909
5c8537
The @command{centos-art.sh} script was redesigned to start translating
5c8537
SVG and other XML-based files (e.g., XHTML and Docbook files) through
5c8537
the @command{xml2po} program and shell scripts files (e.g., Bash
5c8537
scripts) through GNU @command{gettext} tools.  This configuration
5c8537
provided a stronger interface for graphic designers, translators and
5c8537
programmers at time of producing localized content. @file{.sed} files
5c8537
are no longer used to handle translations.
40dd51
5c8537
Improve option parsing through @command{getopt}.
40dd51
40dd51
The @command{centos-art.sh} script is updated to organize
40dd51
functionalities in two groups: ``the administrative functionalities''
40dd51
and ``the productive functionalities''.  The administrative
40dd51
functionalities cover actions like: copying, deleting and renaming
40dd51
directory structures inside the repository. Also, preparing your
40dd51
workstation for using @command{centos-art.sh} script, making backups
40dd51
of the distribution theme currently installed,  installing themes
40dd51
created inside repository and restoring themes from backup.  On the
40dd51
other hand, the productive functionalities cover actions like: content
c33909
rendition, content localization, content documentation and content
c33909
maintainance.