From: "Noé Lopez via Emacs development discussions." <emacs-devel@gnu.org>
To: rms@gnu.org
Cc: dunni@gnu.org, emacs-devel@gnu.org, noelopez@free.fr
Subject: Re: [PATCH] [ELPA] Implement connman in enwc
Date: Sun, 14 Apr 2024 15:01:41 +0200 [thread overview]
Message-ID: <87frvot7wq.fsf@xn--no-cja.eu> (raw)
In-Reply-To: <E1rtxVH-0001Md-Gm@fencepost.gnu.org> (message from Richard Stallman on Mon, 08 Apr 2024 18:30:15 -0400)
Hi,
I've pushed my changes to a fork repository at
https://framagit.org/nll/enwc, but I'm not sure how I'm supposed to do
my changes without breaking any copyright/gpl.
As I understand, the code is part of GNU Emacs because it's in ELPA, and
its copyright is assigned to the FSF. My changes are not part of emacs
so are not subject to my copyright assignment. Does that mean I need to
add a second header to the files I changed mentionning my name and that
my work is also under gpl but not part of emacs ?
Then, the documentation mentions copyright directly to Ian Dunn, so I
suppose that doesn't count as part of emacs ? To modify it I would need
to change its title and other FDL stuff. Or I could rewrite it all,
since its only a few lines right now.
Should I change the name of the project, and update the copyright
information and add a notice that this is a modified version of ENWC, or
is it possible/legal to make my repository the new ELPA source, and make
my work part of emacs, which would mean all copyright to the FSF so no
need to update headers ?
next prev parent reply other threads:[~2024-04-14 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 22:10 [PATCH] [ELPA] Implement connman in enwc Noé Lopez via Emacs development discussions.
2024-04-01 22:51 ` Richard Stallman
2024-04-02 13:06 ` Noé Lopez via Emacs development discussions.
2024-04-04 22:42 ` Richard Stallman
2024-04-04 22:42 ` Richard Stallman
2024-04-05 20:00 ` Noé Lopez via Emacs development discussions.
2024-04-08 22:30 ` Richard Stallman
2024-04-14 13:01 ` Noé Lopez via Emacs development discussions. [this message]
2024-09-27 17:34 ` Joseph Turner
2024-09-28 11:03 ` Noé Lopez via Emacs development discussions.
2024-09-28 18:15 ` Joseph Turner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frvot7wq.fsf@xn--no-cja.eu \
--to=emacs-devel@gnu.org \
--cc=dunni@gnu.org \
--cc=noe@xn--no-cja.eu \
--cc=noelopez@free.fr \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.