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 13:24:36 +0200 [thread overview]
Message-ID: <CAFsi02TEKbPTM=w4veU5H-VeexL-oYXf_JLG1JjR+6LwJox+ew@mail.gmail.com> (raw)
In-Reply-To: <83mu1bo5ng.fsf@gnu.org>
Le dim. 27 sept. 2020 à 12:50, Eli Zaretskii <eliz@gnu.org> a écrit :
>
> > From: Thibaut Verron <thibaut.verron@gmail.com>
> > Date: Sun, 27 Sep 2020 12:34:44 +0200
> > Cc: Richard Stallman <rms@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
> > "Nicolas P. Rougier" <nicolas.rougier@inria.fr>, emacs-devel <emacs-devel@gnu.org>
> >
> > Of course, I agree that we should not take non-free software's example
> > seriously.
>
> I don't think this distinction is relevant when talking about legal
> issues. The GPL is not a revolt against the copyright laws, it uses
> those laws to the benefit of the Free Software. Therefore, relevant
> legal practices, even if used by non-free software, are not to be
> dismissed so easily.
I agree. My point was that some non-free software and services tend to
have EULAs which users would not agree to if they were to read them.
Such software actively discourage users from reading their EULA,
sometimes with a creative interpretation of the law. Your example of
small prints falls into that category.
>
> > > I see all-caps in GUI applications as well.
> >
> > Assuming that you mean free software, do you have examples?
>
> Any program that shows the MIT license will display that part in
> all-caps. (And, as I wrote above, I don't think whether the software
> is free or not is important here.)
Thanks. It looks like there is a bit of flexibility (for instance,
jquery links to https://tldrlegal.com/license/mit-license which shows
a summary without caps first), but those are good examples to keep in
mind.
>
> > 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.
>
> I never said I'm against asking their counsel. Please don't treat
> factual corrections of part of what you say to mean that I reject
> _everything_ that you say. Agreement doesn't have to be total; that's
> a common fallacy ("you are either with us or against us") in this
> divided world nowadays.
>
> > If we deny the fact that several major free software organizations
> > have chosen to display the warranty disclaimer only in their EULA
>
> I didn't deny that, so your arguments should be directed at someone
> else.
Sorry, those were not meant specifically for you. It was my
understanding that the whole discussion about "other software" was
coming from whether there is sufficient reason to ask for renewed
advice.
What I was trying to say was a generic point, that even if Emacs is
not alone in displaying the warranty disclaimer so prominently, in my
opinion there are enough examples of the contrary to justify this
query.
next prev parent reply other threads:[~2020-09-27 11:24 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
2020-09-27 10:50 ` Eli Zaretskii
2020-09-27 11:24 ` Thibaut Verron [this message]
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='CAFsi02TEKbPTM=w4veU5H-VeexL-oYXf_JLG1JjR+6LwJox+ew@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).