unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: philipk@posteo.net, arash@gnu.org, emacs-devel@gnu.org,
	stefankangas@gmail.com, info@protesilaos.com, jemarch@gnu.org
Subject: Re: License Notice for ELPA packages
Date: Sun, 08 Sep 2024 07:32:57 +0300	[thread overview]
Message-ID: <86y142wyrq.fsf@gnu.org> (raw)
In-Reply-To: <jwvmskjdvhy.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 07 Sep 2024 17:11:23 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>,  Arash Esbati <arash@gnu.org>,
>   emacs-devel@gnu.org,  Stefan Kangas <stefankangas@gmail.com>,
>   "Protesilaos Stavrou" <info@protesilaos.com>,  Jose E. Marchesi
>  <jemarch@gnu.org>
> Date: Sat, 07 Sep 2024 17:11:23 -0400
> 
> > As ELPA packages are regarded to be part of Emacs (and distributed under
> > the same license), the comment should say "is part of GNU Emacs".
> 
> I don't think it's that clear.
> It is considered as part of GNU Emacs in the sense that copyright
> assignments that cover Emacs also cover these files, but it is not
> considered as part of the GNU Emacs in the sense that it's not
> (currently) included in the distributed tarball.
> 
> So historically we have accepted both "is part of GNU Emacs" and "is NOT
> part of GNU Emacs".  IMO the better choice is to say neither.

Some ELPA packages are also part of Emacs, so I guess they should say
"is part of GNU Emacs"?

Also, what will we do when we devise a way to bundle ELPA packages
with Emacs release tarballs? rewrite the notice?  Something to keep in
mind for the future, I guess.



  reply	other threads:[~2024-09-08  4:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 19:41 License Notice for ELPA packages Arash Esbati
2024-09-05 19:56 ` Emanuel Berg
2024-09-07  9:47 ` Eli Zaretskii
2024-09-07 10:47   ` Philip Kaludercic
2024-09-07 11:05     ` Protesilaos Stavrou
2024-09-07 13:07     ` Arash Esbati
2024-09-07 13:11       ` Philip Kaludercic
2024-09-07 21:11     ` Stefan Monnier
2024-09-08  4:32       ` Eli Zaretskii [this message]
2024-09-08  9:21         ` Stefan Monnier
2024-09-08 22:03       ` Arash Esbati
2024-09-09 12:31         ` Philip Kaludercic
2024-09-09 13:18           ` Stefan Monnier
2024-09-11  7:28             ` Philip Kaludercic
2024-09-20  4:15       ` Emanuel Berg

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=86y142wyrq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    --cc=jemarch@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=stefankangas@gmail.com \
    /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).