From: Thibaut Verron <thibaut.verron@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel <emacs-devel@gnu.org>, Richard Stallman <rms@gnu.org>,
"Nicolas P. Rougier" <nicolas.rougier@inria.fr>
Subject: Re: [ELPA] New package: splash-screen
Date: Sun, 27 Sep 2020 12:34:44 +0200 [thread overview]
Message-ID: <CAFsi02T4b70PBCW8_+c2vn8jZs-A_Z1tPN=Z2m_b9poLS-+77A@mail.gmail.com> (raw)
In-Reply-To: <83pn67o7hh.fsf@gnu.org>
> > I don't agree that it's a tangent. Emacs shows it "first thing you
> > see", in all caps. Other software require either clicking one's way to
> > the EULA, or requesting this info with --version.
>
> Some software does what you describe. Others display the EULA
> _first_, and won't even let you see the real program's display until
> and unless you click on "agree". (Still others are even nastier: they
> show in small print, or momentarily display, something to the effect
> that "by using this you agree to ...".)
For the record, I was only looking at examples within free software.
It is my impression that most non-free software show and request
approval of the EULA at the time of installing.
Of course, I agree that we should not take non-free software's example
seriously. The question is not whether we should deceive the users (we
shouldn't), it's whether showing this information so prominently to
users who are not asking for it is necessary.
> > And software which display it outside of a terminal tend to follow
> > standard typographical practices when doing so. (Yes, bold is also
> > discouraged as a marker of emphasis, but it is very commonly used for
> > that purpose.)
>
> I see all-caps in GUI applications as well.
Assuming that you mean free software, do you have examples?
> Sure, why not? But let's not maintain the position that Emacs is the
> odd one out here; it's not.
It might not be alone (Screen is another example), but so far it seems
far from being a majority. Even more so if we restrict to GUI
applications.
A lot of the discussion so far has been whether it is worth it to ask
the FSF's counsel for updated advice, valid in the ecosystem and legal
environment of 2020.
If we deny the fact that several major free software organizations
have chosen to display the warranty disclaimer only in their EULA, and
(pending on examples) with friendlier typography than all-caps, yes,
there is indeed little reason for asking for that update.
next prev parent reply other threads:[~2020-09-27 10:34 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:35 [ELPA] New package: splash-screen Nicolas P. Rougier
2020-09-20 11:24 ` Colin Baxter
2020-09-20 12:36 ` Nicolas P. Rougier
2020-09-20 13:34 ` Colin Baxter
2020-09-20 13:16 ` Stefan Monnier
2020-09-20 14:50 ` Nicolas P. Rougier
2020-09-20 17:50 ` Stefan Monnier
2020-09-20 20:33 ` Nicolas P. Rougier
2020-09-20 22:22 ` Stefan Monnier
2020-09-21 3:50 ` Richard Stallman
2020-09-21 5:47 ` Alfred M. Szmidt
2020-09-21 6:06 ` Nicolas P. Rougier
2020-09-21 11:09 ` Philip K.
2020-09-21 11:42 ` Nicolas P. Rougier
2020-09-21 15:24 ` Philip K.
2020-09-21 16:40 ` Philip K.
2020-09-21 17:22 ` Nicolas P. Rougier
2020-09-21 11:53 ` Alfred M. Szmidt
2020-09-21 12:29 ` Nicolas P. Rougier
2020-09-21 13:27 ` Stefan Monnier
2020-09-21 13:45 ` Thibaut Verron
2020-09-20 19:20 ` Juri Linkov
2020-09-20 20:53 ` Nicolas P. Rougier
2020-09-20 19:58 ` Lars Ingebrigtsen
2020-09-21 3:49 ` Richard Stallman
2020-09-22 12:59 ` Lars Ingebrigtsen
2020-09-23 3:42 ` Richard Stallman
2020-09-23 3:59 ` Stefan Monnier
2020-09-23 8:03 ` Mathias Dahl
2020-09-24 1:31 ` Richard Stallman
2020-09-24 6:17 ` Nicolas P. Rougier
2020-09-25 4:39 ` Richard Stallman
2020-09-23 12:36 ` Lars Ingebrigtsen
2020-09-23 16:21 ` Alfred M. Szmidt
2020-09-23 16:36 ` Nicolas P. Rougier
2020-09-24 1:32 ` Richard Stallman
2020-09-24 2:14 ` Stefan Monnier
2020-09-24 13:36 ` Lars Ingebrigtsen
2020-09-25 4:38 ` Richard Stallman
2020-09-25 10:04 ` Lars Ingebrigtsen
2020-09-25 11:26 ` Thibaut Verron
2020-09-26 4:37 ` Richard Stallman
2020-09-26 13:43 ` Lars Ingebrigtsen
2020-09-27 2:43 ` Richard Stallman
2020-09-27 8:54 ` Thibaut Verron
2020-09-27 9:42 ` Eli Zaretskii
2020-09-27 9:56 ` Thibaut Verron
2020-09-27 10:10 ` Eli Zaretskii
2020-09-27 10:34 ` Thibaut Verron [this message]
2020-09-27 10:50 ` Eli Zaretskii
2020-09-27 11:24 ` Thibaut Verron
2020-09-27 11:52 ` Lars Ingebrigtsen
2020-09-27 13:32 ` Jean Louis
2020-09-27 16:08 ` Stefan Monnier
2020-09-28 3:43 ` Richard Stallman
2020-09-28 11:56 ` Lars Ingebrigtsen
2020-09-28 14:02 ` Alfred M. Szmidt
2020-09-26 8:28 ` Dmitry Gutov
2020-09-26 9:45 ` Alfred M. Szmidt
2020-09-26 9:51 ` Eli Zaretskii
2020-09-26 14:34 ` Drew Adams
2020-09-27 2:45 ` Richard Stallman
2020-09-27 8:34 ` Dmitry Gutov
2020-09-27 8:52 ` Alfred M. Szmidt
2020-09-27 8:56 ` Thibaut Verron
2020-09-27 9:47 ` Eli Zaretskii
2020-09-27 10:03 ` Dmitry Gutov
2020-09-27 10:42 ` Nicolas P. Rougier
2020-09-27 14:03 ` Alfred M. Szmidt
2020-09-28 3:42 ` Richard Stallman
2020-09-28 6:29 ` Nicolas P. Rougier
2020-09-29 3:32 ` Richard Stallman
2020-09-27 14:23 ` Alfred M. Szmidt
2020-09-27 16:20 ` Stefan Monnier
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='CAFsi02T4b70PBCW8_+c2vn8jZs-A_Z1tPN=Z2m_b9poLS-+77A@mail.gmail.com' \
--to=thibaut.verron@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=nicolas.rougier@inria.fr \
--cc=rms@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.
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).