From: Maxime Devos <maximedevos@telenet.be>
To: "Damien Zammit" <damien@zamaudio.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Ricardo Wurmus" <rekado@elephly.net>
Cc: guix-devel@gnu.org, bug-hurd@gnu.org
Subject: Re: Regarding copyright assignment to FSF
Date: Fri, 13 Aug 2021 15:42:37 +0200 [thread overview]
Message-ID: <5d6b417ee2133d535db6052271b9b14e7cd5ebff.camel@telenet.be> (raw)
In-Reply-To: <6374f720-89bf-29be-d575-ba556ada7032@zamaudio.com>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
Damien Zammit schreef op do 12-08-2021 om 12:18 [+1000]:
> Hi Ludo,
I'm not Ludo, but here's my response anyway.
(I'm interested in doing some small and larger things with the Hurd,
but I keep being occupied by other things and I'm having a hard time
understanding the inner workings ...)
> On 11/8/21 11:01 pm, Ludovic Courtès wrote:
> > It would be interesting to consider dropping the copyright assignment
> > requirement for Hurd/Mach/MiG. For what remains primarily a hobby
> > project, this looks to me like a hindrance more than anything else.
>
> I imagine it is slightly inconvenient for new contributors, but not a hindrance in my opinion.
> It ensures that FSF has complete control of the licensing.
> For example, how will FSF upgrade the project to GPLv3 if multiple people hold the copyright?
> (There are plans to remove the GPLv2-only code btw, as Samuel said).
When the code is GPLv2-or-later, replace v2 with v3 in the license notices.
If the code uses GPLv2-only code, first upgrade the GPLv2-only code to GPLv3-or-later.
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.
> PS: Why are you promoting a widespread drop of FSF copyright assignment anyway?
> In my opinion, FSF is a better steward for copyright authorship than any company
> would be assuming you are working on free software on an employer's time and don't
> mutually agree with your employer to keep your own authorship.
FWIW, Ludovic does not seem to be promoting assigning copyright to employers.
> 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.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-08-13 13:43 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d6b417ee2133d535db6052271b9b14e7cd5ebff.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=bug-hurd@gnu.org \
--cc=damien@zamaudio.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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/guix.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.