Blame Manuals/Docbook/Repository/Usage/section-7.docbook

e935c3
e935c3
<section>
e935c3
e935c3
    <title>Extending repository organization</title>
e935c3
e935c3
    <para>Occasionly, you may find that new components of The CentOS
e935c3
    Project Corporate Identity need to be added to the repository in
e935c3
    order to work them out. If that is the case, the first question we
e935c3
    need to ask ourselves, before start to create directories blindly
e935c3
    all over, is: @emph{What is the right place to store it?}</para>
e935c3
    
e935c3
    <para>The best place to find answers is in The CentOS Community
e935c3
    (see page @url{http://wiki.centos.org/GettingHelp}), but going
e935c3
    there with hands empty is not good idea. It may give the
e935c3
    impression you don't really care about. Instead, consider the
e935c3
    following suggestions to find your own comprehension in order to
e935c3
    make your own propositions based on it.</para>
e935c3
    
e935c3
    <para>When extending respository structure it is very useful to
e935c3
    bear in mind The CentOS Project Corporate Identity Structure
e935c3
    (@pxref{Directories trunk Identity}) The CentOS Mission and The
e935c3
    CentOS Release Schema. The rest is just matter of choosing
e935c3
    appropriate names. It is also worth to know that each directory in
e935c3
    the repository responds to a conceptual idea that justifies its
e935c3
    existence.</para>
e935c3
    
e935c3
    <para>To build a directory structure, you need to define the
e935c3
    conceptual idea first and later create the directory. There are
e935c3
    some locations inside the repository that already define some
e935c3
    concepts you probably want to reuse. For example,
e935c3
    @file{trunk/Identity/Images/Themes} to store theme artistic
e935c3
    motifs, @file{trunk/Identity/Models/Themes} to store theme design
e935c3
    models, @file{trunk/Manual} to store documentation files,
e935c3
    @file{trunk/Locales} to store translation messages,
e935c3
    @file{trunk/Scripts} to store automation scripts and so on.</para>
e935c3
    
e935c3
    <para>To illustrate this desition process let's consider the
e935c3
    @file{trunk/Identity/Images/Themes/TreeFlower/3} directory
e935c3
    structure as example.  This directory can be read as: the theme
e935c3
    development line of version @file{3} of @file{TreeFlower} artistic
e935c3
    motif. Additional, we can identify that artistic motifs are part
e935c3
    of themes as well as themes are part of The CentOS Project
e935c3
    Corporate Identity. These concepts are better described
e935c3
    independently in each documentation entry related to the directory
e935c3
    structure as it is respectively shown in the list of commands
e935c3
    bellow.
e935c3
    
e935c3
    <itemizedlist> 
e935c3
        <listitem>
e935c3
            <para><command>centos-art help --read turnk</command></para>
e935c3
        </listitem>
e935c3
        <listitem>
e935c3
            <para><command>centos-art help --read turnk/Identity</command></para>
e935c3
        </listitem>
e935c3
        <listitem>
e935c3
            <para><command>centos-art help --read turnk/Identity/Images</command></para>
e935c3
        </listitem>
e935c3
        <listitem>
e935c3
            <para><command>centos-art help --read turnk/Identity/Images/Themes</command></para>
e935c3
        </listitem>
e935c3
        <listitem>
e935c3
            <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower</command></para>
e935c3
        </listitem>
e935c3
        <listitem>
e935c3
            <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3</command></para>
e935c3
        </listitem>
e935c3
    </itemizedlist> 
e935c3
    
e935c3
    </para>
e935c3
    
e935c3
    <para>The concepts behind other location can be found in the same
e935c3
    way described above, just change the path information used above
e935c3
    to the one you are trying to know concepts for.</para>
e935c3
    
e935c3
</section>