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: Fri, 23 Apr 2021 07:20:31 +1000	[thread overview]
Message-ID: <87bla6f01r.fsf@gmail.com> (raw)
In-Reply-To: <843e4e87-415a-0609-f219-ed937fe5617e@memebeam.org>

Anthony Carrico <acarrico@memebeam.org> writes:

> On 4/20/21 12:55 AM, Tim Cross wrote:
>> The error from libreJS is correct - public domain is not a valid
>> license.
> Everyone is licensed to use public domain works (except to obtain a copyright on
> them). I think you mean that libreJS is working by design when it blocks them,
> which is apparently the case.

What I meant is that Public Domain is not a license - it means the
content cannot be copyrighted, which effectively means it is compatible
with a free license, but the content lacks a formal license. The CCO
also puts the content into the public domain, but also includes a formal
license as a fallback, which can be beneficial in some jurisdictions.   

>> As this is a GNU project and correct licensing is important...
> Emacs is a GNU project, but org-mode export is a document processor, and the
> goal here was to avoid including licensed content in an Author's exported
> documents.

Appreciate the intention. Perhaps we need to clarify what exactly we are
licensing here - the content or the Javascript added to the content to
facilitate presentation. The content should be covered by whatever
license the author prefers. The Javascript on the other hand, if
generated by Org, should probably be covered by the GPL as it is
'created' by org. If the document author has not written the Javascript,
I'm not sure they have the right to set the license on it, especially if
it was generated as part of software covered by the GPL.

The CC0 is appropriate for content which is in the public domain. It
is essentially equivalent to public domain, but with a fallback trivial
free license, which can be a useful addition in some jurisdictions.
However, it is less suitable for software (i.e. Javascript) because it
lacks any protection from patent trolling.

Tim Cross

  reply	other threads:[~2021-04-22 22:05 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
2021-04-22 20:42     ` Anthony Carrico
2021-04-22 21:20       ` Tim Cross [this message]
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=87bla6f01r.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).