public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Mon, 18 Jun 2018 13:22:00 -0000	[thread overview]
Message-ID: <a3a5b0d2-842f-4bad-0a92-3779f63aa9b4@linaro.org> (raw)
In-Reply-To: <CAC1wWD1uNxeLGkDUduNVrHh442VU=zcY_==O8RA_8XiOsPpEeQ@mail.gmail.com>

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 <fweimer@redhat.com> 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
> 
> 
> 

  reply	other threads:[~2018-06-18 13:22 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 [this message]
2018-06-18 19:52                 ` Oleh Derevenko
2018-06-18 21:03                   ` Adhemerval Zanella
2018-06-18 21:06                   ` DJ Delorie
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=a3a5b0d2-842f-4bad-0a92-3779f63aa9b4@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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.
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).