From: Christopher Howard <christopher@librehacker.com>
To: Emacs Devel Mailing List <emacs-devel@gnu.org>
Subject: Elisp licensing
Date: Mon, 18 Nov 2024 08:33:02 -0900 [thread overview]
Message-ID: <87mshwphv5.fsf@librehacker.com> (raw)
Hi, if there is a long thread on this question already, please send me the link to that.
I was wondering if somebody could clarify, from a legal perspective, and from the perspective of the Gnu project, what is acceptable licensing for Elisp code? In my personal observations, finding Elisp in the wild, it seems like most people are labeling their Elisp as GPLv3+, not counting the code that doesn't have any license attached at all. But recently I came across an Elisp library marked LGPLv3+, and also another project that was under an ISC license.
My understand was that nearly all Elisp programs heavily utilize the Gnu Emacs API and libraries, and so they should be also licensed under GPLv3+. Maybe with exceptions for programs written for Guile Elisp or one of the non-Gnu Emacs clones that are being developed, like Gypsum or Rune. Actually, I believe Rune is marked GPL-3.0 and Gypsum is AGPL-3.0, though I haven't looked closely at their licensing comments.
--
📛 Christopher Howard
🚀 gemini://gem.librehacker.com
🌐 http://gem.librehacker.com
בראשית ברא אלהים את השמים ואת הארץ
next reply other threads:[~2024-11-18 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 17:33 Christopher Howard [this message]
2024-11-21 4:58 ` Elisp licensing Richard Stallman
2024-11-21 21:10 ` Christopher Howard
2024-11-23 6:12 ` Richard Stallman
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=87mshwphv5.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).