incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ran...@apache.org
Subject cvs commit: incubator-ftpserver/src/doc/content/xdocs ftplet.xml installation.xml ip_restrictor.xml mailing_list.xml who_we_are.xml
Date Wed, 14 Sep 2005 06:17:14 GMT
rana_b      2005/09/13 23:17:14

  Modified:    src/doc/content/xdocs ftplet.xml installation.xml
                        ip_restrictor.xml mailing_list.xml who_we_are.xml
  Log:
  documentation changed
  
  Revision  Changes    Path
  1.2       +95 -95    incubator-ftpserver/src/doc/content/xdocs/ftplet.xml
  
  Index: ftplet.xml
  ===================================================================
  RCS file: /home/cvs/incubator-ftpserver/src/doc/content/xdocs/ftplet.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ftplet.xml	7 Sep 2005 05:07:43 -0000	1.1
  +++ ftplet.xml	14 Sep 2005 06:17:14 -0000	1.2
  @@ -16,41 +16,41 @@
     limitations under the License.
   -->
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
  -<document> 
  -    <header> 
  -        <title>Ftplet</title> 
  +<document>
  +    <header>
  +        <title>Ftplet</title>
           <authors>
               <person id="RB" name="Rana Bhattacharyya" email="rana_b@yahoo.com"/>
           </authors>
  -    </header> 
  -  <body> 
  +    </header>
  +  <body>
         <section>
             <title>Overview</title>
             <p>The Ftplet API is a simple API used to handle different FTP Server
  -             notifications. Apache FTP Server is a Ftplet container, allowing 
  -             administrators to deploy Ftplet to carry out a variety of complex 
  -             FTP event handler tasks. 
  +             notifications. Apache FTP Server is a Ftplet container, allowing
  +             administrators to deploy Ftplet to carry out a variety of complex
  +             FTP event handler tasks.
             </p>
  -          <p>Implementing a custom Ftplet is generally a simple task, most of 
  -             whose complexity lies in coding the actual work to be done by the 
  -             Ftplet. This is largely due to the simplicity of the Ftplet interface 
  -             and the fact that a DefaultFtplet class is provided as part of the 
  +          <p>Implementing a custom Ftplet is generally a simple task, most of
  +             whose complexity lies in coding the actual work to be done by the
  +             Ftplet. This is largely due to the simplicity of the Ftplet interface
  +             and the fact that a DefaultFtplet class is provided as part of the
                Ftplet package.
             </p>
  -          <p>The Ftplet interface supports two lifecycle methods to provide 
  +          <p>The Ftplet interface supports two lifecycle methods to provide
                initialization (the init() method) and shutdown (the destroy() method).
                Main processing is done in different notification methods, which take
                a FtpRequest object and a FtpResponse object. All the notification
                methods return FtpletEnum object to indicate the future action.
             </p>
             <p>There will be one instance of Ftplet object. Notification methods will
  -             be called from different connections running in different threads. So 
  -             Ftplet implementation has to be thread-safe. Each connection will have 
  -             its own request (FtpRequest) and response (FtpResponse) objects. So 
  +             be called from different connections running in different threads. So
  +             Ftplet implementation has to be thread-safe. Each connection will have
  +             its own request (FtpRequest) and response (FtpResponse) objects. So
                FtpRequest and FtpRestonse objects are connection specific.
             </p>
         </section>
  -      
  +
         <section>
             <title>Main Classes</title>
             <section>
  @@ -59,49 +59,49 @@
                    There are four static FtpletEnum values.
                 </p>
                 <ul>
  -                  <li><strong>RET_DEFAULT</strong> : This return value
indicates 
  -                      that the next ftplet method will be called. If no other ftplet 
  +                  <li><strong>RET_DEFAULT</strong> : This return value
indicates
  +                      that the next ftplet method will be called. If no other ftplet
                         is available, the FTP server will process the request.
                     </li>
  -                  <li><strong>RET_NO_FTPLET</strong> : This return value
indicates 
  -                      that the other ftplet methods will not be called but the 
  +                  <li><strong>RET_NO_FTPLET</strong> : This return value
indicates
  +                      that the other ftplet methods will not be called but the
                         FTP server will continue processing this request.
                     </li>
  -                  <li><strong>RET_SKIP</strong> : It indicates that the
FTP server 
  -                      will skip everything. No further processing (both ftplet and server)

  +                  <li><strong>RET_SKIP</strong> : It indicates that the
FTP server
  +                      will skip everything. No further processing (both ftplet and server)
                         will be done for this request.
                     </li>
  -                  <li><strong>RET_DISCONNECT</strong> : It indicates
that the server 
  -                      will skip and disconnect the client. No other request from the 
  +                  <li><strong>RET_DISCONNECT</strong> : It indicates
that the server
  +                      will skip and disconnect the client. No other request from the
                         same client will be served.
                     </li>
                 </ul>
  -              <p>So, RET_DEFAULT &lt; RET_NO_FTPLET &lt; RET_SKIP &gt;
RET_DISCONNECT</p>
  +              <p>So, RET_DEFAULT &lt; RET_NO_FTPLET &lt; RET_SKIP &lt;
RET_DISCONNECT</p>
                 <p>If the Ftplet returns null, RET_DEFAULT is assumed.</p>
             </section>
   
             <section>
                 <title>FtpRequest</title>
  -              <p>It provides the client request information to a ftplet. Ftplet 
  -                 notification methods will always get the same instance of FtpRequest 
  -                 for one connection. So the attributes set by <em>setAttribute()</em>

  -                 will be always available later unless that attribute is removed. 
  -                 Different connections will have different FtpRequest objects. From 
  -                 here we can get user information, data streams, FTP command, argument,

  +              <p>It provides the client request information to a ftplet. Ftplet
  +                 notification methods will always get the same instance of FtpRequest
  +                 for one connection. So the attributes set by <em>setAttribute()</em>
  +                 will be always available later unless that attribute is removed.
  +                 Different connections will have different FtpRequest objects. From
  +                 here we can get user information, data streams, FTP command, argument,
                    user file system view etc.
                 </p>
             </section>
  -          
  +
             <section>
                 <title>FtpResponse</title>
                 <p>Ftplets can use this to send custom code and messges to client.</p>
             </section>
  -          
  +
             <section>
                 <title>Ftplet</title>
  -              <p>There will be only one instance of Ftplet. During startup the Ftplets

  +              <p>There will be only one instance of Ftplet. During startup the Ftplets
                    will be initialized. The initialization sequence is same as the Ftplet
  -                 sequence in the configuration. Then all notification methods will be 
  +                 sequence in the configuration. Then all notification methods will be
                    called and when the FTP server goes down, the Ftplet will be destroyed.
                    The following method describes all the notification methods.
                 </p>
  @@ -112,15 +112,15 @@
                     </tr>
                     <tr>
                         <td>onConnect</td>
  -                      <td>Client connect notification method. This is the first method

  -                          FTP server will call. If it returns RET_SKIP, IP restriction

  -                          check, connection limit check will not be performed and the 
  -                          server will not send the welcome message (220). 
  +                      <td>Client connect notification method. This is the first method
  +                          FTP server will call. If it returns RET_SKIP, IP restriction
  +                          check, connection limit check will not be performed and the
  +                          server will not send the welcome message (220).
                         </td>
                     </tr>
                     <tr>
                         <td>onDisconnect</td>
  -                      <td>Client disconnect notification method. This is the last
method 
  +                      <td>Client disconnect notification method. This is the last
method
                             FTP server will call. Whatever it returns, the client connection
                             will be closed.
                         </td>
  @@ -136,16 +136,16 @@
                         <td>onDeleteStart</td>
                         <td>Before file deletion this method will be called. Before
this FTP
                             server will not check anything like file existance or permission.
  -                          The requested file name can be get from request argument. We
can 
  -                          get the file object from the request file system view. This is

  +                          The requested file name can be get from request argument. We
can
  +                          get the file object from the request file system view. This is
                             called in DELE FTP command.
                         </td>
                     </tr>
                     <tr>
                         <td>onDeleteEnd</td>
                         <td>This method will be called if the file deletion is successful.
In
  -                          this case the FTP server has already sent the command OK (250)

  -                          message. If onDeleteStart() method returns RET_SKIP or RET_DISCONNECT,

  +                          this case the FTP server has already sent the command OK (250)
  +                          message. If onDeleteStart() method returns RET_SKIP or RET_DISCONNECT,
                             this method will not be called by the FTP server. This is called
                             in DELE FTP command.
                         </td>
  @@ -154,7 +154,7 @@
                         <td>onUploadStart</td>
                         <td>This method will be called before the file upload. The
file name
                             can be get from the request argument. We can get the data input
  -                          stream from request. This will be called before the permission

  +                          stream from request. This will be called before the permission
                             check. This is called during STOR command.
                         </td>
                     </tr>
  @@ -162,16 +162,16 @@
                         <td>onUploadEnd</td>
                         <td>This notification method will be called to indicate that
the file
                             transfer is successful and the server has send the replies. In
case
  -                          of any error this method will not be called. If onUploadStart()

  +                          of any error this method will not be called. If onUploadStart()
                             returns RET_SKIP or RET_DISCONNECT, this method will not be called
                             by the FTP server. This is called in STOR command.
                         </td>
                     </tr>
                     <tr>
                         <td>onDownloadStart</td>
  -                      <td>This is file download request notification method called
during 
  +                      <td>This is file download request notification method called
during
                             RETR command. This will be called before the file download. We
  -                          can get the file name argument from request. Similarly, the 
  +                          can get the file name argument from request. Similarly, the
                             data output stream can be get from the request. This will be
called
                             before the file existance and permissoin check.
                         </td>
  @@ -180,39 +180,39 @@
                         <td>onDownloadEnd</td>
                         <td>This notification method will be called to indicate that
the file
                             transfer is successful and the server has send the replies in
RETR
  -                          command. In case of any error this method will not be called.
If 
  -                          onDownloadStart() returns RET_SKIP or RET_DISCONNECT, this method

  +                          command. In case of any error this method will not be called.
If
  +                          onDownloadStart() returns RET_SKIP or RET_DISCONNECT, this method
                             will not be called by the FTP server.
                         </td>
                     </tr>
                     <tr>
                         <td>onRmdirStart</td>
  -                      <td>Before directory deletion this method will be called during
RMD 
  -                          command. Before this FTP server will not check anything like

  -                          directory existance or permission. The requested directory name

  -                          can be get from request argument. 
  +                      <td>Before directory deletion this method will be called during
RMD
  +                          command. Before this FTP server will not check anything like
  +                          directory existance or permission. The requested directory name
  +                          can be get from request argument.
                         </td>
                     </tr>
                     <tr>
                         <td>onRmdirEnd</td>
                         <td>This method will be called if the directory deletion is
successful
  -                          in RMD command. In this case the FTP server has already sent
the 
  +                          in RMD command. In this case the FTP server has already sent
the
                             command OK (250) message. If onRmdirStart() method returns RET_SKIP
                             or RET_DISCONNECT, this method will not be called by the FTP
server.
                         </td>
                     </tr>
                     <tr>
                         <td>onMkdirStart</td>
  -                      <td>Before directory creation this method will be called during
MKD 
  -                          command. Before this FTP server will not check anything like

  -                          directory existance or permission. The requested directory name

  -                          can be get from request argument. 
  +                      <td>Before directory creation this method will be called during
MKD
  +                          command. Before this FTP server will not check anything like
  +                          directory existance or permission. The requested directory name
  +                          can be get from request argument.
                         </td>
                     </tr>
                     <tr>
                         <td>onMkdirEnd</td>
                         <td>This method will be called if the directory creation is
successful
  -                          in MKD command. In this case the FTP server has already sent
the 
  +                          in MKD command. In this case the FTP server has already sent
the
                             command OK (250) message. If onMkdirStart() method returns RET_SKIP
                             or RET_DISCONNECT, this method will not be called by the FTP
server.
                         </td>
  @@ -220,42 +220,42 @@
                     <tr>
                         <td>onAppendStart</td>
                         <td>This is file append request notification method called
in APPE
  -                          command. The file name can be get from the request argument.

  -                          We can get the data input stream from request. This will be called

  +                          command. The file name can be get from the request argument.
  +                          We can get the data input stream from request. This will be called
                             before the permission check.
                         </td>
                     </tr>
                     <tr>
                         <td>onAppendEnd</td>
                         <td>This is file append success notification method called
in APPE
  -                          command. This notification method will be called to indicate

  -                          that the file transfer is successful and the server has send

  -                          the replies. In case of any error this method will not be called.

  -                          If onAppendStart() returns RET_SKIP or RET_DISCONNECT, this method

  +                          command. This notification method will be called to indicate
  +                          that the file transfer is successful and the server has send
  +                          the replies. In case of any error this method will not be called.
  +                          If onAppendStart() returns RET_SKIP or RET_DISCONNECT, this method
                             will not be called by the FTP server.
                         </td>
                     </tr>
                     <tr>
                         <td>onUploadUniqueStart</td>
  -                      <td>This is unique file create request notification method
called in 
  -                          STOU command. We can get the data input stream from request.

  +                      <td>This is unique file create request notification method
called in
  +                          STOU command. We can get the data input stream from request.
                             This will be called before the permission check.
                         </td>
                     </tr>
                     <tr>
                         <td>onUploadUniqueEnd</td>
  -                      <td>This is unique file create success notification method
called in 
  -                          STOU command. This notification method will be called to indicate

  -                          that the file transfer is successful and the server has send

  -                          the replies. In case of any error this method will not be called.

  -                          If onUploadUniqueStart() returns RET_SKIP or RET_DISCONNECT,
this 
  +                      <td>This is unique file create success notification method
called in
  +                          STOU command. This notification method will be called to indicate
  +                          that the file transfer is successful and the server has send
  +                          the replies. In case of any error this method will not be called.
  +                          If onUploadUniqueStart() returns RET_SKIP or RET_DISCONNECT,
this
                             method will not be called by the FTP Server.
                         </td>
                     </tr>
                     <tr>
                         <td>onRenameStart</td>
                         <td>This is file rename start notification method called in
RNFR
  -                          command. This will be called before the file existance or 
  +                          command. This will be called before the file existance or
                             permission check. The &quot;rename from&quot; file object
                             can be get from request object.
                         </td>
  @@ -263,12 +263,12 @@
                     <tr>
                         <td>onRenameEnd</td>
                         <td>This is file rename success notification method called
in RNFR
  -                          command. This will be called before the file existance or 
  +                          command. This will be called before the file existance or
                             permission check. The &quot;rename from&quot; file object
  -                          can be get from request object. This notification method will

  -                          be called to indicate that the file rename is successful and

  -                          the server has send the success reply (250). In case of any error

  -                          this method will not be called. If onRenameStart() returns RET_SKIP

  +                          can be get from request object. This notification method will
  +                          be called to indicate that the file rename is successful and
  +                          the server has send the success reply (250). In case of any error
  +                          this method will not be called. If onRenameStart() returns RET_SKIP
                             or RET_DISCONNECT, this method will not be called by the FTP
Server.
                         </td>
                     </tr>
  @@ -279,31 +279,31 @@
                             or RET_DISCONNECT, the existing SITE commands will not be executed.
                         </td>
                     </tr>
  -              </table>     
  +              </table>
             </section>
  -          
  +
             <section>
                 <title>Configuration</title>
  -              <p>Ftplet will get the Ftplet specific configuration as the init()

  -                 method argument. 
  +              <p>Ftplet will get the Ftplet specific configuration as the init()
  +                 method argument.
                 </p>
             </section>
  -          
  +
             <section>
                 <title>FtpConfig</title>
  -              <p>It encapsulates the FTP server (or Ftplet container). This object

  +              <p>It encapsulates the FTP server (or Ftplet container). This object
                    is passed to Ftplet during initialization. A Ftplet can get logger,
                    user manager, ftle system manager, server statistics information
                    from FtpConfig.
                 </p>
             </section>
  -          
  +
         </section>
  -      
  +
         <section>
             <title>Configuration</title>
  -          <p>First of all, we have to decide a descriptive name for a Ftplet. 
  -             We specify all the Ftplet names (comma separated) in 
  +          <p>First of all, we have to decide a descriptive name for a Ftplet.
  +             We specify all the Ftplet names (comma separated) in
                <em>config.ftplets</em> configuration parameter. The Ftplet name
                must not contain any whitespace character, comma or semicolon. If
                we have three Ftplets (say f1, f2 and f3), the configuration will
  @@ -312,9 +312,9 @@
             <source>
                 config.ftplets=f1,f2,f3
             </source>
  -          <p>The next thing is to specify the fully qualified Ftplet class name.

  -             if in the above case the class name of the Ftplet f1 is 
  -             &quot;com.yourdomain.Ftplet1&quot; the configuration will be:    

  +          <p>The next thing is to specify the fully qualified Ftplet class name.
  +             if in the above case the class name of the Ftplet f1 is
  +             &quot;com.yourdomain.Ftplet1&quot; the configuration will be:
             </p>
             <source>
                 config.ftplet.f1.class=com.yourdomain.Ftplet1
  @@ -328,10 +328,10 @@
                 ....
             </source>
         </section>
  -      
  +
         <section>
             <title>Deployment</title>
  -          <p>The Ftplet must be added to Apache FTP Server classpath so that 
  +          <p>The Ftplet must be added to Apache FTP Server classpath so that
                the Ftplet can be loaded. Edit ftpd or ftpd_ui scripts to modify
                CUSTOM_CLASSPATH environment variable. Of course before that you
                need to uncomment it.
  
  
  
  1.4       +51 -0     incubator-ftpserver/src/doc/content/xdocs/installation.xml
  
  Index: installation.xml
  ===================================================================
  RCS file: /home/cvs/incubator-ftpserver/src/doc/content/xdocs/installation.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- installation.xml	7 Sep 2005 07:51:15 -0000	1.3
  +++ installation.xml	14 Sep 2005 06:17:14 -0000	1.4
  @@ -69,6 +69,57 @@
               </source>
           </section>
           
  +        <section>
  +            <title>Directory Structure</title>
  +            <h3>Source Distribution Hierarchy</h3>
  +            <source><![CDATA[
  + <INSTALL_DIR>
  +      |
  +      |--- src
  +      |     |
  +      |     |--- java
  +      |     |
  +      |     |--- bin
  +      |     |
  +      |     |--- doc
  +      |           |
  +      |           |--- content
  +      |           |      |
  +      |           |      |--- xdocs
  +      |           |
  +      |           |--- resources
  +      |           |
  +      |           |--- skins
  +      |
  +      |--- res
  +            |
  +            |--- conf
  +            |
  +            |--- home
  +            |
  +            |--- log
  +            ]]></source>
  +            
  +            <h3>Binary Distribution Hierarchy</h3>
  +            <source><![CDATA[
  + <INSTALL_DIR>
  +      |
  +      |--- lib
  +      |
  +      |--- doc
  +      |     |
  +      |     |--- javadoc
  +      |
  +      |--- res
  +            |
  +            |--- conf
  +            |
  +            |--- home
  +            |
  +            |--- log
  +            ]]></source>
  +        </section>
  +        
           <section id="build">
               <title>How To Build</title>
               <p>Please download ftpserver-1.0-src.zip file and unzip it.</p>
  
  
  
  1.2       +18 -18    incubator-ftpserver/src/doc/content/xdocs/ip_restrictor.xml
  
  Index: ip_restrictor.xml
  ===================================================================
  RCS file: /home/cvs/incubator-ftpserver/src/doc/content/xdocs/ip_restrictor.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ip_restrictor.xml	7 Sep 2005 05:07:43 -0000	1.1
  +++ ip_restrictor.xml	14 Sep 2005 06:17:14 -0000	1.2
  @@ -16,45 +16,45 @@
     limitations under the License.
   -->
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
  -<document> 
  -    <header> 
  -        <title>IP Restrictor</title> 
  +<document>
  +    <header>
  +        <title>IP Restrictor</title>
           <authors>
               <person id="RB" name="Rana Bhattacharyya" email="rana_b@yahoo.com"/>
           </authors>
  -    </header> 
  -  <body> 
  +    </header>
  +  <body>
         <section id="ip_restrictor">
             <title>IP Restrictor</title>
               <p>
  -                The IP restrictor allows you to restrict access to your FTP server 
  -                by IP address. Client IP addresses can be allowed or denied access 
  +                The IP restrictor allows you to restrict access to your FTP server
  +                by IP address. Client IP addresses can be allowed or denied access
                   according to rules specified.
               </p>
               <p>
  -                IP addresses can be specified with wild cards. The following 
  +                IP addresses can be specified with wild cards. The following
                   special characters may be used.
               </p>
               <ul>
                   <li>
  -                    <strong>*</strong> : A star functions as a wildcard for
checking 
  -                    the IP address. Any name or number will match that section of 
  +                    <strong>*</strong> : A star functions as a wildcard for
checking
  +                    the IP address. Any name or number will match that section of
                       the rule if it is a star.
                   </li>
                   <li>
  -                    <strong>?</strong> : The question mark '?' character functions
as 
  +                    <strong>?</strong> : The question mark '?' character functions
as
                       a wildcard for a single character.
                   </li>
                   <li>
  -                    <strong>[-]</strong> : The hyphen '-' character functions
as a range 
  +                    <strong>[-]</strong> : The hyphen '-' character functions
as a range
                       in an IP address.
                   </li>
               </ul>
               <p>
  -                The order of the rules is important. When a client contacts the 
  -                server, the rules are evaluated from top to bottom in the list 
  +                The order of the rules is important. When a client contacts the
  +                server, the rules are evaluated from top to bottom in the list
                   of rules. The first matching rule applies and evaluation is stopped.
  -                If there is no match, the client is allowed to access the server. 
  +                If there is no match, the client is allowed to access the server.
               </p>
         </section>
         <section>
  @@ -70,14 +70,14 @@
                 </tr>
                 <tr>
                     <td>config.ip-restrictor.file</td>
  -                  <td>The file where IP restriction information will be stored. 
  +                  <td>The file where IP restriction information will be stored.
                         The default value is ./res/ip.gen
                     </td>
                 </tr>
  -          </table>          
  +          </table>
         </section>
         <section>
  -          <title>IP Restructor UI</title>
  +          <title>IP Restrictor UI</title>
             <p>This IP restriction can be configured using server UI.</p>
             <img src="images/ftp_ip_restrictor.jpg"/>
         </section>
  
  
  
  1.2       +33 -23    incubator-ftpserver/src/doc/content/xdocs/mailing_list.xml
  
  Index: mailing_list.xml
  ===================================================================
  RCS file: /home/cvs/incubator-ftpserver/src/doc/content/xdocs/mailing_list.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mailing_list.xml	7 Sep 2005 05:07:43 -0000	1.1
  +++ mailing_list.xml	14 Sep 2005 06:17:14 -0000	1.2
  @@ -16,36 +16,46 @@
     limitations under the License.
   -->
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
  -<document> 
  -    <header> 
  -        <title>Mailing List</title> 
  +<document>
  +    <header>
  +        <title>Mailing List</title>
           <authors>
               <person id="RB" name="Rana Bhattacharyya" email="rana_b@yahoo.com"/>
           </authors>
  -    </header> 
  -    <body> 
  +    </header>
  +    <body>
           <section id="mailing_list">
               <title>Mailing List</title>
  -            <p>General information about the jakarta mailing lists can be found 
  -               <a href="http://jakarta.apache.org/site/mail.html">here</a>.

  -               Please read these guidelines before subscribing or posting to the lists.
  -            </p>
  -            <p>At this point Ftpserver uses Incubator general mailing list.</p>
  -            <p><b>general@incubator.apache.org</b></p>
  -            <p>To subscribe to the user list, send an empty message to 
  -               <a href="mailto:general-subscribe@incubator.apache.org">general-subscribe@incubator.apache.org</a>.
  +            <p>There is no FTP Server specific mailing list now. We shall create
  +               it soon. At this point Ftpserver uses Incubator general mailing list.
  +               (general@incubator.apache.org).
               </p>
  -            <p>To unsubscribe from the user list, send an empty message to 
  -               <a href="mailto:general-unsubscribe@incubator.apache.org">general-unsubscribe@incubator.apache.org</a>.

  -               Note that you must unsubscribe using the same email address you've used
to subscribe. 
  -            </p>   
  -            <p>Once you're subscribed, send mail to general@incubator.apache.org
to post 
  -               messages on the user list. Please add <strong>[Ftpserver]</strong>
prefix to identify Ftpserver
  -               related messages easily.
  -            </p>
  -            <p>All emails sent to general@incubator.apache.org are archived 
  -               <a href="http://www.mail-archive.com/general@incubator.apache.org/">here</a>.
  +            <p>General information about the jakarta mailing lists can be found
  +               <a href="http://jakarta.apache.org/site/mail.html">here</a>.
  +               Please read these guidelines before subscribing or posting to the lists.
               </p>
  +            <table>
  +                <tr>
  +                    <td><b>Name</b></td>
  +                    <td>Incubator General : <a href="mailto:general@incubator.apache.org">general@incubator.apache.org</a></td>
  +                </tr>
  +                <tr>
  +                    <td><b>Subscribe</b></td>
  +                    <td><a href="mailto:general-subscribe@incubator.apache.org">general-subscribe@incubator.apache.org</a></td>
  +                </tr>
  +                <tr>
  +                    <td><b>Unsubscribe</b></td>
  +                    <td><a href="mailto:general-unsubscribe@incubator.apache.org">general-unsubscribe@incubator.apache.org</a></td>
  +                </tr>
  +                <tr>
  +                    <td><b>Archive</b></td>
  +                    <td><a href="http://www.mail-archive.com/general@incubator.apache.org/">http://www.mail-archive.com/general@incubator.apache.org/</a></td>
  +                </tr>
  +            </table>
  +            <note>Once you're subscribed, send mail to general@incubator.apache.org
to post
  +                  messages on the user list. Please add <em>[Ftpserver]</em>
prefix to
  +                  identify Ftpserver related messages easily.
  +            </note>
           </section>
       </body>
   </document>
  
  
  
  1.3       +61 -14    incubator-ftpserver/src/doc/content/xdocs/who_we_are.xml
  
  Index: who_we_are.xml
  ===================================================================
  RCS file: /home/cvs/incubator-ftpserver/src/doc/content/xdocs/who_we_are.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- who_we_are.xml	9 Sep 2005 11:14:59 -0000	1.2
  +++ who_we_are.xml	14 Sep 2005 06:17:14 -0000	1.3
  @@ -16,27 +16,74 @@
     limitations under the License.
   -->
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
  -<document> 
  -    <header> 
  -        <title>Who We Are?</title> 
  +<document>
  +    <header>
  +        <title>Who We Are?</title>
           <authors>
               <person id="RB" name="Rana Bhattacharyya" email="rana_b@yahoo.com"/>
           </authors>
  -    </header> 
  -    <body> 
  +    </header>
  +    <body>
           <section id="weare">
               <title>Who We Are?</title>
  -            <p>Special thanks go to the following people for their contributions
to
  -               this project. We also appreciate documentation, feedback, and bug reports.

  -               This is a living document that describes the key contributors to FTP server.

  +            <p>A successful project requires many people to play many roles.
  +               Some members write code or documentation, while others are valuable
  +               as testers, submitting patches and suggestions.
               </p>
  +            <p>The team is comprised of Members and Contributors. Members have
  +               direct access to the source of a project and actively evolve the
  +               code-base. Contributors improve the project through submission of
  +               patches and suggestions to the Members. The number of Contributors
  +               to the project is unbounded. Get involved today. All contributions
  +               to the project are greatly appreciated.
  +            </p>
  +
  +            <section>
  +                <title>Members</title>
  +                <p>The following is a list of developers with commit privileges
  +                   that have directly contributed to the project in one way or another.
  +                </p>
  +                <table>
  +                    <tr>
  +                        <th>Name</th>
  +                        <th>Email</th>
  +                        <th>Organization</th>
  +                    </tr>
  +                    <tr>
  +                        <td>Rana Bhattacharyya</td>
  +                        <td><a href="mailto:rana_b.{aT}.yahoo.{d0T}.com">rana_b.{aT}.yahoo.{d0T}.com</a></td>
  +                        <td></td>
  +                    </tr>
  +                    <tr>
  +                        <td>Paul Hammant</td>
  +                        <td><a href="mailto:paul.{aT}.hammant.{d0T}.org">paul.{aT}.hammant.{d0T}.org</a></td>
  +                        <td></td>
  +                    </tr>
  +                </table>
  +            </section>
  +
               <section>
  -                <title>Active Commiters</title>
  -                <ul>
  -                    <li>Rana Bhattacharyya (rana_b at yahoo.com)</li>
  -                    <li>Paul Hammant</li>
  -                    <li>Birkir A. Barkarson</li>
  -                </ul>
  +                <title>Contributors</title>
  +                <p>The following additional people have contributed to this project
  +                   through the way of suggestions, patches or documentation.
  +                </p>
  +                <table>
  +                    <tr>
  +                        <th>Name</th>
  +                        <th>Email</th>
  +                        <th>Organization</th>
  +                    </tr>
  +                    <tr>
  +                        <td>Birkir A. Barkarson</td>
  +                        <td></td>
  +                        <td></td>
  +                    </tr>
  +                    <tr>
  +                        <td>David H. DeWolf</td>
  +                        <td><a href="mailto:ddewolf.{aT}.apache.{d0T}.org">ddewolf.{aT}.apache.{d0T}.org</a></td>
  +                        <td>Vivare, INC</td>
  +                    </tr>
  +                </table>
               </section>
           </section>
       </body>
  
  
  

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


Mime
View raw message