incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From leosim...@apache.org
Subject cvs commit: incubator README.txt
Date Mon, 27 Oct 2003 13:18:25 GMT
leosimons    2003/10/27 05:18:24

  Modified:    .        README.txt
  Log:
  formatting, friendly header, reshuffle, bla bla
  
  Revision  Changes    Path
  1.3       +47 -27    incubator/README.txt
  
  Index: README.txt
  ===================================================================
  RCS file: /home/cvs/incubator/README.txt,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- README.txt	23 Oct 2003 09:48:48 -0000	1.2
  +++ README.txt	27 Oct 2003 13:18:24 -0000	1.3
  @@ -1,28 +1,34 @@
  +                       The Apache Incubator Project
  +                       ============================
  +
  +The Incubator project was created in October of 2002 to provide an entry path
  +to the Apache Software Foundation for projects and codebases wishing to become
  +part of the Foundation's efforts. Code donations from external organisations
  +and existing external projects wishing to move to Apache will enter through
  +the Incubator.
   
  -Site Change Policy 
  -===================
   
  -Apache projects usually make releases, and have deliverables. The code 
  -they put in is managed through lazy consensus and voting only when it's 
  -deemed to be required or requested.
  -
  -Incubator releases are basically Incubated Projects' release to the 
  -Sponsor PMC. So how incubation is done is our "code".
  - 
  -Hence there is no need to "ratify" such rules if there seems to be 
  -consensus, as it's much easier to manage.
  - 
  -Because of this, we do not have the "draft" status on our policy docs 
  -and simply use them as our guide, that will change in need without 
  -having to go through tedious votes when there is good consensus.
  +See: Website
  +============
  +Information about the incubator project and the projects it contains is kept
  +at http://incubator.apache.org/. Please look there for more information.
   
  +This module contains the o-so-vital STATUS file. It also contains the
  +sourcefiles from which the website is generated. See below for information on
  +editing the website.
   
  -Website howto
  +
  +Website Howto
   =============
   
  -To generate the website one needs to get CVS forrest and install it.
  +To generate the website one needs to get CVS forrest
  +(http://xml.apache.org/forrest/) and install it.
   
  -Editors can edit the pages without generating the site, and just validate the xml with
a validating editor before committing. For the wiki pages it's plain text, so it's easier.
Ones with Forrest installed (currently nicolaken) and after the Forrestbot will take care
of doing builds, fixing eventual errors and updating the site.
  +Editors can edit the pages without generating the site, and just validate the
  +xml with a validating editor before committing. For the wiki pages it's plain
  +text, so it's easier. Ones with Forrest installed (currently nicolaken) and
  +after the Forrestbot will take care of doing builds, fixing eventual errors
  +and updating the site.
   
   In any case, if someone wants to check the look of the pages, do this:
   
  @@ -37,23 +43,37 @@
    point the browser to http://localhost:8888/ to see the site
    edit the docs *in place* and see changes in teh browser by reloading  the page
   
  -
  -
  -Subproject Website howto
  -=======================
  +Subproject Website Howto
  +========================
   
   Do not use the "incubator" CVS module for project docs, but the module of
   the specific project.
   
  -Check-in the generated pages in the "incubator-site" CVS module under 
  -\incubator-site\build\site\projects\ftpserver\**.
  +Check-in the generated pages in the "incubator-site" CVS module under
  +\incubator-site\build\site\projects\${project-name}\**.
   
   When the site is updated from CVS (it's once a day) it will be live.
   
  -If you have other questions, feel free to post them on  
  +If you have other questions, feel free to post them on
       general@incubator.apache.org
  -    
  -In case of Project development questions, there is 
  +
  +In case of Project development questions, there is
      projects@incubator.apache.org
   
   
  +Site Change Policy
  +===================
  +
  +Apache projects usually make releases, and have deliverables. The code they
  +put in is managed through lazy consensus and voting only when it's deemed to
  +be required or requested.
  +
  +Incubator releases are basically Incubated Projects' release to the Sponsor
  +PMC. So how incubation is done is our "code".
  +
  +Hence there is no need to "ratify" such rules if there seems to be consensus,
  +as it's much easier to manage.
  +
  +Because of this, we do not have the "draft" status on our policy docs and
  +simply use them as our guide, that will change in need without having to go
  +through tedious votes when there is good consensus.
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message