edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] list rules and etiquette
Date: Sun, 27 Apr 2014 06:00:39 -0700	[thread overview]
Message-ID: <877g6budu0.fsf@mushroom.PK5001Z> (raw)

Here's my statement of rules, since I'm the list owner.  It's mostly
common-sense stuff.  If Karl disagrees with any of this, I'm glad to
defer to his judgment.

  The main thing to keep in mind is that this is a
public list.  The archives are searchable via gmane.  So keep it legal!
Don't post anything potentially embarrassing.
Think and look before uploading that debugging output, since it may contain
sensitive info!

As for topics, if it's the least bit related to edbrowse,
it's fine with me.  As the list owner, I generally won't harass folks
about staying on-topic.  When deciding whether something is appropriate
for the list, here's a principle to keep in mind.  The other participants'
time is valuable.  Think in terms of other people, and you probably
won't go wrong.

Keep discourse civil.  I'm just adding this one for completeness.

-- Chris

                 reply	other threads:[~2014-04-27 13:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=877g6budu0.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=edbrowse-dev@lists.the-brannons.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.
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).