11 ms·
Open source confronts its midlife crisis
- microcolonel 8y agoI wouldn't call this a midlife crisis. We have known and continue to know that this is a potential outcome when you sign a CLA. If your company operates an open source project, you should know that if/when you are purchased, the centralized license on that project will inevitably be considered an asset.
- snaky 8y ago> I cannot, however, tell you that you can’t put the book on the same bookshelf as that of my rival, or that you can’t read the book while flying a particular airline I dislike, or that you aren’t allowed to read the book and also work for a company that competes with mine. Really?
- Arnt 8y agoReally. Copyright is just that, copyright. It's not readright, useright, flyright or workforright. The license for foo can say "by copying foo, you affirm your acceptance of the following conditions: …" and if you do copy foo and nothing else gives you the right to copy it, then those conditions are what you must've accepted, right? Of course you may argue the point, but that's the theory. However, if what you do is use foo or fly with KLM, not copy foo, and don't affirm your acceptance by other means (such as signing a document), then copyright doesn't apply. EDIT: And even if it does apply, it's not clear to me that what it applies to is the non-copying bit. If copying and flying with KLM are incompatible, then it's not clear to me that copyright can ban the latter.
- snaky 8y agoThat's not about copyright actually. The license is a contract, and you decide to sign it or not - by deciding to use the software or not. The contract in theory may include any restrictions you can imagine. There are in practice some restrictions on that restrictions by some laws in some countries in some aspects, but rarely about KLM.
- fulafel 8y agoCopyright license and contract are not (necessary) the same thing. An important related fact is that contract breach is generally less penalised than copyright infringement. See eg https://perens.com/2017/05/28/understanding-the-gpl-is-a-contract-court-case/ https://perens.com/2017/05/28/understanding-the-gpl-is-a-con... & https://www.youtube.com/watch?v=6i9sngsv8G0 https://www.youtube.com/watch?v=6i9sngsv8G0 (And keep in mind that per-license US case law doesn't have standing globally)
- antt 8y agoIf you are using IP without a contract you are engaging in copyright infringement. People we've been through this. This fud was deal with when the GPL was ruled valid a decade ago.
- zozbot123 8y agoNope, copyright also covers public performance of the copyrighted work. And that's exactly the part of IaaS or SaaS services that's so controversial lately.
- hlandau 8y agoI'm unaware of any case law establishing that using software to provide a service constitutes "public performance" as defined in copyright law. Got a citation?
- zozbot123 8y ago> using software to provide a service This is not what I said, so could you please not put words in my mouth? It's about statutory provision, not just case law. And it's not about "using" a copyrighted work to provide a service, but when the core of what's being "provided" consists in the copyrighted work being 'acted' or 'played', to paying customers (the statute itself exempts performance that does not occur for pay, nor for commercial purposes), in a way that these customers can readily perceive (but that need not in any way result in a 'copy' of the work being conveyed - copy and public performance are distinct rights under the law!)
- deleted 8y ago[deleted]
- Arnt 8y agoI misunderstood you in the same way as hlandau. Perhaps you could explain what you meant in different words? A concrete example might help.
- kemitchell 8y agoI've heard that the drafters of AGPL wanted to "synthesize" a nonexistent public performance right. But I'm not aware of any US case law interpreting 17 USC 106(4) that way.
- antt 8y ago>Copyright is just that, copyright. It's not readright, useright, flyright or workforright. It is that. There is a reason why IBM got an exception from the JSON license to do evil: https://www.youtube.com/watch?v=-C-JoyNuQJs&feature=youtu.be&t=41m20s https://www.youtube.com/watch?v=-C-JoyNuQJs&feature=youtu.be...
- hodgesrm 8y agoMaybe. However it's the wrong analogy. Open source licenses are just that--licenses that specify conditions for use of the software including running it, building on it, adapting it, etc. As such open source licenses can impose a wide range of conditions for use. Patent detente is a common term in OSS licenses, which demonstrates that such licenses are not just another form of copyright. [0] If you violate the term(s) you lose the right to run the software and may be liable for fees under a different license structure. Companies end up paying for this sort of thing all the time. There's no particular legal reason why you cannot impose the sort of conditions that MongoDB or Confluent have added to their licenses. We can argue whether they are good for particular communities, or whether they are wise for the companies involved. But my guess is that the terms will largely stand up in a court of law as long as the companies involved can demonstrate the terms are reasonable and they have copyrights on the code involved. [0] See for example article 3 of the Apache 2.0 license at https://www.apache.org/licenses/LICENSE-2.0 https://www.apache.org/licenses/LICENSE-2.0.
- nickpsecurity 8y agoI suggested making them copyright licenses and contracts simultaneously. Anything copyright doesnt cover goes into the contract. More, cheaper lawyers should be able to understand it. I think I read here one court already ruled the software licenses are both types of law in action. That's a start. :)
- hyperman1 8y agoIANAL, but lets try to figure this out. The wikipedia article of the Berne Convention says this, regarding what is required to be protected by copyright https://en.wikipedia.org/wiki/Berne_Convention#The_minimum_standards_of_protection_relate_to_the_works_and_rights_to_be_protected https://en.wikipedia.org/wiki/Berne_Convention#The_minimum_s... The first one: you can’t put the book on the same bookshelf as that of my rival seems part of the right to communicate to the public the performance of such works, so it seems an author can forbid a shop to do this. I assume the performance of the work is the reading of the book here. This would imply a user may put the books on the same shelf at home, unless that user takes a picture of it and put that picture on the Internet for everyone to see. This would be insane, but in my experience a strict reading of copyright law gets insane quickly, so in practice you'll need to convince a judge of the merit of the case. The second one: you can’t read the book while flying a particular airline seems to be a right of the reader that can't be blocked . Unless you start to read it aloud for everyone of the plane. Translating, etc... is a protected right, so a copyright holder might forbid reading the book on a plane if you are doing the reading as preparation for a translation etc... And that's only the Berne convention. Isn't copyright nice.
- kemitchell 8y agoFolks from the US might be interested to read up on the case of Vernor v. Autodesk.
- lifeisstillgood 8y agoThis seems to boil down to FAANG is taking your open source code and using it and no license jiggery pokery will stop them. The author seems to think that dual licenses are there to try and persuade Google to pay for your add-on extras. I don't think that's right - the dual license is there to get Google to use the oss version and then snaggle the second tier of the Fortune 5000 into paying. And it might, maybe, be working. (data needed, all i have is anecdata) > business models like “support”, “services” and “training” are entirely viable But that's the problem. They aren't really - at some point the effort in approvals and purchase orders gets so great that anything that is not "you can't use it" is not worth the candle The thing is a license is a subscription - and subscriptions seem to be the only way to make money. Everything else just pales.
- kklimonda 8y agoWhen you say "everything else just pales" do you mean that licenses/subscriptions are the only viable options to make sure you don't go out of business, or are they the only option to justify multi-billion evaluations and multi-million investment rounds?
- lifeisstillgood 8y agoyou can do good lifestyle businesses with just being an OSS developer and reasonable businesses doing support services. But at some point scale matters - stack it high and sell it cheap is the usual scale model IRL. But support services almost always falls down on the first client that means every other client gets the solution for free and you lose the profit making side of selling the same thing multiple times. OSS really does break most business assumptions. I think it is good for society as a whole - i think for example Linux has added billions or maybe trillions to the world economy - but capturing that might reduce the benefits to society as a whole. So long answer short - Inwoukdmlike to see evidence that long term OSS can support businesses of > 100 people > 50 million pa I am hardly seeing it. i could be wrong
- xiphias2 8y agoOpen source is booming by any metrics. My favourite example is Bitcoin, which is just getting started, but even its haters usually agree that it has a huge impact (even if they don't like the impact itself).
- bdcravens 8y agoI would say Bitcoin is lagging compared to where many other open source projects were after 10 years.
- sparkie 8y agoWell, you can expect it might take some time to gain adoption for an idea which has such a profound and extensive impact on many areas of life, and not just software. Bitcoin has changed the way the world thinks about money in just 10 years. I wouldn't call that lagging. It seems to me that it is leading.
- jcranmer 8y ago> Bitcoin has changed the way the world thinks about money in just 10 years. Has it really? I've not seen any evidence that mainstream economists have changed their views on money and monetary policy. Even among the lay public, it doesn't seem that it's really changed anyone's minds, just given some people with minority views on the matter a loud platform to shout them from.
- bdcravens 8y ago> Bitcoin has changed the way the world thinks about money in just 10 years. That's mostly limited to "true believers". For the 99%, Bitcoin the technology doesn't really mean anything, but they rather think of the speculative investment. (for reference, I was mining BTC in 2011, and have made more than a few dollars in it over the years, I just like meat with my Koolaid)
- sparkie 8y agoIt might only be a small minority of people who are true believers in Bitcoin, but many of them have taken it upon themselves to continue building new financial instruments and technologies around it. The internet changed the way the world thought about communication in the 70s. This was a minority opinion all the way up to the naughties when it became impossible to continue ignoring reality. Banks will need to innovate or they'll end up like the record labels and newspapers who failed to keep up with the geeks and entrepreneurs. The banks which embrace technology might survive.
- nqzero 8y agoopen source can certainly be profitable for some personalities and some projects, but there seems to be a large portion of the space that's hard to monetize i've taken a cut at making a license that attempts to bridge the divide - capturing many of the freedoms of open source while still requiring a subscription https://github.com/db4j/pupl https://github.com/db4j/pupl
- dman 8y agoVery well written and timely.
- softwaredoug 8y agoThere’s an assumption that an open source project should “belong” to a single company (Mongo, Elastic, Confluent, etc). I think that model may be more dangerous to OSS than large cloud providers. If it’s truly open source, one business shouldn’t dominate the project’s development. That’s tantamount to the project becoming shared source that accepts community contributions, not community driven open source backed by many orgs. It reinforces a monopoly in that community. And these companies themselves are not tiny victims (many IPOd at multi billions). They also tend to compete with their customers and community in the same way as AWS, so I’m not sure they can cry foul when AWS does the same.
- jfim 8y agoIt's hard to drive non-incremental innovation without a benevolent dictator model. For example, the Hadoop ecosystem moves very slowly, and most of the innovation happens in new projects that are added, not in core infrastructure. An example of moving slowly is the fact that even to this day, the HDFS high availability story for NameNodes is pretty wonky. In a community model, if someone wants to do a large scale refactoring or rework parts of the architecture, these projects die of a thousand cuts with objections or change requests from many stakeholders. The decision-making then becomes "design by committee," instead of pushing towards a long term vision. With a single benevolent dictator, since decision making is more centralized, it's significantly easier to do large reworks of the architecture to improve the product in non-incremental ways.
- jacobian 8y ago> It's hard to drive non-incremental innovation without a benevolent dictator model. Hmm, dunno that this is a universal truth. Most of the biggest improvements to Django came after Adrian and I stepped down and we moved to a more democratic leadership structure.
- zapita 8y agoThe key word is “improvement”, which implies that there was something already there to improve. So, a democratic structure can improve Django once it’s already well-defined and widely used. But could it have created Django and made it successful in the first place? I think the answer is no, and that’s what the gp meant by “non-incremental innovation”.
- boredandroid 8y agoI can address some of the critiques that seemed aimed at the blog post I wrote announcing the Confluent license change: 1. We aren't trying to get cloud providers to license our proprietary features. We run a cloud service of our software. 2. The book analogy is not very accurate. We have an FAQ here the helps clarify interpretation. The limitations it places are extraordinarily small, 99.9999% of users are completely unimpacted, it really only impacts companies wanting to offer, say, KSQL-as-a-service. https://www.confluent.io/confluent-community-license-faq https://www.confluent.io/confluent-community-license-faq 3. We aren't trying to "co-opt" the community or open terminology. We actually tried super hard both in the license and in the blog post to be honest and upfront. Whatever else you think you have to agree that Confluent's license is _exceptionally_ permissive and the software has a pretty great community of users. How do you describe a license that let's you run, modify, fork, and redistribute the code and do virtually anything other than offer a competing SaaS offering of the product? 4. Bryan Cantrill is an amazing engineer, but, well, as a lawyer, I think ours are probably better. We're quite confident in the enforceability, but it's a bit ironic because I remember this being the FUD around GPL that it was "totally unenforceable". 5. The "open source companies are all failing"-meme isn't factually correct. Many open source companies are actually doing quite well. MongoDB has gone up in value about 3x over the last year, Elastic was the breakout IPO of the year. There are a handful of other really strong businesses a year or so behind, including Confluent. An open source project is not in-and-of-itself a business model, but it is, just empirically, a big part of some of the recent successes in the infrastructure space. Probably worth noting that the reverse is true too: if you look at some of the really cool up-and-coming open source platform data technologies, a lot of them have the support of a company behind them. Of course there are plenty of sucky open source companies, but that is true of every category of startup. 6. I agree that it is silly to moralize about the behavior of the cloud providers. They are following their economic interest. The point is that this behavior does undermine the cycle of investment in some of the more promising hard tech open source projects and to try to change this dynamic. 7. This article has a bit of a tone of "Son, new things aren't possible, trust me, I tried them and have the scars to prove it". I have huge respect for Bryan, and I know that to some extent that is his schtick as a public personality, but I'm not sure that attitude is most likely to lead to improvement. I don't think the current crop of licenses was handed down from the mountain on Stone Tablets by our elders to be revered and not questioned. I think CockroachDB, Elastic, MongoDB, and Confluent are building really innovating technology platforms and building pretty cool companies to help fund that. I don't think we need dogma. And I still don't say "GNU/Linux".
- zokier 8y ago> There are many business models that are complementary with respect to open source, and some of the best open source software (and certainly the least complicated from a licensing drama perspective!) comes from companies that simply needed the software and open sourced it because they wanted to build a community around it. I've come to the conclusion that this is pretty much the only long term sustainable ethical way of developing (foss) software. That is to say that I don't believe anymore in pure software businesses.
- kemitchell 8y ago> That is to say that I don't believe anymore in pure software businesses. Does that mean you don't believe in company specialization? Very few companies can afford to develop and maintain a cutting-edge database. Google, for example, can. But one rung down, and the answer is "no". For example, Kafka began at LinkedIn. The team that developed Kafka at LinkedIn ended up leaving to form Confluent, in order to build it out.
- chubot 8y agoI agree that the naming of the non-open-source licenses is confusing, e.g. "commons clause" is not a great name. However, I wonder if there is in fact a fundamental difference between some kinds of reuse and others (thinking aloud here). If I want to use Debian to power my corporate desktops, that's one thing. Or if I want run Debian on cloud machines that provide a Redis service. But if I actually expose the Redis API and protocol through a service to customers, and charge them for it, can that be considered another form of reuse that requires licensing? This is in contrast to running Redis as a backend for say a for-profit Twitter clone. Using Debian, the analogy would be providing a remote-desktop-as-a-service using Debian, as opposed to merely using Debian in a cloud service. ----- Although, I may have missed it -- why not make Redis AGPL? That would prevent proprietary forks, as I understand it. But they want something even stronger than that? They don't want just a level playing field, but an advantage? I suppose I can understand that when you are faced with big cloud providers with tons of locked-in customers. I'm surprised that Cantrill isn't more sympathetic to the business model problems and the lock-in effects of big cloud providers. He seems to take a pretty hard line that the "community" comes first. But what if there's no real community? Is there a community around CockroachDB? It seems to be mainly for for-profit companies to run cloud services. ----- In other words I think there could be another name for software where you have rights to view, modify, and distribute the source, but not to directly sell it as a service. He is saying that nobody is ever going to license this software -- they will just reimplement it or use something else. But I think that is besides the point, which is that there are customers who WOULD pay for a hosted version of Redis or CockroachDB. I guess where this falls down is that it only works for projects in which there have been essentially no external contributors. Although a few people may have contributed the lion's share of the code, it's not clear that you should reserve rights for author A's company but not author B's company, even author B only contributed 10 lines of code. It is hard to draw that line.
- mnutt 8y agoFor me, it's hard to separate "Cloud provider selling a service" and "Cloud provider selling compute, and giving away the free service". On a scale of things that are ok to things that are not ok to open source companies: 1) end-user rents an ec2 server, installs redis themselves, 2) end-user rents an ec2 server, runs a redis AMI that a third party created, 3) same, except amazon created the AMI, 4) Amazon runs an ec2 instance on the user's behalf, puts a nice UI on top for "spin up a redis server", 5) Amazon runs an opaque multi-tenant redis system. Where do you draw the line? Most steps are just Amazon streamlining letting the user run the service, except for the last one which decreases the cost for the end-user.
- platform 8y agoOpensource, seems to be now defining how the overall professional programming develops, and how overall computing technology develops. It is a very powerful phenomena that, may be more akin to development of a writing system(s). There is simply no way to stop it, or reduce it to a 'island' of some sort. So active creators of OSS value, definitely need to keep in mind how wide and long term the influence of their decisions might be. As the societies will continue to use their constructs not just in software but in other areas as well, for a long time. --- Just the other day, I was thinking how many programmers are there in the world (and i my definition -- these are people who had written software for 2+ years, and were paid for it). Older estimates (eg https://news.ycombinator.com/item?id=3555251 https://news.ycombinator.com/item?id=3555251 ) are off. I think the number is closer to 50-70 mln. But I also caught myself thinking, that programming in some scripting language to perform some task that by itself is not creating a new program -- is really a modern type of literacy (such as reading, writing, math).
- carapace 8y agoThe answer lies in your context for programming. The bigger picture. The invention of the microprocessor was a watershed moment in human history, more than that of fire, or even splitting the atom. Mechanical intelligence provides for a realistic Utopia. It's not guaranteed, but it's unarguably possible. "Let the robots do the work and we'll take their pay." From this point of view, anything that restricts the free flow and use of software is regressive. (I'm not going to address the subtle point of whether "Free" or "Open" better foster free flow. On the ten-thousand-foot level that I'm dressing it just doesn't matter.) Trying to make a living from charging for (copies of) software is foolish compared to bringing about a techno-utopia as quickly and directly as possible. The important question is, how do we marshal our resources to achieve a peaceful, ecologically harmonious, high-tech, post-historical world as quickly and painlessly as possible?
- antt 8y agoBy charging for the software we produce and using the economic resources we gather to get the outcome we want through the acceptable channels in our society, e.g. the courts and the legislature.
- carapace 8y agoSell [copies of] software to make money and then lobby politicians. Is that what you're saying?
- nickpsecurity 8y agoAll this talk about ethics, open, and free brings another angle to mind folks like Cantrill seem to be ignoring and therefore misrepresenting what they are achieving in at least U.S.. I used to push for OSS/FOSS in the past. Now I’m switching to hybrids. The reason is that encouraging people to play “give it all away” or “use low-revenue models” in a capitalist country where opponents of freedom make billions of dollars for their software shifted all the money (and therefore power) to the latter. They then paid off politicians and used pricey lawyers to win more power against OSS/FOSS in ways they couldn’t fight against without piles of money. This includes ability to patent/copyright troll users of open/free software and especially Oracle’s API ruling which jeopardizes OSS/FOSS, backwards-compatible implementations of anything that had a proprietary API. From what I see, OSS/FOSS have done great things but are a fundamentally-flawed model in a capitalist country where money wins. As many as possible need to be charging by default both to support contributors and send money/power the other way. They and FOSS-using companies that don’t depend on patent/copyright money need to pool money together to fight legal advances of patent/copyright-trolling companies that want lock-in. Otherwise, in a game where only one side is playing for keeps, the OSS/FOSS groups keep losing by default software freedoms and ability to enforce their licenses while preaching that they’re maintaining them. Seems dishonest. Also, strange I almost never read about these issues in FOSS writers articles about business model and licensing recommendations. Far as hybrids, I can’t give you the answer yet since it’s too soon. For FOSS, I’m looking at Open Core and Dual-Licensing with strongest copyleft available. For non-FOSS, Source-available from public-benefit companies and nonprofits chartered to implement most software freedoms for customers on top of free for non-commercial or under certain use. These freedoms and justifications would also be in licenses and contracts with huge penalties for non-compliance for extra layers of defense. Maybe expire into FOSS after certain time passes or revenue threshold. We need more experimentation that lets companies currently supplying or later releasing as FOSS to get millions to hundreds of millions in revenue collectively to fight this battle. Again, it’s not optional: the other side is actively fighting to remove software freedom inch by inch. And mostly winning despite FOSS organizations’ little victories. Edit: Added a few specifics for hybrid model in this follow-up: https://lobste.rs/s/kbcjnx/open_source_confronts_its_midlife_crisis#c_yokqtn https://lobste.rs/s/kbcjnx/open_source_confronts_its_midlife...
- zizee 8y ago> Of these, the laughably named commons clause is the worst offender (it is plainly designed to be confused with the purely virtuous creative commons) Creative Commons has a "NonCommercial" variant[0], which is much more restrictive than the Commons Clause. To suggest the commons clause is piggybacking off the goodwill of the name of a more restrictive license is silly. > they are almost certainly asserting rights that the copyright holder doesn’t in fact have The author doesn't seem to understand how copyright works.
- antt 8y agoHaving been around for the GPLv3 debate this sounds exactly like it. A lot of gut feelings with very little in the way of factual knowledge of what copyright law is, or what the current problems we are trying to deal with are.
- xte 8y agoThere is NO midlife crisis, only we have two things together: - for first we do not have decent universities anymore, they substantially evolve from the center of our collective knowledge to companies or servant of companies aiming to deliver various kind of Ford-model workers; => we do not have enough developer, mostly only code monkeys unable to think autonomously, tied to proprietary devs model, even when the code is open (see below). - for second we miss hardware. In the past hw was a bit various (different architectures nearly on-par, in concurrence) and reasonably open, now we have essentially arm for low power/mobile and x86 for the rest and they are more and more closed. On software side is even worse since we restore ancient mainframe model with the "mainframe" "outsourced to the cloud". On "proprietary mental tie" in young people: simply new technicians do not think at scale because "the cloud" do that business and do not think in terms of local, desktop/user-centric computing. The "web" seems to be something like a local resource, always available. That's led to bad design for freedom. That's led to webUI instead of ml/news, dependency on someone's else services etc without thinking. All the above crisis are not FOSS nor OpenSource, are social. They can be solved ONLY at social level.