%PDF- %PDF-
Direktori : /proc/self/root/usr/share/licenses/python-crypto/LEGAL/copy/stmts/ |
Current File : //proc/self/root/usr/share/licenses/python-crypto/LEGAL/copy/stmts/Robey_Pointer.asc |
Date: Mon, 16 Feb 2009 12:58:00 -0800 From: Robey Pointer <robey@lag.net> Subject: Re: PyCrypto license clarification To: "Dwayne C. Litzenberger" <dlitz@dlitz.net> Received-SPF: pass (goedel.dlitz.net: domain of robey@lag.net designates 69.61.78.186 as permitted sender) Message-Id: <F469A078-6305-4484-BEA8-F4EC38A4154F@lag.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23 Nov 2008, at 07:42, Dwayne C. Litzenberger wrote: > For the next PyCrypto release, I would like to take steps to move > toward a clearer licensing regime. I am asking as many copyright > holders as I can find if I can release PyCrypto under something > clearer and more standard. Below, I have quoted a public domain > dedication that was recommended in _Intellectual Property and Open > Source: A Practical Guide to Protecting Code_, by Van Lindberg. I > have already contacted A. M. Kuchling, and he has approved the > following dedication for his contributions. > > May I, on your behalf, dedicate to the public domain all your > contributions to PyCrypto, with the following notice? > > > = > ====================================================================== > The contents of this file are dedicated to the public domain. To > the > extent that dedication to the public domain is not available, > everyone > is granted a worldwide, perpetual, royalty-free, non-exclusive > license > to exercise all rights associated with the contents of this file > for > any purpose whatsoever. No rights are reserved. > > = > ====================================================================== > In case I haven't replied to this yet: Yes, this is fine with me. robey -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmZ01gACgkQQQDkKvyJ6cOLvQCfQmYYuVODvIlyLg0hgCI9LAbQ SH8AoLJgaq1lIi7/ZYDc+/Cd8VO0xLbr =Mv6g -----END PGP SIGNATURE-----