From: manningc2@actrix.co.nz
To: "Graeme Sheppard" <nodes@rillion.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Patent or not patent a new idea
Date: Tue, 26 Jun 2007 10:37:12 +1200 (NZST) [thread overview]
Message-ID: <9362.218.101.54.21.1182811032.squirrel@218.101.54.21> (raw)
In-Reply-To: <46803772.7020408@rillion.net>
> Dear devs,
>
> In a moment of serendipity I thought of a concept which may be
> advantageous
> if incorporated into the kernel. I was going to offer it to the OIN but
> they responded they only consider existing patents and I don't have the
> money to afford one.
>
> I am seeking advice on how to proceed. It could be used as a defensive
> patent in which case I can email an expert who can file it. If that is the
> concept is sound. I am not expecting any royalties from this myself. The
> alternative is to dump it here to the LKML.
If your only purpose is to try generate a defensive patent, then just
dumping the idea in the public domain serves the same purpose, probably
better.
I have a few patents, some of which are defensive. That has not prevented
the USPTO issuing quite a few patents that are in clear violation of mine.
A defensive patent clearly did not prevent these patents from being
issued. A defensive patent might make it slightly easier to protect
yourself should one of the later patents try flex their muscle, but an
idea that is well articulated in a public forum should be sufficient
protection too.
AINAL and all that...
next prev parent reply other threads:[~2007-06-25 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 21:45 Graeme Sheppard
2007-06-25 22:04 ` alan
2007-06-25 22:26 ` Graeme Sheppard
2007-06-25 22:33 ` alan
2007-06-25 22:34 ` Attila Kinali
2007-06-25 22:37 ` manningc2 [this message]
2007-06-26 0:11 ` Bryan Henderson
2007-06-26 1:32 ` Graeme Sheppard
2007-06-26 2:20 ` Neil Brown
2007-06-26 3:20 ` Graeme Sheppard
2007-06-26 3:38 ` Neil Brown
2007-06-26 4:22 ` Graeme Sheppard
2007-06-26 4:33 ` Neil Brown
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=9362.218.101.54.21.1182811032.squirrel@218.101.54.21 \
--to=manningc2@actrix.co.nz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nodes@rillion.net \
/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
all inboxes | Powered by JetHome®