From: Brian Leung <leungbk@mailfence.com>
To: help-gnu-emacs@gnu.org
Subject: Licensing question
Date: Sun, 8 Nov 2020 05:59:47 +0100 (CET) [thread overview]
Message-ID: <585007706.32156.1604811587103@ichabod.co-bxl> (raw)
If I copy and properly attribute code distributed under a GPL-compatible license like Apache 2 or Expat, will the code necessarily be ineligible for inclusion in GNU Emacs?
My specific problem: the tree-sitter library has garnered some interest as a tool for structured editing. Assume, for the sake of this discussion, that Emacs has support for it. I would like to read through https://github.com/nvim-treesitter/nvim-treesitter/ to figure out how to develop some user-facing features. But nvim-tree-sitter is distributed under an Apache 2 license, so I'm not sure what I can do with their code.
--
Sent with https://mailfence.com
Secure and private email
next reply other threads:[~2020-11-08 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 4:59 Brian Leung [this message]
2020-11-08 5:13 ` Licensing question Stefan Monnier
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=585007706.32156.1604811587103@ichabod.co-bxl \
--to=leungbk@mailfence.com \
--cc=help-gnu-emacs@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).