From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [Emacs] request: better subject lines
Date: Tue, 2 May 2017 12:38:03 -0600 [thread overview]
Message-ID: <20170502113113016584796@bob.proulx.com> (raw)
In-Reply-To: <012b2d17-acf4-28d5-2650-59ac6db6b611@mousecar.com>
Oh boy! Another subject line tag debate. Again. What is even better
is that it can never be off topic for any mailing list because every
mailing list has a subject line. Therefore this debate is doomed to
happen again and again on every mailing list. Just like quoting
styles. Sigh.
ken wrote:
> I've heard all these arguments/instructions before. They are neither
> comforting nor persuasive.
I have as well. On both sides. In the end I have decided there is no
way to appease everyone. Because people like what they like and each
person likes different things. People work using work flows that are
different and will not change those work flows to the other people's
work flows. Therefore what we end up with are camps of people who
tolerate the diversity of the other camp.
> Also, I've been managing five mailing lists for about ten years, all
> of which have [mailing-list-name] descriptors (and many more other
> mailing lists earlier for fewer numbers of years), and absolutely
> *no one* /ever/ complained, or even mentioned anything, about those
> descriptors.
I find that exceedingly difficult to believe. In fact the possibility
is vanishingly small. Because for example let me complain about those
tags right here and now! Which means you cannot make that claim in
the future moving forward from this point. Because I have now
complained about them. You will never be able to make that claim in
the future or someone will be able to point to this message and show
my complaint. :-)
I have been administering mailing lists for decades and I have been
reading complaints about both the presence and absence of subject line
tags since well before then. The one universal constant is that
people will complain. About everything possible. What color do we
paint the bike shed?
>...
> There are still people today who are new to mailing lists. There always
> will be. Those are the people I am relating to, people who have a problem
> or question, are told to join this or that mailing list, somehow manage to
> find one, wade through the steps to subscribe, aren't sure they're
> subscribed, not even sure what "subscribed" means, then eventually
> (hopefully) find "it's working" for them (sort of)...
That proposal is a race to the bottom. If anyone needs to learn
something then no one can. I reject the idea that we all must move to
the lowest common denominator.
Instead I think we should embrace the diversity of it. For example
there have been proponents for an emacs topic web Q&A site such as
stack exchange, stack overflow, and so forth. (I forget the details
now.) For newcomers that is even more accessible than mailing lists
because one need only know how to browse the web to access it. And so
forth. Maybe a GNU Social or Disaspora group?
> then someone on that list gives them further instructions on
> properly managing their mail. Yes, it's probably no big deal for
> many here to set up and manage mail filters, and they're quite proud
> they can, and so expect everyone to do the same. The fact is, not
> everyone can... not everyone wants to bother.
I think there is a huge value in the community coming together to help
educate, train, help out, lift up people who are coming to the
community. It takes a whole village to raise a child. I think that
is one of the best parts of our communities. We join together help
each other out. We build schools. We educate. We train. An
educated person is more help and benefit to the community. I do not
believe that avoiding the need for education, to enable existence
without education, is a good direction for any community.
> Third, let's put the responsibility shoe on the other foot. Why don't we
> put the descriptors into all list mail and those who don't want them can set
> up filters on their systems to take them out?
That symmetrical argument is reversible. Let's remove all tags from
all mailing lists and the people who want them can add them. Same
thing in reverse. Equally valid.
Bob
next prev parent reply other threads:[~2017-05-02 18:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 15:39 [GNU-Emacs] request: better subject lines Carlos Konstanski
2017-04-30 16:38 ` Óscar Fuentes
2017-04-30 17:15 ` allan gottlieb
2017-05-01 3:03 ` Emanuel Berg
2017-05-02 12:52 ` [Emacs] " ken
2017-05-02 13:41 ` tomas
2017-05-02 15:12 ` Danny YUE
2017-05-03 8:49 ` tomas
2017-05-03 9:49 ` Danny YUE
2017-05-03 10:26 ` tomas
2017-05-02 17:05 ` ken
2017-05-02 17:32 ` hector
2017-05-02 18:38 ` Bob Proulx [this message]
2017-05-03 8:56 ` tomas
2017-05-02 14:34 ` Harry Putnam
2017-05-02 19:04 ` Emanuel Berg
2017-05-02 20:43 ` [GNU-Emacs] " Bob Proulx
2017-05-03 0:57 ` Emanuel Berg
2017-05-03 5:10 ` Bob Proulx
2017-05-03 12:38 ` Óscar Fuentes
2017-05-03 20:12 ` Emanuel Berg
2017-05-03 23:25 ` Nick Dokos
2017-05-04 1:34 ` Emanuel Berg
2017-05-04 17:02 ` Nick Dokos
2017-05-04 18:29 ` Emanuel Berg
2017-05-04 5:26 ` Marcin Borkowski
2017-05-04 6:55 ` Emanuel Berg
2017-05-04 6:59 ` Emanuel Berg
2017-05-04 2:01 ` Emanuel Berg
2017-05-03 2:34 ` allan gottlieb
2017-05-04 15:40 ` Emanuel Berg
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=20170502113113016584796@bob.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).