15 ms·
FSL: A License for the Bazaar, Not the Cathedral
- deleted 3y ago[deleted]
- dsagal 3y agoIt makes sense for a successful product that’s being hurt by competitors packaging it up and selling as a paid service. My advice: for a younger product, keep it actually open-source (FOSS). With either Sentry’s FSL license or FOSS, you as a user can run your own. If you want a paid managed service, you can pay Sentry. With FOSS, there can be competitors who offer such service using the same exact up-to-date version, and undercut Sentry on price (since they aren't paying developers). With FSL, they’d have to run a 2-year old version. That’s a disincentive to competitors. BUT: even with FOSS, a similar disincentive exists, because the maker of the FOSS software could decide to change license, forcing competitors to run a stale version or invest into their own development, or pay up for licensing. Seems if you are small enough, pure FOSS is better for this reason (the option to release future changes under a different license is always there). But if you are big enough to have competitors, and you can’t convince enough competitors to pay or revenue share (e.g. through support agreements), then FSL can be a way to twist their arms without hurting most other users too much. (It does hurt to some extent, as the many arguments in this discussion point out.)
- pabs3 3y agoOpen source means surrendering your monopoly over commercial exploitation: https://drewdevault.com/2021/01/20/FOSS-is-to-surrender-your-monopoly.html https://drewdevault.com/2021/01/20/FOSS-is-to-surrender-your...
- Kharacternyk 3y agoSQLite is the first thing that comes to my mind when I think about "cathedral" projects, but apparently it's not truly "cathedral" in the original meaning ("…with no beta to be released before its time", while SQLite is built in the open, albeit by a few people).
- Throwfi44 3y agoI am not sure this is legal in my country! In Czechia "release" is a legal act done by author(or right holder). You can do it by uploading code on Github etc.. But it is something author did themselfs. You can not perform legal act (releasing) with extra conditions like a delay. Either you did it or not! For the same reason you can not put extra conditions in Last Will (house is yours, but you have to take care of my cats). That part is simply not enforceable and gets ignored by notary! So I am worried, clause about Apache license is invalid, and software may get forever stuck under less permisive license!
- the_mitsuhiko 3y ago> You can not perform legal act (releasing) with extra conditions like a delay. Either you did it or not! There are definitely fundamental legal questions in Open Source licenses that differ from country to country, but you're most likely incorrect that a delay cannot happen in Czechia. Delays in (non software) licenses are very common and have been held up in courts. In fact, that's the common case of many licenses that they hare different rights associated over time. > For the same reason you can not put extra conditions in Last Will I doubt that whatever regulates wills restricts contracts or licenses.
- Throwfi44 3y agoYes, they could put extra paragraphs that become valid after 2 years, that would be OK. But the way it is written, it changes existing license! Effectively making a new release! You can not do that in EU, what if user does not agree with the new licence? It is quite illegal in most EU countries! You can not swap licenses like that! Many scammers do that, and there are strong pro-consumer laws to prevent that! What is worse, it even terminates old license after two years! Really really stupid lawyer worked on this! Here is the text: > On the second anniversary of the date we make the Software available, the Software will become available under the Apache 2.0 license. On that date, the Terms and Conditions above automatically terminate and the following terms become effective:
- the_mitsuhiko 3y ago
- zlg_codes 3y agoHow is the FSL any different than tiered, expiring copyright terms? This is a step backwards for libre software. It's like a mix between copyright and patent, in the sense that the monopoly (patent) expires after a given point, but you're still bound by license terms that are less permissive than they should be to be libre software. For the record I don't care what qualifies as open source, as that is a commercialized term and thus will lean toward permissive or permissive + trademark stuff like the MPL and Apache licenses. It seems the best way to build libre software, from my perspective, is through the AGPL. Compliance is as easy as providing a link to the repository of code you use to provide the service. If a license like FSL catches on, what stops modified licenses from cropping up with extended expiry terms? Before you know it, a SaaS suddenly needs 5, no... 10 years before it becomes profitable! Because we should care about profit in a bazaar or a community... As well-meaning as these efforts are to help developers find more sustainable means of developing, I don't think this is going to help. Security patches in the community-friendly code will be 2 years behind, guaranteed. People who can't pay for the latest version will have to use an old version which might be broken. We need to come to terms with the idea that capitalism and volunteering can't easily coexist. The incentives and goals of business are opposite that of libre software development. Libre software seeks to enable everyone regardless of their assets. By all means, solicit ways to incentivize your work in libre software. Relicense if you must, but I will steer clear of this license like the plague. It is not compatible with software freedom until its expiry date occurs, and even then it's questionable and hard to trust. I care about software freedom but ultimately decided that I wasn't going to spend my time on something where other people participating couldn't respect me, or acknowledge and appreciate my contributions. I've been on both sides of that relationship and I know how it should be done, but few ever reciprocated when I tried to be cordial.
- fidotron 3y agoWhile I am not entirely persuaded the specifics of this license are correct it does seem to be a potential improvement over the status quo and so it is good that it is being tried. With the economic situation how it is I think we will see a lot of these sorts of things shake out as our current direction is unsustainable.
- mst 3y agoIt strikes me as "the least worst compromise license I've yet seen" and I mean that positively.
- mananaysiempre 3y agoI don’t think it’s reasonable to call it a “two-year exclusivity period”—it’s more like a two-year dead man’s switch. As long as the original SaaS is relevant you are never competing with it, because you won’t be able to reuse any security fixes that the original developer made. Unless, of course, you are Amazon or Oracle, and can afford an independent security team. I don’t know how I feel about this. Or, okay, right now I feel that I’ll believe it when I see the old versions actually go open source for, say, several times the declared period. (The first BUSL versions of Sentry, from 2019, only started running out their timers a year ago.) Otherwise, I ... don’t think that, say, Stallman would call it evil? It’s certainly better than the other non-FOSS possibilities. And yet I feel absolutely no desire to contribute (to the non-FOSS versions) under such conditions, and I wouldn’t suggest others do so, either. So I don’t know if there’s a “bazaar” to have here, or if the “bazaar” should spend its efforts on such cases instead of going elsewhere.
- the_mitsuhiko 3y ago> because you won’t be able to reuse any security fixes that the original developer made You are, just not in a competing commercial service. For that you would have to wait for two years. Which is precisely the point. In a non commercial, self hosted setting you're free to incorporate these patches.
- mananaysiempre 3y agoThat’s why I said “competing” and not “using”, yes. It’s just that for me the phrase “exclusivity period” would imply that you could compete as a provider of sufficiently-old versions. And technically you can, except the script kiddies will take you down in a heartbeat, and in that respect you’re in a very different world from the one the original developer was at that point in the past even if alternative offerings are ignored. (Consequently, the original developer is not competing against old versions of their own software the same way as Microsoft used to be competing against old versions of Office or Apple is now competing against older Macbooks.)
- 3y ago
- qznc 3y agoDoesn't the license conflict with itself? The "not-yet-Apache-licensed" code is obviously derived from the "now-Apache-licensed" code, thus it must be "Apache-licensed" too.
- the_mitsuhiko 3y agoNo, but that challenge would exist if it was GPL which is why a hypothetical FSL-GPL would not be possible.
- benj111 3y agoNo. If I write software I can release it how I want. I can release it as gpl. If someone approaches me wanting a closed source version I can do that. If I submit a patch to the Linux kernel I can also give that patch to Microsoft to put in Windows. The closed code isn't 'based on' Apache code. The copyright holders have released the older code as Apache.
- the_mitsuhiko 3y agoThat is true in principle but not how the FSL functions. The FSL ceases to exists at the two year anniversary and turns into another license (eg: Apache 2). If it were to turn into GPL the before and after code pieces would not be compatible. The original author would retain copyright and they alone could make that software available under another license (eg: dual licensing) but nobody else would be in that position.
- benj111 3y agoYes. I release software X under license that turns to Y license after z years. I am free to take exactly the same code and do the same at a later date. Or are you referring to code by a second submitter where their code goes gpl, but then you need to re get their permission to restart the clock. I still think you could work around that if the license is structured correctly. Treat the source tree as it stands at a point in time as a release that becomes open source 2 years later, but keep the core project closed. So all code in the project is always available to be in the project.
- ic_fly2 3y agoI like it. I totally get the problem projects like mongo, redis and sentry face. AWS, azure etc just eat their lunch and don’t help anybody. That will kill open source in the long run. This still gives me access to inspect the code, contribute fixes I might want, self host if I feel like it or pay someone for the SaaS if I don’t, knowing the money goes to someone who contributes to the project. And if the original authors bork the product and after two years it becomes clear they won’t fix their ways, I can fork the old product code I liked and develop it into the product I want. Heck if I’m right and my idea is better than the original I’ll eat their lunch too.
- pjmlp 3y agoWhat we have now is exactly what would have happened if the AT&T vs BSD lawsuit had come to a conclusion before Linux kernel came into the scene. Big iron UNIX would keep going and cherry picking from the BSDs as it had done until the lawsuit took place. It is no surprise that all new FOSS OSes for IoT, none of them embrace copyleft licenses.
- 0xDEF 3y ago>AWS, azure etc just eat their lunch and don’t help anybody I know that AWS made a blatant hosted version of Elasticsearch without contributing back but the other examples are less damning. Azure's MongoDB offering is just the MongoDB API on top of their own document-oriented storage and querying architecture. Their globally scalable Redis offering is most likely also their own implementation and only using the same API as Redis.
- geerlingguy 3y agoTwo years is like 20 years in most software ecosystems. If a JS library or mobile front end used this license, by two years the underlying tech that old version used would all be extinct.
- ic_fly2 3y agoYou’re not going to need this for a js library that doesn’t have a saas component.
- frognumber 3y agoIt's very hard for me to take anything which starts with CatB seriously. It was very charismatic, beating up a strawman which didn't exist, and zero of it played out as expected. Eric Raymond is mostly gone, as everything he's touched has failed. Open-source has started to realize Richard was right about ethics, as the two movements have increasingly converged. Richard, for his part, is still marginalized, socially awkward, and everything seems to be playing out by the playbook he wrote in the nineties. This writing is just as confused. The author is missing the basic points of a license: A license is like a constitution for an ecosystem for how people will interact, a check-and-balance on the monopoly power of the license-holder, and a community contract. The FSL is looked at through none of those lenses. The attempts at empathy with the opposing viewpoints clearly don't express an understanding of those viewpoints. The reasoning is just bad. Even taken at face value, a license which does not set up an ecosystem of equals is a cathedral license, not a bazaar one. The citation is weird. Analyses needed for licensing: - Who will contribute, and why? - What ecosystem is being set up? One of equals? One with a central party? - Why will my customers give me money? Does this preserve my ability to make money? ... and so on. Those require deeper dives. "If you build it, they will come" doesn't work. If you want contributions, for example (not everyone does), you want to do a deep dive on the needs, wants, and motivations of potential contributors. An ecosystem of equals (bazaar) will bring in more contributors, but also more competitors. I'll give a personal example: In my professional work, I use 100% open-source, largely to mitigate for the risk of what happens when the cloud vendor disappears. FSL mitigates that risk, while BUSL doesn't. The license seems non-crazy, though, and a huge step up from BUSL. What's concerning, though, is that it's completely unclear that the author understands why this license makes sense, so it's liable to be misused. It feels more accidentally-stumbled-upon.
- the_mitsuhiko 3y ago> What's concerning, though, is that it's completely unclear that the author understands why this license makes sense, so it's liable to be misused. It feels more accidentally-stumbled-upon. The author of the post (me) was part of the group at Sentry that created that license. I can’t dispel your interpretation that my writing is “confused” but I can assure you that a lot of thought went into the license. That blog post is not a “here are all the reasons for the license” but it narrows down on a very specific aspect of it. You can read the original announcement post for more context and you can also listen to a panel discussion about it with me, Chad from Sentry and Heather Meeker who helped us draft it: https://www.youtube.com/live/UB9fo7pnDzY?si=0HVI6FsR42Pn5yP2 https://www.youtube.com/live/UB9fo7pnDzY?si=0HVI6FsR42Pn5yP2
- James_K 3y agoSo, essentially, this is a closed source or source available licence. Anyone trying to develop open source with this will be stuck two years behind the official release and so it won't be worth trying. I don't get how it solves that freeloader problem either. The one benefit I can see is that it forces software to stay relatively up to date as, if they don't make enough changes in a two year period, they will likely be forked and someone else will add the fixes that the devs weren't. But this is also potentially a negative as it inventiveness regularly breaking compatibility with old versions. I don't see any benefit to the developer using this license except that it makes them feel like they are doing open source. A better approach would just be to accept public contributions under a closed, source-available licence. Or, better still, just offer separate personal and commercial licences.
- vanviegen 3y ago> Anyone trying to develop open source with this will be stuck two years behind the official release and so it won't be worth trying. Only if you're a direct SaaS competitor. In that case, you'll have to diverge based on two year old code, which seems fair to me. (And you're always free to start your own project, if you want to compete...) > I don't get how it solves that freeloader problem either. Because freeloading competitors are stuck with two year old code, putting them at a disadvantage, or compelling then to invest in that old code (some of which might find its way into the original branch). > I don't see any benefit to the developer using this license except that it makes them feel like they are doing open source. Is there really a need for this amount of negativity/scepticism?
- James_K 3y ago> Because freeloading competitors are stuck with two year old code, putting them at a disadvantage, or compelling then to invest in that old code (some of which might find its way into the original branch). This makes no sense though. If you don't want competition, why give your source away? If you do want competition, why put it at a disadvantage? That's why I am so negative about this license. It's just someone trying to have their cake and eat it too. Also, I don't see what's to stop someone free-loading off a two-year-old copy of your work.
- cowsandmilk 3y ago> It also enables contributions by the community for the latest version and not old source code. I have no interest in contributing to a code base that where my contributions wouldn’t be open source for two more years. You’ll find naive developers out there, but my free time won’t be spent contributing and my company would never allow me to contribute.
- bentlegen 3y agoThere are many people who use the software, for free, to monitor their own non-competing software projects (it turns out that overwhelmingly most people aren't competing with Sentry). Some people choose to scratch their own itch and commit small bug fixes. For example, if you are running Sentry internally and you're monitoring a dozen software projects with ~50 users, it might be in your interest to fix some edge case you've hit that's causing your team grief. You could also open up a ticket on GitHub, or do nothing at all and just continue to use free software as-is without contribution. It sounds like you aren't a user and have very little incentive to contribute. So I agree, don't!
- arp242 3y ago> my company would never allow me to contribute. So your company would rather spend significantly more time and effort to work around problems? Because that is what 100% closed source usually means: "I found some problem, the vendor can't be arsed to fix it, the solution probably isn't too complex, and now I need to do some complex stuff to work around it".
- phkahler 3y agoPlease stop using the Apache licenses. License compatibility is too important. Use MIT (my preference) or BSD if you want a "permissive" one and GPL or LGPL otherwise (v3+ preferred). Anything else is just making non-reusable code. Apache is the same org that actively harms one of the highest visibility open source projects by keeping "Open Office" around. Their licenses are similarly unwelcome IMO.
- the_mitsuhiko 3y ago> GPL or LGPL otherwise (v3+ preferred). I'm confused about your concern then if v3+ is preferred. Apache 2 is compatible with the GPL 3 family of licenses, it's just not compatible with the GPL 2 family of licenses. The only incompatibility of Apache 2 are GPLv2 licenses, but so is GPL 3. Apache 2 has some benefits to the user over MIT, but the GPL incompatibility is why there are two flavors of FSL.
- phkahler 3y ago>> Apache 2 is compatible with the GPL 3 family of licenses, it's just not compatible with the GPL 2 family of licenses. I doubt that. I'm not even sure the MIT license is compatible with GPL because it requires the notice be kept intact, which might be considered an additional condition if the code is merged with GPL licensed code. Apache 2 and GPL 3 might be compatible in spirit, but I doubt they are compatible to the point you can pull some Apache code into a GPL3 project and drop the text of the Apache license. Also, if it is essentially the same terms then there is NO reason to actually have a different license and it just confuses things. IMHO we actually need a new "do whatever you want" license besides MIT and BSD that make zero conditions on derived works or their inclusion of any particular license text. OTOH that would seem to imply you could claim the code as your own in the derived work (and then try to sue people using other legit forks for example).
- mst 3y agoThis sort of discussion is what leads me to be fond of license disjunctions - perl's use of Artistic|GPL being the one I'm most familiar with. The idea being that "you may use this software under the terms of ${license} or under the terms of the GPL" means there's absolutely no question as to GPL compatibility for the people who value that, and you can pick the value of $license to taste (I use the same license as perl for CPAN releases, but for other languages using whichever is the most popular permissive license you like in that ecosystem is likely a good answer). I note downthread you have reasons why you can't do that with the GPL, and it might be worth having an explanation of that written up somewhere findable given that honestly hadn't occurred to me so I may not be the only one, but I figure disjunctions are still worth mentioning as a general tool even if not applicable in your case.
- jorams 3y agoI might be missing something here, but this doesn't seem compatible with the bazaar model at all. You say > It also enables contributions by the community for the latest version and not old source code. But you will not be able to accept such contributions without an additional license, because you yourself would be unable to use them for a Competing Use (running your service). This makes it much closer to a cathedral, with a "small bands of mages working in splendid isolation". Sure, your work will be publicly visible, but that's it.
- tedivm 3y agoThat's their goal. The head of sentry's open source policy has openly stated that he, and sentry as a whole, want to change the definition of open source so that it has additional limits that make it easier to profit off of and control. This conversation from three months ago is really enlightening: https://news.ycombinator.com/item?id=36972824 https://news.ycombinator.com/item?id=36972824 When the head of open source was explicitly asked about whether they're trying to redefine open source his response made it very clear that they are- > > your end goal is to exclude commercial reuse from the open source definition > This is fairly accurate, though there are a range of possible outcomes we would be satisfied with. Anything they say should be considered with that in mind. These are not good actors in the industry, but are people who are trying to replace open source software with a shared source version. Unlike other companies, such as Hashicorp, who admit that their software is no longer open source Sentry wants to have their cake and eat it too.
- bentlegen 3y ago> but are people who are trying to replace open source software with a shared source version Note that the thread you link to is a situation where they took an entirely closed source product, CodeCov, and made it source available under BUSL (and now FSL). > Unlike other companies, such as Hashicorp, who admit that their software is no longer open source Sentry wants to have their cake and eat it too. From the parent article (FSL: A License for the Bazaar, Not the Cathedral): > But one thing is clear: until its expiration, the license does not qualify as Open Source. While I recognize the sensitivity around the term “Open Source”, I assert that the FSL's approach is more closely aligned with Open Source ideals than mere source availability. I consider it an “Eventually Open Source” license, though perhaps a more fitting term needs to be found.
- growse 3y agoThe definition of "harmful free-riding" is not good, and its use to justify the license is problematic. > Consequently, the common pool resource may be under-produced, overused, or degraded. Additionally, it has been shown that despite evidence that people tend to be cooperative by nature (a prosocial behaviour), the presence of free-riders causes cooperation to deteriorate, perpetuating the free-rider problem.” Software doesn't wear out, or degrade through use. The analogies offered to other, physical common services are nonsensical. Also, there's plenty of projects that are open source, have an enormous amount of usage, and don't suffer from this problem. The difference between these and projects which perceive they suffer from the "harmful freeloading" problem is not the license, it's a badly-thought-through business model. If your business model relies on no-one else using your software to compete with you, don't open-source the software. Especially don't whine about it and then pretend to open source it. Just do proprietary.
- tzs 3y ago> Software doesn't wear out, or degrade through use. The analogies offered to other, physical common services are nonsensical. But latent bugs are discovered at a rate that is roughly proportional to use, and for application software running under general purpose operating systems on personal computers or servers the operating systems and hardware gets updates which can cause problems for applications. That imposes a maintenance and repair burden if you want to keep applications working that is very similar to the burden imposed by wear and degradation when you want to eep some physical thing running.
- geerlingguy 3y agoI don't understand the philosophy of wanting to use open source and gain the community / benefits of it... but using a proprietary sales model. It just doesn't work, and once you start calling users of your software who contribute nothing back anything resembling "freeloader" (whether or not you use that word), you've lost the whole concept of why most of us care about true open source. We can use it, we can learn from it, and for a very select few, we can even contribute to it or support the main devs monetarily or otherwise.
- 3y ago
- tedivm 3y agoAs a reminder, the head of open source for Sentry came into hacker news and explicitly said he wants to destroy the existing definition of open source and replace it with one that is VC/Corporate friendly. > > your end goal is to exclude commercial reuse from the open source definition > This is fairly accurate, though there are a range of possible outcomes we would be satisfied with. Anything they say should be considered with that in mind. These are not good actors in the industry, but are people who are trying to replace open source software with a shared source version. Unlike other companies, such as Hashicorp, who admit that their software is no longer open source Sentry wants to have their cake and eat it too. Source: https://news.ycombinator.com/item?id=36972824 https://news.ycombinator.com/item?id=36972824
- bentlegen 3y agoThe source you link does not contain the quotes you cite.
- tedivm 3y agoSorry, fixed it.
- bentlegen 3y agoIt feels like you intentionally omitted his immediate follow-up to your quoted comment: > > my theory about embrace/extend/extinguish seems to be as accurate as I thought. > This is confused. Embrace/extend/extinguish means to initially participate in an open standard and then extend the standard in such a way that the non-extended version is sidelined. I'd encourage people to read the entire thread rather than seize on the cherry-picked comment, additionally loaded with terminology like "they want to destroy open source", which doesn't appear in the original thread. I can't speak for whit537, but I do work at Sentry, and I feel your comments about our intentions are disingenuous. We are open in that we feel the existing models don't fit our needs, and we're trying to evolve the language to make non-compete licenses more approachable and thus more mainstream. That doesn't mean an elimination of existing popular OSS licenses. We're even explicit in saying, "FSL is for SaaS businesses". That's pretty narrow, and probably excludes 99% of software. Note that the FSL is developed in the public, and echoes the language I've used above[1]. But if you believe pursuing additional licensing mechanisms means we're destroying OSS, there is probably little I can do to disavow you of that notion. [1] https://github.com/getsentry/fsl.software https://github.com/getsentry/fsl.software
- karmakaze 3y agoWhy doesn't Sentry simply use AGPL instead of this 2-year BSL? Are they so unable to compete in their space that merely copying and hosting a current version is a substantial threat (even if modifications are shared)?
- anonacct37 3y agoI wish Sentry would stop free riding on Free Software movement by pretending their product is part of it. Their product isn't Free Soft anymore. They feel that they can increase revenue with a more restrictive license, a business move that doesn't require this cathedral and bazaar white washing.
- zeeg 3y agoWe haven’t been “FOSS” for many years and don’t pretend to be. What’s your point? We also don’t ask you to build our software for us, and instead give it away for free.