Before you use any software, RTFlicense. Even if you're using "approved" open source licenses you still have to pay attention to them. The dubious idea that some organization should be able to "approve" free/open/redistributable/royalty-free/whatever-you-call-it-this-week software licenses is a big part of the problem... it creates the illusion that so long as you use or apply an "open source" license you're done with the whole licensing thing.
RTFlicense.
I've run across companies violating the GPL, the original BSDL, even the modified BSDL, all quite innocently... they just took the code and used it. I've run into people using licenses with clauses they never intended to enforce because they didn't read them... or discovering that someone doing something they don't like with their software is perfectly in their rights.
Then you have people creating new licenses because they mistakenly think one of the licenses they use has requirements they don't like.
RTFlicense, and decide whether to use the software (or the license) because of what it actually says... not because it's "approved".
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
