From: Randy Yates <yates@digitalsignallabs.com>
To: sourcemaster@sourceware.org, crossgcc@sourceware.org
Subject: Sourceware.Org Mailing Lists 20200830192428
Date: Sun, 30 Aug 2020 20:31:32 -0400 [thread overview]
Message-ID: <87zh6b8xln.fsf@digitalsignallabs.com> (raw)
This email refers to the mailing lists associated with https://sourceware.org/lists.html .
On the page "Suggestions" it is stated:
So, if, for some reason, there is an impediment to your using this site,
whether psychological, moral, technical, or political, please let us know.
I assume I am addressing Christopher Faylor. I take issue with your statement which
was sent out to the crossgcc mailing list this evening:
Subject:
Unsubscribe problems apparently solved
From:
Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
Date:
8/30/20, 4:19 PM
To: crossgcc@sourceware.org
Hi all,
The two people for whom the unsubscribe instructions "did not work"
apparently managed to follow the instructions and unsubscribe.
Sorry for the noise. You'd think that a technical mailing list wouldn't
have these types of problems.
Btw, the name of this mailing list is "crossgcc". I don't know why
something is adding "crosstool-ng" to the subject but it's not being
done by sourceware.org.
cgf
(20 year sourceware.org volunteer admin)
--
For unsubscribe information see http://sourceware.org/lists.html#faq
The tenor of your message (e.g., `noise" and "these types of problems") implies we
are idiots. I am a degreed electrical engineer and mathematician and have engineered
hardware, systems, and software for some 40 years now (see https://www.linkedin.com/in/yatescr/ ).
I submit that these problems are due to several bad server implementation decisions
and poor site design in the web interface layout and text:
1. It is at least an unwritten rule in mailing list organization that all "shotgunned"
messages include a prefix in the subject indicating the mailing list, e.g., [yocto-
developer], [bacnet], [crossgcc], etc. However, the crossgcc mailing list does
not. This should be corrected.
1
\f
2. Why is the crossgcc list being used for crosstools-ng discussions? Why not
have a separate list? crossgcc is only one of a number of utilities (binutils
being another) which are commonly used for cross-platform development.
3. The sourceware.org mailing lists FAQ is poorly laid out. It does not flow well.
(a) The order of the topics are not ordered by the most likely topics list
subscribers want to address.
(b) There is a block of information at the beginning (prior to the table of
contents) that diverts the user's attention. It would be better placed in
table of contents.
(c) There is unwanted humor which must be ignored when attempting to
find useful information.
(d) The unsubscription link at the top is idempotent.
(e) There are links which don't lead anywhere.
4. At the bottom of each shotgunned message is a footer/.sig:
--
For unsubscribe information see http://sourceware.org/lists.html#faq
That link simply leads you to the FAQ which is very general. It is for three
different mail list servers, and a multitude of lists on each.
This requires the user to drill down to the proper topic (unsubscribing), mail
list server (sourceware.org), and mailing list (crossgcc) before they can actu-
ally get to the meat of the unsubscription mechanism.
Instead, the mail server could greatly simplify unsubscribing by generating a
custom link for the server and list directly into the footer: https://sourceware.org/mailman/listinfo/crossgcc *
* .
----Randy Yates
2
Randy Yates, DSP/Embedded Firmware Developer
Digital Signal Labs
http://www.digitalsignallabs.com
next reply other threads:[~2020-08-31 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 0:31 Randy Yates [this message]
2020-08-31 0:47 ` Bryan Hundven
2020-08-31 4:06 ` Christopher Faylor
2020-08-31 4:19 ` Chris Punches
2020-08-31 4:35 ` Chris Punches
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=87zh6b8xln.fsf@digitalsignallabs.com \
--to=yates@digitalsignallabs.com \
--cc=crossgcc@sourceware.org \
--cc=sourcemaster@sourceware.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).