From: Ihor Radchenko <yantar92@posteo.net>
To: Richard Stallman <rms@gnu.org>
Cc: luangruo@yahoo.com, Gregory Heytings <gregory@heytings.org>,
stefankangas@gmail.com, 61325@debbugs.gnu.org
Subject: bug#61325: 30.0.50; Jokes in GNUS manual
Date: Tue, 07 Mar 2023 13:48:17 +0000 [thread overview]
Message-ID: <87cz5kfza6.fsf@localhost> (raw)
In-Reply-To: <E1pUgqq-0000zZ-29@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> I think that when I wrote the Kind Communication Guidelines, I was
> thinking about discussions (like this one). It asks people to try to
> avoid offending anyone else in the discussion. That is a limited set
> of people to be considerate of.
Good point. I agree that it is meaningless if we aim to cater every
possible potential reader of the manual.
> When the same points are applied to a book, which is published, there
> is a problem: anyone might read the book. So it can be interpreted as
> saying that the author should make sure not to offend anyone
> whosoever. That implies that every demand for censorship should be
> catered to.
>
> That is not a good outcome, and not what I intended.
>
> It looks like I will have to think more about this.
I am re-reading the GNU-provided information for maintainers on jokes
(https://www.gnu.org/prep/maintain/maintain.html#Humor) and I note the
following paragraph:
There are people who frown on anything that is slightly risqué or
controversial, including jokes. It would be a terrible shame for
that attitude to prevail, so our policy is that the occasional
risqué joke is ok. GNU is a 21st century project, not a 19th.
AFAIU, this implies that even occasional jokes about controversial or
culturally-sensitive topics, like sex should be OK to have.
The problem with Gnus manual though is that the number of jokes in it is
huge. And it appears that jokes involving sensitive topics are not
occasional.
So far, the discussion on this thread revolved around all-or-nothing
approach with people often treating this bug report as either a demand
to remove all the jokes or a demand to remove all the sensitive jokes.
Originally, I was aiming to handle only the jokes I listed with an idea
in mind to apply the same approach for all other sensitive jokes.
From my current understanding of the "14 Humor and GNU" section, it will
be incorrect to try removing every single "risky" joke. Though I do not
see why replacing the risky topics with more neutral would hurt,
given that the quality of a joke being changed does not degrade.
What is not clear for me is the word "occasional". How many jokes are
considered occasional? I think that it is something worth clarifying in
https://www.gnu.org/prep/maintain/maintain.html#Humor
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-03-07 13:48 UTC|newest]
Thread overview: 136+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 16:01 bug#61325: 30.0.50; Jokes in GNUS manual Ihor Radchenko
2023-02-06 16:20 ` dick
2023-02-12 6:11 ` Jean Louis
2023-02-06 16:27 ` Eli Zaretskii
2023-02-06 16:38 ` Ihor Radchenko
2023-02-06 16:42 ` Ihor Radchenko
2023-02-06 16:51 ` Eli Zaretskii
2023-02-06 17:04 ` Ihor Radchenko
2023-02-18 13:59 ` Petteri Hintsanen
2023-02-19 10:43 ` Ihor Radchenko
2023-02-20 5:18 ` Richard Stallman
2023-02-06 17:23 ` Pankaj Jangid
2023-02-06 17:49 ` Ihor Radchenko
2023-02-06 18:37 ` Pankaj Jangid
2023-02-06 18:45 ` Ihor Radchenko
2023-02-07 2:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 11:24 ` Ihor Radchenko
2023-02-07 12:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 13:01 ` Ihor Radchenko
2023-02-07 14:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 14:43 ` Ihor Radchenko
2023-02-07 15:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 16:15 ` Ihor Radchenko
2023-02-08 1:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 11:40 ` Ihor Radchenko
2023-02-08 11:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 11:59 ` Ihor Radchenko
2023-02-08 12:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-15 14:55 ` Ihor Radchenko
2023-02-16 1:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-17 12:25 ` Ihor Radchenko
2023-02-18 4:19 ` Richard Stallman
2023-02-18 11:14 ` Ihor Radchenko
2023-02-20 5:19 ` Richard Stallman
2023-02-22 13:43 ` Eli Zaretskii
2023-02-25 4:09 ` Richard Stallman
2023-02-08 12:36 ` Eli Zaretskii
2023-02-12 6:38 ` Jean Louis
2023-02-09 4:28 ` Richard Stallman
2023-02-07 19:45 ` Pankaj Jangid
2023-02-07 19:56 ` Ihor Radchenko
2023-02-09 4:28 ` Richard Stallman
2023-02-07 14:15 ` dick
2023-02-07 15:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 15:17 ` Eli Zaretskii
2023-02-08 8:11 ` Michael Albinus
2023-02-08 12:31 ` Eli Zaretskii
2023-02-08 12:59 ` Michael Albinus
2023-02-07 15:41 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 4:28 ` Richard Stallman
2023-02-09 16:44 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 4:03 ` Richard Stallman
2023-02-08 4:31 ` Richard Stallman
2023-02-08 4:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 6:46 ` Jean Louis
2023-02-15 14:47 ` Ihor Radchenko
2023-02-16 1:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-17 12:38 ` Ihor Radchenko
2023-02-17 5:22 ` Jean Louis
2023-02-19 4:50 ` Richard Stallman
2023-02-19 5:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 4:33 ` Richard Stallman
2023-02-22 6:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-26 2:59 ` Richard Stallman
2023-02-08 13:06 ` dick
2023-02-08 15:35 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 16:06 ` dick
2023-02-15 14:37 ` Ihor Radchenko
2023-02-16 1:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-17 12:49 ` Ihor Radchenko
2023-02-19 4:50 ` Richard Stallman
2023-02-19 10:36 ` Ihor Radchenko
2023-02-19 11:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 11:13 ` Eli Zaretskii
2023-02-20 11:50 ` Ihor Radchenko
2023-02-20 12:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 13:29 ` Ihor Radchenko
2023-03-07 20:02 ` No Wayman
2023-03-07 20:12 ` Eli Zaretskii
2023-02-19 12:24 ` Stefan Kangas
2023-02-19 13:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 13:45 ` Stefan Kangas
2023-02-20 18:29 ` Gregory Heytings
2023-02-21 2:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 4:34 ` Richard Stallman
2023-02-22 4:35 ` Richard Stallman
2023-03-07 13:48 ` Ihor Radchenko [this message]
2023-03-08 0:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08 14:05 ` Ihor Radchenko
2023-03-09 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 4:25 ` Richard Stallman
2023-03-10 7:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-09 4:28 ` Richard Stallman
2023-03-08 5:34 ` Jean Louis
2023-03-08 14:13 ` Ihor Radchenko
2023-03-09 1:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-13 14:50 ` Jean Louis
2023-03-09 4:26 ` Richard Stallman
2023-03-10 11:33 ` Ihor Radchenko
2023-03-10 11:34 ` Ihor Radchenko
2023-03-10 12:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 12:37 ` Eli Zaretskii
2023-03-10 12:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-13 15:01 ` Jean Louis
2023-02-19 15:56 ` Drew Adams
2023-02-20 12:00 ` Ihor Radchenko
2023-02-20 12:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 14:28 ` Michael Albinus
2023-02-20 14:34 ` Ihor Radchenko
2023-02-20 17:01 ` Drew Adams
2023-02-20 11:55 ` Ihor Radchenko
2023-02-27 3:26 ` Richard Stallman
2023-02-19 5:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 4:19 ` Richard Stallman
2023-02-19 10:25 ` Ihor Radchenko
2023-02-15 15:34 ` Stefan Kangas
2023-02-15 16:00 ` Robert Pluim
2023-02-18 4:19 ` Richard Stallman
2023-02-17 5:24 ` Jean Louis
2023-02-19 4:50 ` Richard Stallman
2023-02-08 13:42 ` Visuwesh
2023-02-12 6:56 ` Jean Louis
2023-02-12 6:32 ` Jean Louis
2023-02-14 4:51 ` Richard Stallman
2023-02-14 11:17 ` Jean Louis
2023-03-09 4:05 ` Sam James
2023-03-09 14:10 ` Dmitry Gutov
2023-03-09 14:17 ` Robert Pluim
2023-03-09 16:57 ` Dmitry Gutov
2023-03-09 17:06 ` Robert Pluim
2023-03-09 20:10 ` Jose A. Ortega Ruiz
2023-03-10 10:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-13 15:05 ` Jean Louis
2023-09-06 6:53 ` Stefan Kangas
2023-09-06 7:10 ` Ihor Radchenko
2023-09-06 7:30 ` Stefan Kangas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz5kfza6.fsf@localhost \
--to=yantar92@posteo.net \
--cc=61325@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).