From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Oleh Derevenko <oleh.derevenko@gmail.com>
Cc: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Tue, 19 Jun 2018 13:09:00 -0000 [thread overview]
Message-ID: <a3175628-e41f-b4f5-d2fc-d4facacdab2b@linaro.org> (raw)
In-Reply-To: <CAC1wWD2hF7AJhaSse47NKqaJYabR=jJpt9dwikGz3hi6DVd7pg@mail.gmail.com>
On 19/06/2018 09:42, Oleh Derevenko wrote:
> Adhemerval,
>
>
> On Tue, Jun 19, 2018 at 3:07 PM, Adhemerval Zanella
> <adhemerval.zanella@linaro.org> wrote:
>
>>> Regarding the note of DJ Delorie -- the patent covers the
>>> synchronization method (the approach), not a particular
>>> implementation. You will not be able to create an implementation of
>>> yours without violating the patent anyway. So, don't worry about the
>>> effects of looking in the code.
>>>
>>> That said, I understand that my idea is not going to be accepted at
>>> this time. I would like to apoligize for you time I have taken. In
>>> case anyone is going to change their opinions on the matter feel free
>>> to contact me.
>>
>> To be clear: it is not your idea that is being rejected, but rather
>> your imposing rules we need to accept so you can disclosure your idea.
>
> All the patent texts (except for those that contain sectecy matter)
> are publicly available from the USPTO or similar corresponding
> national/international patent management offices. In particular, there
> is a search form at the USPTO website you can use to view any present
> or past patents and published applications. The sole idea of patents
> is to create and save descriptions any other skilled individuals can
> later use to re-create the inventions. Just, an exclusive use period
> is granted to authors as a reward for their binging the inventions to
> public. Later, after patents expire, they can (and should) be used to
> advance everyday life of all the humanity (or other more humble
> purposes -- whatever they are good for). In my opinion, most of the
> patents in the database are good for nothing and are just wasted
> money. Or they can be treated as enforced losses businesses have to
> take due to the competitive environment they exist in. But sometimes
> there are things that are worth the application/maintenance fees paid.
>
> So to resume, there is no problem in disclosing the idea. And it
> already was disclosed here and is permanently being disclosed at the
> USPTO website. I posted a link to it.
>
I am far from Copyright and patent expert and correct if I am wrong,
but my understanding is for GNU projects all your description does not
mean anything if you, the one holding the patent, do not sign a
Copyright assignment for FSF so any projects which the idea or code
derived from it are protected for Copyright enforcements by third
parties (you inclusive).
next prev parent reply other threads:[~2018-06-19 13:09 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
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 [this message]
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=a3175628-e41f-b4f5-d2fc-d4facacdab2b@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=oleh.derevenko@gmail.com \
/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).