4 ms·
Am I the only one who never care about licenses? It says "free" so I download it. What is the worst thing that can happen?
by Kiro 13y ago
Am I the only one who never care about licenses? It says "free" so I download it. What is the worst thing that can happen?
- pearjuice 13y agohttps://www.gnu.org/philosophy/free-sw.html https://www.gnu.org/philosophy/free-sw.html
- taspeotis 13y agoYeah some not-so-diligent person added some "free" code to our commercial, closed-source application. "Free" as in GPL2. Ripped that out pretty quickly.
- rahimnathwani 13y agoDid you 'rip it out' in the sense of rolling back the commit, or did you refactor the code (and replace the GPL2 code with code that did the same/similar thing)? If it were the latter, would your entire codebase be considered a derivative work (just as if I took some GPL2 code and refactored it until all the original code was gone)?
- Trufa 13y agoFor some reason, I had never read the GNU definition of free software. Very interesting thanks! One question though, did I understand it correctly or have a got it wrong: I can make a free software (free as in speech), and charge you X amount of money for it, but it is within your right to sell it to the next person as long as you keep the freedom to modify etc?
- jshen 13y agoYou can get sued.
- oafitupa 13y ago"Free" for what? You need a license because you want to know exactly what you can and can't do, especially if you are a company. And it better be a well known license, that has stood in trial. The worst thing that can happen is going to jail or having to repair whatever damage they claim you have caused. Though it's very unlikely in your case and for this library.
- eggbrain 13y agoAs an individual with personal projects, probably nothing bad will ever happen even if you mangle licenses to their fullest extent. The issue becomes when you then decide to build something commercial with photos/libraries/etc that have non-commercial/attribution features to them. If I wanted to use this theme to build a Startup, it could become very enticing to companies to target litigation against me. Above and beyond litigation, it could be a PR nightmare if press found out I had built something on top of code that I wasn't allowed to use. Think of all the questions it would raise -- well if he used non-commercial code commercially, what if he had stolen code from other places? It also lends a sense of credibility to the project/photo/download in that the author thought about the way that his creation was to be used. We used a "free" open source iPhone mockup that seemed perfectly legitimate, and implemented it into one of our client's websites. A few months later, Getty Images had detected that a commercial copyrighted image had been used in the background of the iPhone mockup and sent a litigation letter to our client demanding payment. It was an expensive lesson for us to learn that just because something says it's one thing doesn't mean we can take them at their word.