public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Oleh Derevenko <oleh.derevenko@gmail.com>
To: libc-alpha@sourceware.org
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Fri, 15 Jun 2018 14:05:00 -0000	[thread overview]
Message-ID: <CAC1wWD0u26uh7zdyB5+iE3HWcUvoUkrAJQc3-hLRVrqDRAqAPw@mail.gmail.com> (raw)
In-Reply-To: <CAC1wWD0OwFLqUD2uXnavBzfEw=HCRn3fGW54zYfxRozxp8HsyA@mail.gmail.com>

 Hi everyone,

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?

Believe me, would it be some junk I would not be pushing it here. I'm
42, I'm in software development since year 1995 and coding in C/C++ since
year 2000. I understand what kind of thing the C library is pretty well. In
my opinion there will be absolutely no harm to have some code people
would be free to include and redistribute while it is not used, or if
it is used in free software. And if they would want to make a
commercial product they will always have a choice to stay with
condvars or to pay a small premium to the author for using the
invention if they would see that benefitial for themselves. For
anything serious, benefits will greatly outweight those several cents
it will cost.

I could provide use examples with detailed explanations if you need
that. And I can also contribute to references/manuals.
I need a general decision: either "yes" or "no".

On Thu, May 31, 2018 at 1:10 AM, Oleh Derevenko
<oleh.derevenko@gmail.com> wrote:
> Hi everyone!
>
> So, as an update, the patent has been granted. I had to amend the
> claims as the initial ones in the application were not acceptable. You
> can view the final text from the search page
> (http://patft.uspto.gov/netahtml/PTO/search-adv.htm) having entered
> "PN/9983913" in the field there.
>
> My initial offer remains valid. I could release the thing for GPL. As
> for the rest, the idea is to license for something like 0.2% of
> product price; 0.01USD minimum; 1.00USD maximum; free for free
> software (including free exclusions of paid software for user
> groups/regions and similar free programs). I will work on exact
> wordings but this should describe the general approach and I believe
> it should be compatible with the principles you guys work by. If you
> find this acceptable I believe lots of software could benefit from the
> synchronization approach/objects I developed.
>
> The implementation sources were posted here on December 14th, 2017. I
> can re-send if they are not accessible for whatever reason anymore.
>
> Open for discussion and waiting for your commentaries.
>
-- 
Oleh Derevenko

-- Skype with underscore

  parent reply	other threads:[~2018-06-15 14:05 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 [this message]
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=CAC1wWD0u26uh7zdyB5+iE3HWcUvoUkrAJQc3-hLRVrqDRAqAPw@mail.gmail.com \
    --to=oleh.derevenko@gmail.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).