From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66583 invoked by alias); 18 Jun 2018 13:22:38 -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 66562 invoked by uid 89); 18 Jun 2018 13:22:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Ben, accord X-HELO: mail-qt0-f174.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=cTIVl/W4ZRV8smEg11MuXT8x/QwSYjAaNarQCgWK5Xo=; b=ZCrUhRxAi7pYbd82wEA7lpLStOR1HhtfuQGXM91g44Gq1j8qhlKNVdaQHArIt3kOH3 NfIEvMpvDlHAdFVwtKtSJ5FvMbJ9lPcPsVrGy5BL4hog9Q45WMCtzS/poWxYPBAilKqn TTVeRoLygAXbczExtPUaPj2NgP9oijrpv10CxboWmSfVwzorHlBlhzUXiJW2VAr2+oee N44Wzc0O+UfbhfiyID+71Dcg0/M/QyZutMX8QxRn+KXp0ouZJFNFg6pXfXnqoMskKJ6B tp96UNoW1OY1T8J9Dgb6NwzlUzBuOsSILmYOtVu2vbR+pfG9Bxn3gVx+VIVUrZ+LFx+q tnrQ== X-Gm-Message-State: APt69E3xOPkvw3VKs3pkuoapEms7paICNmfCZ+VPxNidREdCXWhvHkaR okEePc6g5tdzbVFQ304/zlY5qtFfnLY= X-Google-Smtp-Source: ADUXVKIh31tiOM7mez1K/IQQsprK2PbNLnRyDiacgU5802Y52LynkBO5EGMQ+RwUggpu6k6vBHvvAQ== X-Received: by 2002:a0c:a8e1:: with SMTP id h33-v6mr10517870qvc.131.1529328154679; Mon, 18 Jun 2018 06:22:34 -0700 (PDT) Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread To: libc-alpha@sourceware.org References: <1522762896.2654.94.camel@codethink.co.uk> From: Adhemerval Zanella Openpgp: preference=signencrypt Message-ID: Date: Mon, 18 Jun 2018 13:22:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2018-06/txt/msg00482.txt.bz2 As Ben Hutchings has noted, new code additions are expected to have be licensed with LGPL 2.1+ following the default FSF copyright assignment (as Carlos has noted in previously message). You seemed to not be in accord on such criteria, so I think we won't be able to take your contribution. On 16/06/2018 15:37, Oleh Derevenko wrote: > Hi Florian, > > Would not it work if a warning and a license text would be put in the > header and in respective manual pages to declare and explain what are > the use conditions/restrictions? That would be a kind of offer the > public could accept and it would provide them legal grounds. Of > course, I will have little (if any) means to verify and control. But > this is more a honesty oriented approach and I guess I'll be fine with > that. > > On Fri, Jun 15, 2018 at 5:30 PM, Florian Weimer wrote: >> On 06/15/2018 04:05 PM, Oleh Derevenko wrote: >>> >>> Could it be that a project like libc does not have a group of people >>> eligible for making decisive judgements and saying "yes" or "no" on >>> behalf of it? Or do you need more time? >> >> >> You said you want to avoid “misuse within commercial so[f]tware”. I don't >> see how you can do that while still contributing to glibc, so I didn't look >> at your proposal in detail. >> >> Thanks, >> Florian > > >