diff --git a/Manual/Introduction/repo-convenctions.texi b/Manual/Introduction/repo-convenctions.texi index a0a764d..19b6a49 100644 --- a/Manual/Introduction/repo-convenctions.texi +++ b/Manual/Introduction/repo-convenctions.texi @@ -2,7 +2,7 @@ The CentOS Artwork Repository is supported by Subversion (@url{http://subversion.tigris.org/}), 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. In Subversion repositories there is one source +like CVS, RCS or SCCS. 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, @@ -14,14 +14,14 @@ at any time. @subsection Repository policy -The CentOS Artwork Repository is a collaborative tool where many -people can have access to. However, changing that tool in any form is -something that should be requested in @email{centos-devel@@centos.org} -mailing list. 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 work the way expected and request access to commit them up to -the CentOS Artwork Repository for others to benefit from them. +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 @email{centos-devel@@centos.org} mailing +list. 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 work the +way expected and request access to commit them up to the CentOS +Artwork Repository for others to benefit from them. 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 @@ -87,24 +87,25 @@ capitalized (e.g., @samp{Identity}, @samp{Themes}, @samp{Motifs}, @subsection Repository work lines -Work lines describe different areas of content production inside -CentOS Artwork Repository. 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. To produce content in a syncronized but descentralized -way, it is required to define a standard for content production that -let each work line to exists that way. +Inside CentOS Artwork Repository there are four major production work +lines which are: @emph{graphic design}, @emph{documentation}, +@emph{localization} and @emph{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. To produce content in a syncronized but +descentralized way, it is required to define a @emph{content +production standard} that lead everyone work in order for the content +produced in each different work line to gear correctly once it is put +together. The standard way of producing content inside CentOS Artwork Repository is implemented through @command{centos-art.sh} script and described in @file{trunk/Scripts} documentation entry (@pxref{Directories trunk Scripts}). -Inside CentOS Artwork Repository there are four major production work -lines. They are: @emph{graphic design}, @emph{documentation}, -@emph{localization} and @emph{automation}. @subsubsection Graphic design @@ -187,12 +188,12 @@ organized under @file{trunk/Manual} directory structure using repository directories as reference. Directories inside CentOS Artwork Repository are created based on conceptual idea, so one documentation entry exists for each directory inside the repository in order to -describe the conceptual ideas such directory is based. +describe the conceptual ideas such directory is based on. Directory documentation entries are stored under @file{trunk/Manual/Directories} directory structure and controlled by the @code{help} functionality of @command{centos-art.sh} script. -Using @code{help} functionality you can create, edit and remove +Using the @code{help} functionality you can create, edit and remove directory documentation in a way you don't need to take care of updating menus, nodes and cross reference information inside the manual structure; the functionality takes care of it for you. @@ -257,11 +258,11 @@ Artwork Repository be sure to use source files supported either by @subsubsection Automation The automation work line exists to standardize content production -inside CentOS Artwork Repository. There is no need to repeat several +inside CentOS Artwork Repository. There is no need to type several tasks time after time if they can be programmed into just one script that groups them all. -The automation work line is take place under @file{trunk/Scripts} +The automation work line takes place under @file{trunk/Scripts} directory structure. Here is developed the @command{centos-art.sh} script, a bash script specially designed to automate most frequent tasks inside CentOS Artwork Repository. Basically, the @@ -271,8 +272,8 @@ functionalities relay on repository organization to work as expected. @quotation @strong{Tip} If you need to improve the way content is produced, look -inside automation scripts and make your improvement there for every -one to benefit. +inside automation scripts and make your improvement there for everyone +to benefit. @end quotation @xref{Directories trunk Scripts}, for more information on automation. @@ -284,21 +285,28 @@ Repository, it is required that all work lines be connected somehow. This is the way automation scripts can know what design model and what translation files to use when specific contents are produced, also where to save the content produced as result. This connection between -directories takes place through two path constructions named -@emph{The Master Path} and @emph{The Auxiliar Paths}. - -As master path consider the last directory, inside a directory -structure, which contains the source files (e.g., SVG files) required -to produce base content (e.g., PNG files). Master paths are backup by -auxiliar paths. - -Auxiliar paths provide the files that modify production of base -content produced from master paths. Auxiliar paths take their -structure from one unique master path. Master paths can have several +directories takes place through two path constructions named @emph{The +Master Paths} and @emph{The Auxiliar Paths}. + +The master paths point to directories which contain the source files +(e.g., SVG files) required to produce base content (e.g., PNG files). +Each master path inside the repository has several auxiliar paths +associated. + +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 the master +path (e.g., through translation messages) or provides the output +information of where to store the content produced from master path. +When an auxiliar path points to a file, that file has no other purpose +but document the master path it refers to. + +The relation between auxiliar paths and master paths is realized +taking one unique master path as reference. Master paths define how +auxiliar paths are constructed. Master paths can have several auxiliar paths associated, but auxiliar paths can have only one master -path associated. - -For example, consider The CentOS Brands path relation: +path associated. For example, consider the following path relation +and note how there are constant and variable values in them: @table @file @item trunk/Identity/Models/Brands @@ -309,31 +317,52 @@ produce the brand images of The CentOS Project. Here is where you, as graphic designers, define design models used to produce the brand images of The CentOS Project. -The path to this directory is considered master because it contains -the most critical information (i.e., the information that can't be -absent) required to produce the brand images of The CentOS Project. +The path to this directory is considered a master path because it +contains the most critical information (i.e., the information that +can't be absent) required to produce the brand images of The CentOS +Project. @item trunk/Manual/Directories/trunk/Identity/Models/Brands.texi This file contains documentation, in Texinfo format, for design models -used to produce the brand images of The CentOS Project. +used to produce the brand images of The CentOS Project. The path to +this file is made of three parts: + +@verbatim + A B C +|-----------------------|----------------------------|---| +trunk/Manual/Directories/trunk/Identity/Models/Brands.texi +|-----------------------|----------------------------|---| + +A = The documentation manual source location. +B = The master path we are building documentation for. +C = The file extension used by Texinfo documentation files. +@end verbatim Here is where you, as documentor, describe construction of desing models used to produce the brand images of The CentOS Project. In this description you can include image dimensions, color information, image -location inside CentOS Distribution filesystem, image packaging and -similar things. +location inside CentOS Distribution filesystem, packaging and similar +things. -The path to this file is considered auxiliar to -@file{trunk/Identity/Models/Brands} master path because it provides -the description required to let everyone know how to build design -models used to produce the brand images of The CentOS Project. +The path to this directory is considered auxiliar path of +@file{trunk/Identity/Models/Brands} master path. @item trunk/Locales/Identity/Models/Brands This directory contains translation files, as @command{gettext} portable objects, for design models used to produce the brand images -of The CentOS Project. +of The CentOS Project. The path to this directory made of two parts: + +@verbatim + A B +|------------|---------------------| +trunk/Locales/Identity/Models/Brands +|------------|---------------------| + +A = The translation messages source location. +B = The master path we are building translation messages for. +@end verbatim Here is where you, as translator, localize translatable strings retrived in English language from design models used to produce the @@ -342,100 +371,130 @@ here the translation tasks are skipped to produce no translation at all, obviously there is no portable object to retrive translation messages from. -The path to this directory provides language-specific information -required to produce the brand images of The CentOS Project, so it is -considered auxiliar path of @file{trunk/Identity/Models/Brands} master -path. +The path to this directory is considered auxiliar path of +@file{trunk/Identity/Models/Brands} master path. @item trunk/Manual/Directories/trunk/Locales/Identity/Models/Brands.texi This file contains documentation, in Texinfo format, for translation -messages retrived from design models used to produce The CentOS Brands -required by The CentOS Project. +messages retrived from design models used to produce brand images +required by The CentOS Project. The path to this file is made of three +parts: -Here is where you, as documentor, describe localization of desing -models used to produce The CentOS Brands images required by The CentOS +@verbatim + A B C +|-----------------------|------------------------------------|---| +trunk/Manual/Directories/trunk/Locales/Identity/Models/Brands.texi +|-----------------------|------------------------------------|---| + +A = The documentation manual source location. +B = The master path we are building documentation for. +C = The file extension used by Texinfo documentation files. +@end verbatim + +Here is where you, as documentor, describe localization of those +desing models used to produce brand images required by The CentOS Project. In this description you can include image dimensions, color -information, image location inside CentOS Distribution filesystem, -image packaging and similar things. +information, image location inside the file system of CentOS +Distribution, packaging and similar things. -The path to this file provides documentation to language-specific -directory structure used to store translation messages used to produce -the brand images of The CentOS Project, so it is considered auxiliar -path of @file{trunk/Identity/Models/Brands} master path. +The path to this file is considered auxiliar path of +@file{trunk/Identity/Models/Brands} master path. @item trunk/Identity/Images/Brands -This directory contains the final image produced from The CentOS -Brands design models used by The CentOS Project. +This directory contains the final brand images produced from brand +design models used by The CentOS Project. -Here is where you, as packager, can find the images you need to -rebrand the brand images related to CentOS Distribution. +Here is where you, as packager, can find the brand images you need to +rebrand the CentOS Distribution. -The path to this directory contains the final brand images of The -CentOS Project, so it is considered auxiliar path of +The path to this directory is considered auxiliar path of @file{trunk/Identity/Models/Brands} master path. @item trunk/Manual/Directories/trunk/Identity/Images/Brands.texi This file should contains documentation, in Texinfo format, about how to implement final brand images of The CentOS Project. However, this -documentation entry is rarely created because the related design model -documentation entry already covers implementation of images produced -here. The only reason to create this documentation entry is to put in -an admonition that redirect people up to the design model related -documentation entry where documentation related to implementation is. +documentation entry is rarely used because the related design model +documentation entry already covers implementation of brand images. +The only reason to create this documentation entry is to put in an +admonition that redirect people up to the correct place (i.e., the +related design model coumentation entry). @end table The configuration described above for organizing brand component inside the repository is the one used by direct rendition and can be used as reference to organize other components inside the repository that are produced through direct rendition too. Just change the -component name from brands to that one you want to add without -changing the path structure around it. +component name from @file{Brands} to a different one without changing +the path structure around it. The file organization used by theme rendition, however, is a bit different from that used by direct rendition. In theme rendition, both -master paths and auxiliar paths are built dynamically based on the -design model and the artistic motif you specify at rendition time. As -a mnemotechnic resource, consider theme rendition as two independent -lists, one list of design models and one list of artistic motifs, -which are arbitrary combined between themselves in order to render -images. For example, consider the organization used to produce -Anaconda images for CentOS distribution major release 5 that use the -Default design model and the Flame version 3 artistic motif: +the master paths and the auxiliar paths are built dynamically based on +one design model and one artistic motif specified by you at rendition +time. As a mnemotechnic resource, you could consider theme rendition +as two independent lists, one of design models and one of artistic +motifs, which are arbitrary combined between themselves in order to +render images in specific ways. For example, consider the organization +used to produce Anaconda images; for CentOS distribution major release +5; using @file{Default} design models and version @file{3} of +@file{Flame} artistic motif: @table @file @item trunk/Identity/Themes/Models/Default/Distro/5/Anaconda This directory contains source files used to produce Anaconda images -for CentOS distribution major release 5 using Default design models. +for CentOS distribution major release 5. This specific information has +been named the @file{Default} design model. The path to this directory +is made of three parts: -Here is where you, as graphic designers, define Default design models for -Anaconda images used in CentOS distribution major release 5. +@verbatim + A B C +|---------------------------|-------|----------------| +trunk/Identity/Themes/Models/Default/Distro/5/Anaconda +|---------------------------|-------|----------------| + +A = The theme model source location. +B = The theme model name. +C = The visual manifestation the theme model is created for. +@end verbatim -The path to this directory is considered master because it contains -the most critical information (i.e., the information that can't be -absent) required to produce Anaconda images used inside CentOS -distribution major release 5. +Here is where you, as graphic designers, define @file{Default} design +models for Anaconda images in major release 5 of CentOS distribution. + +The path to this directory is considered the master path because it +contains the most critical information (i.e., the information that +can't be absent) required to produce Anaconda images for major release +5 of CentOS distribution. @item trunk/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi -This file contains documentation, in Texinfo format, for Default -design models used to produce the Anaconda images used inside CentOS -distribution major release 5. +This file contains documentation, in Texinfo format, for +@file{Default} design models used to produce the Anaconda images +required by major release 5 of CentOS distribution. -Here is where you, as documentor, describe construction of Default -desing models used to produce the Anaconda images for CentOS -distribution major release 5. In this description you can include -image dimensions, color information, image location inside -distribution filesystem, image packaging and similar things. +@verbatim + A B C +|-----------------------|------------------------------------------------------|---| +trunk/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi +|-----------------------|------------------------------------------------------|---| + +A = The documentation manual source location. +B = The master path we are building documentation for. +C = The file extension used by Texinfo documentation files. +@end verbatim -The path to this file is considered auxiliar to -@file{trunk/Identity/Themes/Models/Default/Distro/5/Anaconda} master -path because provides the description required to let everyone know -how to build Default design models used to produce Anaconda images -required by CentOS distribution major release 5. +Here is where you, as documentor, describe construction of +@file{Default} design models used to produce the Anaconda images +required by major release 5 of CentOS distribution. In this +description you can include image dimensions, color information, image +location inside the file system of CentOS distribution, packaging and +similar things. + +The path to this directory is considered auxiliar path of +@file{trunk/Identity/Themes/Models/Default/Distro/5/Anaconda} master path. @item trunk/Locales/Identity/Themes/Models/Default/Distro/5/Anaconda @@ -464,7 +523,7 @@ Here is where you, as documentor, describe localization of Default desing models used to produce the Anaconda images used in CentOS distribution major release 5. In this description you can include image dimensions, color information, image location inside -distribution filesystem, image packaging and similar things. +distribution filesystem, packaging and similar things. The path to this file is considered auxiliar to @file{trunk/Identity/Themes/Models/Default/Distro/5/Anaconda} master diff --git a/Manual/repository.info.bz2 b/Manual/repository.info.bz2 index aacb46e..8feddb1 100644 Binary files a/Manual/repository.info.bz2 and b/Manual/repository.info.bz2 differ diff --git a/Manual/repository.pdf b/Manual/repository.pdf index 89be08d..67c9132 100644 Binary files a/Manual/repository.pdf and b/Manual/repository.pdf differ diff --git a/Manual/repository.txt.bz2 b/Manual/repository.txt.bz2 index d2c2af9..483e8a5 100644 Binary files a/Manual/repository.txt.bz2 and b/Manual/repository.txt.bz2 differ diff --git a/Manual/repository.xhtml.tar.bz2 b/Manual/repository.xhtml.tar.bz2 index d9a0cbc..ab13707 100644 Binary files a/Manual/repository.xhtml.tar.bz2 and b/Manual/repository.xhtml.tar.bz2 differ diff --git a/Manual/repository.xml b/Manual/repository.xml index 61ee0a8..a397f6a 100644 --- a/Manual/repository.xml +++ b/Manual/repository.xml @@ -294,11 +294,11 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Introduction
Repository Convenctions - Repository convenctionsThe CentOS Artwork Repository is supported by Subversion (http://subversion.tigris.org/), 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. In Subversion repositories 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 works in a descentralized way. The source repository, on the other hand, provides a central place for all independent working copies to interchange data and the information required to permit extracting previous versions of files at any time. + Repository convenctionsThe CentOS Artwork Repository is supported by Subversion (http://subversion.tigris.org/), 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. 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 works in a descentralized way. The source repository, on the other hand, provides a central place for all independent working copies to interchange data and the information required to permit extracting previous versions of files at any time. Repository policy - The CentOS Artwork Repository is a collaborative tool where many people can have access to. However, changing that tool in any form is something that should be requested in centos-devel@centos.org mailing list. 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 work the way expected and request access to commit them up to the CentOS Artwork Repository for others to benefit from them. + 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 centos-devel@centos.org mailing list. 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 work the way expected and request access to commit them up to the CentOS Artwork Repository for others to benefit from them. 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 good community citizen. As a good community citizen one understand of a person whom respects the work already done for others and share ideas with authors before changing relevant parts of their work, specially in situations when the access required to realize those 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 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. 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 comply its mission which is: to provide a colaborative tool for The CentOS Community where The CentOS Project Corporate Identity is built and maintained from The CentOS Community itself. @@ -337,9 +337,8 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Repository work lines - Work lines describe different areas of content production inside CentOS Artwork Repository. 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. To produce content in a syncronized but descentralized way, it is required to define a standard for content production that let each work line to exists that way. + Inside CentOS Artwork Repository there are four major production work lines 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. To produce content in a syncronized but descentralized way, it is required to define a content production standard that lead everyone work in order for the content produced in each different work line to gear correctly once it is put together. The standard way of producing content inside CentOS Artwork Repository is implemented through centos-art.sh script and described in trunk/Scripts documentation entry (see Directories trunk Scripts). - Inside CentOS Artwork Repository there are four major production work lines. They are: graphic design, documentation, localization and automation. Graphic design @@ -360,8 +359,8 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Documentation The documentation work line exists to describe what each directory inside the CentOS Artwork Repository is for and how to produce content inside them. - The CentOS Artwork Repository documentation is supported by Texinfo, a documentation system that uses a single source file to produce both online information and printed output. The repository documentation is organized under trunk/Manual directory structure using repository directories as reference. Directories inside CentOS Artwork Repository are created based on conceptual idea, so one documentation entry exists for each directory inside the repository in order to describe the conceptual ideas such directory is based. - Directory documentation entries are stored under trunk/Manual/Directories directory structure and controlled by the help functionality of centos-art.sh script. Using help functionality you can create, edit and remove directory documentation in a way you don't need to take care of updating menus, nodes and cross reference information inside the manual structure; the functionality takes care of it for you. However, if you need to write repository documentation that have nothing to do with repository directories (e.g., Preface, Introduction and similar) you need to do it manually, there is no functionality to automate such process yet. + The CentOS Artwork Repository documentation is supported by Texinfo, a documentation system that uses a single source file to produce both online information and printed output. The repository documentation is organized under trunk/Manual directory structure using repository directories as reference. Directories inside CentOS Artwork Repository are created based on conceptual idea, so one documentation entry exists for each directory inside the repository in order to describe the conceptual ideas such directory is based on. + Directory documentation entries are stored under trunk/Manual/Directories directory structure and controlled by the help functionality of centos-art.sh script. Using the help functionality you can create, edit and remove directory documentation in a way you don't need to take care of updating menus, nodes and cross reference information inside the manual structure; the functionality takes care of it for you. However, if you need to write repository documentation that have nothing to do with repository directories (e.g., Preface, Introduction and similar) you need to do it manually, there is no functionality to automate such process yet. See Directories trunk Manual, for more information on documentation. @@ -380,10 +379,10 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Automation - The automation work line exists to standardize content production inside CentOS Artwork Repository. There is no need to repeat several tasks time after time if they can be programmed into just one script that groups them all. - The automation work line is take place under trunk/Scripts directory structure. Here is developed the centos-art.sh script, a bash script specially designed to automate most frequent tasks inside CentOS Artwork Repository. Basically, the centos-art.sh script is divided in several functionalities that perform specific tasks inside the repository. Such functionalities relay on repository organization to work as expected. + The automation work line exists to standardize content production inside CentOS Artwork Repository. There is no need to type several tasks time after time if they can be programmed into just one script that groups them all. + The automation work line takes place under trunk/Scripts directory structure. Here is developed the centos-art.sh script, a bash script specially designed to automate most frequent tasks inside CentOS Artwork Repository. Basically, the centos-art.sh script is divided in several functionalities that perform specific tasks inside the repository. Such functionalities relay on repository organization to work as expected. - Tip If you need to improve the way content is produced, look inside automation scripts and make your improvement there for every one to benefit. + Tip If you need to improve the way content is produced, look inside automation scripts and make your improvement there for everyone to benefit. See Directories trunk Scripts, for more information on automation. @@ -391,75 +390,124 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Connection between directories - In order to produce content correctly inside CentOS Artwork Repository, it is required that all work lines be connected somehow. This is the way automation scripts can know what design model and what translation files to use when specific contents are produced, also where to save the content produced as result. This connection between directories takes place through two path constructions named The Master Path and The Auxiliar Paths. - As master path consider the last directory, inside a directory structure, which contains the source files (e.g., SVG files) required to produce base content (e.g., PNG files). Master paths are backup by auxiliar paths. - Auxiliar paths provide the files that modify production of base content produced from master paths. Auxiliar paths take their structure from one unique master path. Master paths can have several auxiliar paths associated, but auxiliar paths can have only one master path associated. - For example, consider The CentOS Brands path relation: + In order to produce content correctly inside CentOS Artwork Repository, it is required that all work lines be connected somehow. This is the way automation scripts can know what design model and what translation files to use when specific contents are produced, also where to save the content produced as result. This connection between directories takes place through two path constructions named The Master Paths and The Auxiliar Paths. + The master paths point to directories which contain the source files (e.g., SVG files) required to produce base content (e.g., PNG files). Each master path inside the repository has several auxiliar paths associated. + 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 the master path (e.g., through translation messages) or provides the output information of where to store the content produced from master path. When an auxiliar path points to a file, that file has no other purpose but document the master path it refers to. + The relation between auxiliar paths and master paths is realized taking one unique master path as reference. Master paths define how auxiliar paths are constructed. Master paths can have several auxiliar paths associated, but auxiliar paths can have only one master path associated. For example, consider the following path relation and note how there are constant and variable values in them: trunk/Identity/Models/Brands This directory contains source files (e.g., SVG, XCF, etc.) used to produce the brand images of The CentOS Project. Here is where you, as graphic designers, define design models used to produce the brand images of The CentOS Project. - The path to this directory is considered master because it contains the most critical information (i.e., the information that can't be absent) required to produce the brand images of The CentOS Project. + The path to this directory is considered a master path because it contains the most critical information (i.e., the information that can't be absent) required to produce the brand images of The CentOS Project. trunk/Manual/Directories/trunk/Identity/Models/Brands.texi - This file contains documentation, in Texinfo format, for design models used to produce the brand images of The CentOS Project. - Here is where you, as documentor, describe construction of desing models used to produce the brand images of The CentOS Project. In this description you can include image dimensions, color information, image location inside CentOS Distribution filesystem, image packaging and similar things. - The path to this file is considered auxiliar to trunk/Identity/Models/Brands master path because it provides the description required to let everyone know how to build design models used to produce the brand images of The CentOS Project. + This file contains documentation, in Texinfo format, for design models used to produce the brand images of The CentOS Project. The path to this file is made of three parts: + + Here is where you, as documentor, describe construction of desing models used to produce the brand images of The CentOS Project. In this description you can include image dimensions, color information, image location inside CentOS Distribution filesystem, packaging and similar things. + The path to this directory is considered auxiliar path of trunk/Identity/Models/Brands master path. trunk/Locales/Identity/Models/Brands - This directory contains translation files, as gettext portable objects, for design models used to produce the brand images of The CentOS Project. + This directory contains translation files, as gettext portable objects, for design models used to produce the brand images of The CentOS Project. The path to this directory made of two parts: + Here is where you, as translator, localize translatable strings retrived in English language from design models used to produce the brand images of The CentOS Project. If no portable object is found here the translation tasks are skipped to produce no translation at all, obviously there is no portable object to retrive translation messages from. - The path to this directory provides language-specific information required to produce the brand images of The CentOS Project, so it is considered auxiliar path of trunk/Identity/Models/Brands master path. + The path to this directory is considered auxiliar path of trunk/Identity/Models/Brands master path. trunk/Manual/Directories/trunk/Locales/Identity/Models/Brands.texi - This file contains documentation, in Texinfo format, for translation messages retrived from design models used to produce The CentOS Brands required by The CentOS Project. - Here is where you, as documentor, describe localization of desing models used to produce The CentOS Brands images required by The CentOS Project. In this description you can include image dimensions, color information, image location inside CentOS Distribution filesystem, image packaging and similar things. - The path to this file provides documentation to language-specific directory structure used to store translation messages used to produce the brand images of The CentOS Project, so it is considered auxiliar path of trunk/Identity/Models/Brands master path. + This file contains documentation, in Texinfo format, for translation messages retrived from design models used to produce brand images required by The CentOS Project. The path to this file is made of three parts: + + Here is where you, as documentor, describe localization of those desing models used to produce brand images required by The CentOS Project. In this description you can include image dimensions, color information, image location inside the file system of CentOS Distribution, packaging and similar things. + The path to this file is considered auxiliar path of trunk/Identity/Models/Brands master path. trunk/Identity/Images/Brands - This directory contains the final image produced from The CentOS Brands design models used by The CentOS Project. - Here is where you, as packager, can find the images you need to rebrand the brand images related to CentOS Distribution. - The path to this directory contains the final brand images of The CentOS Project, so it is considered auxiliar path of trunk/Identity/Models/Brands master path. + This directory contains the final brand images produced from brand design models used by The CentOS Project. + Here is where you, as packager, can find the brand images you need to rebrand the CentOS Distribution. + The path to this directory is considered auxiliar path of trunk/Identity/Models/Brands master path. trunk/Manual/Directories/trunk/Identity/Images/Brands.texi - This file should contains documentation, in Texinfo format, about how to implement final brand images of The CentOS Project. However, this documentation entry is rarely created because the related design model documentation entry already covers implementation of images produced here. The only reason to create this documentation entry is to put in an admonition that redirect people up to the design model related documentation entry where documentation related to implementation is. + This file should contains documentation, in Texinfo format, about how to implement final brand images of The CentOS Project. However, this documentation entry is rarely used because the related design model documentation entry already covers implementation of brand images. The only reason to create this documentation entry is to put in an admonition that redirect people up to the correct place (i.e., the related design model coumentation entry).
- The configuration described above for organizing brand component inside the repository is the one used by direct rendition and can be used as reference to organize other components inside the repository that are produced through direct rendition too. Just change the component name from brands to that one you want to add without changing the path structure around it. - The file organization used by theme rendition, however, is a bit different from that used by direct rendition. In theme rendition, both master paths and auxiliar paths are built dynamically based on the design model and the artistic motif you specify at rendition time. As a mnemotechnic resource, consider theme rendition as two independent lists, one list of design models and one list of artistic motifs, which are arbitrary combined between themselves in order to render images. For example, consider the organization used to produce Anaconda images for CentOS distribution major release 5 that use the Default design model and the Flame version 3 artistic motif: + The configuration described above for organizing brand component inside the repository is the one used by direct rendition and can be used as reference to organize other components inside the repository that are produced through direct rendition too. Just change the component name from Brands to a different one without changing the path structure around it. + The file organization used by theme rendition, however, is a bit different from that used by direct rendition. In theme rendition, both the master paths and the auxiliar paths are built dynamically based on one design model and one artistic motif specified by you at rendition time. As a mnemotechnic resource, you could consider theme rendition as two independent lists, one of design models and one of artistic motifs, which are arbitrary combined between themselves in order to render images in specific ways. For example, consider the organization used to produce Anaconda images; for CentOS distribution major release 5; using Default design models and version 3 of Flame artistic motif: trunk/Identity/Themes/Models/Default/Distro/5/Anaconda - This directory contains source files used to produce Anaconda images for CentOS distribution major release 5 using Default design models. - Here is where you, as graphic designers, define Default design models for Anaconda images used in CentOS distribution major release 5. - The path to this directory is considered master because it contains the most critical information (i.e., the information that can't be absent) required to produce Anaconda images used inside CentOS distribution major release 5. + This directory contains source files used to produce Anaconda images for CentOS distribution major release 5. This specific information has been named the Default design model. The path to this directory is made of three parts: + + Here is where you, as graphic designers, define Default design models for Anaconda images in major release 5 of CentOS distribution. + The path to this directory is considered the master path because it contains the most critical information (i.e., the information that can't be absent) required to produce Anaconda images for major release 5 of CentOS distribution. trunk/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi - This file contains documentation, in Texinfo format, for Default design models used to produce the Anaconda images used inside CentOS distribution major release 5. - Here is where you, as documentor, describe construction of Default desing models used to produce the Anaconda images for CentOS distribution major release 5. In this description you can include image dimensions, color information, image location inside distribution filesystem, image packaging and similar things. - The path to this file is considered auxiliar to trunk/Identity/Themes/Models/Default/Distro/5/Anaconda master path because provides the description required to let everyone know how to build Default design models used to produce Anaconda images required by CentOS distribution major release 5. + This file contains documentation, in Texinfo format, for Default design models used to produce the Anaconda images required by major release 5 of CentOS distribution. + + Here is where you, as documentor, describe construction of Default design models used to produce the Anaconda images required by major release 5 of CentOS distribution. In this description you can include image dimensions, color information, image location inside the file system of CentOS distribution, packaging and similar things. + The path to this directory is considered auxiliar path of trunk/Identity/Themes/Models/Default/Distro/5/Anaconda master path. @@ -474,7 +522,7 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh trunk/Manual/Directories/trunk/Locales/Identity/Themes/Models/Default/Distro/5/Anaconda.texi This file contains documentation, in Texinfo format, for translation messages retrived from Default design models used to produce the Anaconda images used inside CentOS distribution major release 5. - Here is where you, as documentor, describe localization of Default desing models used to produce the Anaconda images used in CentOS distribution major release 5. In this description you can include image dimensions, color information, image location inside distribution filesystem, image packaging and similar things. + Here is where you, as documentor, describe localization of Default desing models used to produce the Anaconda images used in CentOS distribution major release 5. In this description you can include image dimensions, color information, image location inside distribution filesystem, packaging and similar things. The path to this file is considered auxiliar to trunk/Identity/Themes/Models/Default/Distro/5/Anaconda master path because provides the language-specific information required to produce Anaconda Default design models in different languages. Each master path has its own auxiliar path to store their specific documentation and whatever the artistic motifs used to produce images be is somthing irrelevant.