unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Cc: Andy Wingo <wingo@pobox.com>
Subject: Relaxing the copyright assignment policy
Date: Thu, 06 Oct 2022 22:18:00 +0200	[thread overview]
Message-ID: <87tu4ghfk7.fsf@inria.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]

Hello Guilers!

Until now, we required copyright for “legally significant¹”
contributions to Guile to be assigned to the Free Software Foundation
(FSF).  This requirement did not exist for code not initially written
for Guile—e.g., (ice-9 match), sxml-match, etc.  The purported advantage
of copyright assignment is described at
<https://www.gnu.org/licenses/why-assign.html>.

Your unreachable-but-nonetheless-friendly co-maintainers, Andy Wingo and
myself, came to the conclusion that the cost/benefit ratio of mandatory
copyright assignment is not good for Guile.  Like other projects such as
GCC², we have decided to relax that policy.

Nothing changes for contributors who have already assigned copyright on
future changes to Guile to the FSF.

New contributors are encouraged to assign copyright to the FSF by
emailing them one of the forms at
<https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/>,
especially if they intend to contribute significantly going forward.

New contributors may instead choose to not assign copyright to the FSF.
In that case, copyright on the new code is held by the contributor
themself or, possibly, by their employer—contributors who choose this
option are expected to clarify which of these two applies to their
situation.  A copyright line for the new copyright holder is added to
files modified in a “legally significant” way³.

Guile remains under the same license, the GNU Lesser General Public
License, version 3 or any later version; contributions are expected
under the same terms.

We hope this to be one of the changes that will make it easier to
contribute to Guile.

Let us know if you have any questions, and enjoy the good hack!

Ludo’ & Andy.

¹ https://www.gnu.org/prep/maintain/maintain.html#Legally-Significant
² https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html
³ https://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

             reply	other threads:[~2022-10-06 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 20:18 Ludovic Courtès [this message]
2022-10-06 20:34 ` Relaxing the copyright assignment policy Jean Abou Samra
2022-10-06 20:59   ` Dr. Arne Babenhauserheide
2022-10-06 20:45 ` Thompson, David
2022-10-07  9:58 ` Maxime Devos
2022-10-07 12:05   ` Ludovic Courtès
2022-10-08 14:07 ` Jean Abou Samra
2022-10-29  5:44 ` Ian Kelling
2022-10-29  6:39   ` Ian Kelling

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/guile/

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

  git send-email \
    --in-reply-to=87tu4ghfk7.fsf@inria.fr \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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.
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).