Blame Identity/Manual/repository-latex/centos-art.sh-latex/Workstation/configuration.tex

39a1ed
% Part   : Preparing Your Workstation
39a1ed
% Chapter: Configuration
39a1ed
% ------------------------------------------------------------
39a1ed
% $Id: configuration.tex 6191 2010-08-02 02:36:14Z al $
39a1ed
% ------------------------------------------------------------
39a1ed
39a1ed
This chapter describes configurations you need to set up before using
39a1ed
CentOS Artwork Repository.
39a1ed
39a1ed
\section{Firewall}
39a1ed
39a1ed
The CentOS Artwork Repository lives on the following URL:
39a1ed
39a1ed
\begin{quote}
39a1ed
https://projects.centos.org/svn/artwork/
39a1ed
\end{quote}
39a1ed
39a1ed
To reach this location you need to have Internet access and be sure no
39a1ed
rule in your firewall is denying this site. Note that the URL uses the
39a1ed
SSL protocol (port 443).
39a1ed
39a1ed
\section{Subversion Behind Squid}
39a1ed
39a1ed
Sometimes it is convenient to proxy Subversion client's requests
39a1ed
through a proxy-cache server like Squid. In cases like this, the Squid
39a1ed
proxy server is in the middle between you and CentOS Artwork
39a1ed
Repository. If you want to proxy Subversion client's requests through
39a1ed
Squid proxy-cache server, you need to configure your Subversion client
39a1ed
and your Squid proxy server to do so.
39a1ed
39a1ed
\subsection{Subversion Client Configuration}
39a1ed
39a1ed
Subversion client needs to be configured to send requests to your
39a1ed
Squid proxy-cache server. This configuration takes place in the file
39a1ed
\texttt{$\sim$/.subversion/servers}.
39a1ed
39a1ed
\subsection{Squid Server Configuration}
39a1ed
39a1ed
Squid proxy-cache server needs to be configured to accept the
39a1ed
extension methods \texttt{REPORT MERGE MKACTIVITY CHECKOUT MKCOL}.
39a1ed
This configuration takes place in the file
39a1ed
\texttt{/etc/squid/squid.conf}, specifically in the configuration tag
39a1ed
illustrated in \autoref{fig:Workstation:Configuration:Squid}.
39a1ed
39a1ed
\begin{figure}[!hbp]
39a1ed
\hrulefill
39a1ed
\begin{verbatim}
39a1ed
#  TAG: extension_methods
39a1ed
#       Squid only knows about standardized HTTP request methods.
39a1ed
#       You can add up to 20 additional "extension" methods here.
39a1ed
#
39a1ed
#Default:
39a1ed
# none
39a1ed
extension_methods REPORT MERGE MKACTIVITY CHECKOUT MKCOL
39a1ed
\end{verbatim}
39a1ed
\hrulefill
39a1ed
\caption{Squid configuration to proxy Subversion client's requests.%
39a1ed
   \label{fig:Workstation:Configuration:Squid}}
39a1ed
\end{figure}
39a1ed
39a1ed
\section{Working Copy}
39a1ed
39a1ed
A Subversion working copy is an ordinary directory tree on your local
39a1ed
system, containing a collection of files (i.e.  Translations, Designs,
39a1ed
Manuals, and Scripts). You can edit these files however you wish. Your
39a1ed
working copy is your own private work area: Subversion will never
39a1ed
incorporate other people's changes, nor make your own changes
39a1ed
available to others, until you explicitly tell it to do so.  You can
39a1ed
even have multiple working copies of the same project.\footnote{Even
39a1ed
this is basically correct, doing so when using CentOS Artowrk
39a1ed
Repository can bring some confusion when executing scripts. Presently,
39a1ed
only one absolute path can be defined as absolute path for scripts'
39a1ed
execution.  You can have as many working copies of CentOS Artwork
39a1ed
Repository as you want but scripts will be executed from just one
39a1ed
working copy absolute path. That is, the one stored under
39a1ed
\texttt{/home/centos/artwork/}}.
39a1ed
39a1ed
Once you've made some changes to your working copy files and verified
39a1ed
that they work properly, Subversion provides you with commands to
39a1ed
``publish'' your changes to the other people working with you on your
39a1ed
project (by writing to the repository). If other people publish their
39a1ed
own changes, Subversion provides you with commands to merge those
39a1ed
changes into your working directory (by reading from the repository).
39a1ed
39a1ed
\begin{figure}[!hbp]
39a1ed
\hrulefill
39a1ed
\begin{verbatim}
39a1ed
svn co https://projects.centos.org/svn/artwork /home/centos/
39a1ed
\end{verbatim}
39a1ed
\hrulefill
39a1ed
\caption{Subversion command used to download the working copy.%
39a1ed
   \label{fig:Workstation:WC:Download}}
39a1ed
\end{figure}
39a1ed
39a1ed
The subversion command illustrated in
39a1ed
\autoref{fig:Workstation:WC:Download} brings a CentOS Artwork
39a1ed
Repository working copy down to your workstation, specifically to your
39a1ed
home directory (\texttt{/home/centos/artwork/}). This process may take
39a1ed
some time.  Once the working copy is available in your workstation,
39a1ed
you are ready to start exploring and improving available works.
39a1ed
39a1ed
Note that you need to have a username called \texttt{centos} in your
39a1ed
system.  If you don't have it, you can create it using the comand
39a1ed
\texttt{useradd} as superuser (\texttt{root}).
39a1ed
39a1ed
\subsection{Standardizing Absolute Path}
39a1ed
39a1ed
When using Inkscape to import raster images inside SVG files the
39a1ed
absolute image path is required. If everyone stores the working copy
39a1ed
on a different absolute path imported images will not be loaded in
39a1ed
those location different from those they were conceived. There is no
39a1ed
way to find the right absolute image path but defining a convenction
39a1ed
about it. 
39a1ed
39a1ed
On a path string (e.g., /home/centos/artwork/trunk/) the username
39a1ed
(`centos') is the variable component, so it is the component we need
39a1ed
to standardize--in the sake of keeping the working copy inside user's
39a1ed
/home/ structure. Thus, analysing which username to use, the CentOS
39a1ed
Project is what join us all together, so the `centos' word in
39a1ed
lower-case seems to be a nice choise for us to use as common username. 
39a1ed
39a1ed
\section{User Identification}
39a1ed
39a1ed
At this point you probably have made some changes inside your working
39a1ed
copy and wish to publish them.  To publish your changes on CentOS
39a1ed
Artwork Repository you need to have a registered account with commit
39a1ed
privilege in CentOS Artwork Repository.
39a1ed
39a1ed
If you are new in CentOS Artwork Repository it is possible that you
39a1ed
can't commit your changes. That is because new registered accounts
39a1ed
haven't commit privilege set by default.  In order for your registered
39a1ed
account to have commit privilege inside CentOS Artwork Repository you
39a1ed
need to request it. See section
39a1ed
\ref{sec:Configuration:User:Privileges}.
39a1ed
39a1ed
\subsection{User Account Registration}
39a1ed
\label{sec:Configuration:Account}
39a1ed
39a1ed
To register a user account inside CentOS Artwork Repository, you need
39a1ed
to go to the following URL:
39a1ed
39a1ed
\begin{quote}
39a1ed
\url{https://projects.centos.org/trac/artwork/}
39a1ed
\end{quote}
39a1ed
39a1ed
\subsection{User Account Privileges}
39a1ed
\label{sec:Configuration:User:Privileges}
39a1ed
39a1ed
To have commit privileges in CentOS Artwork Repository it is needed
39a1ed
that you show your interest first, preferably with something useful
39a1ed
like a new or improved design, translation, manual, or script. As
39a1ed
convenction, people working on CentOS Artwork Repository share ideas
39a1ed
in the mailing list
39a1ed
\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}. If you
39a1ed
are interested in joining us go there and express yourself.
39a1ed
39a1ed
\section{Repository Tagged Revisions}
39a1ed
39a1ed
The CentOS Artwork Repository is also available as tagged revisions.
39a1ed
Tagged revisions are checkpoints on the CentOS Artwork Repository
39a1ed
developing lifetime. They are inmutable copies of the CentOS Artwork
39a1ed
Repository state through time.  Tagged revisions contain the files
39a1ed
used to produce images but not images themselves.  Inside tagged
39a1ed
revisions you can find scripts (\texttt{.sh}), design templates
39a1ed
(\texttt{.svg}), translation files (\texttt{\.sed}), gimp projects
39a1ed
(\texttt{.xcf}), and documetation files (\texttt{.tex}).
39a1ed
39a1ed
CentOS Artowrk Repository tagged revisions are available for
39a1ed
downloading in the following location:
39a1ed
39a1ed
\begin{description}
39a1ed
\item[URL:] https://projects.centos.org/svn/artwork/tags
39a1ed
\end{description}
39a1ed
39a1ed
and alternatively, you can find references in the CentOS Project's
39a1ed
wiki, specifically in the ArtWork page:
39a1ed
39a1ed
\begin{description}
39a1ed
\item[URL:] http://wiki.centos.org/ArtWork
39a1ed
\end{description}