unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eduardo Ochs <eduardoochs@gmail.com>, Richard Stallman <rms@gnu.org>
Cc: emacs-tangents@gnu.org
Subject: Re: Emacs-Lua: question about the license of one file
Date: Tue, 07 Sep 2021 09:24:01 +0300	[thread overview]
Message-ID: <83r1e0q4xq.fsf@gnu.org> (raw)
In-Reply-To: <CADs++6guhrt6crmp8f-9qobpLtYEXLU4jX8HpCfv_A39VE6VBg@mail.gmail.com> (message from Eduardo Ochs on Tue, 7 Sep 2021 01:09:04 -0300)

> From: Eduardo Ochs <eduardoochs@gmail.com>
> Date: Tue, 7 Sep 2021 01:09:04 -0300
> 
> I am working on a package that contains a module written in C++ that
> loads a Lua interpreter, and that implements a REPL that lets us run
> that interpreter interactively from Emacs. It is here:
> 
>   https://github.com/edrx/emacs-lua
> 
> At this moment my package is just a poorly-documented prototype, but I
> would like to submit it to ELPA when it grows up.
> 
> QUESTION. The code in the module in C++ was written by a guy who sent
> it to the Lua mailing list. His message is here:
> 
>   http://lua-users.org/lists/lua-l/2021-03/msg00084.html
> 
> Here is my version of his code:
> 
>   https://raw.githubusercontent.com/edrx/emacs-lua/main/emlua.cpp
>   http://angg.twu.net/emacs-lua/emlua.cpp.html
>   http://angg.twu.net/emacs-lua/emlua.cpp
> 
> When my REPL became functional I sent him an e-mail saying that I
> would like to prepare the package to submit it to ELPA in the future,
> and asked him what he thought about doing the paperwork thing... and I
> told him that if he preferred a paperworkless way that _I guessed_
> that he could just send an e-mail to the Lua mailing list declaring
> his code to be in the public domain, but I would have to check that
> possibility with people who are more knowledgeable than me - and he
> said something equivalent to "wow, yes, great, please check!"...
> 
> So: can we do that? And are there any other licenses that you would
> recommend besides public domain?

I think using a PD code may also need some paperwork, some kind of
disclaimer?  Richard, what are the rules in these cases?



      reply	other threads:[~2021-09-07  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  4:09 Emacs-Lua: question about the license of one file Eduardo Ochs
2021-09-07  6:24 ` Eli Zaretskii [this message]

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=83r1e0q4xq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eduardoochs@gmail.com \
    --cc=emacs-tangents@gnu.org \
    --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.
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).