7 ms·
In defense of a third way in open software licensing
- m1el 8y agoMaybe the reason there's not much "public-domain" "closed-source" software is the same as there's not much "all rights reserved" "source-available" software: https://i.imgur.com/bSdusjH.png https://i.imgur.com/bSdusjH.png It's not about "two-party system", it's about the "natural" distribution of software distribution models.
- pmyteh 8y agoThere was lots of closed-source public domain software in earlier eras. The ethos of most of the non-commercial software on the British micros, for example, was never about the source. Stuff written in BASIC naturally came with its own sources, but even then people would often obfuscate it to avoid derivative works being made. People wanted reputation, not money, and they didn't want their work ripped off, or for others to profit off their labours. In the RISC OS community I was a part of, releasing source as a matter of course only became common with the influence of Linux. Before that, binary-only PD with homebrew or completely absent licensing was the norm.
- kemitchell 8y agoYour comment about obfuscated BASIC is very interesting. Thanks for sharing. Might you be able to mention any particularly important or memorable programs distributed that way? I'd be really interesting to go back and try to find contemporaneous writing about the motivations you mentioned.
- pmyteh 8y agoNot so much important or memorable: most of the really important stuff on RISC OS was small-scale commercial. There was also a tendency to use BASIC minifiers to make the program fractionally faster and somewhat smaller, so the boundaries with obfuscation weren't that clear. As for the contemporaneous writing, I'd start with the comp.sys.acorn.* newsgroup archive on Google Groups, because it's searchable (and I definitely remember this stuff being discussed in the late 90s, mainly as a reaction against the rise of Free Software. Incidentally, the decline of the RISC OS market really brought home to me the value of having sources available (and being allowed to use them). We had two significant breaking architectural changes (StrongARM architecture in 96 and the move from ARM's 26-bit to 32-bit addressing mode in the 00s) which cost us a lot of good software because the authors had moved on and nobody could fix the code.
- kemitchell 8y ago> There was also a tendency to use BASIC minifiers to make the program fractionally faster and somewhat smaller, so the boundaries with obfuscation weren't that clear. Interesting! > comp.sys.acorn.* newsgroup archive Thanks! > Incidentally, the decline of the RISC OS market really brought home to me the value of having sources available (and being allowed to use them). I have a few of these stories, but now I have one more.
- mntmn 8y agoSame on the C64, on the Amiga (where sometimes stuff had sources but no license), and on MS-DOS. Coverdisks often had PD on them and there were PD collections like Fish and later PD CD-ROMs.
- kemitchell 8y agoThank you so much for this comment. I've just added this page to my reading list: https://en.wikipedia.org/wiki/Fred_Fish https://en.wikipedia.org/wiki/Fred_Fish
- cperciva 8y agoCommercial "source-available" software is probably more common than you realize -- it's more common in B2B and B2gov contexts than in B2C contexts though. You can be sure that when the US military buys licenses for software, they want to be able to audit the source code! Similarly, Tarsnap isn't open source but I provide the source code (and actively encourage people to audit it).
- m1el 8y agoWell, then your comment dismantles the topic of the article.
- antt 8y agoNot really. There are three main roles in todays software eco-system. The developer, the administrator and the user. Each have interests that are orthogonal to the interests others. The developer wants to get paid to develop the source code. The administrator wants to be able to modify and deploy the source code and be paid for running the resulting program. The user wants to be able to review the source code and administration logs. Open source as currently defined covers 100% of the interests of the administrators and none of the interests of the other groups. The AGPL kind of covers some of the interests of the users. Closed source protects the interests of the developer. Being a member of all three groups I would be very interested in a license that manages the trade offs so the admins, in the guise of google and amazon, don't suck up all the money from developers and turn users into a commodity.
- antt 8y agoFreeware/shareware is also a thing. Publicly available without the source code. WinZip comes to mind.
- gus_massa 8y agoThe Windows source code is available for some universities and some governmental agencies and some big companies, after signing a DNA and some additional paperwork, so it is somewhat in the "all rights reserved" "source-available" category. https://www.microsoft.com/en-us/sharedsource/ https://www.microsoft.com/en-us/sharedsource/ I'm not sure if many webapps like gmail that have a big chunk of the UI in javascript count as "all rights reserved" "source-available". The code is minimized, obfuscated, and perhaps is the result of the transpilation of the real source, and it must talk to the servers that has not public source code.
- kemitchell 8y agoFor those interested in this topic, the whole Microsoft Shared Source program is worth reviewing. So is the reaction to it.
- kemitchell 8y agoThere is plenty of source-available software, and I'd suggest your perception to the contrary might have more to do with thinking in the limited terms I described. For a recent example, isn't all software using the Commons Clause source-available, as I define it? The reason there isn't much in the public-domain, closed-source quadrant is that permission without code is completely useless. For example: I hereby grant you, m1el, an MIT license for the short novelty program I have just fixed in the tangible medium of expression know as my hard drive, project name Caveman. Enjoy! Compare code without permission, which still has some limited value for others, especially educational and inspection value, as well as for the developers, in the form of access to free services. I'd also put a number of public-patent-grant programs in that family. That's potentially much more interesting.
- jmillikin 8y agoThe article spends a lot of words to obfuscate the truth that their "third way" is traditional proprietary software. Their online license store offers two products: * "Parity Public License" is a poorly drafted and extremely aggressive alternative to the AGPL, requiring users to "Contribute all source code for software you develop, deploy, monitor, or run with this software". * "Prosperity Public License" is a proprietary shareware license with a 32-day free trial.
- antt 8y agoNot at all. This license is trying to square the circle of having source code open to individuals who want to tinker with it and at most cover their costs, and those who want to build multi billion dollar empires out of it. Facebook, Google and Amazon wouldn't be the monopolies they are today if the software cost of spinning up 1 server wasn't the same as the cost of spinning up 1,000,000. This is a very hard problem where intention matters far more than anything concrete. I can run 50 copies of some IoT code and still have it be non-commerial, I can run one copy of linux and have it as the core of a multi million dollar business. Today we have the problem of centralized servers far more than of secret source code. The GPL can't deal with this at all, and the AGPL is one small step in the right direction. Spreading the gains of the internet giants is one way of dealing with the problem of monopoly, one that is much less violent than splitting each company into several smaller ones that should compete against each other, as nearly happened to Microsoft.
- jmillikin 8y ago> This license is trying to square the circle of having source > code open to individuals who want to tinker with it and at > most cover their costs, and those who want to build multi > billion dollar empires out of it. If the goal is to restrict which people use your software, then the solution is and always has been a proprietary license. Placing your software under a proprietary license allows you to say that specific companies can't use it, or people with specific political beliefs. Open-source software can't be restricted to non-commercial use because that would violate the Open Source Definition (https://opensource.org/osd https://opensource.org/osd). > Today we have the problem of centralized servers far more > than of secret source code. The GPL can't deal with this at > all, and the AGPL is one small step in the right direction. You're free to choose a license that forbids commercial use of your software, or restricts use by businesses above some size threshold. Your software would then be proprietary software, not open-source, even if the entire source repository was public.
- segphault 8y agoI have no problem with somebody deciding that a shareware or dual-licensing model are the best choice for their business. But it's incredibly toxic for the people pursuing those models to muddy and contort the accepted definition of "open" in order to misrepresent what they are doing. It's deeply disingenuous for this blog post to use the word "bullying" to describe the community's rejection of software distributed under undesirable or ill-considered terms. You can ship your code under whatever terms you want, but don't act like users and contributors have an obligation to support you when you make choices that don't serve their interests.
- kemitchell 8y agoIf you mean the Open Source Definition, I once shared your view. I can't any longer. Most times I bring it up, my conversation partner has never heard of it. When I explain, most times they don't care. As for "bullying", that very adequately describes behavior on GitHub, Twitter, mailing lists, and news sites toward those behind React, Commons Clause projects, and Lerna. "Failure to support" is a straw man.
- HumanHater 8y ago> Most times I bring [Open Source Definition] up, my conversation partner has never heard of it. That really doesn't matter. All they know about open source is based on this definition. There millions of articles about open source on the internet that use it. You are trying to invalidate all of them for no good reason. As a consequence every opinion about open source they ever read prior to your efforts would be outdated. Most people understand danger of these actions which leads to behavior you described as "bullying".
- kemitchell 8y ago> All they know about open source is based on this definition. The Open Source Definition says nothing about source control, patch submission, bug tracking, releases, versioning, dependencies, package repositories, continuous integration, test coverage, style guides, codes of conduct, and so on. There are also articles on the Internet that talk about a "post-Open Source" GitHub generation, and articles that affirmatively reject definitions of open source in terms of license conditions, rather than community. OSI has been controversial since inception, and there's plenty about that, too. If the OSD were merely a descriptive framework, that would be one thing. "Here is a class of licenses we can describe, and here are benefits we can correlate with them." But OSD gets used far beyond that. It's used prescriptively. It's used to sanction. Those are social functions of a movement, and the crux of a movement is participation, not definition. It matters that people making open source haven't heard of OSD, because they neither participated in its adoption nor consented to its authority. It has no sway over them. The idea that a mailing list could define their community rankles. I don't consider debate about OSD, DFSG, or "What is free software?" bullying. I do consider peer pressure on maintainers to adopt terms that don't advance their goals, against their stated interests, bullying. I consider unfounded legal FUD to the same effect bullying. Have a look at the Lerna GitHub issues, or Twitter conversation about Commons Clause.
- misterbowfinger 8y agoI'm still confused about the paranoia around AGPL. If MongoDB is AGPL, why does everyone else throw a shit fit? Despite its faults, MongoDB is still massively popular, so I assume it's used at many enterprises. Also, side note: can anyone point a blog post (preferably from a lawyer) that explains why AGPL is so problematic?
- mikekchar 8y agoI can only give you my opinion as I'm not involved with MongoDB, I'm not a lawyer and I'm not an expert on AGPL. However, I spend a fair bit of my spare time reading licenses and thinking about them. There are really 2 issues you need to keep in mind: 1) there is a difference of opinion about whether linking to an unmodified, GPL or AGPL licensed library is considered to be a "modification" of that library; 2) GPL and AGPL are different in terms of software that is only accessed via a network (i.e., the user does not receive a copy of the executable code). In the first point, the FSF (who maintains these licenses) believes that linking to a GPL or AGPL license creates a "combined work" that requires a license that is compatible with the GPL or AGPL. In other words, you can't "convey" (distribute) the combined program unless the overall license has compatible terms. Other people disagree. To my knowledge, this point has not been tested in court. While the GPL itself is well tested in court now, that is for applications that are clearly based on a GPL licensed piece of code. Whether or not a library that is providing a utility function has that same legal protection is still untested (as far as I know). However, there are a couple of things that I think are important about this. First, the intent of the licenses is clear. It's a completely jerk move to use a GPL or AGPL licensed library without considering the intent of the authors that chose that license. You might get away with it legally, but why be a jerk just to save a few bucks? (Not that it stops people...) Secondly, the intent of the license is clear, if you want people to use the software in a different way, please pick a different license! There are many appropriate licenses (and probably the LGPL is what a project like MongoDB should be licensed as). I'll talk a bit about that at the end. With the second point, it's important to understand the difference in use cases for the GPL and AGPL. The GPL is intended for applications that are meant to be "conveyed" (distributed) to the user. The user then runs the program themselves. With a GPL or similar license, they enjoy the 4 freedoms of being able to run the software for any purpose, inspect the source code, modify the source code, and to distribute their modifications if they wish (as long as they grant the 4 freedoms to their users). The AGPL is designed to give similar freedoms to people who do not receive an executable -- their only interact with the software is through the network. The only reason for choosing the AGPL is to ensure that users can receive the source code to: run the code for any purpose (rather than just the purpose the service provider allows), inspect the source code, modify the source code, and distribute their changes. I don't know the history of MongoDB, so I don't know why they chose the AGPL. It is frankly a bizarre choice, IMHO. My only guess is that they intended that users of an online service be given access to the MongoDB source code. Why they thought that was important, I really don't know. The MongoDB developers are pretty adamant that the license does not restrict people from building services that are not AGPL. In practical terms, for the moment anyway, it's not a big deal. Even if the AGPL applies to the combined software (and FWIW, I believe that it does), the only people who have standing to sue are the copyright holders of MongoDB. They have clearly said that they are happy with people not offering the 4 freedoms when making services using MongoDB. In other words, you can be relatively sure they aren't going to sue you -- and nobody else has standing to do so. On the other hand, it's still a legal liability. If MongoDB changes hands some day and the new copyright holder has a different opinion, will you end up getting sued? Although I think it is incredibly unlikely, it could definitely happen. Crazier things have happened. To sum up, AGPL is not problematic at all, if you are using it as intended (as an aside, I actually don't like some of the wording, which I think is a bit hand-wavy at times, but it's the best license that I know of for the niche that it occupies). The only problem is that MongoDB developers are using it in a way that differs from its intended purpose and are thereby muddying the waters in terms of communicating what they want. I suspect they simply made a mistake originally and now it's just too difficult to make the license change.
- marknadal 8y agoAs an active maintainer of a popular 8.8K+ starred Open Source project, I can attest to how hard and difficult it is to run, fund, finance, etc. But, at the end of the day, there is no excuse - we cannot sacrifice our ideals/values just because Open Source can be rough. True Open Source is worth making the sacrifice for, but there are a lot of new/old licenses trying to evangelize themselves as "Open Source" but are secretly masked proprietary/cripple-ware. This needs to be stopped. We had a good discussion about this on Twitter the other day: https://twitter.com/marknadal/status/1032763711008559104 https://twitter.com/marknadal/status/1032763711008559104
- kemitchell 8y agoA noncommercial license like Prosperity differs from a permissive license like MIT only in withholding permission for unlimited, free commercial use. If that delta holds your value system, then your value system amounts to business welfare, financed largely by individual sacrifices. That's a strange kind of martyrdom. There's no question that useful software that costs for commercial use produces less economy-wide benefit than useful software that's always free of charge. But the question isn't how much potential benefit open source can pump out, but rather how much benefit open source can pump out for the cost, and how that cost gets allocated. I've never held Prosperity, or its predecessor, out as open source licenses in the traditional sense. Others have called them so, even after I pointed out my own opinion. I have and do hold Parity out as an open source license. If copyleft licenses don't meet your definition of open source, or only copyleft licenses with known, practical software-freedom vulnerabilities, I can certainly square that with your view of open source's purpose. But I can't square it with open source's history, or with most stacks we call "open source".
- zekevermillion 8y agoCommercial freedom is an important part of the "free" in free software, no? The values you're calling strange are basically the ethics of RMS. Perhaps there is a bit of a martyrdom to RMS' lifestyle, but I would hardly say that his ethics are strange at this point. I think it would work better to argue, open source is about leaving aside the ethical considerations (which are highly charged topics) to focus on how effective is code sharing as a development methodology, and within that, what licensing regime under current law works best from a business perspective. And the question is different for an academic talking about larger society, vs. an individual business or developer who is choosing his/her/its own license. Obviously your duty as an attorney is to grapple with the latter question. Thus, while I personally am more or less with RMS on the ethical inquiry, I see no reason why your L0 ideas should not be discussed within the context of open source. I personally would not choose to use your license, but that is irrelevant. One point of errata in your essay: free software (I hope) does not depend on copyright protection. Far from it. Free software viewpoint is that copyright protection should not extend to software. Rather, the law should require published software to be free software. However, given that the law is not going to change anytime soon, the GPL was written as a clever hack to use copyright to promote the values of software freedom. This has been successful to some degree, so it is a perfectly fair question to ask what we would do for software freedom if copyright protection as we know it today did not extend to functional software. But this is probably not a question that would be asked within the context of "open source" I guess...
- true_religion 8y agoA license for only people within one group is simply a proprietary license. It does not matter how easy it is to join or leave that group. I would never put such a license in the same category as the MIT or Apache licence.
- ChristianBundy 8y agoThe world needs more License Zero, I'm always happy to see this important work on tha the ttop of HN.
- ddingus 8y agoWould we have this discussion if the authors of powerful software powering multi billion dollar enterprises benefited more? I wonder what happens when these peolle are given financial security? As an investment in the future, the returns could be amazing! Many, if not all, authors really care and it shows. Would making sure they are free to care, live well, maybe create more be such a bad thing? Secondly, with that on the table, I wonder about the quality, and drive to create like that. We may see amazing tools. Re: Open Source Being able to see the source is high value. Being able to build on others work is high value. Arguably, high enough value to trigger this kind of mess. Pay them. Seriously. Is the problem one of ego? AwesomeSauce.com wants to be recognized and get value from their work. Is recognizing CantLiveWithout DB or Language, Toolkit, etc... taking away from all that somehow? Is it one of confusion? AwesomeSauce.com paid, only to see AlsoAwesomeSauce.com not pay? Does that matter, if bazillions are being made? Seems to me this all can be litigated to our mutual detriment, or it can be handled as a family struggle, or worse. Have to say, I do not blsme people looking hard at billion dollar enterprises, and their many big fix, support requests with a jaded eye, maybe a hungry one. Fixing that scenario may well be ultra cheap compared to the mess and opportunity costs to come. I put this here to stimulate some discussion, not as judgement, or anything aimed at anyone. Really open licenses are a good thing. Really, really good thing. Many of us know the story. Pick up some code, any computer we can find and just build. Breaking that seems extreme. Maybe it just does not need to be that way. Maybe it should not. What is worth what here? Perhaps those conversations go far easier than the current ones will, and it is not like tech as a whole can't afford a solution. Again, not a negative, or statement against anyone. Just thinking out loud here.
- zzzcpan 8y agoThere is some resistance in these discussions though. Some people don't seem to like the idea of not being able to commercially benefit from free software for free, while working at organizations abusively dominating markets. Sort of oxymoron, restricting freedoms using unrestricted freedoms. The supply of unrestricted will dry out of course, as somebody has to pay for all of this. Either way changes are inevitable.
- 8y ago