From: Don Saklad <dsaklad@gnu.org>
Subject: How to resolve complaints or threatening.
Date: Tue, 17 Sep 2002 14:54:53 GMT [thread overview]
Message-ID: <68sn08is3n.fsf@fencepost.gnu.org> (raw)
Guarding against
a. lack of due process and
b. preemptory allegation
how would you folks look into a complaint of abuse involving the
news group gnu.emacs.gnus ?...
I've received a complaint and threat of abuse. One way to go might be
resolving matters using such processes advocted for example by
http://pon.harvard.edu/outreach/drf/index.php3
http://pon.harvard.edu
I remain, as always, advocating better and more open negotiatory
strategies for resolving differences among GNU/Linux advocates!
cordially,
oo__ don Warner saklad
dsaklad@gnu.org
next reply other threads:[~2002-09-17 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 14:54 Don Saklad [this message]
[not found] ` <d6rctvth.fsf@hschmi22.userfqdn.rz-online.de>
2002-09-17 19:22 ` Lute Kamstra
[not found] ` <68it14mces.fsf@fencepost.gnu.org>
2002-09-18 3:43 ` Luke A. Olbrish
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=68sn08is3n.fsf@fencepost.gnu.org \
--to=dsaklad@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.
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).