Interesting. The post is about whether a license prohibiting SaaS competitors is "open source" and whether it might work out as a good way to ensure project sustainability. In this context "source available" means that you have the source code but you can't use it to compete with the project owner. [Kinda puts Omarchy in a different light don't you think?] There is another, I think different, form of "source availabl…
'Source available' is not open source, and that's okay
11–20 of 172 posts
Re: 'Source available' is not open source, and that's okay
#12What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? To an outsider it looks like counterproductive bickering between people on the same team.
Re: 'Source available' is not open source, and that's okay
#13Re: 'Source available' is not open source, and that's okay
#14What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? To an outsider it looks like counterproductive bickering between people on the same team.
The moment you change a single line of that license I now have to pay extremely close attention to those details again.
This isn't a naive idealism thing - there are very solid, boring, selfish reasons for caring about this.
Re: 'Source available' is not open source, and that's okay
#15Re: 'Source available' is not open source, and that's okay
#16What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? To an outsider it looks like counterproductive bickering between people on the same team.
> What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? The part where the license says "Don't run this on your server and charge people money for it, or we will sue you"? I know that everyone thinks of Big Tech absorbing your project into their SaaS when they do this, but there are other ways (say AGPL) to combat that. O'Saa…
I kind of thought that it was more about stuff like sharing and personal development and edification and the ability to see inside and understand things. But let's get really divisive over the money stuff.
Re: 'Source available' is not open source, and that's okay
#17What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? To an outsider it looks like counterproductive bickering between people on the same team.
> What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? The part where the license says "Don't run this on your server and charge people money for it, or we will sue you"? I know that everyone thinks of Big Tech absorbing your project into their SaaS when they do this, but there are other ways (say AGPL) to combat that. O'Saa…
A bit offtopic but could re-generation of the project with LLM (with for example prompt "rewrite the changing every line of code") help protecting from being sued? If yes, then the OS licensing is doomed to fail.
Re: 'Source available' is not open source, and that's okay
#18Earlier quoted context omitted.
> What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? The part where the license says "Don't run this on your server and charge people money for it, or we will sue you"? I know that everyone thinks of Big Tech absorbing your project into their SaaS when they do this, but there are other ways (say AGPL) to combat that. O'Saa…
I didn't ask which part of the license violates OSS values, I asked what those principles and values are. I will infer that "anybody can do whatever they want with the code" is the principle you are referring to. I kind of thought that it was more about stuff like sharing and personal development and edification and the ability to see inside and understand things. But let's get really divisive over the money stuff.
In the case of the janky new 37signals license: what exactly counts as "... where the primary value of the service is the functionality of the Software itself"?
Who gets to define the "primary value" of the thing I built?
Re: 'Source available' is not open source, and that's okay
#19What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? To an outsider it looks like counterproductive bickering between people on the same team.
Re: 'Source available' is not open source, and that's okay
#20Earlier quoted context omitted.
> What principles and values of the open source movement are protected by staunchly refusing to allow "source available" to call itself open source? The part where the license says "Don't run this on your server and charge people money for it, or we will sue you"? I know that everyone thinks of Big Tech absorbing your project into their SaaS when they do this, but there are other ways (say AGPL) to combat that. O'Saa…
I didn't ask which part of the license violates OSS values, I asked what those principles and values are. I will infer that "anybody can do whatever they want with the code" is the principle you are referring to. I kind of thought that it was more about stuff like sharing and personal development and edification and the ability to see inside and understand things. But let's get really divisive over the money stuff.
> I will infer that "anybody can do whatever they want with this code, OR ELSE YOU'RE NOT WORTHY" is the principle you are referring to.
I feel like there's cynicism in your phrasing, but a perhaps more neutral phrasing would be "Don't pick and choose what specific circumstances your users can use this for".