5 ms·
I've actually had discussions with several people, separately and at a legal summit that specifically discussed the topic of software liability, that proposed a
by JoshTriplett 9y ago
I've actually had discussions with several people, separately and at a legal summit that specifically discussed the topic of software liability, that proposed a good solution to this:
Make the liability proportional to the degree to which you've given them the degree to find and fix any issues that might arise. If you give someone FOSS software to solve some particular problem, even a potentially-high-liability problem, you've given them everything they need to both analyze the software for potential issues, and fix them themselves. (Auto manufacturers like FOSS because it means they can always support it themselves if the vendor won't, and they have far longer support lifetimes than many other products.) So disclaiming all liability there seems reasonable, for anything short of intentional malice (e.g. backdoors).
On the other hand, if you give someone a piece of opaque proprietary software, then you're selling them a solution to a problem, and it'd better work because they can't do anything but go to you if it doesn't. They also can't introspect it, and black-box testing only goes so far. So this should increase liability. Even more so if you supply it in an obfuscated form that's difficult to reverse-engineer or test, or if you lock it down to make it irreplaceable.
The same thing would go for changing software yourself, on a high-liability device. If you don't change it, it's not your fault; if you change it, it might be your fault.
- sitharus 9y agoNew Zealand consumer law has a requirement that goods must be 'fit for purpose'. This means that if a company sells you a clothes washer for example it must clean clothes, but if you try to wash your shoes and it breaks it's not the manufacturer's fault (unless they said it could of course). I think something like this could apply very well to software. If someone uploads source code to github they haven't sold it to you with any purpose in mind, but commercial sales have functionality promises so they could be held to them.
- DannyBee 9y agowarranty of merchantability and fitness for a particular purpose exist in the US. Whether it can be disclaimed is per-state though. (Some states allow disclaiming implied warranties, some do not).
- stephengillie 9y agoAnsible has disclaimed theirs[0]: > #!/usr/bin/env python # (c) 2012, Michael DeHaan <michael.dehaan@gmail.com> # This file is part of Ansible # Ansible is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. # Ansible is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. # You should have received a copy of the GNU General Public License # along with Ansible. If not, see <http://www.gnu.org/licenses/> http://www.gnu.org/licenses/>. ############################### [0]https://github.com/ansible/ansible/blob/devel/bin/ansible https://github.com/ansible/ansible/blob/devel/bin/ansible
- JoshTriplett 9y agoThat's a standard part of the disclaimer for the GPL and other licenses.
- DannyBee 9y agoI think you misunderstand. What i'm saying is, if sold by ansible to a consumer, these disclaimers are completely ineffective in a bunch of states. The UCC (which is what governs these transactions) is model legislation, and provides for a few options that states can choose in various parts. One option allows disclaimer of implied warranty in all transactions. One option allows disclaimer of implied warranty in all transactions except those with consumers. One option disallows disclaimers of implied warranties. Depending on which option a given state chose, the language you are citing would have different effectiveness.
- closeparen 9y agoWhy hasn't the open source community figured this out? Seems like a bad idea to ever distribute source code at below the cost of liability insurance. Or should we be geo-restricting open source software? "Sorry, Linux is not available in your state." Thanks for pointing this out. I imagine most people who publish open source software aren't aware of this risk, and will stop when they learn about it.