From: greg misiorek <greg_not_so@hotmail•com>
To: Peter Todd <pete@petertodd•org>, <bitcoin-dev@lists•linuxfoundation.org>
Cc: defensivepatent@gmail•com
Subject: Re: [bitcoin-dev] Defensive Patent License Offer Notice
Date: Thu, 13 Oct 2016 09:03:45 -0400 [thread overview]
Message-ID: <BLU407-EAS131B6644332EB36C06C5780B1DC0@phx.gbl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2589 bytes --]
Interesting and thx for sharing what a DPL is.
gm
________________________________
From: Peter Todd via bitcoin-dev<mailto:bitcoin-dev@lists•linuxfoundation.org>
Sent: 10/13/2016 4:51 AM
To: bitcoin-dev@lists.linuxfoundation.org<mailto:bitcoin-dev@lists•linuxfoundation.org>
Cc: defensivepatent@gmail.com<mailto:defensivepatent@gmail•com>
Subject: [bitcoin-dev] Defensive Patent License Offer Notice
Also published at https://petertodd.org/2016/defensive-patent-license-offer,
and Bitcoin txid b4bf94f5c457d080924aa163106d423670373cfe3b10f8ec00742c2234b01b72
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I, Peter Todd, hereby declare myself and all technology companies that I
control as "Defensive" by committing to offer a Defensive Patent License,
version 1.1, for any of my patents either existing or future, to any DPL User.
Neither I nor any companies that I control have any patents at this time.
My contact address is pete@petertodd•org
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJX/t11AAoJEGOZARBE6K+yR00H/0xp3oO7FiMvM4pjfoHZPPOa
m3KjT4RSbFQLa9uniz0u/9bkc5I70CggkY3jtNLtDMbMBTwcMP61ABsvx+5y2gGD
zE6VZ9DPcHVg/Eup6WSBlQO3HQKuFVz7vXSMuaidG7A+fpkU71SjDpB4M6hdvWnS
+L9XBQ1GtQe0lSM73s4mld/IvB1giwPN1bOheQ9koYcQjj+B8PWyt2gIUwctxyvA
7bC+KtCQT4RJPsQHbHx569CDkyIi3dNt0rTjCo5bOeUKrJF7eA3YktYdTJefZ+Rf
00dbRZMslrg3dW9VWECfC0xC/kn+heStJ7WqJJKqYWo4apm6IiKPZxlwIcVscF0=
=xrPk
-----END PGP SIGNATURE-----
# Notes
* On the advice of my lawyer, I'm currently offering only a specific version of
the DPL. I probably will offer licenses under subsequent versions in the
future, but I'd prefer to see how the DPL evolves and whether or not the
license stewards behind it prove trustworthy before committing to doing so.
* The language "all technology companies I control" is there to avoid any
complications with non-technology companies that I may control in the future,
e.g. family real-estate holding companies, and the non-profit caving group
I'm a part of. To my knowledge, I only control one company as of writing, the
numbered company I do all my consulting through; I consider that company a
"technology company", and thus the above offer applies to it.
* Equally, if by some stroke of luck I do end up in control of any other
technology companies - maybe Bill Gate's blockchain smart-contract will
mysteriously gives me control of Microsoft - then the above offer will apply.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #1.2: Type: text/html, Size: 4382 bytes --]
[-- Attachment #2: Type: text/plain, Size: 174 bytes --]
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists•linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next reply other threads:[~2016-10-13 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 13:03 greg misiorek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-13 8:51 Peter Todd
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=BLU407-EAS131B6644332EB36C06C5780B1DC0@phx.gbl \
--to=greg_not_so@hotmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=defensivepatent@gmail$(echo .)com \
--cc=pete@petertodd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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