4 ms·
I don't think companies should be forced to maintain their software forever -- that's too much of an unpredictable burden for the company to bear. Also it's fr
by jedberg 5y ago
I don't think companies should be forced to maintain their software forever -- that's too much of an unpredictable burden for the company to bear. Also it's fraught with problems, like what happens if the company goes out of business?
But what I do think is they should be forced to release their source code if they no longer want to maintain it. If a server is required for the software, then they should release the server source such that anyone can run one. If there is a hostname that the software connects to, they should be required to push an update that allows you to change that before shutting down the service and releasing the source.
- djur 5y agoYou could have a system of "software trusts" where source code is held in escrow. Businesses and governments could require this in vendor contracts.
- Buttons840 5y agoGood idea. The escrow company should also be in the business of advertising for their clients. "Here is a list of SaaS products you can depend on for the long term" they'd say, and I'd believe them because, worst case, the source code gets released. Whenever I thought something like "I need a finance app" I'd head on over to saasescro.com to see who they recommend. The escrow company could then use this clout to win more customers. We're heading towards a world where there's 20 SaaS apps for everything imaginable (or are we already there?), this could be a competitive edge.
- jandrewrogers 5y agoThis has been common practice for decades.
- Silhouette 5y agoBut what I do think is they should be forced to release their source code if they no longer want to maintain it. This is a common suggestion from open source fans but it quickly fails on practicality. What if the code includes licensed software from a third party? What about trade secrets of the developer, or information provided to them in confidence by a third party? You quickly end up back at software developers either having to maintain indefinitely or accept an onerous set of restrictions and either way the end result is that a lot of software never gets made at all. There is definitely a serious problem with having our modern dependence on software and yet accepting the very limited support that some developers have tried to get away with lately, but I don't think attempts to force the source open are likely to be the solution we need.
- jedberg 5y agoIf they begin the project knowing that it will one day be open source, they can build accordingly. Make the law only apply to products released one year after the law goes into effect. > What if the code includes licensed software from a third party? The third party would be subject to the same law, or the law could be written that liability is removed. Then it's up to the third party to evaluate the risk. > What about trade secrets of the developer, That's a tradeoff they'd have to make -- reveal the trade secret or pay to maintain the software. > or information provided to them in confidence by a third party? Since the third party would be aware of the potential for the software to be open source, they would have to decide if they want to reveal that or not, or require that part to be removed before open sourcing and replaced with equivalent functionality.
- Silhouette 5y agoSorry, but this just seems completely unrealistic. The commercial software development industry in any country that adopted such a law would become a toxic wasteland. Open source has always had a terrible track record of producing effective, commercially viable results, and you would be reducing the whole industry to that kind of level. Not that you could pass the laws required to make it happen without causing a major diplomatic problem anyway since it would probably violate about a million provisions of the WIPO treaties and so on.
- watwut 5y agoTo be honest, the biggest problem I see is that with massive corporate projects, fixing them after original company lost interest will be too difficult and expensive.
- jandrewrogers 5y agoHow would this work? Any such law has limited jurisdiction. There are already many examples of software development moving to avoid problematic laws. There are circumstances where further maintenance is all but impossible that happen in the real world. Open sourcing software cannot always grant all rights required to use said software legally, many of which may not be owned by the company. Some software has dependencies on third-parties that can void the relationship and for which no alternative exists, in some cases because the capabilities are unique and trade secrets. This either creates a de facto requirement to support all released versions of software indefinitely or a giant and easily exploitable loophole that renders it useless. How does removal of features, common in long-lived software, work under this regime? It would be nearly impossible to define "maintenance" in law such that it doesn't lead to de facto non-maintenance that also doesn't create unlimited liability that courts are unlikely to enforce. Furthermore, this would violate laws that expressly prohibit disclosure of code in some cases, that are unlikely to be repealed anytime soon. Any such exceptions would be widely exploited. This policy would create some perverse incentives and a massive number of loopholes.
- jedberg 5y agoI'm not sure why any of that stuff should be protected in the first place. 100 years ago, a company could build a machine. It could be full of "trade secrets". But at the end of the day, anyone could tear it apart and figure out how it was made and how to repair it. If you were willing to fix it, you could use that machine forever. Why should a modern "machine" be any different? Why should how the machine works be legally protected after the company no longer makes it or supports it? This is basically just an extension of the right to repair argument.
- WorldMaker 5y agoIt could work like intellectual property law was meant to work in the first place? Patents are a limited monopoly granted in exchange for all of the technical details of the invention so that the invention can be built by others after the monopoly period expires. "All of the technical details" for a software patent should be expanded explicitly require "all of the relevant source code" and for good measure "relevant" should be described widely and probably "virally" (ala "copyleft"; maybe requiring a "copyleft" license?). Copyright is a limited monopoly granted in exchange for helping to insure that the product eventually is available to use by the public domain. For many years the US had a legal requirement for active copyright that a copy of every book be sent to the Library of Congress for cataloging. (This is no longer a requirement, though some US publishers still do it as a courtesy.) A requirement could easily be made that for software copyrights to be enforced in a court of law that same software must have all source code registered with a US Software Source Code Depository. We collectively could do a lot of interesting things to build automated tools for that. Back in the day when copyright required published books to be sent to the Library of Congress not every publisher followed the law and so it was exploited some, but if you get caught (exploiting it) not registering your source code and then get taken to court over it: you lose your copyright immediately, the court has the power to order you to hand over your source code, and at the very least makes it fair game as a part of the public domain to reverse engineer your software if your source code can't be found. On the surface it sounds like a great idea. It's also a very unlikely idea because it would require new legislation and would be opposed by many lobbies of corporate lawyers.