From: Bastien <bzg@gnu.org>
To: Jorge P. de Morais Neto <jorge+list@disroot.org>
Cc: emacs-orgmode@gnu.org, Kyle Meyer <kyle@kyleam.com>,
Anthony Carrico <acarrico@memebeam.org>
Subject: Re: Bug: JavaScript in HTML export not recognized by LibreJS as free [9.4.5 (9.4.5-16-g94be20-elpaplus @ /home/jorge/.config/emacs/elpa/org-plus-contrib-20210412/)]
Date: Mon, 26 Apr 2021 18:57:19 +0200 [thread overview]
Message-ID: <87bla1m1ao.fsf@bzg.fr> (raw)
In-Reply-To: <87o8e1gqox.fsf@disroot.org> (Jorge P. de Morais Neto's message of "Mon, 26 Apr 2021 09:45:18 -0300")
Hi Jorge,
Jorge P. de Morais Neto <jorge+list@disroot.org> writes:
> Therefore, when a verifiably public domain script
> is blocked by LibreJS, LibreJS users (like me) get unhappy; this ought
> to be solved.
this has just been resolved - see my other message today.
Legally, one could dispute the fact that these lines are copyrightable
because the code here is trivial and hardly qualifies as "orginal".
So I understand Anthony's willingness to put them in the public domain
and your proposal to put them under CC0, which is also valid. But I'd
rather stick to the GPLv3+, because there is no real issue about this
licensing of these lines.
I hope both you and Anthony agree with this, or at least recognize
that the current solution is acceptable.
next prev parent reply other threads:[~2021-04-26 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 20:26 Bug: JavaScript in HTML export not recognized by LibreJS as free [9.4.5 (9.4.5-16-g94be20-elpaplus @ /home/jorge/.config/emacs/elpa/org-plus-contrib-20210412/)] Jorge P. de Morais Neto
2021-04-20 3:09 ` Kyle Meyer
2021-04-20 4:55 ` Tim Cross
2021-04-22 20:42 ` Anthony Carrico
2021-04-22 21:20 ` Tim Cross
2021-04-22 22:35 ` Anthony Carrico
2021-04-22 20:29 ` Anthony Carrico
2021-04-23 1:42 ` Anthony Carrico
2021-04-26 12:43 ` Bastien
2021-04-26 20:36 ` Anthony Carrico
2021-05-01 9:30 ` Bastien
2021-04-26 12:45 ` Jorge P. de Morais Neto
2021-04-26 16:57 ` Bastien [this message]
2021-04-27 17:57 ` Jorge P. de Morais Neto
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bla1m1ao.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=acarrico@memebeam.org \
--cc=emacs-orgmode@gnu.org \
--cc=jorge+list@disroot.org \
--cc=kyle@kyleam.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/org-mode.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).