(edit: typo)
(edit: typo)
It's an AGPL + AWS-is-killing-our-support/monitoring/ops-business license.
If I found a bug, and was adventurous to fix it, I can still open a JIRA and submit a PR to the project ...
The license is no longer OSI approved, so how do you know what you're allowed or not allowed to do?
How do you know that what's keeping AWS from using it isn't also creating a problem from you?
Have you consulted with a lawyer?
That's one benefit of using actual Open Source. You have a definition that all licenses have to comply with, such that developers know exactly the set of freedoms that's common between all of them.
Once you step out of that definition, you're on your own. So you know, I wouldn't take legal advice from random people on HN, you might run into problems.
Free software: free for modification, expansion or forking. Possibly free for profit (BSD license)
Source Available: Source is available but under restrictions. Locked room source viewing under NDA to confirm there aren't vulnerabilities for example.
Source-available: You can view the source, perhaps freely, but can't modify or release your modifications.
As you can see, "open source" give s only half of those freedoms: to study code, it is not mandadory that you actually can modify it.
So, not all opens source software is free. Check out licence comparison and approvals page at Wikipedia.[3]
[1] https://www.fsf.org/ [2] https://www.gnu.org/philosophy/free-sw.en.html [3] https://en.wikipedia.org/wiki/Comparison_of_free_and_open-so...
At the same time, we see a MongoDB example: a software, which definitely is open source, but also definitely is non-free.