Copyright Protection Problems For OSS Project
An anonymous reader writes "There's a federal case in the Northern District of California where copyright for open source is being challenged. The free software project JMRI discovered that a commercial company was
using some of their files in a product, in violation of the license. They added a copyright claim to an ongoing legal action about cybersquatting, software patent abuse, etc. The patent case was covered on Slashdot back in June but the copyright part is new. The other side came back with an argument that copyright law didn't apply, simply because they software was 'being given away for free.'"
They absolutely need to agree to a license (not sign a contract) to use the software. The terms of the license say that you have the traditional rights granted by copyright (which means you're not allowed to copy someone else's original work), but that *if* you comply with the terms of the license, they'll grant you the right to redistribute, modify, etc.
One of the conditions in the terms of the license is that you aren't allowed to *change* the terms of the license in a number of ways. If you do, then those rights are rescinded, and you go back to only having the rights granted under copyright law (which means, you have to ask my permission to do anything with it).
You said (in part):
You're bound by the terms of the license that the software is distributed under. The person who distributed the software to you did so with the knowledge that there were certain things that had to be done to be in compliance with the license. One of those things is to make sure that the license is distributed with the software, so that it's clear what's allowed and what's not.
If you received the software without the license (i.e. the person who distributed it failed in their duties to comply with the licensing requirements), then that doesn't mean you are allowed to ignore copyright law or that your copy is magically license free. Just ask the folks at the BSA about that. Millions of illegally-licensed copies of Windows are installed and used every year, and there are very real penalties for knowingly doing so.
You also said:
If the contract was for support, then they paid for support. The license is a separate thing...it covers under what conditions you may use the software under, not whether you will receive support.
You mentioned that you wouldn't be bound by that agreement (the support one) any more than redhat would be bound to give you support. True, since you didn't enter into a support contract with them (although you could do so very easily). You then mentioned that:
This almost true, since you would be bound by the terms of the license of the software you received, not by a contract signed directly with a particular company or person. Traditionally, copyright was the only legal condition allowed for distributing a work, but the GPL is becoming common, and allows more freedom. The GPL says (in part):
The only reason you are *ever* allowed to redistribute is because of the license. If you don't accept the terms of the license, there isn't anything else that magically gives you distribution rights. It doesn't matter if you got it direct from RedHat, or from some guy in a van behind a seedy building, the only rights you have are copyright and the license the work is distributed under. Copyright gives you certain fair-use rights, none of which would apply to you distributing someone else's software.
"Murphy was an optimist" - O'Toole's commentary on Murphy's Law