Hacker News new | past | comments | ask | show | jobs | submit login

I don't care so much about the AGPL specifically, but it's a single known license, rather than every time I find a new project having to find out what "interesting" license they cooked up this time.



yes but afaict SSPL was kiiinda becoming a de facto "f off AWS" license that was generally becoming standard. thats all any of these vendors want, they're not coming up with new licenses just for shits and giggles.

standards evolve over time, it was entirely possible that Grafana could have thrown its weight behind SSPL and helped legitimize it more.


> Grafana could have thrown its weight behind SSPL and helped legitimize it more.

Which would not have been a good thing in any way, so I'm glad they didn't do that.


This would've been nice. I think we are not far from the OSI having to recognize that SSPL is the future whether they like it or not, and possibly moving from obstructionist to a more constructive point, where they help evolve the SSPL to address their concerns, while recognizing that it is a copyleft open source license.


A license doesn't get to be called open source just because it's popular. Look how popular Windows is. Is it open source too?


The only thing that differs between SSPL and the AGPL in terms of being open source or not is that one particular group of people has decided one is Open Source(TM) and one is not.


> one particular group of people

I assume you mean the OSI. But it's not just them with a problem with the SSPL. Debian and Fedora both reject it too, independently, for being non-free.


But it is free. It solely conveys an expectation that you also release related tooling for free as well. If it's not a free license, the AGPL isn't either.


What's your definition of "free"? Because it's certainly not the same as the FSF's.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: