emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jay Kerns <gjkernsysu@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: posting guide?
Date: Wed, 13 Mar 2013 17:07:08 -0400	[thread overview]
Message-ID: <CAFiLVrbCNHRXjBpLNNFug18m3cKxY1eNdOdS_8tsH=isDHy8SQ@mail.gmail.com> (raw)
In-Reply-To: <87y5drjazp.fsf@bzg.ath.cx>

Dear Bastien,


On Wed, Mar 13, 2013 at 4:33 PM, Bastien <bzg@altern.org> wrote:
> Hi Jay,

> Well, I would not invest too much time on this, personally.

No, you don't seem to be bothered at all; those attacks seem to
wash off you like water off a duck's back, or scandals off of Bill
Clinton's resume.  ;-)

> From experience, such a drafting process takes a lot of time.  And at
> the end, you're not always sure that the whole community comes: to an
> agreement... only the ones who care, who are obviously not the ones
> the guidelines want to reach.


Drafting takes about five seconds. In fact, let me do one right now:

"Please note that messages to the emacs-orgmode list are expected
to be civil and focused toward our mutual interest of Org
mode. /Ad hominem/ or other attacks of a personal nature will not
be tolerated by the community."

Any strenuous objections?


> Why not trying another approach and have a hall of fame for great
> posts sent on this lists?  Examples of good/thorough explanations,
> example of detailed bug reports, etc.  It would be both encouraging
> and educating, maybe.
>
> What do you think?
>


I think that's a great idea!, actually.  My mental catalogue of
excellent posts probably isn't as extensive as yours, but even
just last night I got a great response that fits a Hall of Fame
in my book. Surely there must be other people who got a great
response to some question they asked at some point in their past.

-- 
Jay

  reply	other threads:[~2013-03-13 21:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 19:13 posting guide? Jay Kerns
2013-03-13 19:21 ` Ista Zahn
2013-03-13 19:59 ` Andreas Röhler
2013-03-13 20:31   ` Jay Kerns
2013-03-13 21:56     ` François Pinard
2013-03-13 20:33 ` Bastien
2013-03-13 21:07   ` Jay Kerns [this message]
2013-03-13 22:50     ` Bastien
2013-03-14  0:34       ` Robert Horn
2013-03-14  0:54         ` Thorsten Jolitz
2013-03-14  2:36         ` Jay Kerns
2013-03-14  2:59           ` Bastien
2013-03-14 13:17             ` Rainer M Krug
2013-03-14 14:59     ` Carsten Dominik
2013-03-14 16:02       ` Memnon Anon
2013-03-14 19:12         ` Bernt Hansen
2013-03-14 19:41           ` Jay Kerns
2013-03-14 19:53             ` Jay Kerns
2013-03-14 21:56               ` Carsten Dominik
2013-03-13 22:16 ` Thomas S. Dye
2013-03-13 22:44   ` Jay Kerns
2013-03-13 22:48   ` Bastien
2013-03-14  0:33 ` James Harkins

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFiLVrbCNHRXjBpLNNFug18m3cKxY1eNdOdS_8tsH=isDHy8SQ@mail.gmail.com' \
    --to=gjkernsysu@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).