From: Patrick Gundlach <gundlach@irb.cs.uni-dortmund.de>
Subject: suggestion
Date: Mon, 28 Jan 2002 11:59:27 +0100 [thread overview]
Message-ID: <200201281059.g0SAxRf26692@sol.cs.uni-dortmund.de> (raw)
Hi,
concerning the suggestion Hans has made, I'd like to add some
comments:
We have to analyse the questions asked on the list. In my
opinion it does not make sens just to copy the question and the
correct answer and make a digest. This would not do any good,
because we then just have a mere copy of the mailinglist
(stripped down to the essentials, indeed)
More important is to "rate" the questions:
1) is it a question to wich the answer can be found in the
manual? Then there is already a documentation for it and we do
not need to answer it again.
2) is it a question that has not yet been documented? Say for
example "how can I draw a line below the headline?". (I actually
do not know if this is in the manual). In this case, we (Hans :->
) should see this as an opportunity to add a few lines to the
manual, so the next time this questions will not be asked again.
3) a questions that is related to the installation. For example
the texhash or mktexlsr thing. Or the cont-sys.ori/cont-sys.tex
stuff. I think these are worth being documented in some extra
document.
4) bug reports. We do not need to collect them, since one hour
later 96% of them are already fixed. Just search the archive if
you have some trouble.
5) Questions regarding fonts/encodings. Yuck. I have no clue what to do
with them. There is really something that has to be done. I know
that there is are docs. But there are a many questions on the
list concerning this subject.
6) request for improvements. They are probably documented in
Hans' privat todo list... I there a need to collect them? I
think yes.
7) Questions like "How can this feature xyz (just think of gb's
indefinate long page that got cut off after each chapter) be
achieved? These questions are often very esoteric. But imho they
are worth being collected.
So what is my conclusion? Ignore some questions, improve the
documentation where necessary, collect some stuff for an extra
doc. We do not need an faq.
Viele Grüße,
Patrick Gundlach
next reply other threads:[~2002-01-28 10:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Sun, 27 Jan 2002 19:02:33 +0100." <5.1.0.14.1.20020127190025.02af2008@server-1>
2002-01-28 10:59 ` Patrick Gundlach [this message]
2002-01-28 12:01 ` suggestion Hans Hagen
2002-01-28 20:11 ` Re[2]: suggestion Giuseppe Bilotta
2002-01-28 12:33 ` suggestion Hans Hagen
2002-01-28 12:40 ` suggestion Taco Hoekwater
2002-01-28 12:48 ` suggestion Eckhart Guthöhrlein
2002-01-28 13:02 ` suggestion Eckhart Guthöhrlein
2002-01-28 13:44 ` suggestion Hans Hagen
2002-01-28 21:28 ` suggestion Daniel Pittman
2009-06-15 11:55 Suggestion Arun Dev
2009-06-16 7:42 ` Suggestion R. Bastian
2009-06-16 7:50 ` Suggestion Taco Hoekwater
2009-06-19 3:55 ` Suggestion Yue Wang
2009-06-19 6:29 ` Suggestion luigi scarso
2009-06-19 7:06 ` Suggestion Yue Wang
2009-06-19 7:33 ` Suggestion luigi scarso
2009-06-19 9:23 ` Suggestion Arthur Reutenauer
-- strict thread matches above, loose matches on Subject: below --
2002-01-25 13:07 suggestion Hans Hagen
2002-01-25 14:23 ` suggestion Berend de Boer
2002-01-25 18:03 ` suggestion Frans Goddijn
2002-01-25 18:36 ` suggestion Eckhart Guthöhrlein
2002-01-25 18:46 ` suggestion Frans Goddijn
2002-01-27 18:02 ` suggestion Hans Hagen
2002-01-25 22:47 ` suggestion Daniel Pittman
2000-11-03 23:06 suggestion Denis B. Roegel
1999-06-01 19:04 Suggestion David Arnold
1999-06-02 7:22 ` Suggestion Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200201281059.g0SAxRf26692@sol.cs.uni-dortmund.de \
--to=gundlach@irb.cs.uni-dortmund.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).