cziegeler 2003/07/03 02:46:27
Modified: src/documentation/content/xdocs site.xml
Added: src/documentation/content/xdocs/community mail-lists.xml
mail-archives.xml
Log:
Moving info about mailing lists to top level
Revision Changes Path
1.7 +2 -0 cocoon-site/src/documentation/content/xdocs/site.xml
Index: site.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/site.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- site.xml 16 Jun 2003 11:02:10 -0000 1.6
+++ site.xml 3 Jul 2003 09:46:27 -0000 1.7
@@ -23,6 +23,8 @@
<community label="Community" href="community/">
<members label="Members" href="members.html"/>
+ <link label="Mail Lists" href="mail-lists.html"/>
+ <link label="Mail Archives" href="mail-archives.html"/>
</community>
<external-refs>
1.1
cocoon-site/src/documentation/content/xdocs/community/mail-lists.xml
Index: mail-lists.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
"dtd/document-v12.dtd">
<document>
<header>
<title>Mailing Lists</title>
</header>
<body>
<section>
<title>Important Notice</title>
<p><strong>IMPORTANT: Before posting a question or problem to any mailing
list,
</strong>please first look at the following resources:</p>
<ol>
<li><link
href="http://cocoon.apache.org/2.1/faq/index.html";>FAQs</link></li>
<li><link href="http://cocoon.apache.org/2.1/link/index.html";>Cocoon
Links</link></li>
<li><link href="mail-archives.html">Mailing list archives</link> -
a veritable goldmine of Cocoon-specific information - if you know where
to look!</li>
</ol>
<p><strong>IMPORTANT:</strong> Careful postings please.
These are high-volume lists, so we all needs ways to help us all
work smarter.
See tips for <link
href="http://cocoon.apache.org/2.1/contrib.html#tips";>Contributing</link>
</p>
</section>
<section>
<title>Tips (keeping focus helps your points come across!)</title>
<p>We use the mail list both as a media to transmit our thoughts and as a
virtual location to hang around and feel part of something.
</p><p>
In order for the second to happen, you just have to subscribe. That's
it, nothing fancy.
</p><p>
But in order for the first to happen (transmit your thoughts) it's an
entirely different matter.
</p><p>
Here are a few things that help a lot:
</p><p>
1) reduce noise, increase signal: your email client will quote the
message you are replying to automatically, but it's *your*
responsibility to remove those parts that aren't part of the signal of
your email. Sure, you might let this operation to the reader, but you
must understand that the reader is not supposed to do this. Or, at
least, it should be *you* to make the reader confortable.
</p><p>
2) be respectful, be aware of community dynamics: sending HTML in the
mail more than *doubles* the message size and interferes with text-based
mail clients. You want your point to come across, so make sure that
everybody can get to that point with the *easiest* possible effort, or,
otherwise, your signal might be wasted in the noise and the time you
think you are saving, you are, in fact, loosing it completely.
</p><p>
3) promote your signal: people on mail lists are used to read tons of
email a day. Without a good 'promotion' of your points, they might get
missed in the noise. (note: 'noise' is a subjective notion, what is
signal for you might be noise for others, it's up to you to make your
signal stand up). Things that help in this respect:
</p><p>
a) a simple yet effective email title. Geeks are ultimately curious
animals, tickle their curiosity!
</p><p>
b) be elegant and visually effective. Sure, you have to use ASCII,
but there is a lot that you can convey with ASCII
</p><source><![CDATA[
+---------------------------------+
| I'm sure nobody will miss this! |
+---------------------------------+
]]></source><p>
c) structure your text. Whenever possible, use *strong* or
_underline_ or /italic/ or use bullet lists and so on. Consider textual
RFC, that's how you should write your emails. Sure, it takes a little
more time, but I guarantee you that it saves a lot of it later on.
</p><p>
d) keep paragraphs short! you can go on and on forever, I'm sure you
do, but keep your point focused, so that the signal/noise ratio is
increased.
</p><p>
4) be respectful of other's opinion: your email will be stored forever,
archived in several locations around the world, indexed by Google,
locked in magnetic tapes into the NSA caves and so on. Just keep this in
mind before you hit "send", this will keep your ego honest :)
</p><p>
5) admit your incapacity/ignorance/mistakes: there is nothing more
appreciated in a community that someone that can stand up and apologize
for something. Remember: if you don't make mistakes, you can't learn.
And if you don't admit you made it, nobody knows you are learning :)
</p><p>
Keep all these things in mind and you'll be impressed by how much fun
and knowledge you can get out of all this open development thing.
</p>
</section>
<section>
<title>Cocoon Users</title>
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
<p>The general Cocoon list, for problems, bug reports, asking for advice
on how
best to implement a site, comparisons with other XML frameworks, etc.
But don't forget to look in the FAQ first, please!</p>
<p><strong>This is not an appropriate list for general XSL and XML
questions.</strong>
Instead look at the various resources listed at the
<link href="http://cocoon.apache.org/2.1/link/index.html";>Cocoon
Links</link> pages,
or try the
<link href="http://www.mulberrytech.com/xsl/";>Mulberrytech XSL
list</link>.</p>
<p><strong>This is also not an appropriate list for general Java
questions.</strong>
Instead try <link
href="news:comp.lang.java.help";>news:comp.lang.java.help</link>
or <link href="http://hotdispatch.com/";>http://hotdispatch.com/</link>,
for
example.</p>
<p><strong>IMPORTANT:</strong> If you are posting about a problem you are
having
(as most people do), it will aid in finding a speedy resolution if you
provide
full configuration details (especially the <strong>Cocoon version
number</strong>,
but also your operating system, JDK version, and servlet engine), and
full details
of any errors encountered (including full error messages and stack
traces).</p>
<p>Please also have some consideration for the other users on the list -
this is a
busy list and we do not appreciate getting the exact same message posted
impatiently
several times a day/week! Doing so is only likely to make your question
answered more
slowly, or not at all, not faster.</p>
<note>This list is moderated, so the first time you post, there will be a
delay before your post is reviewed and accepted. This is to prevent
spam.</note>
</section>
<section>
<title>Cocoon Dev</title>
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
<p>This list is for developers <strong>working on</strong> or wanting to
work on
Cocoon itself (not developers merely working <strong>with</strong>
Cocoon),
for code patches to Cocoon to be posted (please use <code>diff -u</code>
format),
and for general Cocoon questions.</p>
<p>Note this is <strong>NOT</strong> for general Cocoon questions like "Why
isn't Cocoon working on my machine?" -
please ask those sorts of questions on cocoon-users (after reading the
FAQ first, of course).</p>
<note>This list is moderated, so the first time you post, there will be a
delay before your post is reviewed and accepted. This is to prevent
spam.</note>
</section>
<section>
<title>Cocoon Docs</title>
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
<p>This list is for everyone (users and developers) to assist with building
the Cocoon documentation.
</p>
<p>
Please be careful to limit cross-posting between the Cocoon lists. You can
assume that all developers are also subscribed to cocoon-docs.
Any docs-related thread on -users or -dev should be moved to -docs (do not
Cc the original list, but send a short reply to indicate that the thread
has moved).
</p>
<note>This list is moderated, so the first time you post, there will be a
delay before your post is reviewed and accepted. This is to prevent
spam.</note>
</section>
<section>
<title>Cocoon Cvs</title>
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
<p>This <strong>read-only</strong> list sends out notification messages
detailing
any change made to the CVS repository where all the source code and
libraries
are stored for development purposes. The average user probably doesn't
need to
subscribe to this list.</p>
<note>You should never post to this list at all. Only the
CVS server should post to it.</note>
</section>
<section>
<title>XSP Dev</title>
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
<p>This list began life on November 2000, and was created to discuss the
standardisation and implementation of the dynamic content language XSP,
which is used not only in Cocoon but in other software such as AxKit.
You are recommended to have a strong working knowledge of XSP before
joining
this list.</p>
<p>Note this is <strong>NOT</strong> for general XSP questions like
"Why doesn't my XSP page work?" - please ask those sorts of questions on
the relevant list for your XSP software (e.g. cocoon-users if you're using
Cocoon) - after checking the FAQ first of course!
</p>
</section>
<section>
<title>Related Mailing Lists</title>
<p>(See also <link
href="http://dmoz.org/Computers/Data_Formats/Markup_Languages/XML/";>
ODP XML links</link> for related websites.)</p>
<ul>
<li><link href="http://www.mulberrytech.com/xsl/";>Mulberrytech XSL
list</link> -
more appropriate than Cocoon Users for general XSL questions.</li>
<li><link href="http://xml.apache.org/mail.html";>XML Apache
Projects</link> -
list of mailing lists for all the projects on xml.apache.org.</li>
<li>Some servlet engines have their own mailing lists for servlet-engine
configuration questions, such as
<link href="mailto:[EMAIL PROTECTED]">tomcat-user</link> (note it is
"user"
and not "users").</li>
</ul>
</section>
</body>
</document>
1.1
cocoon-site/src/documentation/content/xdocs/community/mail-archives.xml
Index: mail-archives.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
"dtd/document-v12.dtd">
<document>
<header>
<title>Mail Archives</title>
</header>
<body>
<section>
<title>Mailing List Archives</title>
<p>
There are a number of mailing list archives available. Email
<link
href="mailto:[email protected]";>users.at.cocoon.apache.org</link> if you
know of more.
</p>
<table>
<tr>
<th>Cocoon-users</th>
<th>Cocoon-dev</th>
<th>Cocoon-docs</th>
<th>Regularly updated?</th>
<th>Searchable?</th>
<th>Speed</th>
<th>Other features?</th>
</tr>
<!-- this has been broken for a while
we hid this entry on 2001-11-23 (bring it back when the server recovers)
<tr>
<td colspan="2"><link
href="http://mail-archives.apache.org/";>http://mail-archives.apache.org</link></td>
<td>No, at present</td>
<td>No</td>
<td>3/5</td>
<td></td>
</tr>
-->
<tr>
<td><link
href="http://marc.theaimsgroup.com/?l=xml-cocoon-users&r=1&w=2";>
Aims Group - U</link></td>
<td><link
href="http://marc.theaimsgroup.com/?l=xml-cocoon-dev&r=1&w=2";>
Aims Group - De</link></td>
<td><link
href="http://marc.theaimsgroup.com/?l=xml-cocoon-docs&r=1&w=2";>
Aims Group - Do</link></td>
<td>Yes</td>
<td>Onsite, by subject/author/body</td>
<td>4/5</td>
<td>Chunked listings</td>
</tr>
<!-- real-time.com has been broken for a while
we hid this listing on 2001-11-23 (bring it back when they recover)
<tr>
<td><link href="http://mailman.real-time.com/pipermail/cocoon-users/";>
RealTime - U</link></td>
<td><link href="http://mailman.real-time.com/pipermail/cocoon-devel/";>
RealTime - D</link></td>
<td>No, at present</td>
<td>Yes</td>
<td>Yes - use www.google.com and prepend search with
<code>site:mailman.real-time.com cocoon-users</code></td>
<td>3/5</td>
<td>Sort by author/subject/date</td>
</tr>
-->
<tr>
<td><link href="http://www.mail-archive.com/[email protected]/";>
Mail Archive - U</link></td>
<td><link href="http://www.mail-archive.com/[email protected]/";>
Mail Archive - De</link></td>
<td>No, at present</td>
<td>Yes</td>
<td>Onsite and can also use www.google.com and prepend search with
<code>site:www.mail-archive.com cocoon-users</code></td>
<td>4/5</td>
<td>Sort by thread/date</td>
</tr>
<tr>
<td><link href="http://xml.apache.org/mail/cocoon-users/";>
xml.apache.org - U</link></td>
<td><link href="http://xml.apache.org/mail/cocoon-dev/";>
xml.apache.org - De</link></td>
<td><link href="http://xml.apache.org/mail/cocoon-docs/";>
xml.apache.org - Do</link></td>
<td>Yes</td>
<td>No</td>
<td>2/5</td>
<td>Bulk retrieval (gzipped monthly)</td>
</tr>
<tr>
<td>Ezlm archives (email <link href="mailto:[EMAIL PROTECTED]">
cocoon-users-help @ xml.apache.org</link> for automated
instructions)</td>
<td>Ezlm archives (email <link href="mailto:[EMAIL PROTECTED]">
cocoon-dev-help @ xml.apache.org</link> for automated instructions)</td>
<td>??? (Does someone know?)</td>
<td>Yes</td>
<td>No</td>
<td>1/5</td>
<td>Bulk retrieval</td>
</tr>
</table>
</section>
</body>
</document>
