From: Protesilaos Stavrou <info@protesilaos.com>
To: Philip Kaludercic <philipk@posteo.net>, Eli Zaretskii <eliz@gnu.org>
Cc: Arash Esbati <arash@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org, Stefan Kangas <stefankangas@gmail.com>,
"Jose E. Marchesi" <jemarch@gnu.org>
Subject: Re: License Notice for ELPA packages
Date: Sat, 07 Sep 2024 14:05:50 +0300 [thread overview]
Message-ID: <87bk0zhgfl.fsf@protesilaos.com> (raw)
In-Reply-To: <874j6rzqo0.fsf@posteo.net>
> From: Philip Kaludercic <philipk@posteo.net>
> Date: Sat, 7 Sep 2024 10:47:27 +0000
> [... 24 lines elided]
>> Stefan and Philip, what are our policies in this regard?
>
> 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".
>
> By grepping through the ELPA packages, I notice a lot (most? all?)
> packages by Protesilaos and Jose (both in the CCs) have the wrong
> comment. I hope they can fix that. For the other packages I'd have to
> check if they are maintained in elpa.git or not, and then contact the
> maintainers accordingly.
Thanks for the reminder! I will do it as soon as possible. Though note
that the changes may take a while to trickle down in some cases as I
have to write change logs first.
--
Protesilaos Stavrou
https://protesilaos.com
next prev parent reply other threads:[~2024-09-07 11:05 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 [this message]
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
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=87bk0zhgfl.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=arash@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).