From: Michael Banck <mbanck@gmx.net>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guix-devel@gnu.org, Damien Zammit <damien@zamaudio.com>,
bug-hurd@gnu.org
Subject: Re: Regarding copyright assignment to FSF
Date: Sat, 14 Aug 2021 15:12:34 +0200 [thread overview]
Message-ID: <6117c143.1c69fb81.14cfe.cded@mx.google.com> (raw)
In-Reply-To: <874kbsxlq7.fsf@web.de>
Hi,
On Sat, Aug 14, 2021 at 02:19:12PM +0200, Dr. Arne Babenhauserheide wrote:
> Michael Banck <mbanck@gmx.net> writes:
>
> > I don't mind that, but I also think the Hurd is not a tactical FSF asset
> > anymore that needs to be kept under tight control. The FSF has enough
> > copyright in the Hurd that it can enforce it whenever it likes, even if
> > other people's copyrighted code (as is already the case with the pfinet
>
> I wouldn’t be so sure about that.
>
> 1. Without copyright assignment of all code involved, enforcement
> becomes much harder.
I don't think "much harder" can be quantified in a meaningful way,
seeing how parts of the Hurd aren't under the FSF copyright at this
point, anyway.
> 2. The Hurt still provides capabilities other OS’es don’t — while
> maintaining POSIX compatibility. We’ve seen audacity basically
> being taken over by a company in the past months, so the danger of
> losing Hurd to proprietarization rather got bigger than smaller.
Nobody proposes that the FSF relicenses the Hurd to a non-copyleft
license before relinquishing the copyright assignment mandate, so I
don't see how the Hurd continueing to be under a GPLv2+ license will
ever be able to be taken proprietary.
I'm not going to respond further on this thread, this is starting to get
off-topic really quick and if there are further things to be discussed,
gnu-system-discuss or whatever other mailing list is likely the better
place.
Michael
next prev parent reply other threads:[~2021-08-15 13:36 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
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 [this message]
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=6117c143.1c69fb81.14cfe.cded@mx.google.com \
--to=mbanck@gmx.net \
--cc=arne_bab@web.de \
--cc=bug-hurd@gnu.org \
--cc=damien@zamaudio.com \
--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).