From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Title page for book latex export Date: Wed, 20 Oct 2010 00:11:15 -0400 Message-ID: <13071.1287547875@gamaville.dokosmarshall.org> References: <19644.5557.627178.686601@goeland.ups-tlse.fr> <9312871.193.1287423634931.JavaMail.root@zm-cesbio-01> <19644.43988.128890.607963@goeland.ups-tlse.fr> <28722569.197.1287437982941.JavaMail.root@zm-cesbio-01> <19645.14060.654947.268170@goeland.ups-tlse.fr> <21835.1287497077@gamaville.dokosmarshall.org> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=49942 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P8Q1W-00005A-Ol for emacs-orgmode@gnu.org; Wed, 20 Oct 2010 00:11:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P8Q1V-0001q6-B2 for emacs-orgmode@gnu.org; Wed, 20 Oct 2010 00:11:34 -0400 Received: from vms173017pub.verizon.net ([206.46.173.17]:55362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P8Q1V-0001pv-6L for emacs-orgmode@gnu.org; Wed, 20 Oct 2010 00:11:33 -0400 Received: from gamaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173017.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LAK007H0MASF830@vms173017.mailsrvcs.net> for emacs-orgmode@gnu.org; Tue, 19 Oct 2010 23:11:16 -0500 (CDT) In-reply-to: Message from Jeff Horn of "Tue\, 19 Oct 2010 22\:33\:34 EDT." List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jeff Horn Cc: Jordi Inglada , nicholas.dokos@hp.com, emacs-orgmode@gnu.org Jeff Horn 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. >=20 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: ...=20=20 o you can submit bug reports =E2=80=93 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