cvs commit: www organization.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Sun Mar 21 04:38:42 PST 2004


jeroen      04/03/21 05:38:42

  Modified:    .        organization.html
  Log:
  Add logistics to the organizational doc. Add internal links to make it more navigatable. Add the introductory text.
  
  Revision  Changes    Path
  1.7       +41 -13    www/organization.html
  
  Index: organization.html
  ===================================================================
  RCS file: /home/cvsroot/www/organization.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- organization.html	19 Mar 2004 17:23:15 -0000	1.6
  +++ organization.html	21 Mar 2004 12:38:42 -0000	1.7
  @@ -2,7 +2,7 @@
   <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   
   <head>
  -	<title>Template - Linux From Scratch</title>
  +	<title>Organization - Linux From Scratch</title>
   	<meta name="description" content="Linux From Scratch - build your own Linux distribution from scratch" />
   	<meta name="keywords" content="Linux, LinuxFromScratch, Linux From Scratch, build your own Linux, DIY Linux, do-it-yourself Linux, create your own Linux" />
   	<meta name="MSSmartTagsPreventParsing" content="true" />
  @@ -48,24 +48,36 @@
   <div id="content">
   	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
   
  +	<h2>Introduction</h2>
  +<p>The Linux From Scratch (LFS) project has grown, over time, to a state that requires more formalized structure, activity, and management tools. A set of documents is being designed and implemented to satisfy those needs. They will:</p>
  +<ul>
  +	<li>Provide the drivers for the organization, the <a href="#manifesto">Manifesto</a>;</li>
  +	<li>Define <a href="people.html">LFS Teams</a> and provide their <a href="manifesto.html">Mission Statements</a>, which implement the <a href="#manifesto">Manifesto's</a> objectives;</li>
  +	<li>Establish the Policies to which LFS and its team members will adhere;</li>
  +	<li>Determine <a href="lfs/roadmap.html">Future Directions</a> of LFS;</li>
  +	<li>Provide the guidelines against which LFS organization performance is measured.</li>
  +</ul>
  +
  +<p>Each team will generate a mission statement, which will be in conformance with the objectives and policies that derive from the Manifesto. This mission statement will incorporate many of the facets from the manifesto, and is a subset of those facets, augmented as needed for the team to effectively perform its mission and accurately convey its commitments to the community.</p>
  +	
   <h2>The LFS Organization</h2>
  -<h2>Manifesto</h2>
  +<h2 id="manifesto">Manifesto</h2>
   
   	<p>The LFS manifesto contains documents that drive  the definition of the organization's structure and activities. Its purpose is to describe LFS in terms of goals, strategies, major policies and functions, and similar attributes.</p>
   	<p>By nature, the contents of the documents at this level must be somewhat non-specific. They must provide enough detail that constructive examination and criticism can occur, but not so much that detail-level implementation details are either locked in here or they would prevent the generation of the necessary effective design detail in the lower-level documents.</p>
   	<p>The actual definition of LFS occurs in "lower level" documents that describe, in some detail, how the attributes described in the manifesto will be satisfied - the implementation of the desired attributes. These can be seen at Organization Documents.</p>
   	<p>The manifesto itself consists of several documents, formally structured as might be found in any formal organization. We currently have these:</p>
   	<ul>
  -	 	<li>Preface - a brief description of purpose and a little background,</li>
  -	 	<li>Scope - a brief description of goals for each of the LFS projects,</li>
  -	 	<li>Bounds - some general limitations to LFS goals,</li>
  -	 	<li>Objectives - general results that are desired and also serve as subjective assessment tools for judging the success of the LFS project, making decisions about tactics to be used, and determining future strategies and tactics,</li>
  -	 	<li>Strategy - general methods used to accomplish the overall goals,</li>
  -	 	<li>Logistics - specific deliverables that will satisfy the goals and objectives and provide some guidance as to tactics employed.</li>
  +	 	<li><a href="#preface">Preface</a> - a brief description of purpose and a little background,</li>
  +	 	<li><a href="#scope">Scope</a> - a brief description of goals for each of the LFS projects,</li>
  +	 	<li><a href="#bounds">Bounds</a> - some general limitations to LFS goals,</li>
  +	 	<li><a href="#objectives">Objectives</a> - general results that are desired and also serve as subjective assessment tools for judging the success of the LFS project, making decisions about tactics to be used, and determining future strategies and tactics,</li>
  +	 	<li><a href="#strategy">Strategy</a> - general methods used to accomplish the overall goals,</li>
  +	 	<li><a href="#logistics">Logistics</a> - specific deliverables that will satisfy the goals and objectives and provide some guidance as to tactics employed.</li>
   	</ul>
   	<p>An additional document is needed at this level, "Policies". However, it is derived from the tenets established in the preceding six and cannot be seriously undertaken until those are finalized. It should be noted that it is not a repeat of the ideas in those documents, but is both a "clarification" and "augmentation" of them. Its ultimate purpose is to provide defining instructions for areas that may be necessarily subjective or somewhat vague. For example, "a friendly environment" may mean different things to different people. A policy might be established that says "Things like calling people dummy or telling them precisely 'do not waste our time until you grow up'" is not in keeping with the LFS spirit. Or it could be something as mundane as "We will try to use the latest available stable packages when reasonable". These will often be generalities and good sound judgment must be used in their application. </p>
   
  -<h2>Preface</h2>
  +<h2 id="preface">Preface</h2>
   
   <h3>Purpose of the LFS Organization Documents</h3>
   	<p>Present the goals, strategies, scope, bounds and logistics that govern the implementation of the "Linux From Scratch" projects.</p>
  @@ -79,20 +91,20 @@
   	<p>These documents, including sections "Scope", "Bounds", "Objectives", "Strategy", and "Logistics", provide common and public project direction, principals guiding decision-making, foundation tenets for team activities, and are used to determine appropriateness of decisions and activities.</p>
   	<p>Other needed documents, based on the tenets established in those documents mentioned above, will be generated and made publicly available to provide guidance to the organization, its activities, and goals. These additional documents will include such things as "LFS Organization", "LFS Roadmap" and documents appropriate to each team in the organization as are needed to effect a "Mission Statement" for that team. Further information deemed necessary to accomplish the goals of the LFS project will be provided as it is identified.</p>
   
  -<h2>Scope</h2>
  +<h2 id="scope">Scope</h2>
   	<p>"Linux From Scratch" (LFS) will educate Unix/Linux users about considerations, decisions, components and commands used to build a working GNU/Linux system, using program sources and a GNU/Linux host platform. The target audience is "intermediate-to-advanced" users of UNIX/Linux. Tools include publications and support via the internet.</p>
   	<p>The "Beyond Linux From Scratch" (BLFS) project will continue on to application-specific components as might be used for work stations, content servers and gateways.</p>
   	<p>"Automated Linux From Scratch" (ALFS) will offer an automatic build that is configurable and repeatable. A variation of this will support internal and "Linux Standard Base" project test and verification needs. Although not a full regression-capable automated test system, it (or a derivative of it) will undergo modification to achieve full-regression test capability.</p>
   	<p>"Hardened Linux From Scratch" (HLFS) will educate Unix/Linux users about considerations, decisions, components and commands used to build a working GNU/Linux system (with strong emphasis on teaching and resolving security concerns), using program sources and a GNU/Linux host platform.  The target audience is "intermediate-to-advanced" users of UNIX/Linux.  The HLFS project will continue on to application-specific components as might be used for work stations, content servers and gateways with focus on the latter two. Tools include publications and support via the Internet.</p>
   
   
  -<h2>Bounds</h2>
  +<h2 id="bounds">Bounds</h2>
   	<p>"Linux From Scratch" will not supplant commonly available sources of help (tutorials, "HOWTOS", ...) for users unfamiliar with basic GNU/Linux user utilities. These include typical shell operations (directory, environmental variables, scripts, I/O redirection, ...), file manipulation (copy, move, rename, locate, ...), text manipulation (edit, find in file, concatenate, ...), file system operations (partitioning, mounts, ...), list and print (cat, tee, more, ...), and operations requirements (dump, boot, restore, ...).</p>
   	<p>"Beyond Linux From Scratch" will not educate users on the underlying administration principals that must be considered when configuring for the different applications included in its scope.</p>
   	<p>"Automated Linux From Scratch" will not be an entirely "hands off" build system. The user still needs a thorough understanding of the LFS book used to generate their ALFS profile to successfully build and use an LFS system using ALFS tools.</p>
   	<p>"Hardened Linux From Scratch" will not supplant the (B)LFS books' instructions.  It will not teach the basics of installing an operating system included in the LFS book, nor will it teach the basics of add-on packages that are in the BLFS book. It will contain only the instructions and educational text that differs from the (B)LFS books.</p>
   
  -<h2>Objectives</h2>
  +<h2 id="objectives">Objectives</h2>
   	<p>Users that are:</p>
   	<ul>
   		<li>knowledgeable in construction of a basic GNU/Linux system,</li>
  @@ -108,7 +120,7 @@
   	<p>High-quality on-going support and services, such as a friendly and informative web site, problem-resolution assistance and certain discussion forums that promote the on-going development and enhancement of the LFS experience and products.</p>
   	<p>All of the above produced by a force of "volunteers" that are knowledgeable, enthusiastic, friendly, and remain with the project for a long time.</p>
   
  -<h2>Strategy</h2>
  +<h2 id="strategy">Strategy</h2>
   	<p>Briefly, the goal is a user that is more informed about:</p>
   	<ul>
   		<li>GNU/Linux system construction techniques,</li>
  @@ -124,6 +136,22 @@
   	</ul>
   	<p>In the last three items, care must be taken to not overstep the Bounds set for the project. Briefly, existing available documents that offer comprehensive education in a particular area are not to be supplanted. This will be very subjective, due to the nature of the project's Scope and Objectives.</p>
   	<p>A "volunteer" force, organized into teams, will be the implementers of this strategy.</p>
  +
  +<h2 id="logistics">Logistics</h2>
  +
  +	<p>An ideal implementation of the strategy is a dynamic thing, evolving as the environment changes. Maximum use of available tools will be needed to stay current in this rapidly changing environment.</p>
  +
  +	<p>The core delivery system for educating the user is an on-line and downloadable "book" and, recently instituted, a traditional printed version. Auxiliary delivery, to allow aggressive users to stay 100% current, is provided via CVS access that delivers the latest updates.</p>
  +
  +	<p>A vital adjunct to these core products are various support services. Implemented using mailing lists, forums, "chat", dynamically built web pages and a "wiki", these services will help users resolve problems they experience while progressing through the process of constructing the system the book defines. A side-effect is increased knowledge in areas that are precluded by the "Scope" and "Bounds" of the project proper, but it is encouraged if it does not detract from the primary goal.</p>
  +
  +	<p>To support the wide array of activities encompassed by pursuing this strategy, a substantial number of personnel resources with a wide range of skill-sets are needed. To obtain and keep these resources, an organizational structure, appropriate to the volunteer nature of the project, is instituted - a rather "flat" structure of "teams" and "team leaders". The "authoritarian" tone of "traditional" management structures is to be de-emphasized while the cooperative, responsive and imaginative nature of an ideal team is to be enhanced.</p>
  +
  +	<p>In conjunction with the "teams", we will attempt to provide an environment that makes it attractive for people to join, and remain with, the LFS project and teams. This goal is to be achieved by providing acknowledgement, a friendly and helpful environment, latitude to contribute in areas of special interest, and exposure to the "latest" advances in the realm of GNU/Linux systems construction.</p>
  +
  +	<p>Additionally, all appropriate resources available to enable and encourage the participation of the community-at-large in all areas will be provided. These include "unconventional" use of the support services mentioned above. For example, direct acknowledgement by community members of extraordinary contributions by other community members will be supported via the "wiki". This will also provide additional input for determination of acknowledgement in the book.</p>
  +
  +	<p>The details of organization, team "mission statements", team constituents and operational procedures, and all other appropriate documentation needed by the project, will be detailed in other documents to be produced by the LFS teams in conjunction with the overall project leaders.</p>
   
   
   </div> <!-- end content -->
  
  
  



More information about the website mailing list