Or am I reading it wrong? I am not a lawyer.
Also how does this work with contributor contributions? Does the owning SaaS get the benefit of contributor work instantly while everyone else has to wait 2 years? What about the contributers themselves?
You may want to allow certain uses (self-hosting, etc) even before it transitions to a fully open-source license. Having access to the source code can also help SaaS users debug certain situations.
And yeah, by my reading essentially people can contribute code or publish patches (with just a plain MIT license in principle), just the original and derivatives still can't be used for non-permitted purposes until the timer is up.
That requires trust that the company will do this. The FSL is irrevocable and comes with a future promise.
> Also how does this work with contributor contributions?
The same way as any other thing with a CLA works. If you don't have a CLA, then you have a bit of a mess.
But then again I think this only prevents small players from "competing" by self-hosting, so the revenue loss there would be minimal either way. Large enterprises are too incompetent to even self-host a single self-contained binary, so for those the availability of source code and ease of hosting would make no difference, they would still use the SaaS.
That Sentry is a pain to deploy is not really intentional, it just happened over the years. However because it's a pain to deploy it also opens up a market for people that create managed deployments so I would say, that if anything, it made it worse. For self deployed Sentry you do not need to pay cent, the license explicitly allows it.
I'm personally on the fence how much of it is intentional... from the_mitsuhiko's side it probably isn't, but "the purpose of a system is what it does" and all.
O'Sassy came up recently in one of the forums I lurk in [0], and as discussed there, I tend to agree with Adam Jacob (SystemInit) and others that FSL is definitely one way out but doesn't totally solve the commercialization aspect, because the code & all that IP is still readily available.
Adam, in this talk [1], argues that like RedHat (and unlike Canonical), Open Source businesses must learn to separate source license from distribution license and if they do so, the money is there to be made (in a b2b setting, at least).
> What I have found interesting in the years since is that many companies are wrestling with the same problem, but feel that the two year head start the FSL gives is too aggressive.
... if the companies conflate Open Source and business models, rather it being merely a Go-To-Market (like open core).
Especially true for dev/infra upstarts competing with incumbents (PostHog v Amplitude / GitLab v GitHub [2]), and lately for AI labs (DeepSeek/Qwen/Llama v GPT/Gemini/Claude). In a role reversal, BigTech also uses Open Source to commodotize its competition's advantages (Android v iOS / k8s v Swarm / IE v Firefox/Chrome) [3].
[0] https://forum.fossunited.org/t/6878
[1] https://www.youtube-nocookie.com/embed/watch?v=rmhYHzJpkuo / Summary: https://gemini.google.com/share/e21cd1bacff6 (mirror: https://archive.vn/Jzhk3)
[2] https://www.heavybit.com/library/video/commercial-open-sourc... / https://archive.vn/jQh27
Whereas, for example, trademark protections have shown to fail easily.
So people can argue it doesn’t work, but so far we only have evidence to the contrary and Sentry is quite successful.
So, RedHat has also been successful?
GP says that some companies don't find FSL aggressive enough, despite it having worked nicely for Sentry. And that's similar to the point Adam makes: That Open Source (per OSI not FSF) is a development model not a business model. Companies that don't want/need to prioritize collaboration tend to use FSL / BUSL / etc; but those licenses aren't really going to significantly change their development or business (other than prevent competition from using it as-is, but now the code is out there anyway [0][1]), and so they might as well go close source (and Lockdown the code, too).
> issue is these are mostly academic points of view
Both, commodotizing competition (through OSS) and using OSS as Go-To-Market aren't academic PoVs, I don't think.
[0] And trained on by LLMs, which makes cloning probably that much faster? https://x.com/paultoo/status/1999245292294803914 / https://archive.vn/kTiyZ
[1] Companies will deep pockets and technical expertise can/will anyway clone it: https://bcantrill.dtrace.org/2018/12/14/open-source-confront...
The idea that FSL ~= Closed Source is entirely wrong and misunderstands the value that an open distribution gives. We have 10s of thousands of customers that run Sentry self-hosted. We regularly get contributations back to our core service - both in code and (what we prefer) other artifacts like feedback.
We were "Single Origin Open Source", which is extremely common whether people like to believe it or not. Its the entire premise of the sustainability issue in the industry. Thats not just an issue for commercial entities, its also most of the big open source software people rely on. In our case though we have a great business model that makes it entirely sustainable, and now have built a solid licensing mechanism around it that protects that, while ensuring our community is still successful.
Ive written about a lot of these kinds of things:
https://cra.mr/open-source-is-not-a-business-model https://cra.mr/open-source-and-a-healthy-dose-of-capitalism https://cra.mr/the-busl-factor
These same issues around single origin open source are why we started the no-strings-attached funding mechanism via Open Source Pledge (https://opensourcepledge.com), why we push Fair Source (https://fair.io).
Maybe others will find defensible models, but I'm skeptical. I also respect Adam, but last I understood it the model they were going after sounded pretty similar to trademark protection (which doesnt work).
I don't think we're disagreeing at all. I quoted Adam to drive the point that tech shops that value collaboration will tend to prefer OSI-approved licenses. That doesn't seem to be the case for Sentry:
[Sentry is] single-source. That is, [the Company behind it] are the authors and maintainers of the software, and [does] not expect the community to provide us with contributions. We still allow it, and are thankful, but we consider it our duty to develop our software.
At the other end of the "single-source" spectrum is SQLite which is closed to collaboration but is dedicated to public domain and requests a fee for "Warranty": https://sqlite.org/copyright.htmlIt does seem like Sentry wants control over distribution, but by the way of license? Adam proposes something similar (and I guess that's the reason he's okay with "Fair Source", like a few others too who want to unchain the idea and go beyond OSI / Open Source [0]):
[Sentry wants] to allow people to self-host our software.
> I also respect Adam, but last I understood it the model they were going after sounded pretty similar to trademark protection (which doesnt work).A counter example: The Android Open Source Project is OSS, and is firmly gate-kept by Google via trademark and other collaborative arrangements like the Open Handset Alliance and Linaro. That said, this is the happy case. Sentry clearly had a different experience with bigger tech shops (GitLab?) trying to monetize its offering without contributing anything back, which (tbh) sounds super terrible.
To me, there seem to be pathways to both succeed & fail with OSI-approved licenses (probably you'd argue... one'd fail more than succeed), and these licenses on their own are neither the only condition nor a sufficient one for business build around them to stumble and falter. That said, I get your point that "Fair Source" gives "single-source" projects a fighting chance, like it did for Sentry. I'd also have thought that the OSI-approved AGPLv3 (your reservations about copyleft notwithstanding) is enough to keep big shops from leeching from other high-quality mostly single-source projects... but may be I was mistaken (given MongoDB / Elastic / Redis / CockroachDB didn't think so; even if, Elastic & Redis switched back to including OSI-approved license, specifically the AGPLv3).
[0] as indicated here (linked to from one of your blog posts): https://medium.com/@nayafia/i-hate-the-term-open-source-a65f... / https://archive.vn/K7CHs
Our way of dealing with this was delayed open source publication. That led to the FSL [1], and later to bootstrapping the Fair Source initiative [2] to establish an umbrella term that does not conflict with Open Source. What I have found interesting in the years since is that many companies are wrestling with the same problem, but feel that the two year head start the FSL gives is too aggressive.
I actually still find that surprising. I would like to know whether this is a legitimate concern that two years is not enough, or mostly a perceived one. To me, moving to an Apache 2 or MIT license after a relatively short period is a much stronger statement than a license that risks the project effectively ending if the commercial entity is unwilling to relicense it more openly at the end of its life such as the O'saasy license.
[1]: https://fsl.software/
[2]: https://fair.io/