This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC 0/1] Contributing a compound object to the libpthread
- From: Oleh Derevenko <oleh dot derevenko at gmail dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Sat, 16 Jun 2018 21:37:35 +0300
- Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
- References: <CAC1wWD1CVdQtXcAj4kRgJ1mxDHrKf0vRRq5kpRCgEH-a15H40g@mail.gmail.com> <CAC1wWD0ZWef6JBdt3J89vD5Nq0kCukSoe6O1tAs=4tK9F+PixA@mail.gmail.com> <1522762896.2654.94.camel@codethink.co.uk> <CAC1wWD21wh_ZMRDpz0Tk65Jzrcj3nRe_6jj-MKc-6paK3zsoVw@mail.gmail.com> <CAC1wWD0OwFLqUD2uXnavBzfEw=HCRn3fGW54zYfxRozxp8HsyA@mail.gmail.com> <CAC1wWD0u26uh7zdyB5+iE3HWcUvoUkrAJQc3-hLRVrqDRAqAPw@mail.gmail.com> <a1dcbff6-cd11-61ef-e30b-03e64b6c91ce@redhat.com>
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
--
Oleh Derevenko
-- Skype with underscore