Near Public Domain license
DShofi at atmi.com
DShofi at atmi.com
Thu Jul 26 15:01:51 UTC 2007
I find it quite unbelievable that a clear and unequivocal statement that
an original copyrighted work is dedicated to the public would not serve to
provide the necessary rights to anyone choosing to use the work in an OSS
project, regardless of the OSS license used by that project. That being
said, like all software, a recipient of the work would want to do some due
diligence to understand that the author actually wrote the work from
scratch without reliance on another work that may itself be copyrighted by
another. In other words, I would think that the public domain is an
acceptable manner of putting your work out there for others to copy,
modify and distribute. You may want to include a statement about the
pedigree of the code to allay concerns as described above.
Of course, you should engage with your own attorney if you want to be sure
of your rights... :)
Good luck!
David M. Shofi
"Jean-Marc Lienher" <jml at whoow.org>
07/26/2007 09:13 AM
To
<license-discuss at opensource.org>
cc
Subject
Near Public Domain license
Hi,
Sorry if this is a FAQ, but I've not found any searchable archive of this
list.
I need a very permissive license, Public Domain is a option but I've found
that it is OSI incompatible.
( http://linuxmafia.com/faq/Licensing_and_Law/public-domain.html )
Is there any such license already available ?
Zlib is nice. But the
"If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required."
sentence is too much.
I don't want any acknowledgement on which I don't have any control.
And the Zlib disclaimer looks very short compared to the MIT/BSD.
I don't like the BSD because you must put a copy of the license in the
documentation or in a README.txt file.
I don't like the MIT because the license must be included in the binaries.
I've just seen a message talking about a simplified BSD license, but I
can't
find it on the archive. (there is nothing after march 2007
http://www.crynwr.com/cgi-bin/ezmlm-cgi?ddp:0:0#b )
Does this simplified BSD license fits to my needs ?
I wrote my own license, which is a mix between MIT/BSD/ISC licenses with
zero condition.
Here it is :
-----------------------------------------------------------------------
Copyright (c) <year> <copyright holders>
Permission to use, copy, modify, sublicense, and/or distribute this
work for any purpose with or without fee is hereby granted.
THE WORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS WORK.
-------------------------------------------------------------------------
But it looks like the approval process will cost me a lot of money.
I need to find a English speaking lawyer in my country to create the legal
analysis...
So if there is an other license, which is currently in the approval
process,
and which is compatible with my needs, I will use it.
*************************************************
This email message may contain information that is confidential and/or
privileged and is intended only for use of the individual or entity named
above. If the reader of this message is not the intended recipient, or
the employee or agent responsible to deliver it to the intended recipient,
you are hereby notified that any dissemination, distribution, or copying
of this communication is strictly prohibited. If you have received this
communication in error, please notify sender immediately and destroy the
original message. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20070726/ea10e811/attachment.html>
More information about the License-discuss
mailing list