From: "Dr. Tom McKellips" <tom@computechnology.net>
To: libreplanet-discuss@libreplanet.org
Subject: Re: on libreplanet-discuss moderation, and topics going forward
Date: Tue, 17 Sep 2019 08:53:13 -0500 [thread overview]
Message-ID: <4eae1f36-c065-247d-9832-e3fa8b5baeb1@computechnology.net> (raw)
In-Reply-To: <75r24fqcj3.fsf@freestation10.office.fsf.org>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
Hello Greg and everyone else,
i would like to share a lesson from all of this, that I so often shared
with my students while teaching at a local college.
When speaking in any public forum, news media, social media, etc. stick
to your area of expertise. Stay away from statements that will draw you
out into another area. Do not offer opinions that have nothing to do
with your core focus. What has happened here with RMS is just another of
many examples of this. I have been in the news many times over my career
and many times recently, but I learned many years ago, stick to my area
of expertise and don't let the interviewer take me another direction and
don't offer opinions outside of my core focus area.
This being said I will offer some advice not only to the FSF but
everyone on this list as I did my students.
1. Stay professional and think before you speak (or write).
2. Stay on course to your core expertise.
3. Don't offer your opinion on topics outside of your core expertise.
4. Try to keep a positive or neutral spin on your discussion. Even in
the face of true tragedy something positive can come of it to say. I am
a live example of this because I took a violent death and created
something positive from it, so the person which died is not in vain.
--
Dr. Tom McKellips, RODC
On 9/17/19 8:26 AM, Greg Farough wrote:
> Hi, everyone,
>
> This is a difficult time for all of us. We believe that it's important
> to give our supporters room to express their feelings on current events
> in our community, and so we have given libreplanet-discuss a little more
> moderation leeway than usual.
>
> Still, please keep your comments reserved to how we can move forward as
> a movement, and refrain from personal attacks against other members of
> the mailing list. This is also not the venue to be engaging in ethical
> debates other than those directly relating to free software.
>
> All the best,
> -Greg
>
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2509 bytes --]
[-- Attachment #3: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
prev parent reply other threads:[~2019-09-17 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 13:26 on libreplanet-discuss moderation, and topics going forward Greg Farough
2019-09-17 13:53 ` Dr. Tom McKellips [this message]
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4eae1f36-c065-247d-9832-e3fa8b5baeb1@computechnology.net \
--to=tom@computechnology.net \
--cc=libreplanet-discuss@libreplanet.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 read-only IMAP folder(s) and NNTP newsgroup(s).