[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-cvs
Subject:    cvs commit: jakarta-log4j/src/xdocs contactUs.xml
From:       ceki () apache ! org
Date:       2002-04-30 13:57:51
[Download RAW message or body]

ceki        02/04/30 06:57:51

  Modified:    src/xdocs contactUs.xml
  Log:
  Cosmetic changes.
  
  Revision  Changes    Path
  1.12      +87 -66    jakarta-log4j/src/xdocs/contactUs.xml
  
  Index: contactUs.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-log4j/src/xdocs/contactUs.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- contactUs.xml	25 Apr 2002 21:18:15 -0000	1.11
  +++ contactUs.xml	30 Apr 2002 13:57:51 -0000	1.12
  @@ -6,75 +6,96 @@
       <title>Contact us</title>
     </properties>
   
  -<body>
  -
  -<section name="Bug reporting">
  -
  -<p>Bugs should be reported by using the 
  -<a href="http://nagoya.apache.org/bugzilla">Apache Bug Database</a>.</p>
  -
  -<p>Before reporting a problem, please <a
  -href="http://nagoya.apache.org/bugzilla/query.cgi">check the
  -database</a> and the <a href="HISTORY">project history file</a> to see
  -if the problem is not already known. After this first verification
  -step, you are highly encouraged to send email to the
  -<em>log4j-user</em> mailing list (see below) describing the bug. Only
  -after these precautionary steps should you file a bug
  -report. Moreover, requests for enhancements should not be entered in
  -Bugzilla but posted on the log4j-user mailing list instead.</p>
  -
  -</section>
  -
  -<section name="Mailing lists">
  -
  -<p>Discussion on log4j and logging in general are held on the
  -<em>log4j-user</em> mailing list.  To subscribe to
  -this list send an e-mail to <A
  -HREF="mailto:log4j-user-subscribe@jakarta.apache.org">log4j-user-subscribe@jakarta.apache.org</A>.</p>
  -
  -<p>Development related discussions are held on the <em>log4j-dev</em>
  -mailing list. To subscribe to this list send an e-mail to <A
  -HREF="mailto:log4j-dev-subscribe@jakarta.apache.org">log4j-dev-subscribe@jakarta.apache.org</A>.</p>
  -
  -<p>All developers are encouraged to subscribe to the
  -<em>log4j-cvs</em> list which will notify the subscribers of CVS any
  -commits to the repository.  To subscribe to this list send an e-mail
  -to <A
  -HREF="mailto:log4j-cvs-subscribe@jakarta.apache.org">log4j-cvs-subscribe@jakarta.apache.org</A>.
  -Committers <em>should</em> subscribe to this list with their Apache
  -e-mail address.</p>
  -
  -<p><b>To prevent spam, we expect you to be subscribed to a list before
  -posting to it. Otherwise, your mail needs to be approved by an
  -administrator which delays your posting and creates needless work for us.</b></p>
  -
  -<p>Most Jakarta mailing lists, in particular the log4j mailing lists,
  -are archived. Some of the known archives are listed below:</p>
  -
  -<ul>
  -
  -<li>
  -<a href="http://www.mail-archive.com/">http://www.mail-archive.com</a>
  -</li>
  -
  -<li>Full mbox archives of all Jakarta lists are available at <a
  -href="http://jakarta.apache.org/mail/">http://jakarta.apache.org/mail/</a>
  -</li>
  -
  -<li>
  -<a href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</a>
  -</li>
  -
  -</ul>
  -
  -<p>Please do your best to ensure that you are not sending HTML or
  -"Stylelized" email to the list.  If you are using Outlook or Outlook
  -Express or Eudora, chances are that you are sending HTML email by
  -default. There is usually a setting that will allow you to send "Plain
  -Text" email. </p>
  +  <body>
   
   
  +    <section name="Mailing lists">
   
  +      <p>Discussion on log4j and logging in general are held on the
  +	<em>log4j-user</em> mailing list.  To subscribe to this list
  +	send an e-mail to <a
  +	HREF="mailto:log4j-user-subscribe@jakarta.apache.org">log4j-user-subscribe@jakarta.apache.org</a>.
  +      </p>
  +
  +      <p>Development related discussions are held on the
  +	<em>log4j-dev</em> mailing list. To subscribe to this list
  +	send an e-mail to <A
  +	HREF="mailto:log4j-dev-subscribe@jakarta.apache.org">log4j-dev-subscribe@jakarta.apache.org</A>.</p>
  +
  +      <p>All developers are encouraged to subscribe to the
  +	<em>log4j-cvs</em> list which will notify the subscribers of
  +	CVS any commits to the repository.  To subscribe to this list
  +	send an e-mail to <A
  +	HREF="mailto:log4j-cvs-subscribe@jakarta.apache.org">log4j-cvs-subscribe@jakarta.apache.org</A>.
  +	Committers <em>should</em> subscribe to this list with their
  +	Apache e-mail address.
  +      </p>
  +
  +      <p><b>To prevent spam, we expect you to be subscribed to a list
  +	  before posting to it. Otherwise, your mail needs to be
  +	  approved by an administrator which delays your posting and
  +	  creates needless work for us.</b>
  +      </p>
  +
  +      <p>Most Jakarta mailing lists, in particular the log4j mailing
  +	lists, are archived. Some of the known archives are listed
  +	below:
  +      </p>
  +
  +      <ul>
  +
  +	<li>
  +	  <a href="http://www.mail-archive.com/">http://www.mail-archive.com</a>
  +	</li>
  +
  +	<li>Full mbox archives of all Jakarta lists are available at
  +	    <a
  +	    href="http://jakarta.apache.org/mail/">http://jakarta.apache.org/mail/</a>
  +	</li>
  +
  +	<li>
  +	  <a href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</a>
  +	</li>
  +
  +      </ul>
  +
  +      <p>Please do your best to ensure that you are not sending HTML
  +	or "Stylelized" email to the list.  If you are using Outlook
  +	or Outlook Express or Eudora, chances are that you are sending
  +	HTML email by default. There is usually a setting that will
  +	allow you to send "Plain Text" email. 
  +      </p>
  +    </section>
  +
  +
  +    <section name="Bug reporting">
  +
  +      <p>Bugs should be reported by using the 
  +	<a href="http://nagoya.apache.org/bugzilla">Apache Bug Database</a>.
  +      </p>
  +
  +      <p>Before reporting a problem, please make sure to <a
  +	  href="http://nagoya.apache.org/bugzilla/query.cgi">check the
  +	  database</a> and the <a href="HISTORY">project history
  +	  file</a> to see if the problem is not already known. Before
  +	  filing a report, you should first send email to the
  +	  <em>log4j-user</em> mailing list describing the bug. Only
  +	  after these precautionary steps should you file a bug
  +	  report. 
  +      </p>
  +
  +      <p>Although Bugzilla allows users to flag enhancement requests
  +	 as such, enhancement requests are not bugs and should not be
  +	 treated as such. The preferred way to request for
  +	 enhancements is by posting on the log4j-user list. This
  +	 allows other interested parties to participate in the ensuing
  +	 discussion.
  +      </p>
  +
  +      <p><b>Just reporting a bug will not fix it. A good bug report
  +      includes a detailed description of the problem and a succinct
  +      test case which can reproduce the problem.</b> 
  +      </p>
   
   </section>
   
  
  
  

--
To unsubscribe, e-mail:   <mailto:log4j-cvs-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-cvs-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic