httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org (Ralf S. Engelschall)
Subject cvs commit: apache-devsite mailing-lists.html index.html
Date Thu, 26 Feb 1998 07:53:22 GMT
rse         98/02/25 23:53:21

  Modified:    .        index.html
  Added:       .        mailing-lists.html
  Log:
  Because the frontdoor of our dev.apache.org website was really messed due to
  recent additions and changes I tried to clear it up by first putting the
  mailing-list info into an own document and then sorting the remaining items
  into a few topics. Hopefully now it is a little easier to find something...
  
  Revision  Changes    Path
  1.17      +77 -136   apache-devsite/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/index.html,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- index.html	1998/02/12 14:39:22	1.16
  +++ index.html	1998/02/26 07:53:20	1.17
  @@ -12,189 +12,130 @@
     ALINK="#FF0000"
    >
   <!--#include virtual="header.html" -->
  -  <H1 ALIGN="CENTER"><SAMP>Dev.Apache.Org</SAMP> - Developer Resources</H1>
  +  <H1 ALIGN="CENTER"><SAMP>Dev.Apache.Org</SAMP><BR>Developer Resources</H1>
     <P>
  +  <BLOCKQUOTE>
     This site includes many of the reference materials used by the Apache
     Project.
  -  </P>
  -  <BLOCKQUOTE>
      Note that a lot of these documents may not be entirely up-to-date.
      Some may have been superseded by other references, and some may just
      be waiting for someone to get around to updating them.
  -  </BLOCKQUOTE>
  +
  +  <P>
  +  <H2>User Feedback</H2>
     <UL TYPE="SQUARE">
  -   <LI><A HREF="guidelines">Apache Project Guidelines</A>, currently
in
  -       draft form.  <A HREF="voting" >Old Guidelines</A>.
  -   </LI>
  -   <LI><A HREF="devnotes">Apache Development Notes</A> about
  -       using CVS and maintaining the Apache site.
  +   <LI><A HREF="http://bugs.apache.org/">User access</A> (submit and
query)
  +	to the Apache Bug Report Database.
      </LI>
  -   <LI><A HREF="http://bugs.apache.org/">Read-only</A>, or
  -    <A HREF="http://bugs.apache.org/private/">read-write</A> access to the
  -    bug database.  (Read-write access requires authorisation.)
  +   <LI><A HREF="http://bugs.apache.org/private/">Developer access</A>
  +	(submit, query and edit) to the
  +    Apache Bug Report Database.
  +	Requires authorisation.
  +   </LI>
  +   <LI>
  +   <A
  +     HREF="mailing-lists"
  +    >Information</A>
  +	about the available Apache Mailing Lists.
      </LI>
  -   <LI>Archives of the
  +   <LI>
       <A
        HREF="mail/"
  -    >mailing lists</A>
  +    >Archives</A> 
  +	of the Apache Mailing Lists.
      </LI>
  +  </UL>
  +
  +  <P>
  +  <H2>General Developer Guidelines</H2>
  +  <UL TYPE="SQUARE">
      <LI>The latest draft of the
       <A
        HREF="project-plan"
  -    >Apache project plan</A>
  +    >Apache project plan</A><BR>
       (last modified on <!--#flastmod virtual="project-plan.html" -->)
      </LI>
  +   <LI><A HREF="guidelines">Apache Project Guidelines</A>, currently
in
  +       draft form.  [<A HREF="voting">Old Guidelines</A>].  <BR>
  +    (last modified on <!--#flastmod virtual="guidelines.html" -->)
  +   </LI>
      <LI>The Apache coding
       <A
        HREF="styleguide"
  -    >style guide</A>
  +    >style guide</A><BR>
       (last modified on <!--#flastmod virtual="styleguide.html" -->)
      </LI>
      <LI>Some notes on
       <A
        HREF="API"
  -    >the API</A>
  +    >the API</A><BR>
       (last modified on <!--#flastmod virtual="API.html" -->)
      </LI>
  -   <LI>Instructions for
  -    <A
  -     HREF="how-to-release"
  -    >rolling the release tarballs</A>
  -    (last modified on <!--#flastmod virtual="how-to-release.html" -->)
  +  </UL>
  +
  +  <P>
  +  <H2>Source Repository Guidelines</H2>
  +  <UL TYPE="SQUARE">
  +   <LI><A HREF="devnotes">Apache Development Notes</A> about
  +       using CVS and maintaining the Apache site.<BR>
  +    (last modified on <!--#flastmod virtual="devnotes.html" -->)
      </LI>
  -   <LI>How to
  -    <A
  -     HREF="binaries"
  -    >build binary distributions</A>
  -    (last modified on <!--#flastmod virtual="binaries.html" -->)
  +   <LI><A HREF="anoncvs.txt">Instructions</A>
  +	on developer access to the repository via Anonymous CVS.<BR>
  +    (last modified on <!--#flastmod virtual="anoncvs.txt" -->)
      </LI>
  -   <LI>A <A HREF="binbuild.sh">shell script to build a binary release</A>.
  +   <LI><A HREF="http://www.engelschall.com/pw/apache/cvsguide/">Instructions</A>
  +	on developer access to the repository via CVSup.
  +   </LI>
  +   <LI>The
  +    <A
  +     HREF="todo"
  +    >to-do list</A> of the Apache developers.<BR>
  +    (last modified on <!--#flastmod virtual="todo.html" -->)
      </LI>
      <LI>Record of changes to the
       <A
        HREF="mmn"
  -    >module magic number</A>
  +    >module magic number</A><BR>
       (last modified on <!--#flastmod virtual="mmn.txt" -->)
      </LI>
  -   <LI>The
  +  </UL>
  +
  +  <P>
  +  <H2>Source Repository Access</H2>
  +  <UL TYPE="SQUARE">
  +   <LI>A Web-based view of the
       <A
  -     HREF="todo"
  -    >to-do list</A>
  -    (last modified on <!--#flastmod virtual="todo.html" -->)
  +     HREF="http://www.apache.org/websrc/cvsweb.cgi"
  +    >CVS history</A>
  +    of the development effort
      </LI>
      <LI>The <A HREF="from-cvs/">latest source tree</A> pulled from the
          CVS repository, packaged with <SAMP>tar</SAMP>, and compressed
          with <SAMP>gzip</SAMP>.  Not guaranteed
          to do anything, especially not compile or work.
      </LI>
  -   <LI><A HREF="anoncvs.txt">Instructions</A>
  -	on using anonymous CVS to access the development repository.
  -   </LI>
  -   <LI><A HREF="http://www.engelschall.com/pw/apache/cvsguide/">Instructions</A>
  -	on developer access to the repository via CVSup.
  +  </UL>
  +
  +  <P>
  +  <H2>Release Guidelines</H2>
  +  <UL TYPE="SQUARE">
  +   <LI>Instructions for
  +    <A
  +     HREF="how-to-release"
  +    >rolling the release tarballs</A><BR>
  +    (last modified on <!--#flastmod virtual="how-to-release.html" -->)
      </LI>
  -   <LI>A Web-based view of the
  +   <LI>How to
       <A
  -     HREF="http://www.apache.org/websrc/cvsweb.cgi"
  -    >CVS history</A>
  -    of the development effort
  +     HREF="binaries"
  +    >build binary distributions</A><BR>
  +    (last modified on <!--#flastmod virtual="binaries.html" -->)
      </LI>
  -  </UL>
  -  <HR>
  -  <H2 ALIGN="CENTER">
  -   Mailing Lists
  -  </H2>
  -  <P>
  -  The Apache Project makes very heavy use of mailing lists.  Aside from
  -  the main development mailing list, the following are also available.
  -  All of these are Majordomo lists, which means that if you want to
  -  subscribe, just send a mail message to
  -  &lt;<A
  -       HREF="mailto:Majordomo@Apache.Org?subject=Subscribe"
  -      ><SAMP>Majordomo@Apache.Org</SAMP></A>&gt;
  -  with the following in the message <STRONG>body</STRONG> (<EM>not</EM>
the
  -  <STRONG>subject</STRONG>!).  (The &quot;<SAMP>End</SAMP>&quot;
keeps
  -  Majordomo from trying to treat any signature text as commands.)
  -  </P>
  -  <P>
  -  <DL>
  -   <DD><SAMP>Subscribe <EM>list-name</EM>
  -    <BR>
  -    End</SAMP>
  -   </DD>
  -  </DL>
  -  </P>
  -  <UL>
  -   <LI><A
  -       	HREF="mailto:Majordomo@Apache.Org?subject=Subscribe%20BugDB&body=Subscribe%20Apache-BugDB%0DEnd"
  -       ><SAMP>apache-bugdb</SAMP></A>
  -    <P>
  -    This is the mailing list to which all activity in the problem report
  -    database is logged.  If you are a member of this list, you will
  -    receive a message each time a report is added or modified.
  -    </P>
  -    <P>
  -    There is a &quot;magic&quot; mail address associated with the bug
  -    database: <SAMP>apbugs@Apache.Org</SAMP>.  This address is
  -    intercepted by the bug DB software; if it recognises the syntax of
  -    the <SAMP>Subject:</SAMP> line, it will attach the message text to
  -    the appropriate PR and report the transaction to the
  -    <SAMP>apache-bugdb</SAMP> list (but <STRONG>not</STRONG> to
the
  -    originator of the PR - so you need to manually add that address as a
  -    <SAMP>CC</SAMP> on your message if you want the originator to
  -    receive a copy).
  -    </P>
  -    <P>
  -    The requisite syntax for GNATS to understand the subject line is:
  -    </P>
  -    <P>
  -    <DL>
  -     <DD><SAMP>Re: <EM>category</EM>/<EM>number</EM>:</SAMP>
  -     </DD>
  -    </DL>
  -    </P>
  -    <P>
  -    So a reply to <SAMP>apbugs@Apache.Org</SAMP> with a subject line of
  -    &quot;<SAMP>Re: general/120: this is the synopsis</SAMP>&quot;
would
  -    be attached to PR #120.  (It doesn't matter if the text following
  -    the colon actually matches the real synopsis or not.)
  -    </P>
  -    <BLOCKQUOTE>
  -     <P ALIGN="CENTER">
  -     <STRONG>Note</STRONG>
  -     </P>
  -     <P>
  -     There are some caveats about using this email method to update
  -     problem reports:
  -     </P>
  -     <P>
  -     <UL>
  -      <LI><STRONG><EM>Don't</EM></STRONG> quote excessive
parts of the
  -       message in your reply unless the message wasn't already logged to
  -       the PR.  (This can happen when discussions occur in private mail
  -       and you want to log the conclusions in the database.)
  -      </LI>
  -      <LI>If you send something to <SAMP>apbugs@Apache.Org</SAMP> that
  -       <EM>doesn't</EM> match the required <SAMP>Subject:</SAMP>
syntax,
  -       or if the category/number don't exactly match an entry in the
  -       database, the message will be entered as a new report.
  -       <EM>This</EM> can happen if the PR category is changed and you
  -       reply to a message that was sent before the change.
  -      </LI>
  -     </UL>
  -     </P>
  -    </BLOCKQUOTE>
  -   </LI>
  -   <LI><A
  -       	HREF="mailto:Majordomo@Apache.Org?subject=Subscribe%20CVS&body=Subscribe%20Apache-CVS%0DEnd"
  -       ><SAMP>apache-cvs</SAMP></A>
  -    <P>
  -    This list is used to notify developers of changes to the master CVS
  -    repository.  As changes are applied, CVS log messages are sent to
  -    everyone who is a member of the list.
  -    </P>
  +   <LI>A <A HREF="binbuild.sh">shell script to build a binary release</A>.
      </LI>
     </UL>
  +  </BLOCKQUOTE>
   <!--#include virtual="footer.html" -->
    </BODY>
   </HTML>
  
  
  
  1.1                  apache-devsite/mailing-lists.html
  
  Index: mailing-lists.html
  ===================================================================
  <HTML>
  <HEAD>
  <TITLE>Apache Mailing Lists</TITLE>
  </HEAD>
  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
   <BODY
    BGCOLOR="#FFFFFF"
    TEXT="#000000"
    LINK="#0000FF"
    VLINK="#000080"
    ALINK="#FF0000"
   >
  <!--#include virtual="header.html" -->
  <CENTER>
  <H1 ALIGN=CENTER>Apache Mailing Lists</H1>
  </CENTER>
  
    <P>
    The Apache Project makes very heavy use of mailing lists.  Aside from
    the main development mailing list, the following are also available.
    All of these are Majordomo lists, which means that if you want to
    subscribe, just send a mail message to
    &lt;<A
         HREF="mailto:Majordomo@Apache.Org?subject=Subscribe"
        ><SAMP>Majordomo@Apache.Org</SAMP></A>&gt;
    with the following in the message <STRONG>body</STRONG> (<EM>not</EM>
the
    <STRONG>subject</STRONG>!).  (The &quot;<SAMP>End</SAMP>&quot;
keeps
    Majordomo from trying to treat any signature text as commands.)
    </P>
    <P>
    <DL>
     <DD><SAMP>Subscribe <EM>list-name</EM>
      <BR>
      End</SAMP>
     </DD>
    </DL>
    </P>
    <UL>
     <LI><A
         	HREF="mailto:Majordomo@Apache.Org?subject=Subscribe%20BugDB&body=Subscribe%20Apache-BugDB%0DEnd"
         ><SAMP>apache-bugdb</SAMP></A>
      <P>
      This is the mailing list to which all activity in the problem report
      database is logged.  If you are a member of this list, you will
      receive a message each time a report is added or modified.
      </P>
      <P>
      There is a &quot;magic&quot; mail address associated with the bug
      database: <SAMP>apbugs@Apache.Org</SAMP>.  This address is
      intercepted by the bug DB software; if it recognises the syntax of
      the <SAMP>Subject:</SAMP> line, it will attach the message text to
      the appropriate PR and report the transaction to the
      <SAMP>apache-bugdb</SAMP> list (but <STRONG>not</STRONG> to
the
      originator of the PR - so you need to manually add that address as a
      <SAMP>CC</SAMP> on your message if you want the originator to
      receive a copy).
      </P>
      <P>
      The requisite syntax for GNATS to understand the subject line is:
      </P>
      <P>
      <DL>
       <DD><SAMP>Re: <EM>category</EM>/<EM>number</EM>:</SAMP>
       </DD>
      </DL>
      </P>
      <P>
      So a reply to <SAMP>apbugs@Apache.Org</SAMP> with a subject line of
      &quot;<SAMP>Re: general/120: this is the synopsis</SAMP>&quot; would
      be attached to PR #120.  (It doesn't matter if the text following
      the colon actually matches the real synopsis or not.)
      </P>
      <BLOCKQUOTE>
       <P ALIGN="CENTER">
       <STRONG>Note</STRONG>
       </P>
       <P>
       There are some caveats about using this email method to update
       problem reports:
       </P>
       <P>
       <UL>
        <LI><STRONG><EM>Don't</EM></STRONG> quote excessive
parts of the
         message in your reply unless the message wasn't already logged to
         the PR.  (This can happen when discussions occur in private mail
         and you want to log the conclusions in the database.)
        </LI>
        <LI>If you send something to <SAMP>apbugs@Apache.Org</SAMP> that
         <EM>doesn't</EM> match the required <SAMP>Subject:</SAMP>
syntax,
         or if the category/number don't exactly match an entry in the
         database, the message will be entered as a new report.
         <EM>This</EM> can happen if the PR category is changed and you
         reply to a message that was sent before the change.
        </LI>
       </UL>
       </P>
      </BLOCKQUOTE>
     </LI>
     <LI><A
         	HREF="mailto:Majordomo@Apache.Org?subject=Subscribe%20CVS&body=Subscribe%20Apache-CVS%0DEnd"
         ><SAMP>apache-cvs</SAMP></A>
      <P>
      This list is used to notify developers of changes to the master CVS
      repository.  As changes are applied, CVS log messages are sent to
      everyone who is a member of the list.
      </P>
     </LI>
    </UL>
  <!--#include virtual="footer.html" -->
   </BODY>
  </HTML>
  
  
  

Mime
View raw message