bloritsch    2003/08/15 09:28:49

  Modified:    src/documentation/content/xdocs index.xml
               src/documentation/content/xdocs/project index.xml
  Log:
  add page describing new development with repository access
  
  Revision  Changes    Path
  1.7       +9 -1      avalon-site/src/documentation/content/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/avalon-site/src/documentation/content/xdocs/index.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- index.xml 4 Mar 2003 12:43:47 -0000       1.6
  +++ index.xml 15 Aug 2003 16:28:49 -0000      1.7
  @@ -4,7 +4,15 @@
           <header> 
             <title>Apache Avalon project</title> 
           </header> 
  -        <body> 
  +     <body> 
  +             <section>
  +                     <title>News and Information</title>
  +                     <!-- Please keep this to a limit of three items,
  +                     we don't want to clutter the front page. -->
  +                     <ul>
  +                     <li>8/15/2003<link href="project">Avalon repositories opening 
up to other Apache projects.</link></li>
  +                     </ul>
  +             </section>
       <section>
   <title>What is it?</title>
         <p>
  
  
  
  1.2       +35 -1     avalon-site/src/documentation/content/xdocs/project/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/avalon-site/src/documentation/content/xdocs/project/index.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.xml 25 Jan 2003 18:19:51 -0000      1.1
  +++ index.xml 15 Aug 2003 16:28:49 -0000      1.2
  @@ -4,7 +4,41 @@
           <header> 
             <title>Apache Avalon project: Project Guidelines</title> 
           </header> 
  -        <body> 
  +     <body>
  +          <section>
  +         <title>Opening up Avalon's Repositories</title>
  +         <p>
  +           Avalon has continually been looking at ways they can cooperate
  +           better with other projects, especially here at Apache.  Recently,
  +           the Avalon team decided to open up the "avalon-excalibur"
  +           repository to the Apache Cocoon community.  The response has been
  +           favorable as the libraries there now have a wider group of
  +           developers to support the libraries.  As a result, the Avalon
  +           team decided to take this process one step further and open up
  +           the "avalon-components" repository to both the Apache Cocoon
  +           and Apache JAMES projects.
  +           </p>
  +        <p>
  +           If you are from another Apache project, and would like to have
  +           all the committers from your project have access to the Avalon
  +           Repositories, all you have to do is ask the Avalon PMC
  +           (<link href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</link>).
  +           The repositories that are available for wider access are:
  +           </p>
  +        <ul>
  +                <li>avalon-components</li>
  +                <li>avalon-excalibur</li>
  +                <li>avalon-sandbox</li>
  +        </ul>
  +        <p>
  +             The PMC will let you know if your request is accepted or not.  If
  +          you are interested in commit privileges, but are not part of one
  +          of the Apache projects, then you have to do it the old fashioned
  +          way and participate on the mailing lists and post patches, etc.
  +          We are taking advantage of the Apache infrastructure to make this
  +          happen.
  +        </p>
  +       </section>      
             <section>
               <title>Shaping up....</title>
               <p>We're still working on our project guidelines. We're sort-of waiting 
for
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to