emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: 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: Tue, 20 Apr 2021 14:55:39 +1000	[thread overview]
Message-ID: <877dkxk0q3.fsf@gmail.com> (raw)
In-Reply-To: <87czupy7mn.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> writes:

> Jorge P. de Morais Neto writes:
>> Hi.  The HTML export has JavaScript that LibreJS does not recognize as
>> free.
> Thanks for noting this.  That's certainly not ideal.
>> My first attempt at an workaround (inspired by the Org Mode mailing
>> list) was merely encoding the ampersand in the magnet link, but that
>> *did not make LibreJS happy*.  Then I checked LibreJS manual and saw
>> this excerpt:
>> https://www.gnu.org/software/librejs/manual/librejs.html#Free-Licenses-Detection-1
>>     Public domain is not a license (see
>>     https://www.gnu.org/licenses/license-list.html#PublicDomain).  If
>>     you want to release your work to the public domain, the FSF
>>     recommends using CC0.
>> Then I came up with a successful workaround.  I included the following
>> code in my Org Mode customization file:
> Hmm, the public domain switched happen with 471054136 (ox-html.el: Use
> classList and put in the public domain, 2020-09-05) and the associated
> thread is
>   https://orgmode.org/list/20200617002335.l4lg3slfxm74vx3h@silver/
> (+cc author and committer)
>> ;; [2021-04-16 sex]: HACK Work around a bug that confuses LibreJS
>> (with-eval-after-load 'ox-html
>>   (setq org-html-scripts
>> 	(string-replace "\
>> // @license magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt Public Domain"
>> 			"\
>> // @license magnet:?xt=urn:btih:90dc5c0be029de84e523b9b3922520e79e0e6f08&amp;dn=cc0.txt CC0-1.0"
>> 			org-html-scripts)))
>> This works; it makes LibreJS happy.
> Okay.  Anthony/Bastien/others, thoughts on using CC0 instead?

The error from libreJS is correct - public domain is not a valid

As this is a GNU project and correct licensing is important, I don't
think there is any option other than to change the line to reference the
CC license (or any appropriate free license). If 'public domain' was
used due to some other issue, either we have to verify the code is
covered by a free (not just open source) license or replace it with code
that is and is acceptable by the FSF. 
Tim Cross

  reply	other threads:[~2021-04-20  5:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 20:26 Jorge P. de Morais Neto
2021-04-20  3:09 ` Kyle Meyer
2021-04-20  4:55   ` Tim Cross [this message]
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
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:

  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=877dkxk0q3.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=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/)]' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).