4 ms·
I agree in some sense. My issue is pulling the trigger to fast and too hard, and there doesn't seem to be a good answer to that. Even though I do my best to fo
by dizzystar 9y ago
I agree in some sense. My issue is pulling the trigger to fast and too hard, and there doesn't seem to be a good answer to that.
Even though I do my best to follow licenses, I may be making a mistake somewhere. If I heard a case where was sued for $1M to a GPLv2 software, I'd strongly consider moving over to a propriety product and pay $10 a month to mitigate my risk.
Remember that every uninstall is one less user, which is one less incentive to maintain the product, and once that gets close to zero, it's game over.
- pbhjpbhj 9y agoIf you heard of a case where someone without a driving license was punished, would you - having done your due diligence to get a license and conky with its requirements - get worried you also would be punished and so choose to always take taxis? Are these non-compliant companies using cracked versions of other closed-source software? I'll bet they pay for their MS licenses, because they know MS will sue them if they don't.
- dizzystar 9y agoOf course there are companies using cracked versions of software. We also know kids use all sorts of cracked software as well. The reason they don't get sued is because the companies know that it is bad blood to sue. They know that, in the future, these kids will be running offices and they will buy that software they loved. Granted, the goodwill ends up with money coming in, but it's the same theory with open source. Most large projects are backed by companies that earn millions. The idea of a single dude doing free work is often times a myth.
- boomlinde 9y ago> Even though I do my best to follow licenses, I may be making a mistake somewhere. There are plenty of resources available on how to comply and how to setup a process to minimize this risk. Simply dump all the versions and licenses of third party software you use to a file and accompany your distribution with a written offer to share the source code or links to their official repositories if they are unmodified. > If I heard a case where was sued for $1M to a GPLv2 software, I'd strongly consider moving over to a propriety product and pay $10 a month to mitigate my risk. You're considering this from the perspective of an end user? Let me clarify that the limitations of GPLv2 kick into effect once you distribute software. As far as respecting copyright goes, you can use GPL software and modify it freely without any legal forethought. It's when you distribute such software that you'd get in trouble by not also sharing the source code. In fact, this is better for the consumer, who will be able to use the bundled GPLv2 licensed software without buying the product. > Remember that every uninstall is one less user, which is one less incentive to maintain the product, and once that gets close to zero, it's game over. This implies that the amount of users is the only incentive when it really is not, For one, some users are more important than other users. Companies like Intel, Google, IBM, SUSE, Red Hat and AMD are important users in that they also make significant contributions to the kernel for their own benefit. There is a huge incentive for these to contribute back even if they don't need to distribute their changes because getting it into the mainline kernel simplifies maintenance. Whether some Shenzhen set top box that violates the GPL uses Linux doesn't make a difference. If anything, their continued illicit use detracts from the credibility of the license and discourages contributors that give a hoot about people respecting their individual property and the overall philosophy of free software. Then, particularly for smaller projects than the kernel, there are the individual contributors who are usually users of the software they contribute to. I think you've maybe made the connection "users == customers" where there is none. In those terms, companies that ignore free software licenses are simply pirates.