cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [DAISY] Updated: Communication tools that we use
Date Mon, 04 Dec 2006 14:29:35 GMT
A document has been updated:

Document ID: 1275
Branch: main
Language: default
Name: Communication tools that we use (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 12/4/06 2:29:21 PM
Updated by: Mark Lundquist

A new version has been created, state: draft


This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 2594 bytes (previous version: 37 bytes)
Content diff:
--- <html><body><p>TODO</p></body></html>
+++ <html>
+++ <body>
+++ <h1>Mailing lists</h1>
+++ <p>Observe common-sense netiquette when posting.  In particular:</p>
+++ <ul>
+++ <li>When replying, please
+++ <a href="">edit the
+++ original message</a> and include only enough to establish context, not the
+++ entire message.</li>
+++ <li>Only reply to a message if you are really posting a reply on that thread;
+++ don't use your mailer's "Reply" function as a shortcut to get the list address
+++ into the "To:" field.  Instead, use your mailer's "new message" function to
+++ start a fresh thread.  When people abuse "Reply" and just change the "Subject:"
+++ line to a new topic, it makes it harder for threaded mailreaders to display the
+++ subjects accurately.  This can make it less likely that your message will be
+++ seen and replied to.</li>
+++ </ul>
+++ <p>Regarding content:</p>
+++ <ul>
+++ <li>Ask your questions on the list.  If someone helps you out, don't email them
+++ off-list to ask your next question.  You will get the best answers if you stay
+++ on-list, and that way the question and answers can also benefit the current and
+++ future community.</li>
+++ <li>When asking for help, don't forget to include:</li>
+++ <ul>
+++ <li>The version of Cocoon you are using (the most important thing to not forget!
+++ :-)</li>
+++ <li>The servlet container (e.g. Jetty, Tomcat etc.) you are using.</li>
+++ <li>Platform details: JDK version and host OS</li>
+++ <li>Any relevant sitemap configuration, XSLT, Java or Javascript source code you
+++ are working with</li>
+++ <li>If you're getting an exception thrown, include the stack trace</li>
+++ </ul>
+++ <li>Don't just say that something "doesn't work"; explain (a) exactly what you
+++ did; (b) what you expected to happen; and (c) what happened instead of what you
+++ expected.  That type of explanation gives people a lot more information to work
+++ with.</li>
+++ <li>If you can show that you at least made some effort to figure something out,
+++ you will get a better response.  In particular, if you have in mind some idea
+++ that might help and it is an easy thing to try, don't post to the list to ask
+++ "Can I....".  Just try it for yourself and see! :-)</li>
+++ <li>If you ask for help with something, and then you later figure it out for
+++ yourself, please follow up on the list and describe what you did to fix the
+++ problem.  We like to prepend "SOLVED: " to the Subject: line when doing this.
+++ </li>
+++ </ul>
+++ <h2>User list</h2>
+++ <p>Subscribe</p>
+++ <h3>Gmane</h3>
+++ <h3>Archive</h3>
+++ <h2>Developer list</h2>
+++ <p>Subscribe</p>
+++ <h3>Gmane</h3>
+++ <h3>Archive</h3>
+++ <h1>Wiki</h1>
+++ <h1>IRC</h1>
+++ <h1>JIRA</h1>
+++ <p>[TODO: finish ]</p>
+++ </body>
+++ </html>

View raw message