Christian Haul wrote: > I have one very simple request for all users of this list: > > Please follow up to an answer you've received by summarizing > the thread, ideally adding "SUMMARY" to the subject.
Yes! This is an excellent idea. In fact this is part of listserver etiquette. In the early days of mail listservers, this used to happen all the time. It makes the list much more productive. > First of all, *YOU* are the only person on earth that can > judge if the help was correct, helpful, and on target. > _You_ know best how to describe _your_ problem, and > _you_ can judge which information _you_ got is the key. > Of course _we_ need to take the time not only to throw > pieces of information at you but _explain_ and give pointers. > > The effect would be that these summaries can easily be searched > and used for building docs, at least FAQs. > > It doesn't take much time and it is only fair enough if you > 'pay' for the help you got. And it makes answering questions > much more fun if it is followed up with a positive feedback. > > This codex cannot be enforced, but I for my part tend to > ignore questions from those that never follow up. Me too. After we have discussed this thread a bit, then we can add a section to the cocoon/mail-lists.html doc. Does anyone know a good link that we can add about general mail list etiquette. --David > Oh, for this to work, make sure that your mail user agent > keeps the "In-Reply-To:" header so it threads well. > > As a side node, sun-managers works like this (only that > replies are allowed only directly to the initial individual, > not the list) and it works well. > > Chris. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
