From: Ivan Shmakov <ivan@siamics.net>
To: guix-devel@gnu.org, bug-hurd@gnu.org
Subject: Re: Regarding copyright assignment to FSF
Date: Sat, 14 Aug 2021 03:42:47 +0000 [thread overview]
Message-ID: <20210814034247.awjj2dtwkvxql6g4@violet.siamics.net> (raw)
In-Reply-To: <6374f720-89bf-29be-d575-ba556ada7032@zamaudio.com>
>>>>> On 2021-08-12 12:18:20 +1000, Damien Zammit wrote:
>>>>> On 11/8/21 11:01 pm, Ludovic Courtès wrote:
This seem somewhat off-topic for the lists, so I’m open to
suggestions on what other forum to use (should anyone wish
to continue this thread.) My suggestion is, as usual,
to use a Usenet newsgroup, such as comp.misc, for the purpose.
(See http://www.aioe.org/ for a free, no registration needed,
IPv4-only newsserver; or http://www.eternal-september.org/ for
free registration, IPv6 + IPv4 one.)
>> 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.
I’m going to concur; there’s some delay, sure, but not that much
of actual effort on the part of the new contributor. Unless, of
course, one’s employer is uncooperative, but I’m afraid that
can’t be helped.
> It ensures that FSF has complete control of the licensing.
And enforcement.
I’d argue that in a better world, no copyright assignment would
be necessary (nor would be GPL, but that’s another matter), as
anyone would be able to bring an infringement case to the court
entirely by themselves. As it is, however, some considerations
apply.
As I understand it (though IANAL), there’re two parts to this
story. First of all, copyright enforcement is, in general, a
process that itself requires certain effort. Do you have time
to spare on filing a suit? Will you have some more to see it
through? Do you know a good lawyer to hire, or do you have the
necessary skills to represent yourself in the court? What remedy
will you seek?
Moreover, /copyleft/ enforcement is tricky by itself. Copyright
was devised, basically, as a legal tool for author to sue his
publisher for royalties. As such, even though that does seem
to slowly change, the first question of the court for your newly-
brought GPL-infringement case would be: what sum, in your opinion,
does the company owe you? Are you prepared to answer that?
Given the above, I’m inclined to think that assigning copyright
to a party legally prepared to fight for it to be a sensible
choice /whether it is required or not./ And /especially/ for
hobby projects; for I presume that for something you do for
living, you’ll be quite in position to estimate damages arising
from someone infringing your copyright.
From here, we may try to rank different charities on how well
they handle their enforcement cases. My guess is that FSF will
come near the top.
The other part concerns one’s employer, and the terms of the
contract. For instance, the contract I’m currently under says
that I’m entitled to copyright on any and all works I create,
/unless/ I’ve been specifically directed by the employer to
create any given work.
From what I’ve heard, however, some contracts allow the
/employer/ (variant: school) to claim copyright over any work
created by the employee during the term of the contract. In
this case, it’s arguably better for all parties involved to have
the employer’s position clarified and known. Copyright
assignment is one, though perhaps not the only, way it can be done.
--
FSF associate member #7257 http://am-1.org/~ivan/
next prev parent reply other threads:[~2021-08-15 13:37 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
2021-08-14 3:42 ` Ivan Shmakov [this message]
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=20210814034247.awjj2dtwkvxql6g4@violet.siamics.net \
--to=ivan@siamics.net \
--cc=bug-hurd@gnu.org \
--cc=guix-devel@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 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).