From: Nick Dokos <nicholas.dokos@hp.com>
To: Jeff Horn <jrhorn424@gmail.com>
Cc: Jordi Inglada <jordi.inglada@cesbio.cnes.fr>,
nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Title page for book latex export
Date: Wed, 20 Oct 2010 00:11:15 -0400 [thread overview]
Message-ID: <13071.1287547875@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Jeff Horn <jrhorn424@gmail.com> of "Tue\, 19 Oct 2010 22\:33\:34 EDT." <AANLkTimucZYrP1C2PhmrQdO8Peukz6Mj8THzgwY=3vQf@mail.gmail.com>
Jeff Horn <jrhorn424@gmail.com> wrote:
> Reading the list for a short while before posting, it became fairly
> obvious to me what was expected in order to receive help. But, since
> posting a rant to the mail list only informs people who read the list
> of your displeasure, and given that the group most likely to benefit
> from your advice are new list members, it might behoove us to post a
> clear(er) list of expectations on the org-mode site when we introduce
> potential users to the list.
>
You are right that only the current members get to see the rant. I can
save it and repost it at appropriate times in the future.
Just kidding.
There is a fairly clear list of expectations in section 1.4, Feedback,
of the Org manual. And the "How to contribute" page on Worg
(http://orgmode.org/worg/org-contribute.php) contains the admonition:
...
o you can submit bug reports – Before sending a bug report, make
sure you have read this section of Org's manual: Feedback
...
Perhaps people asking questions don't think of them as bug reports, but
they are: if one cannot find a way to do something, it's a bug: it may
be a code bug or a documentation bug - or it may be a user bug. But to
figure out which it is, we need information: relevant information to be
sure, but complete information as well - as complete as possible.
There are also many, many guides on the web on how to ask questions
(e.g. http://www.catb.org/esr/faqs/smart-questions.html). But when push
comes to shove, all of that seems to go out the window - at least
sometimes. The point is that all of us have asked questions badly and
all of us will do it again, no matter what.
I overdid the rant (and didn't put any smilies in there), so it came
across too harsh, which was not my intention, but apart from that, an
occasional rant on the list can serve as a useful reminder about these
expectations.
But if you have ideas on how to make us all ask smarter questions, I for
one, am all ears.
Nick
PS. BTW, my favorite example of a "minimal example" was something that
Bernt Hansen posted a little more than a year ago: an obscure bug that
had plagued Org for a while and that was very tricky to reproduce.
Bernt came up with a method that involved a minimal .emacs and an .org
file and more than a dozen steps - but it was a consistent reproducer of
the bug and Carsten had it fixed in no time: a textbook case of an
exemplary bug report and an ideal to aspire to!
See the thread starting at
http://thread.gmane.org/gmane.emacs.orgmode/16970
next prev parent reply other threads:[~2010-10-20 4:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 9:39 Title page for book latex export Jordi Inglada
2010-10-18 17:44 ` Jeff Horn
[not found] ` <9312871.193.1287423634931.JavaMail.root@zm-cesbio-01>
2010-10-18 20:19 ` Jordi Inglada
2010-10-18 21:43 ` Nick Dokos
2010-10-19 6:18 ` Carsten Dominik
[not found] ` <28722569.197.1287437982941.JavaMail.root@zm-cesbio-01>
2010-10-19 6:13 ` Jordi Inglada
2010-10-19 14:04 ` Nick Dokos
2010-10-20 2:33 ` Jeff Horn
2010-10-20 4:11 ` Nick Dokos [this message]
[not found] ` <AANLkTiks0Om7sdkFfiR5CiJncixhD5AKE2htZcexKLcW@mail.gmail.com>
2010-10-20 4:49 ` Jeff Horn
2010-10-20 5:05 ` Jambunathan K
2010-10-27 22:28 ` Bastien
2010-10-28 9:00 ` Jeff Horn
[not found] ` <493995.8239.1287496847211.JavaMail.root@zm-cesbio-01>
2010-10-19 14:36 ` Jordi Inglada
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=13071.1287547875@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jordi.inglada@cesbio.cnes.fr \
--cc=jrhorn424@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.