From: DJ Delorie <dj@redhat.com>
To: Oleh Derevenko <oleh.derevenko@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Mon, 18 Jun 2018 21:06:00 -0000 [thread overview]
Message-ID: <xna7rrn6si.fsf@greed.delorie.com> (raw)
In-Reply-To: <CAC1wWD0LUPt+ocRgH8ZkaUso5VMh1HoEq7Xu2f-5QLqJzNkGUg@mail.gmail.com> (message from Oleh Derevenko on Mon, 18 Jun 2018 22:52:31 +0300)
Adding my not-a-lawyer two cents...
Oleh Derevenko <oleh.derevenko@gmail.com> writes:
> Just out of curiosity, may I ask why? Just to blindly obey the rules?
Consider that the GNU C Library is... GNU. It's owned by the FSF, and
they make the rules when it comes to legalities, and they have lawyers
that have done all the hard work for us too. And the project has to
have a consistent license to avoid ambiguity. And the LGPL guarantees
freedoms that other licenses might not.
But in general, yes, we obey the rules as laid out by the copyright
holder.
> After all, I would judge based on the feature's benefits or lack of
> those first.
Unfortunately, because of the copyright and patent issues, we really
can't even *look* at your code yet. If we did look at your code, and
your license ended up not changing, we would be unable to be fair about
writing similar code in the future and cleanly licensing it with a
different license. Anyone who read your code would be "tainted".
I admit this makes "just writing code" a bit more difficult and
cumbersome, but that's what we have to do to protect our investments in
our own code in today's legal environment.
next prev parent reply other threads:[~2018-06-18 21:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:35 Oleh Derevenko
2018-04-02 23:07 ` Oleh Derevenko
2018-04-03 13:41 ` Ben Hutchings
2018-04-03 20:06 ` Oleh Derevenko
[not found] ` <CAC1wWD0OwFLqUD2uXnavBzfEw=HCRn3fGW54zYfxRozxp8HsyA@mail.gmail.com>
2018-06-15 14:05 ` Oleh Derevenko
2018-06-15 14:31 ` Florian Weimer
2018-06-16 18:37 ` Oleh Derevenko
2018-06-18 13:22 ` Adhemerval Zanella
2018-06-18 19:52 ` Oleh Derevenko
2018-06-18 21:03 ` Adhemerval Zanella
2018-06-18 21:06 ` DJ Delorie [this message]
2018-06-18 22:26 ` Oleh Derevenko
2018-06-19 12:07 ` Adhemerval Zanella
2018-06-19 12:42 ` Oleh Derevenko
2018-06-19 13:09 ` Adhemerval Zanella
2018-06-19 15:36 ` Patrick McGehearty
2018-06-19 16:28 ` DJ Delorie
2018-06-19 16:52 ` Zack Weinberg
2018-06-19 19:26 ` Joseph Myers
2018-06-19 19:55 ` DJ Delorie
2018-06-19 22:39 ` Oleh Derevenko
2018-06-20 13:14 ` Carlos O'Donell
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=xna7rrn6si.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=oleh.derevenko@gmail.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).