"Fossies" - the Fresh Open Source Software Archive

Member "ark-20050419/arksf1/webpages/who-how.htma" (26 May 2004, 4364 Bytes) of package /linux/privat/old/ark-arksf1-20050419.tar.gz:

    1 <!-- -*-Mode: html;-*- -->
    2 <!-- ............................................................
    3  . 
    4  . Copyright (c) 2001,2004, Will Partain
    5  . All rights reserved.
    6  . 
    7  . Redistribution and use in source and binary forms, with or
    8  . without modification, are permitted provided that the
    9  . following conditions are met:
   10  . 
   11  . * Redistributions of source code must retain the above
   12  .   copyright notice, this list of conditions and the
   13  .   following disclaimer. 
   14  . 
   15  . * Redistributions in binary form must reproduce the above
   16  .   copyright notice, this list of conditions and the
   17  .   following disclaimer in the documentation and/or other
   18  .   materials provided with the distribution.
   19  . 
   20  . * Neither the name of the Arusha Project nor the names of
   21  .   its contributors may be used to endorse or promote
   22  .   products derived from this software without specific prior
   23  .   written permission.
   24  . 
   25  . THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
   26  . CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
   27  . INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   28  . MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
   29  . DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
   30  . CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   31  . SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
   32  . NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
   33  . LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
   34  . HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
   35  . CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   36  . OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   37  . SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   38  . 
   39  ............................................................ -->
   40 <!-- $Revision: 1.4 $ -->
   41 <!-- tag: Who? How? -->
   42 <h1>Who? How?</h1>
   43 
   44 <!-- ================================================= -->
   45 <h2><a name="who">Who's behind the Arusha Project (ARK)?</a></h2>
   46 
   47 The Arusha Project provides a framework for collaborative
   48 Unix system administration; as such, we hope there will
   49 eventually be <em>a lot</em> of people behind it!
   50 <p>
   51 The initial core developers are a group of people linked to
   52 the Computing Science Department, Glasgow University,
   53 in Scotland.
   54 <p>
   55 Will Partain (one of the above) started the project, so he
   56 got to name it.  He once lived in <a
   57 href="why-arusha.html">Arusha</a>, and the rest is history
   58 :-)
   59 
   60 <!-- ================================================= -->
   61 <h2><a name="how">How does Arusha Project collaboration work?</a></h2>
   62 
   63 ARK collaboration works by sysadmin "<a
   64 href="glossary.html#team">teams</a>" making some of their
   65 "added value" available to others, typically as "<a
   66 href="glossary.html#package">packages</a>".  A team then
   67 assembles their own solutions from all of the available
   68 material, including their own and including tweaks they've
   69 made to others' stuff.
   70 <p>
   71 The core developers "control" the base team, `ARK', which
   72 provides the core code that all Arusha teams will build on.
   73 <p>
   74 `<a href="index-ARK.html">ARK</a>' is a mechanism-not-policy
   75 team.  We (the core developers) also have a separate
   76 how-we-think-you-should-do-it (policy) team, called `<a
   77 href="index-sidai.html">Sidai</a>'.  For example, we think
   78 most people should use a "hubs-and-clients" sendmail
   79 configuration package.
   80 <p>
   81 If our Sidai team had made such a sendmail configuration
   82 package, you could use it, or not.  Maybe you prefer qmail.
   83 Maybe you think we've fluffed the sendmail configuration.
   84 Maybe you want to make one of your own.  You can offer yours
   85 "in competition" to our configuration.
   86 <p>
   87 A lot of people communication will be required for this
   88 process.  Certain teams will have a particular "angle" on
   89 doing things, and perhaps develop a following (or the
   90 opposite :-).  The ARK mailing lists can be used for these
   91 discussions.
   92 <p>
   93 We hope there will be a process of "commoning up" of
   94 packages and even of whole teams.  "Our Amanda
   95 configurations are nearly the same; why don't we get
   96 together and make a single glorious (parameterised)
   97 config..."
   98 <p>
   99 All in all, separate Arusha sites could be <em>very</em>
  100 different, with wildly varying approaches to doing things.
  101 The Arusha Project provides a "language" in which all of
  102 these choices may be systematically expressed and compared.
  103 We think that's a big step forward.
  104 
  105 <!-- the end -->