From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27295 invoked by alias); 18 Jun 2018 21:06:41 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 27279 invoked by uid 89); 18 Jun 2018 21:06:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=holder, investments, todays, today's X-HELO: mx1.redhat.com From: DJ Delorie To: Oleh Derevenko Cc: libc-alpha@sourceware.org Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread In-Reply-To: (message from Oleh Derevenko on Mon, 18 Jun 2018 22:52:31 +0300) Date: Mon, 18 Jun 2018 21:06:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2018-06/txt/msg00527.txt.bz2 Adding my not-a-lawyer two cents... Oleh Derevenko 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.