Near Public Domain license

Jean-Marc Lienher jml at
Thu Jul 26 15:32:23 UTC 2007

> And where would you place such a license, if not in the sources or
> with the binaries?  I am not a lawyer, but I do believe that reason

The license must be in the sources and in a README with the binaries,
otherwise it is not OSI compliant.
But I want to allow derivative works or copies to be closed source.
I create Open Source software, but I don't care if other people don't.
It's like "Public Domain".

> The license approval process itself costs no money at all.  However,
> as you recognize, you may need to spend money on legal advice to
> ensure that the license you submit does the things you want it to do.

No, it's not only a legal advice for me. It is part of the approval process.

The OSI approval process requires :
"Create a legal analysis of the license as it complies with the terms of the
Open Source Definition. Each paragraph of the license should be followed by
an explanation of how the paragraph interacts with each numbered term of the
Open Source Definition. The analysis should come from a licensed
practitioner of the law in your country."

It's not 10 minutes work for a lawyer who musts learn about the OSI
I'm a geek, not a "practitioner of the law" so I can't do it myself.

More information about the License-discuss mailing list