7 ms·
One more small step toward the right to software repair
- ComradePhil 5y agoI don't think GPL will help in the software repair space, at all. If they are able to get Vizio to distribute their source code for this, I forsee Vizio just doing a clean room rewrite to move away from the codebase... and even more companies will never touch anything GPL with a 10-foot pole. Software repair will come from different kind of regulations, not from bullying companies for not being careful with software licenses. (Sidenote: if you use GitHub, the Insights page can help you find out whether one of your dependencies use GPL, so that you can seek alternatives).
- Mystlix 5y agoI might be mistaken, but at least in Europe (but I believe it's the same case for the US) reverse engineering proprietary software in order to fix critical bugs, add necessary features or port it somewhere else out of necessity is allowed, provided you don't share the modified program. Of course being able to share your fixes would be great, but in a sense Software Right to Repair already exists and is in a much better shape that the Hardware's one
- progbits 5y agoThe problem is that most people who would need and benefit of those changes don't have the time or skill to make them themselves. So being able to share and distribute the modified version is an absolute bare minimum for the right to repair.
- Proven 5y ago
- White_Wolf 5y agoYou made me wonder if sharing a patcher that modifies the program files would be legal under the EU law.
- noduerme 5y agoIANAL but sharing the patcher probably wouldn't be. Sharing the code it patched, or a patched version of that code, would be piracy.
- Mystlix 5y agoSorry, what farmer has the ability to repair a design problem in an engine? In reality the vast majority of fixes are just temporary patches using materials that quickly degrade and need to be constantly replaced.
- Robotbeat 5y agoMore than you think. Farmers often know how to weld, etc.
- noduerme 5y agoHiring your own people to branch and maintain the software for your own purposes is not "distribution". If you're a company relying on software you don't own, and you need it to do something different, you can hire coders to maintain it in your direction. That's totally different from reselling it.
- pabs3 5y agoWhen the people you are hiring are an external contractor, that probably counts as distribution though.
- noduerme 5y agoNo, I don't think so. If the company has the right to edit the code, then it can contract that out. If someone paid the company to clone or use the code, that would be distribution.
- pabs3 5y agoFrom the FSF's GPL FAQ: However, when the organization transfers copies to other organizations or individuals, that is distribution. In particular, providing copies to contractors for use off-site is distribution. https://www.gnu.org/licenses/gpl-faq.html#InternalDistribution https://www.gnu.org/licenses/gpl-faq.html#InternalDistributi...
- noduerme 5y agoFor use off-site. Hiring a programmer off-site to maintain it isn't "use". Giving it to someone to use in a productive way in furtherance of your business or in exchange for money would be "use".
- Jiro 5y agoDistribution matters because it triggers legal consequences--you need a license to distribute. The FSF can't rewrite the law. So they can't say "doing X is distribution" and then claim that doing X requires a license. So whether the FSF calls something distribution in their own FAQ is irrelevant, unless the FSF is your lawyer and giving you legal advice.
- denton-scratch 5y agoQuite. Being allowed to fix the OS yourself, but not share the result, is like being allowed to fix your car yourself, but being forbidden to set up business as a mechanic-for-hire. I used to be able to fix a Morris Minor; but I wouldn't dream of trying to fix anything but the bodywork on a modern car.
- pabs3 5y agoIn the EU it sounds like the modifications allowed are limited to "within its intended purpose", which could block some modifications, although it would be hard to discover modifications you made locally without sharing them. https://en.wikipedia.org/wiki/Computer_Programs_Directive https://en.wikipedia.org/wiki/Computer_Programs_Directive Wikipedia says that software ToS can override the legality of reverse engineering in the USA: https://en.wikipedia.org/wiki/Reverse_engineering#Legality https://en.wikipedia.org/wiki/Reverse_engineering#Legality It also sounds like in the US the modifications allowed are only for circumventing DRM, and only for interoperability, not for adding features or fixing bugs.
- Terry_Roll 5y agoIn Europe, I understand it as only legal to reverse engineer to fix bugs, thats it. Now Copyright is a bit more difficult, because the process of reverse engineering code to fix a bug can also mean copyright can be discovered, ie learning how something works, like a driver for some hardware to work in an operating system or app.
- 7steps2much 5y agoYou are allowed to add necessary features or port the software as well. Of course, what counts as a "necessary feature" is always up to debate, but if you for example own a software that only runs on Microsoft DOS and you want to port it to Windows 10, that's allowed. Also, as far as copyright/patents are concerned those aren't a Problem with reverse engineering. If you reverse engineering something and you then discover copyrighted code while fixing a bug that's not a problem. Knowing of that code is not copying it. If you were to copy that code or use knowledge you gained by reverse engineering to build your own product that would be an issue though.
- Terry_Roll 5y agoI dont think I've ever sold software, just a licence to use said software, so I think my old dos programs will be safe. > If you were to copy that code or use knowledge you gained by reverse engineering to build your own product that would be an issue though. And thats the hard part, how do you prove a thought process existed before you had your thought confirmed by seeing it used in some code that you are reverse engineering? Even if I had written such thought down, proving the date & time on the piece of paper isnt back dated is also tricky.
- foxfluff 5y ago> In Europe, I understand it as only legal to reverse engineer to fix bugs, thats it. Yep. AIUI doing such things as reverse-engineering to analyze malware (or to detect otherwise malicious behavior, such as breaches of GDPR) is not permitted.
- noduerme 5y agoThis is true in America as well. You stated it exactly. The recipient of a binary or a set of scripts who has a right to use them in production also has a right to repair them, just not to distribute them. I don't understand what contract law has to do with this case. I was actually mildly alarmed to hear that they think using GPL software somehow enters them into a contract. If I read it correctly. That could become quite nasty and be very bad for FOSS if a court upheld the idea, since it's often corporations relying on FOSS and not the other way around.
- pabs3 5y agoThe article clearly states that the GPL is both a license and a contract: But many lawyers have advised us that contract law is a useful parallel avenue. This approach has the advantage of empowering users of the software who are not necessarily copyright holders. The mantra of “the GPL is not a contract” is a mistruth that has been so often repeated that it became widely accepted and typically unchallenged. (We expect you'll hear this theory repeated even more loudly now that the our Vizio lawsuit brought the question to the forefront in a federal court case.) Yet, prominent legal experts outside of FOSS social circles have long scoffed at the assertion. Indeed, case law in the USA has held the opposite. In multiple cases, courts have been convinced, specifically, that the GPL operates as both a contract and a copyright license. The law appears clear on this, and this is among the reasons why we believe our motion to remand will succeed. In short, we'll say it plainly here and now for everyone: the GPL operates both as a copyright license and as a contract; litigation can proceed under either of those legal theories. Our motion to remand in the Vizio case explains the legal details as to why that's true.
- jevoten 5y agoTo see the absurd legal overreach of these laws, write "examining how it works" instead of "reverse engineering".
- MaxBarraclough 5y ago> [...] allowed, provided you don't share the modified program Would it be legal to share the binary diff of the fix, provided it contained none of the original binary?
- galaxyLogic 5y agoI think dual-licensing is a good solution. Customers who want to profit from your software will purchase a "shared source" license. Customers who care for Open Source will use and detect bugs in the copyleft licensed version. "Software Repair" is a feature, not a God-given right. And isn't it always better if the maintainers of the software do it for you so you don't have to do it yourself? If they do it it will benefit others besides the single do-it-yourself software repairer. In practice I think only the maintainers of an open sourced software will actually fix bugs in it, although many users may report bugs. Therefore there needs to be some mechanism which promotes the flow of financial incentives to the maintainers of open source software. Dual-licensing would seem to be a solution. Give the bug-fixes and improved features, usability and performance improvements to paying customers first. If there are security problems those should of course be expeditiously shared with everyone.
- pabs3 5y ago"Software Repair" is a GPL and copyleft given right though, which is what the Software Freedom Conservancy lawsuit is attempting to prove. It isn't always better for the maintainers to repair software, since they could refuse to do it, take years to do it, require more money than you have to do it, or require signing unacceptable agreements to do it and also since maintainers are overworked already, so preparing a good patch and sending it back to them helps reduce their workload. I personally have fixed many bugs in open source software I am not maintainer for, including a couple in the Linux kernel. There are many software developers and other technical people who are in this position. Dual licensing can lead to the downstream customers of the customers taking out the non open source license being stripped of their right to repair the software. Personally I think it would be better to keep all copies of open source software under an open source license. There are many different ways to fund open source other than dual licensing, many of them benefit the maintainers too: https://github.com/fossjobs/fossjobs/wiki/resources https://github.com/fossjobs/fossjobs/wiki/resources
- jabl 5y ago> I think dual-licensing is a good solution. sfconservancy lays out why they don't agree with that in https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/ https://sfconservancy.org/blog/2020/jan/06/copyleft-equality...
- pwdisswordfish9 5y ago> While Vizio's original request to “remove” the case from state court to federal court is, in the general sense, a standard litigation tactic and our response is a relatively standard response So, nothing happened yet.
- brian-armstrong 5y agoAs anyone who has used a Vizio TV knows, the software is really of no particular value. Input lag abounds. They should dump it all out on Github and move on as the software could not possibly be construed as any kind of moat for them.
- ryandrake 5y agoThere are many hardware companies where their embedded software is not actually a crucial moat or even value-add, compared to open source options. Look at WiFi routers: Do any of them have software that is better than OpenWRT or Tomato? Why do they even try? If I were Netgear or ASUS, I'd get rid of 90% of our software developers and just use one of the great open source options. Why is anyone spending money developing bespoke router firmware? I've worked as a software engineer writing embedded code, at several hardware companies, and nearly all of them see software as just another line item on the BOM, like a bolt or a screw, to make as cheap and quickly as they can. "We need to source 32 screws, 50 resistors, 45 capacitors, a waterproofing gasket, oh, and this 'software' thing. Make some 'software,' and ensure we fasten it to the product at station 25 on the assembly line." That's almost certainly how Vizio thinks of its software.
- _fat_santa 5y ago> I've worked as a software engineer writing embedded code, at several hardware companies, and nearly all of them see software as just another line item on the BOM It kind of blows my mind that this is the case. Do these companies not realize that bad software can easily tank their product?.
- nebula8804 5y agoIt is not a problem until someone comes along with a significantly better experience (eg. Apple). Until then, the mass market cares more about price.
- ryandrake 5y agoThey don't seem to realize, nor care. I mean, my cable box's UI is horrendous. Icons that look like they were cut/pasted from a "Download Powerpoint Clipart" web page, complete with obvious aspect ratio bugs. 16x8 pixel bitmap fonts straight out of 1988, UI elements not centered, not padded/inset consistently, silly full-saturation colors (like someone literally picked 0xff0000, 0x00ff00, and 0x0000ff for their color palette), poorly translated error messages ("feature not invoke"), button presses take 1-3 seconds to take effect, channel changing takes 2 seconds. It's like a 15 year old's HelloWorldGUI project made it into production. At some point during development, some non-software person at the subcontractor looked at the software, checked some checkboxes and said "Yup, this horrible thing our devs cobbled together in a frantic rush meets the minimum criteria that were spelled out in the contract we signed with TvManufacturer. Ship it!"
- mnd999 5y agoIt does feel like we’re coming towards the end of the open source era, imho for several reasons. * Developers looking to try out new tech are increasing looking towards hosted free tiers instead of OSS. It’s just easier not having to figure out how to run a backend. * The well documented (in this article) push away from copyleft licences due to the selfish and non-participatory approach of major cloud providers to OSS. * The reduced incentive to contribute to OSS as hiring trends have drifted away from positive contributions towards leetcode etc.
- iqanq 5y agoI feel the opposite. Each day more and more projects are choosing to launch using truly free licences like the MIT or the BSD. Software now is more open and freer than ever.
- kibwen 5y agoYou're free to license things however you wish, however let's not delude ourselves into thinking that permissive licenses somehow result in more "freedom" than copyleft licenses. The only freedom that you get with a permissive license is the freedom to make code non-free, which is to say, permissive licenses result in strictly less code being free.
- jkaplowitz 5y agoDepends on which freedoms a given software author prioritizes. For authors who want to maximize the freedoms of developers who directly download their software to make and redistribute derivatives and reverse dependencies and to redistribute the whole stack of their application under their choice of license with no obligations other than a notice requirement, yes, MIT and BSD style licenses maximize those freedoms. For authors who want to maximize the ability of indirect downstream end users of their code, even those who are unaware of the origin of the code running on their system, to make sure they can fix it or have it fixed to remove bugs or better meet their needs, copyleft licenses such as the GPL do better protect those freedoms. For the user-style freedoms in the above paragraph as applied to direct (rather than indirect) downstream users of the software author, either license is equally protective. All of these licenses protect software freedoms, but they differ a lot in the details.
- frankfrankfrank 5y agoIf we are talking about a right to software repair, we also need to talk about a right to not have our devices’ performance degraded. A related issue that is somewhat the inverse, which has always bothered me, is the seemingly intentional sabotage of performance and hardware by way of software updates, essentially building in incremental sabotage and obsolescence. What I am referring to is that fundamental performance is negatively impacted by OS updates that are usually mandatory, e.g., an iPhone or windows computer cannot load a basic website as fast as it could in the past, a basic function of the device, due to imposed software updates. There should be a legal requirement that the basic functions and performance of a device cannot degrade without justification over time. Imagine if your car required mandatory computer updates or maintenance that resulted in things like losing 100hp over 5 years, or it took longer and longer between hitting the unlock button and the locks actuating, or the brake responsiveness got worse and worse with every update; and then being told you have to buy a new car to get all those features back. I understand that there are certain things that cause preference degradation, but when it is imposed without real choice and there is no incentive for developers to actually prevent degradation, then there is also San incentive to intentionally sabotage customers. If anyone remembers the push and emphasis on performance that Steve Jobs imposed on apple engineers after using an older apple device, it is clearly possible. I clearly recall that when that update went out, it majorly improved the performance and UX of older apple devices.
- pabs3 5y agoA lot of performance degradations are driven by external factors; increase in the prevalence of JavaScript, a larger variety of web features, higher resolution images, higher resolution video, new video codecs, new image formats, advertising etc. Some degradations are driven by fundamental physical things, for example batteries and storage devices have physical degradation. So you have to be careful how you define things.
- frankfrankfrank 5y agoI anticipated a response like that and you have a valid point, but it does not explain nearly all the issues. Just as an example, not only why does simple swiping home screens on an iPhone/iPad lag after a few years when nothing has fundamentally changed about that behavior, but an even greater question is why is it permissible that/if other features and expensive computations are added that are impacting performance of such fundamental and core functionality/behavior. There should be no right that barring some major security changes, that core functionality is not only impacted, but that added features impact performance or that a user should have the right to choose performance over features. I reiterate my example, would it be ok with you if your car lost 100 hp or 20 mpg fuel economy over 5 years because there were things added to your car that weigh it down so much or due to a roughshod rebuilding of your engine every time you changed your oil? It is really a clear case of fraud and destruction of property when, e.g., a phone becomes so laggy that it is unusable over 5 years solely due to updates that were imposed and required by manufacturers even if they try to justify it by adding things you did not request or need or want. I am actually surprised that an enterprising technology aware lawfirm has not latched onto this issue. It seems to me to be a rather simple case of proving at the very least the negligence and willful destruction and degradation of others' property. To simplify the concept, e.g., we are constantly told by phone makers that next-phone is N times faster/more powerful; so how is it that the phone I was told is 5 times more powerful than the predecessor, all the sudden lags when swiping between home/app screens or launching a dialer, a core functionality that hasn't changed in years and like it never did before? At best, we are facing an immensely sloppy industry that damages our products and property through forced updates; at best.
- RcouF1uZ4gsC 5y ago> The mantra of “the GPL is not a contract” is a mistruth that has been so often repeated that it became widely accepted and typically unchallenged. (We expect you'll hear this theory repeated even more loudly now that the our Vizio lawsuit brought the question to the forefront in a federal court case.) Yet, prominent legal experts outside of FOSS social circles have long scoffed at the assertion. Indeed, case law in the USA has held the opposite. In multiple cases, courts have been convinced, specifically, that the GPL operates as both a contract and a copyright license. The law appears clear on this, and this is among the reasons why we believe our motion to remand will succeed. In short, we'll say it plainly here and now for everyone: the GPL operates both as a copyright license and as a contract; litigation can proceed under either of those legal theories. I think that if this case succeeds, it would actually be a huge blow for the GPL. We are actually just now starting to get over all the FUD about the GPL and convince corporate lawyers to allow using GPL. However, if they win this case on those terms, I expect every corporate lawyer to to have major heartburn about GPL. If for example, they successfully are glue that GPL gives every user of the software the right to sue, doesn’t that massively increase liability for the corporation? I can see many lawyers pushing to completely ban copyleft licensed software use.
- pabs3 5y agoThe copyright holders can already sue for GPL violations (and some do), so if corporate lawyers are fine with the GPL now and companies are complying now, they should be fine after the case is won. The problem will come for companies like Vizio who aren't complying.
- zucker42 5y agoIn the argument of the SF conservancy, the contract is between a distributor of the software and someone receiving the software. If a company only writes the GPL software in question, they wouldn't be liable to their customers in the same way as in this article because they aren't on the receiving end of any code. If a company uses and redistributes GPL code someone else wrote, they could be sued by their customers to enforce the GPL, but SF conservancy argues that's a good thing. IANAL
- nfriedly 5y ago