Selecting a Software Licence?
indraneil asks: "I am a code monkey and have been so for close to 5 years now. I have recently been doing some self-started work that lets me design, implement and test stuff all by myself. A couple of people have liked my prototype and wanted to use it. I would be happy to let others use it, but I am unsure of what license to release it under. My CS course did not include any awareness of licensing and while I am aware of GPL, LGPL, Apache, BSD and Creative Commons licenses, I never got around to understanding them well enough to be able to form an opinion on what suits me best. I notice that SourceForge also expects me to specify my licensing choice, while I am setting up my project. If a person doesn't know about software licensing, where should they educate themselves about the ins and outs, so they can properly choose the license that is right for their project?"
The short version:
BSD: Anyone can use your code, any way they want, as long as they mention your name.
GPL: Anyone can use your code, as long as they mention your name and allow others to use the code as you have let them use it.
LGPL: Same as GPL, but with some exceptions allowing others not to be bound to your licence if they don't actually touch your code in their project, but just use it.
Other licenses have variations on the above. In general I think most people should stick to one of those three, if for no other reason than to stop the confusion.
Pick the philosophy you like the best. That is the main point.
'Sensible' is a curse word.