in reply to ~OT Licens(?:es)|(?:ing)

I too tend to avoid licensing issues. I mean, it's free code. What the hell do i care what you do with it, right?

Well, then i realized that someone might turn around and use my code maliciously, roll it up and smoke it, sell it to a minor, etc. So, i think an important addition to your license might be something along the lines of:

I like giving away free software - and i would sure hate to be a victim of that.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Replies are listed 'Best First'.
Re: (jeffa) Re: ~OT Licens(?:es)(?:ing)
by cjf (Parson) on Mar 22, 2002 at 17:34 UTC

    The standard disclaimer is something resembling this:

    (your program name) comes with ABSOLUTELY NO WARRANTY; for details, see the LICENSE file. This is free software, you are welcome to redistribute it under certain conditions; for details, see the LICENSE file.

    When choosing a license you should also consider two things:

    • Do you mind if someone takes your code, improves it and then doesn't release the changes?
    • Do you mind if someone takes your code, compiles it, and starts selling it to people without giving them the source code, or otherwise restricts the buyer from having equal rights as you gave the seller?

    If either of these bugs you, I recommend using one of the GNU licenses. For more information on free software licenses, please consult this.

[reply]
Re: (jeffa) Re: ~OT Licens(?:es)(?:ing)
by belg4mit (Prior) on Mar 22, 2002 at 20:37 UTC
    indemnity. Though perhaps grant would be a better word choice than accept.

    --
    perl -pe "s/\b;([st])/'\1/mg"

[reply]

In Section Meditations