A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1275.html
Document ID: 1275
Branch: main
Language: default
Name: Communication tools that we use (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 12/4/06 6:59:50 PM
Updated by: Mark Lundquist
A new version has been created, state: draft
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 3440 bytes (previous version: 2594 bytes)
Content diff:
(9 equal lines skipped)
<a href="http://en.wikipedia.org/wiki/Top-posting#Inline_replying";>edit the
original message</a> and include only enough to establish context, not the
entire message.</li>
+++ <li>Don't crosspost to the user and developer lists. The developers also
read
+++ the users list.</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
(26 equal lines skipped)
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>
+++ you will in turn get a more helpful 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>A very common response to user questions is "What are you trying to
+++ accomplish"? Try to supply that information when you first ask the
question,
+++ and you will get a definitive answer that much sooner. Cocoon is a rich
+++ framework that gives you a lot of tools, so that it's not always obvious to
new
+++ users which tool set is the best to use for a particular problem. New users
+++ sometimes get wrapped around the axle on some detail of the solution they
are
+++ trying to make for a given scenario, and then end up posting to the list to
ask
+++ how to do some exotic or bizarre thing. If you can take a step back and
+++ describe the scenario itself, the more experienced users may be able to
suggest
+++ one or more simpler solutions.</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.
(29 equal lines skipped)
