From de471479869e7c383de6911c4f29d3dcfd5389d5 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Jun 24 2011 20:40:44 +0000 Subject: Update repository documentation manual in docbook format. --- diff --git a/Manuals/Repository/Docbook/Commons.ent b/Manuals/Repository/Docbook/Commons.ent index bb482c0..f42fa3b 100644 --- a/Manuals/Repository/Docbook/Commons.ent +++ b/Manuals/Repository/Docbook/Commons.ent @@ -34,7 +34,7 @@ &TCA; Repository"> &TCA; SIG"> - +&TCAR; User's Guide"> &TCA; Mailing List"> &TC; Developers Mailing List"> diff --git a/Manuals/Repository/Docbook/Identity/Project/behaviour.docbook b/Manuals/Repository/Docbook/Identity/Project/behaviour.docbook index 2f8220d..bd22f04 100755 --- a/Manuals/Repository/Docbook/Identity/Project/behaviour.docbook +++ b/Manuals/Repository/Docbook/Identity/Project/behaviour.docbook @@ -1,4 +1,21 @@ + Corporate Behaviour - ... + + + &TCP; corporate behaviour is focused on the effective + interaction of each member involved in the organization (e.g., + core developers, community members, etc.). It is related to + ethics and politics used to do the things inside the + organization. It is related to the sense of direction chosen + by the organization and they way the organization projects + itself to achieve it. + + + + &TCP; corporate behaviour takes place through &TCP; corporate + communication, as described in . + + diff --git a/Manuals/Repository/Docbook/Identity/Project/communication.docbook b/Manuals/Repository/Docbook/Identity/Project/communication.docbook index 463efcc..b87dd32 100755 --- a/Manuals/Repository/Docbook/Identity/Project/communication.docbook +++ b/Manuals/Repository/Docbook/Identity/Project/communication.docbook @@ -1,4 +1,141 @@ + Corporate Communication - ... + + + &TCP; corporate communication is focused on the effective + propagation of corporate messages. Propagation of corporate + messages is closely related to the media the organization uses + as vehicle to distribute its corporate messages. + + + + &TCP; corporate communication takes place through the + following visual manifestations: + + + + + &TCD; + + + This visual manifestation communicates its existence + through software packages. There are packages that make a + remarkable use of images, packages that make a moderate + use of images, and packages that don't use images at all. + This visual manifestation is focused on providing &TCP; + images required by software packages that do use images in + a remarkable way, specially those holding the upstream + brand (e.g., anaconda, + grub, syslinux, + gdm, kdebase). + + + + + The Community Enterprise Operating System itself + (communicates the essense of &TCP; existence.). + + + + + Release Schema (Lifetime) and all the stuff related (e.g., + Release Notes, Documentation, Erratas, etc.). + + + + + + + + &TCW; + + + This visual manifestation communicates its existence + through web applications. These web applications are free + software and come from different providers which + distribute their work with predefined visual styles. + Frequently, these predefined visual styles have no visual + relation among themselves and introduce some visual + contraditions when they all are put together. Removing + these visual contraditions is object of work for this + visual manifestation. + + + + + The CentOS Chat. + + + + + The CentOS Mailing Lists. + + + + + The CentOS Forums. + + + + + The CentOS Wiki. + + + + + Special Interest Groups (SIGs). + + + + + Social Events, Interviews, Conferences, etc. + + + + + The extensive network of mirrors available for downloading + ISO files as well as RPMs and SRPMs used to build them up + in different architectures. + + + + + + + + &TCS; + + + This visual manifestation communicates its existence + through production of industrial objects carrying &TCB;. + These branded objects are directed to be distributed on + social events and/or shops. They provide a way of + promotion and commercialization that may help to reduce + &TCP; expenses (e.g., electrical power, hosting, servers, + full-time-developers, etc.), in a similar way as donations + may do. + + + + + Stationery (e.g., Posters, Stickers, CD Lables and Sleeves). + + + + + Clothes (e.g., Shirts, T-shirts, Pullovers, Caps). + + + + + Installation media (e.g., CDs, DVD, Pendrives). + + + + + + + + diff --git a/Manuals/Repository/Docbook/Identity/Project/design.docbook b/Manuals/Repository/Docbook/Identity/Project/design.docbook index b8a8568..c1df9af 100755 --- a/Manuals/Repository/Docbook/Identity/Project/design.docbook +++ b/Manuals/Repository/Docbook/Identity/Project/design.docbook @@ -3,7 +3,7 @@ Corporate Design - The corporate design is focused on the effective communication + The corporate design is focused on the effective presentation of corporate messages. As corporate messages we understand all the information emitted from the organization; and when we say all we mean everything that can be @@ -14,14 +14,14 @@ When the organization doesn't take control over the corporate - messages it produces, the organization is letting that area to - the unknown and the results might be good or not so good, it - is hard to know. The issue to see here is that even the - organization doesn't take control over its corporate messages, - they are always talking about the organization. Taking - control of corporate messages is a decition the organization - needs to take by itslef, based on its need of better describe - what it is. + messages it produces, the organization is letting that area of + its identity to the unknown and the results might be good or + not so good, it is hard to know. The issue to see here is + that even the organization doesn't take control over its + corporate messages, they are always talking about the + organization. Taking control of corporate messages is a + decition the organization needs to take by itself, based on + its need of better describe what it is. @@ -29,10 +29,11 @@ attention on corporate messages that reach us through the visual sense. This is, all the visual manifestations &TCP; is made of. As visual manifestaions we understand all the visible - media &TCP; uses to manifest its existence. At this point it - necessary to consider what &TCP; is, what its mission is and - what it is producing; this in order to define which are the - visual manifestation demanding attention of corporate design. + media &TCP; uses to manifest its existence on. At this point + it is necessary to consider what &TCP; is, what its mission is + and what it is producing. This, in order to identify which + visual manifestations the organization is demanding attention + of corporate design for. @@ -43,11 +44,10 @@ &TCD; — This visual manifestation exists to cover - all actions related to artwork production and rebranding - required by &TCP; in order to comply with its - upstream's redistribution guidelines. This visual - manifestation is described in . + all actions related to artwork production and rebranding, + required by &TCD; in order to comply with upstream's + redistribution guidelines. This visual manifestation is + described in . @@ -76,13 +76,13 @@ - The visual manifestations above seem to cover most media - required by &TCP; as organization, to show its existence. - However, other visual manifestations could be added in the - future, as long as they be needed, to cover different areas - like stands, building, offices, road transportation or - whaterver visual manifestation &TCP; thouches to show its - existence. + The visual manifestations identified above seem to cover most + media required by &TCP;, as organization, to show its + existence. However, other visual manifestations could be + added in the future, as long as they be needed, to cover + different areas like stands, buildings, offices, road + transportation or whaterver visual manifestation &TCP; + thouches to show its existence. @@ -90,7 +90,7 @@ defined through design models, it is time to visually remark their connection with &TCP;. This kind of connection is realized by applying &TCB; to design models inside visual - manifestation supported through corporate design. + manifestations supported through corporate design. diff --git a/Manuals/Repository/Docbook/Identity/Project/mission.docbook b/Manuals/Repository/Docbook/Identity/Project/mission.docbook index b369ab1..507873d 100644 --- a/Manuals/Repository/Docbook/Identity/Project/mission.docbook +++ b/Manuals/Repository/Docbook/Identity/Project/mission.docbook @@ -1,10 +1,40 @@ + Corporate Mission + - The CentOS Project exists to provide The CentOS Distribution. - Additionally, The CentOS Project provides The CentOS Web and - The CentOS Showroom to support and promote the existence of - The CentOS Distribution, respectively. + &TCP; exists to produce &TCD;, an Enterprise-class Linux + Distribution derived from sources freely provided to the + public by a prominent North American Enterprise Linux vendor. + &TCD; conforms fully with the upstream vendors redistribution + policy and aims to be 100% binary compatible. (&TCD; mainly + changes packages to remove upstream vendor branding and + artwork.). - + + &TCD; is developed by a small but growing team of core + developers. In turn the core developers are supported by an + active user community including system administrators, network + administrators, enterprise users, managers, core Linux + contributors and Linux enthusiasts from around the world. + + + + &TCD; has numerous advantages including: an active and growing + user community, quickly rebuilt, tested, and QA'ed errata + packages, an extensive mirror network, developers who are + contactable and responsive of a reliable Enterprise-class + Linux Distribution, multiple free support avenues including a + Wiki, + IRC + Chat, Email Lists, Forums, and + a dynamic FAQ. + + + diff --git a/Manuals/Repository/Docbook/Identity/Project/structure.docbook b/Manuals/Repository/Docbook/Identity/Project/structure.docbook index 0dcc103..b1042d7 100755 --- a/Manuals/Repository/Docbook/Identity/Project/structure.docbook +++ b/Manuals/Repository/Docbook/Identity/Project/structure.docbook @@ -1,4 +1,91 @@ + Corporate Structure - ... + + + &TCP; corporate structure is based on a &MCVIS;. In this + configuration, one unique name and one unique visual style is + used in all visual manifestation &TCP; is made of. + + + + In a monolithic corporate visual identity structure, internal + and external stakeholders use to feel a strong sensation of + uniformity, orientation, and identification with the + organization. No matter if you are visiting web sites, using + the distribution, or acting on social events, the one unique + name and one unique visual style connects them all to say: + Hey! we are all part of &TCP;. + + + + Other corporate structures for &TCP; have been considered as + well. Such is the case of producing one different visual style + for each major release of &TCD;. This structure isn't + inconvenient at all, but some visual contradictions could be + introduced if it isn't applied correctly and we need to be + aware of it. To apply it correctly, we need to know what &TCP; + is made of. + + + + &TCP;, as organization, is mainly made of (but not limited to) + three visual manifestions: &TCD;, &TCW; and &TCS;. Inside + &TCD; visual manifestations, &TCP; maintains near to four + different major releases of &TCD;, parallely in time. + However, inside &TCW; visual manifestations, the content is + produced for no specific release information (e.g., there is + no a complete web site for each major release of &TCD; + individually, but one web site to cover them all). Likewise, + the content produced in &TCS; is industrially created for no + specific release, but &TCP; in general. + + + + In order to produce the &TCPMCVIS; correctly, we need to + concider all the visual manifestations &TCP; is made of, not + just one of them. If one different visual style is + implemented for each major release of &TCD;, which one of + those different visual styles would be used to cover the + remaining visual manifestations &TCP; is made of (e.g., &TCW; + and &TCS;)? + + + + Probably you are thinking: yes, I see your point, but &TCB; + connects them all already, why would we need to join them up + into the same visual style too, isn't it more work to do, and + harder to maintain? + + + + Harder to maintain, more work to do, probably. Specially when + you consider that &TCP; has proven stability and consistency + through time and, that, certainly, didn't come through + swinging magical wands or something but hardly working out to + automate tasks and providing maintainance through time. With + that in mind, we consider &TCPCVIS; must be consequent with + such stability and consistency tradition. It is true that + &TCB; does connect all the visual manifestations it is present + on, but that connection is strengthened if one unique visual + style backups it. In fact, whatever thing you do to strength + the visual connection among &TCP; visual manifestations would + be very good in favor of &TCP; recognition. + + + + Obviously, having just one visual style in all visual + manifestations for eternity would be a very boring thing and + would give the idea of a visually dead project. So, there is + no problem on creating a brand new visual style for each new + major release of &TCD;, in order to refresh &TCD; visual + style; the problem itself is in not propagating the brand new + visual style created for the new release of &TCD; to all other + visual manifestations &TCP; is made of, in a way &TCP; could + be recognized no matter what visual manifestation be in front + of us. Such lack of uniformity is what introduces the visual + contradition we are precisely trying to solve by mean of + themes production in &TCAR;. + + diff --git a/Manuals/Repository/Docbook/Introduction.docbook b/Manuals/Repository/Docbook/Introduction.docbook index 556e8ef..03f3458 100644 --- a/Manuals/Repository/Docbook/Introduction.docbook +++ b/Manuals/Repository/Docbook/Introduction.docbook @@ -1,33 +1,11 @@ - + - Introduction + Repository - - - - Welcome to &TCARUG;. - - - - &TCARUG; describes how &TCPCVI; is organized and produced - inside &TCAR;. If you are looking for a comprehensive, - task-oriented guide for understanding how &TCPCI; is produced, - this is the manual for you. - - - - This manual assumes you have a basic understanding of &TCD;. - If you need help with it, refer to the help page on The CentOS Wiki for - a list of different places you can find help. - - - - - &intro-history; - &intro-copying; - &intro-usage; - &intro-worklines; - &intro-layout; + &repo-history; + &repo-copying; + &repo-usage; + &repo-worklines; + &repo-layout; diff --git a/Manuals/Repository/Docbook/Introduction.ent b/Manuals/Repository/Docbook/Introduction.ent index 0def013..9f38ae1 100644 --- a/Manuals/Repository/Docbook/Introduction.ent +++ b/Manuals/Repository/Docbook/Introduction.ent @@ -1,28 +1,28 @@ - + - - - - + + + + - - + + - + - - - - - - + + + + + + - + - - - - - + + + + + - + diff --git a/Manuals/Repository/Docbook/Introduction/Copying.docbook b/Manuals/Repository/Docbook/Introduction/Copying.docbook index 20cdc88..7021d72 100644 --- a/Manuals/Repository/Docbook/Introduction/Copying.docbook +++ b/Manuals/Repository/Docbook/Introduction/Copying.docbook @@ -1,4 +1,4 @@ - + Repository Copying Conditions diff --git a/Manuals/Repository/Docbook/Introduction/History.docbook b/Manuals/Repository/Docbook/Introduction/History.docbook index 354a6e6..7738cef 100644 --- a/Manuals/Repository/Docbook/Introduction/History.docbook +++ b/Manuals/Repository/Docbook/Introduction/History.docbook @@ -1,4 +1,4 @@ - + Repository History @@ -34,8 +34,8 @@ the repository to produce slide images in their own languages. - &intro-history-2009; - &intro-history-2010; - &intro-history-2011; + &repo-history-2009; + &repo-history-2010; + &repo-history-2011; diff --git a/Manuals/Repository/Docbook/Introduction/Layout.docbook b/Manuals/Repository/Docbook/Introduction/Layout.docbook index 16f3ba4..46fc98b 100644 --- a/Manuals/Repository/Docbook/Introduction/Layout.docbook +++ b/Manuals/Repository/Docbook/Introduction/Layout.docbook @@ -1,4 +1,4 @@ - + Repository Layout @@ -46,20 +46,18 @@ The second level of directories in the repository provides organization for each work line described in . + linkend="repo-worklines" />. All other subsequent levels of directories in the repository, from third level on, are created to organize specific concepts - related to the work line they are in. A complete reference for - each directory inside &TCAR; is available at . + related to the work line they are in. - &intro-layout-filenames; - &intro-layout-relbdirs; - &intro-layout-syncpaths; - &intro-layout-extending; + &repo-layout-filenames; + &repo-layout-relbdirs; + &repo-layout-syncpaths; + &repo-layout-extending; diff --git a/Manuals/Repository/Docbook/Introduction/Layout/extending.docbook b/Manuals/Repository/Docbook/Introduction/Layout/extending.docbook index 3b050a6..d99c721 100644 --- a/Manuals/Repository/Docbook/Introduction/Layout/extending.docbook +++ b/Manuals/Repository/Docbook/Introduction/Layout/extending.docbook @@ -1,4 +1,4 @@ - + Extending Repository Layout diff --git a/Manuals/Repository/Docbook/Introduction/Layout/filenames.docbook b/Manuals/Repository/Docbook/Introduction/Layout/filenames.docbook index d66230a..6941b4e 100644 --- a/Manuals/Repository/Docbook/Introduction/Layout/filenames.docbook +++ b/Manuals/Repository/Docbook/Introduction/Layout/filenames.docbook @@ -1,4 +1,4 @@ - + File Names diff --git a/Manuals/Repository/Docbook/Introduction/Layout/relbdirs.docbook b/Manuals/Repository/Docbook/Introduction/Layout/relbdirs.docbook index d97d300..967bb8e 100644 --- a/Manuals/Repository/Docbook/Introduction/Layout/relbdirs.docbook +++ b/Manuals/Repository/Docbook/Introduction/Layout/relbdirs.docbook @@ -1,4 +1,4 @@ - + Path Types diff --git a/Manuals/Repository/Docbook/Introduction/Layout/syncpaths.docbook b/Manuals/Repository/Docbook/Introduction/Layout/syncpaths.docbook index a6e8219..7b4ec2d 100644 --- a/Manuals/Repository/Docbook/Introduction/Layout/syncpaths.docbook +++ b/Manuals/Repository/Docbook/Introduction/Layout/syncpaths.docbook @@ -1,4 +1,4 @@ - + Path Syncronization diff --git a/Manuals/Repository/Docbook/Introduction/Usage.docbook b/Manuals/Repository/Docbook/Introduction/Usage.docbook index 56e91e2..b989fc4 100644 --- a/Manuals/Repository/Docbook/Introduction/Usage.docbook +++ b/Manuals/Repository/Docbook/Introduction/Usage.docbook @@ -1,4 +1,4 @@ - + Repository Usage Conditions diff --git a/Manuals/Repository/Docbook/Introduction/Worklines.docbook b/Manuals/Repository/Docbook/Introduction/Worklines.docbook index 3e0c156..e07819f 100644 --- a/Manuals/Repository/Docbook/Introduction/Worklines.docbook +++ b/Manuals/Repository/Docbook/Introduction/Worklines.docbook @@ -1,4 +1,4 @@ - + Repository Work Lines @@ -13,9 +13,9 @@ descentralized environment. - &intro-worklines-identity; - &intro-worklines-l10n; - &intro-worklines-manuals; - &intro-worklines-scripts; + &repo-worklines-identity; + &repo-worklines-l10n; + &repo-worklines-manuals; + &repo-worklines-scripts; diff --git a/Manuals/Repository/Docbook/Introduction/Worklines/identity.docbook b/Manuals/Repository/Docbook/Introduction/Worklines/identity.docbook index f920bc0..78205e7 100644 --- a/Manuals/Repository/Docbook/Introduction/Worklines/identity.docbook +++ b/Manuals/Repository/Docbook/Introduction/Worklines/identity.docbook @@ -1,6 +1,6 @@ - + - Graphic Design + Visual Identity In the production cycle, the first step takes place through @@ -23,8 +23,4 @@ images required by each visual manifestaions. - - Most works related to graphic design are - - diff --git a/Manuals/Repository/Docbook/Introduction/Worklines/l10n.docbook b/Manuals/Repository/Docbook/Introduction/Worklines/l10n.docbook index 31f5ebc..8134155 100644 --- a/Manuals/Repository/Docbook/Introduction/Worklines/l10n.docbook +++ b/Manuals/Repository/Docbook/Introduction/Worklines/l10n.docbook @@ -1,4 +1,4 @@ - + Localization diff --git a/Manuals/Repository/Docbook/Introduction/Worklines/manuals.docbook b/Manuals/Repository/Docbook/Introduction/Worklines/manuals.docbook index 1718f28..ef40f87 100644 --- a/Manuals/Repository/Docbook/Introduction/Worklines/manuals.docbook +++ b/Manuals/Repository/Docbook/Introduction/Worklines/manuals.docbook @@ -1,4 +1,4 @@ - + Documentation diff --git a/Manuals/Repository/Docbook/Introduction/Worklines/scripts.docbook b/Manuals/Repository/Docbook/Introduction/Worklines/scripts.docbook index 0ceaa6b..53780f9 100644 --- a/Manuals/Repository/Docbook/Introduction/Worklines/scripts.docbook +++ b/Manuals/Repository/Docbook/Introduction/Worklines/scripts.docbook @@ -1,4 +1,4 @@ - + Automation diff --git a/Manuals/Repository/Docbook/Preface.docbook b/Manuals/Repository/Docbook/Preface.docbook new file mode 100644 index 0000000..e6e0f1c --- /dev/null +++ b/Manuals/Repository/Docbook/Preface.docbook @@ -0,0 +1,26 @@ + + + Introduction + + + Welcome to &TCARUG;. + + + + &TCARUG; describes how &TCPCVI; is organized and produced + inside &TCAR;. If you are looking for a comprehensive, + task-oriented guide for understanding how &TCPCI; is produced, + this is the manual for you. + + + + This manual assumes you have a basic understanding of &TCD;. + If you need help with it, refer to the help page on The CentOS Wiki for + a list of different places you can find help. + + + &intro-docconvs; + &intro-feedback; + + diff --git a/Manuals/Repository/Docbook/Preface.ent b/Manuals/Repository/Docbook/Preface.ent index 0befb95..0f4f354 100644 --- a/Manuals/Repository/Docbook/Preface.ent +++ b/Manuals/Repository/Docbook/Preface.ent @@ -1,2 +1,3 @@ - - + + + diff --git a/Manuals/Repository/Docbook/Preface/Docconvs.docbook b/Manuals/Repository/Docbook/Preface/Docconvs.docbook index aae176d..8ee2ff3 100644 --- a/Manuals/Repository/Docbook/Preface/Docconvs.docbook +++ b/Manuals/Repository/Docbook/Preface/Docconvs.docbook @@ -1,4 +1,4 @@ - +
Document Convenctions @@ -247,4 +247,4 @@ render_getDirOutput.sh render.sh corrupted system environment. - +
diff --git a/Manuals/Repository/Docbook/Preface/Feedback.docbook b/Manuals/Repository/Docbook/Preface/Feedback.docbook index 499ee25..f690b2a 100644 --- a/Manuals/Repository/Docbook/Preface/Feedback.docbook +++ b/Manuals/Repository/Docbook/Preface/Feedback.docbook @@ -1,4 +1,4 @@ - +
Send in Your Feedback @@ -15,4 +15,4 @@ find it easily. - +
diff --git a/Manuals/Repository/Docbook/repository.docbook b/Manuals/Repository/Docbook/repository.docbook index 4bd43a7..49d6d34 100644 --- a/Manuals/Repository/Docbook/repository.docbook +++ b/Manuals/Repository/Docbook/repository.docbook @@ -10,7 +10,6 @@ - %Commons.ent; @@ -20,7 +19,6 @@ %Locales.ent; %Manuals.ent; %Scripts.ent; -%Directories.ent; %Licenses.ent; ]> @@ -31,6 +29,7 @@ User's Guide + Alain @@ -61,7 +60,17 @@ - Jun, 2011 + + + 5.5-1 + Fri Jun 24, 2011 + + + ... + + + + @@ -74,16 +83,14 @@ - &preface-docconvs; - &preface-feedback; + &intro; - &intro; + &repo; &identity; &locales; &manuals; &scripts; - &dirs; &licenses;