public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Oleh Derevenko <oleh.derevenko@gmail.com>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: "Carlos O'Donell" <carlos@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Tue, 03 Apr 2018 20:06:00 -0000	[thread overview]
Message-ID: <CAC1wWD21wh_ZMRDpz0Tk65Jzrcj3nRe_6jj-MKc-6paK3zsoVw@mail.gmail.com> (raw)
In-Reply-To: <1522762896.2654.94.camel@codethink.co.uk>

Ben,

LGPL in this case is just the same as freeware. You simply create a
LGPL shared library, export functionality from it, and use it
absolutely for whatever you want.

Regarding the patent, I'm not sure it will be approved at all yet. Of
course, I'll do my best but there is some amount of bureaucracy one
has to overcome and there is no certainty who will win. I fully
realize that options available to me are very limited and I'm on mercy
of examiners.
In any case the patent is not for money. So far I have invested about
$700 into it and it is yet going to additionally cost at minimum about
$2500 for 20 years of patent validity period. If I'll be able to earn
that money back that'll already be a big achievement. :-)
All this is more to get a publication and to have a new life experience.

-- 
Oleh Derevenko

On Tue, Apr 3, 2018 at 4:41 PM, Ben Hutchings
<ben.hutchings@codethink.co.uk> wrote:
> On Tue, 2018-04-03 at 02:07 +0300, Oleh Derevenko wrote:
>> Hi All,
>>
>> Well guys, really! This is a cool thing!
> [...]
>
> Maybe, but unless you are prepared to license your code and patent
> under LGPL 2.1+ terms then there is no point in bringing it up here.
>
> Ben.
>
> --
> Ben Hutchings
> Software Developer, Codethink Ltd.
>

  reply	other threads:[~2018-04-03 20: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 [this message]
     [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
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=CAC1wWD21wh_ZMRDpz0Tk65Jzrcj3nRe_6jj-MKc-6paK3zsoVw@mail.gmail.com \
    --to=oleh.derevenko@gmail.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=carlos@redhat.com \
    --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).