in reply to ~OT Licens(?:es)|(?:ing)
For most small projects (modules in particular) the standard blurb of 'This project is licensed under the same terms as Perl itself' should suffice.
However, if you're planning anything larger than a module, I encourage you to use one of the GNU licenses. While there's no case law currently backing them, they were written with the assistance of law professors and should be fairly solid. The enforcability of the artistic license on the other hand, has been questioned many times. From Bruce Perens essayon the open source definition...
It is, in my opinion, a sloppily-worded license, in that it makes requirements and then gives you loopholes that make it easy to bypass the requirements. Perhaps that's why almost all Artistic-license software is now dual-licensed, offering the choice of the Artistic License or the GPL.
Section 5 of the Artistic License prohibits sale of the software, yet allows an aggregate software distribution of more than one program to be sold. So, if you bundle an Artistic-licensed program with a five-line hello-world.c , you can sell the bundle.
He goes on to list a couple more flaws in the license. Definately worth a read for those who are considering licenses.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: ~OT Licens(?:es)(?:ing)
by metadoktor (Hermit) on Mar 23, 2002 at 02:16 UTC | |
by cjf (Parson) on Mar 23, 2002 at 10:53 UTC |