From: Protesilaos Stavrou <info@protesilaos.com>
To: Philip Kaludercic <philipk@posteo.net>,
"Ruijie Yu via Emacs development discussions."
<emacs-devel@gnu.org>
Cc: Ruijie Yu <ruijie@netyu.xyz>
Subject: Re: [elpa] externals/denote 51bd02b95c 1/2: Add initial version of 'denote-rename-buffer' extension
Date: Sun, 28 May 2023 14:15:02 +0300 [thread overview]
Message-ID: <87leh8r9l5.fsf@protesilaos.com> (raw)
In-Reply-To: <87fs7gzpf5.fsf@posteo.net>
> From: Philip Kaludercic <philipk@posteo.net>
> Date: Sun, 28 May 2023 11:05:50 +0000
>
> Ruijie Yu via "Emacs development discussions." <emacs-devel@gnu.org>
> writes:
> [... 20 lines elided]
>> I'm curious, should GNU elpa packages be considered part of Emacs or
>> not? I have previously contributed to pyim, a GNU elpa package, whose
>> maintainer asked me whether I had FSF CA before including my proposed
>> changes, and whose package header says it is part of Emacs.
>
> I believe this is a mistake, the package is part of the GNU ELPA
> repository, where all packages are regarded to be part of GNU Emacs. It
> might be that Prot used a template to generate this file, and that the
> template defaulted to "... is not a part ...".
I didn't know this. To my mind, the modus-themes are "part of Emacs".
The rest have copyright assigned to the FSF and, as such, "could be part
of Emacs".
I am happy to change this in all my packages.
--
Protesilaos Stavrou
https://protesilaos.com
next prev parent reply other threads:[~2023-05-28 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168526066293.9832.17189979431838421656@vcs2.savannah.gnu.org>
[not found] ` <20230528075743.4D45AC22A3C@vcs2.savannah.gnu.org>
2023-05-28 8:39 ` [elpa] externals/denote 51bd02b95c 1/2: Add initial version of 'denote-rename-buffer' extension Ruijie Yu via Emacs development discussions.
2023-05-28 11:05 ` Philip Kaludercic
2023-05-28 11:15 ` Protesilaos Stavrou [this message]
2023-05-28 11:51 ` Philip Kaludercic
2023-05-29 22:39 ` 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=87leh8r9l5.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=ruijie@netyu.xyz \
/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).