From: Anthony Carrico <acarrico@memebeam.org>
To: Kyle Meyer <kyle@kyleam.com>,
"Jorge P. de Morais Neto" <jorge+list@disroot.org>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.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: Thu, 22 Apr 2021 21:42:49 -0400 [thread overview]
Message-ID: <86e54de8-ef5a-0f4b-3eed-64e7559eed42@memebeam.org> (raw)
In-Reply-To: <073538d9-09ac-7c6f-0188-6e75d0daf438@memebeam.org>
On 4/22/21 4:29 PM, Anthony Carrico wrote:
> Practically speaking, the script included by org-mode is in the public
> domain, so it could never conflict with whatever license the author
> chooses. Therefore, we should remove the LibreJS tag from the <script>,
> perhaps leaving behind the public domain notice in the <script> comment.
> With that tag removed, the LibreJS web filter should respect whatever
> LibreJS license the document's author includes, if any.
I sent a patch to the mailing list to this effect, if it seems appropriate.
--
Anthony Carrico
next prev parent reply other threads:[~2021-04-23 1:44 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 [this message]
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
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=86e54de8-ef5a-0f4b-3eed-64e7559eed42@memebeam.org \
--to=acarrico@memebeam.org \
--cc=bzg@gnu.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).