@ 10/05/2004 16:26 : wrote Benjamin Cutler :
I was giving a little thought to a library I might write, and was
thinking of a few things that would concern me about its use. I whipped
up a quick license governing its use. I'm thinking that it's still
DSFG-free because it allows a choice, one of which is the GPL, but I
thought I should run it by here first just in case. The library itself
would be GPL.
I don't like your license, but I think you're right... but... You tried
to specify the license of programs linking to (using?) your library...
but forgot to permit free (re-?)distribution/modification of the library
itself, which renders the library non-DFSG-free...
It just proves that making up licenses is hard :-)
A better option IMHO is to license your library under the GPL. Any other
terms can be worked out with you (see #3 below)
---start license
Programs using this library fall under one of the following license
terms: (choose one)
1. Distribution must be consistent with all terms of the GNU GPL. (The
primary concern being that distributing the program must include an
offer of source code, whether or not you're selling the program or
giving it away for free.)
2. You may distribute your program in a pre-compiled form, WITHOUT
releasing source code, but you MAY NOT charge for its distribution
whatsoever. You must also include notice of the use of this library
somewhere in your credits or documentation.
If the person makes modifications to the library, what's up?
3. If you wish to SELL your program or otherwise charge for its
distribution, and NOT include the source code and/or otherwise make it
non-freely redistributable, licensing terms must be worked out with the
author of <the library> in advance.
---end license
This one is a no-op... IF you are the sole copyright holder of the library.
--
br,M
