unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel@gnu.org, Damien Zammit <damien@zamaudio.com>,
	bug-hurd@gnu.org
Subject: Re: Regarding copyright assignment to FSF
Date: Fri, 13 Aug 2021 22:48:29 +0200	[thread overview]
Message-ID: <87sfzdoyua.fsf@web.de> (raw)
In-Reply-To: <5d6b417ee2133d535db6052271b9b14e7cd5ebff.camel@telenet.be>

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


Maxime Devos <maximedevos@telenet.be> writes:

> Upgrading the GPLv2-only code might be dificult if multiple people hold
> the copyright, so for the GPLv2-only code, it might be a good idea to still
> require copyright assignment.

When we did it for Mercurial, going from GPLv2 only to or later took
years and a *lot* of work. That’s why I consider copyright assignment to
the FSF as a good idea. They still get restricted to only use that to
further Free Software (if they violate that, the assignment loses the
reliablility that they need).

>> Even if you do keep it yourself, it makes it more difficult for anyone to enforce
>> the GPL for that project.
>
> A fair point, though I don't know how accurate that is.

From what I read, it’s the most important point, because the first
answer the other sides lawyers always give is „you’re not authorized by
*all* authors to enforce the GPL, so you lose.“

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

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

  parent reply	other threads:[~2021-08-13 20:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210810020240.wpd5pksgdh5e2e3u@begin>
2021-08-10  4:55 ` Fwd: Hurd Security vulnerabilities, please upgrade! jbranso
2021-08-10 15:52 ` Ricardo Wurmus
2021-08-10 15:56   ` Samuel Thibault
2021-08-11 13:01     ` Ludovic Courtès
2021-08-12  2:18       ` Regarding copyright assignment to FSF Damien Zammit
2021-08-13 13:42         ` Maxime Devos
2021-08-13 16:23           ` Samuel Thibault
2021-08-14 21:26             ` Svante Signell
2021-08-14 21:40               ` Samuel Thibault
2021-08-13 20:48           ` Dr. Arne Babenhauserheide [this message]
2021-08-14  3:42         ` Ivan Shmakov
2021-08-14  5:43         ` Michael Banck
2021-08-14  9:00           ` Sergey Bugaev
2021-08-14 12:19           ` Dr. Arne Babenhauserheide
2021-08-14 13:12             ` Michael Banck
2021-08-14 14:16               ` Akib Azmain Turja

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87sfzdoyua.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=bug-hurd@gnu.org \
    --cc=damien@zamaudio.com \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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/guix.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).