incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: incubator/src/documentation/content/xdocs faq.xml howtopartecipate.cwiki index.xml resolution.xml site.xml tabs.xml whoweare.cwiki
Date Tue, 07 Oct 2003 15:53:20 GMT
nicolaken    2003/10/07 08:53:20

  Added:       src/documentation/content/xdocs faq.xml
                        howtopartecipate.cwiki index.xml resolution.xml
                        site.xml tabs.xml whoweare.cwiki
  First pass at making the new website.
  It generates correctly with Forrest, please give it a try;
  suggestions are welcome :-)
  Revision  Changes    Path
  1.1                  incubator/src/documentation/content/xdocs/faq.xml
  Index: faq.xml
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.2//EN" "dtd/faq-v12.dtd">
  <faqs title="Frequently Asked Questions">
    <part id="general">
      <faq id="do_I_really_need_Incubation">
          Does the X Project really have to go in the Incubator to get to Apache?
      <faq id="can_Incubation_be_skipped">
          I'm the sponsor of this project, and I think that I'm able to do it by myself.
          The Incubator doesn't add anything, do I have to do it?
          <p> Yes.</p> 
          <p>Do it right, do it well, and add something in the process. </p> 
              Incubation is not about handing it over to some other group and 
              seeing what happens. The Incubator is simply the name of the place 
              that governs your actions when you process a new project into Apache.  
              It moves at the same rate you do, and achieves whatever you achieve 
              -- the only difference is that we have a permanent record in <strong>one</strong>
              place that we can go back to if there are later IP problems, and there 
              is a gate that must be passed through before the project is given 
              the right to release software on behalf of the ASF.  
              That gate will not be ignored or bypassed just because one group or 
              another feels they have earned the right to bypass it; allowing that 
              kind of exception destroys the potential to build a tradition of effective 
              oversight, which is the reason we created incubator.
    <part id="howtopartecipate">
      <title>How to partecipate</title>
      <faq id="site">
        <question>How can I update the site?</question>
        <p>Refer to <link href="">How
to Partecipate</link>
      <faq id="projectstatus">
        <question>How do I update the STATUS of a project?</question>
         <p>Look in the incubator CVS module for the STATUS files.</p>
  1.1                  incubator/src/documentation/content/xdocs/howtopartecipate.cwiki
  Index: howtopartecipate.cwiki
  !!!How to Partecipate
  __TODO__: Need to add all Incubator project resources here
  !!Mailing lists
  As with everything else in Apache, most of what goes on happens or is discussed on electronic
mailing lists. Here are the lists associated with this project, and their purposes:
  This is where general and public discussion of things about the project take place. It's
also where follow-up messages sent in reply to cvs commit reports get sent (see the next list).
There is a 'digest' form of this list, which collects individual messages and sends the collection
when enough have accumulated or a given amount of time has passed since the last digest. Anyone
may subscribe; only subscribers may post.
  *To subscribe, send a message to
  *To subscribe to the digest, send a message to

  *To unsubscribe, send a message to
  When changes are made to the code repository, the details are automatically sent to this
list. Its Reply-To is set to the 'general' list, so if you reply to a cvs message that's where
your reply is going to end up. Anyone may subscribe; only subscribers may post.
  *To subscribe, send a message to 
  *To unsubscribe, send a message to 
  This is the list to which you should be subscribed if you want to be kept apprised of significant
events or milestones in the project's activities, but don't want to track the full traffic
in the 'general' list. Anyone may subscribe; all posts are moderated.
  *To subscribe, send a message to 
  *To unsubscribe, send a message to 
  *This is a private list for the project management committee. It is not open to general
  !!Updating the site
  The process for submitting new documentation or modifying an existing page is as follows.
  !Download Forrest
  Download [Apache Forrest!], or obtain it from CVS:
  {{{   export
     cvs login
     (press enter)
     cvs checkout xml-forrest
     cd xml-forrest
     export PATH=`pwd`/build/dist/shbat/bin:$PATH}}}  
  !Download incubator-site
  Download the {{incubator-site}}  CVS module.
  Continuing from the previous example:
  {{{   cd ..
     cvs checkout incubator-site}}}  
  !Make your changes
  Edit the XML docs in <code>incubator-site/src/documentation/content/xdocs/</code>.
 If you are not familiar
  with DTDs, the syntax is best learned [by example|href="*checkout*/xml-forrest/src/documentation/content/xdocs/document-v11.xml?rev=HEAD&amp;content-type=text/xml].
  From the Forrest site, [here is quite a complete example of the xml format|],
and [here of the wiki format|].
  If you add a new page or change a page's name, update {{site.xml}}, from which the menu
is generated.  More details can be found [in Forrest's documentation|].
  !Render the site
  In the <code>incubator-site/</code> directory, type 'forrest' to render the
HTML and PDF files in <code>build/site</code>.  Forrest validates the XML, so
will catch any syntax errors.
  !Submit or commit the change
  If the site built without errors, you can now make a patch with the command <code>cvs
diff -u >  incubator-site.diff</code> in the <code>incubator-site/</code>
directory, and submit it to the mailing list, with '<code>[PATCH]</code>' in the
email subject.
  Incubator committers can just commit the contents of <code>build/site</code>
(after checking it is okay!).
  1.1                  incubator/src/documentation/content/xdocs/index.xml
  Index: index.xml
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
      <title>Apache Incubator Project</title>
        <person name="The Apache Incubator Project"
          email="" />
      <abstract>Apache Incubator introduction.</abstract>
        <title>What Is It?</title>
        <p>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.</p>
        <p>A large part of the Incubator's effort will be devoted
        to providing documentation on how the Foundation works,
        and how to get things done within its framework.  As a
        consequence, it is expected that the Incubator will also
        become a reference for new contributors to any of the
        Apache projects.</p>
        <p>Since the Incubator project is one of the primary gateways
        into Apache involvement, a lot of the documentation about the
        structural and philosophical details of the Foundation will
        probably be prototyped and developed right here.  When they
        seem to accurately reflect reality and cover the information
        they should, they'll probably be moved up to the Foundation's
        main Web site.</p>
        <title>The Apache Software Foundation</title>
        <p>The Apache Software Foundation (ASF) is a non-profit
        (USA IRS 501(c)(3) compliant) membership organisation.
        You can find out more about the ASF proper at the
        <link href="">main site</link>.</p>
        <p>The main unit of participation in the ASF is the
        individual.  Individuals may have one or more roles in
        the ASF; you can find out more about them
        <link href="">here</link>.</p>
  1.1                  incubator/src/documentation/content/xdocs/resolution.xml
  Index: resolution.xml
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
      <title>Incubator Formation Resolution</title>
        <person name="The Apache Incubator Project"
          email="" />
      <abstract>ASF board resolution that created the Apache Incubator
        <title>Resolution that Created the Incubator Project</title>
        <p>Here is the text of the ASF Board resolution that was adopted
        in October 2002
        (see the
        <link href=""
          >meeting minutes</link>)
        and thereby created the Incubator project:</p>
          WHEREAS, the Board of Directors deems it to be in the best
          interests of the Foundation and consistent with the
          Foundation's purpose to establish a Project Management
          Committee charged with accepting new products into the
          Foundation, providing guidance and support to help each new
          product engender their own collaborative community, educating
          new developers in the philosophy and guidelines for
          collaborative development as defined by the members of the
          Foundation, and proposing to the board the promotion of such
          products to independent PMC status once their community has
          reached maturity.
          NOW, THEREFORE, BE IT RESOLVED, that a Project Management
          Committee (PMC), to be known as the "Apache Incubator PMC", be
          and hereby is established pursuant to the Bylaws of the
          Foundation; and be it further
          RESOLVED, that the Apache Incubator PMC be and hereby is
          responsible for the acceptance and oversight of new products
          submitted or proposed to become part of the Foundation; and be
          it further
          RESOLVED, that the Apache Incubator PMC is responsible for
          providing guidance and ensuring that subprojects under its
          purview develop products according to the Foundation's
          philosophy and guidelines for collaborative development; and be
          it further
          RESOLVED, that the Apache Incubator PMC is responsible for
          regularly evaluating products under its purview and making the
          determination in each case of whether the product should be
          abandoned, continue to receive guidance and support, or
          proposed to the board for promotion to full project status as
          part of an existing or new Foundation PMC; and be it further
          RESOLVED, that the office of "Vice President, Apache Incubator"
          be and hereby is created, the person holding such office to
          serve at the direction of the Board of Directors as the chair
          of the Apache Incubator PMC, and to have primary responsibility
          for management of the subprojects within the scope and
          responsibility of the Apache Incubator PMC; and be it further
          RESOLVED, that the persons listed immediately below be and
          hereby are appointed to serve as the initial members of the
          Apache Incubator PMC:
            Aaron Bannert
            Nicola Ken Barozzi
            Ken Coar
            Roy T. Fielding
            B. W. Fitzpatrick
            Jim Jagielski
            Greg Stein
            Sander Striker
          NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Jagielski be
          and hereby is appointed to the office of Vice President, Apache
          Incubator, to serve in accordance with and subject to the
          direction of the Board of Directors and the Bylaws of the
          Foundation until death, resignation, retirement, removal or
          disqualification, or until a successor is appointed; and be it
          RESOLVED, that the initial Apache Incubator PMC be and hereby
          is tasked with the creation of a set of bylaws intended to
          encourage open development and increased participation in the
          Apache Incubator Project.
  1.1                  incubator/src/documentation/content/xdocs/site.xml
  Index: site.xml
  <?xml version="1.0"?>
  <site label="ApacheIncubator" xmlns="" tab="home">
    <about label="About">
      <index label="Index" href="index.html"/>
      <whatwedo label="Creation" href="resolution.html"/>
      <whoweare label="Who we are" href="whoweare.html"/>
      <howtopartecipate label="How to partecipate" href="howtopartecipate.html"/>
      <faq label="FAQ" href="faq.html"/>
    <incubation label="Incubation" href="incubation/">
      <index label="Index" href="index.html"/>
      <process label="Incubation Process" href="process.html"/>
      <missionbylaws label="Mission/Bylaws" href="bylaws.html"/>
      <finaldrafts label="Final Drafts">
        <policy label="Incubation Policy" href="Incubation_Policy.html"/>
        <process label="Process Description" href="Process_Description.html"/>
        <rolesandersponsibilities label="Roles and Responsibilities" href="Roles_and_Responsibilities.html"/>
  	<forms label="Forms" href="forms.html"/>
    <projects label="Projects" href="projects/" tab="projects">
      <index label="Index" href="index.html"/>
    <learn label="Learn" tab="learn" href="learn/">
      <index label="Index" href="index.html"/>
      <license label="License" href=""/>
      <glossary label="Glossary" href="glossary.html"/>
      <voting label="Voting" href="voting.html"/>
      <theapacheway label="'The Apache Way'" href="theapacheway.html"/>
      <newcommitters label="New Committers" href="newcommitters.html"/>
      <mailinglists label="Apache Mailing Lists" href="mailing-lists.html"/>       
     <references label="References">
      <faq label="the Apache FAQ"
      <rulesforrevolutionaries label="Rules for Revolutionaries"
      <newjakartasubproject label="Jakarta 'New Subproject' Page"
    <translations label="Translations (Web)">
      <japanese label="Japanese"
    <!-- Uncomment this if we want aggregate HTML/PDFs for this site 
    <pdfs label="PDFs">
      <whole_site_html label="Whole site HTML" href="site.html"/>
      <whole_site_pdf label="Whole site PDF" href="site.pdf"/>
      < href="">
        <forrest href="forrest/"/>
      <jakarta href="">
        <ant href="ant/"/>
        <gump href="gump/"/>
      <apache-stats href=""/>
  1.1                  incubator/src/documentation/content/xdocs/tabs.xml
  Index: tabs.xml
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN" "tab-cocoon-v10.dtd">
  <tabs software="Apache Incubator"
    title="Apache Incubator"
    copyright="Apache Software Foundation"
    <tab label="Home" id="home" dir="."/>
    <tab label="Projects" id="projects" dir="projects/"/>
    <tab label="Learn" id="learn" dir="learn/"/>
    <tab label="Drafts" href=""/>
  1.1                  incubator/src/documentation/content/xdocs/whoweare.cwiki
  Index: whoweare.cwiki
  !!!Incubator Project members
  Here are the volunteers that keep the project running.
  !!PMC (Project Management Commitee)
  * Aaron Bannert
  * Nicola Ken Barozzi  (Chair select)
  * Noel Bergman
  * Ken Coar
  * Roy Fielding
  * B. W. Fitzpatrick
  * Paul Hammant
  * Ted Leung
  * Jim Jagielski (Chair)
  * Sam Ruby
  * Leo Simmons
  * Davanum Srinivas
  * Greg Stein
  * Sander Striker 
  !! Committers
  * Berin Lautenbach
  none yet

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message