View Single Post
Old 04-21-2009, 05:43 PM   #17 (permalink)
itsnotabigtruck
you lost the game.
zB Programmer
Moderator
Elite Zuner
 
itsnotabigtruck's Avatar
 
Join Date: May 2008
Posts: 2,434
itsnotabigtruck has much to be proud ofitsnotabigtruck has much to be proud ofitsnotabigtruck has much to be proud ofitsnotabigtruck has much to be proud ofitsnotabigtruck has much to be proud ofitsnotabigtruck has much to be proud ofitsnotabigtruck has much to be proud of
Default

You clearly don't understand the fundamental concept of open-source. What you did is release the source; while this is obviously necessary to make your program open-source, it isn't the whole story. It's kinda like how you need the Internet to win a presidential election (e.g. Obama), but you can't win an election with just the Internet (e.g. Ron Paul).

In order to be open-source, your program's license needs to comply with each and every item in the Open Source Definition from the OSI. This definition requires that you allow many of the things you're explicitly forbidding with your current terms. You would definitely be best off by using a popular license that has been certified as open-source, like the GPL or the BSD license. It's easy, well-understood, and you don't have to worry about unintended consequences. You can write your own if you really want to, but it's going to need to be way different from what you've got now.

Also, copying and pasting legalese from elsewhere is generally a bad idea - it tends to be inappropriate, verbose, and confusing. A better way to state that you provide no warranty is to say it straight up: "Your use of this software confers no warranty whatsoever, be it express or implied." There's also less formal ways of saying it, such as "This program is not guaranteed to do, or not do, anything. If it kills your dog, totals your car, or just plain doesn't work, tough."
__________________

signature by vettexl




itsnotabigtruck is offline   Reply With Quote