all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jeremy Bryant <jb@jeremybryant.net>
To: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org,  stefankangas@gmail.com,  emacs-devel@gnu.org
Subject: Re: magit copyright assignments
Date: Thu, 18 Jul 2024 15:02:38 +0100	[thread overview]
Message-ID: <874j8mdcht.fsf@jeremybryant.net> (raw)
In-Reply-To: <E1sUHi3-0005mF-1W@fencepost.gnu.org> (Richard Stallman's message of "Wed, 17 Jul 2024 23:21:35 -0400")

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > > For the magit contributors that have signed papers for Emacs, we
>   > > should ask each one to send an email confirming that perse will regard
>   > > per contributions to magit as contributions to Emacs, once magit is
>   > > included in Emacs.
>
>   > So far I have asked the contributors to consider returning the copyright
>   > assignment form, which names Emacs.  Would this not be sufficient?
>
> Yes and no.
>
> Since Magit is not part of Emacs, interpreting the Emacs assignment in
> a strict sense says it does not cover magit now.
>
> However, we aim to make magit part of Emacs.
>
> So a lawyer gave me the advice that you've quoted above,
> to clarify that the Emacs assignmets DO cover magit.

Thanks for explaining the origin of the advice.

For future iterations and given the importance of defending the GPL
using unambiguous language as far as possible, perhaps it may help to
define a standard text to provide to contributors?

How about something in the style of the 'form' to send to
assign@gnu.org, and that can be distributed by maintainers, proposed
wording below.  WDYT?


--- PROPOSED WORDING
--- INSTRUCTIONS TO SEND TO THE FSF - PACKAGE RELATED

[What is the package considered for inclusion Emacs?]
Package Foo

[Assigment statement]
"I confirm that I regard my contributions to Package Foo as
contributions to Emacs, once Package Foo is included in Emacs."







  reply	other threads:[~2024-07-18 14:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 15:50 magit copyright assignments Jeremy Bryant
2024-07-13 16:25 ` Eli Zaretskii
2024-07-13 21:39   ` Jeremy Bryant
2024-07-14  4:50     ` Eli Zaretskii
2024-07-15 20:10       ` Jeremy Bryant
2024-07-15 20:49         ` Stefan Kangas
2024-07-16  2:17   ` Richard Stallman
2024-07-16  5:53     ` Lele Gaifax
2024-07-16 10:29       ` Eli Zaretskii
2024-07-16 17:23         ` Lele Gaifax
2024-07-16 18:25           ` Eli Zaretskii
2024-07-16 19:09             ` Lele Gaifax
2024-07-18  3:21             ` Richard Stallman
2024-07-18  5:15               ` Eli Zaretskii
2024-07-21  3:00                 ` Richard Stallman
2024-07-16  2:18   ` Richard Stallman
2024-07-16 21:27     ` Jeremy Bryant
2024-07-17 11:23       ` Eli Zaretskii
2024-07-17 13:53         ` Jeremy Bryant
2024-07-18  3:21       ` Richard Stallman
2024-07-18 14:02         ` Jeremy Bryant [this message]
2024-07-18 15:31           ` Eli Zaretskii
2024-07-18 16:53             ` Jeremy Bryant
2024-07-18 17:40               ` Eli Zaretskii
2024-07-18 20:36                 ` Jeremy Bryant
2024-07-19 17:32                   ` Eli Zaretskii
2024-07-21  3:02                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874j8mdcht.fsf@jeremybryant.net \
    --to=jb@jeremybryant.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --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 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.