Which open source license should I use for ssLinks?

[Skunk]

I'm releaseing version 1.2 of my open source links database PHP script ssLinks (http://www.sslinks.co.uk/) shortly, and I've decided to slap a proper license on it. Problem is I don't know which one to use.

The terms I want are standard open source thingy (i.e anyone can have it, modify it etc). I don't want people to be able to pinch it and pass it off as their own.

In addition I've got two voluntary things:

1. I'd prefer it if people left the "Powered by ssLinks" link on the pages generated by the script.
2. I'd prefer it if people told me where they are running the script so I can add it to the list on the site.

Obviosuly the voluntary things don't have to go in the license as they are voluntary.

So... which one would I be best off with? The GPL, LGPL or what?

Any advice would be most welcome,

Skunk

[aef]

Assuming your script is a stand-alone thing (as opposed to a library or module), you probably want the GPL. For a further discussion, see the pages about licensing on http://www.gnu.org/

AEF

[Godin]

you might wanna look at the artistic license (its listed on sourceforge somewhere :/) it has a clause to force people to keep copyright notices.

[Skunk]

I reckon I'll go for a standard GPL - LGPL seems a bit iffy and I couldn't find the artistic license.

[aef]

The LGPL is for libraries, really. The Artistic License is also good:

http://www.perldoc.com/perl5.6/Artistic.html

AEF

[Edited by aef on 10-05-2001 at 02:51 PM]