This is beginning to sound like they’re calling open source piracy.
No, they’re pointing to things in the past like what Amazon was doing to Elastic, MongoDB, Redis, and others where they (legaly) took the others companies code and made it available in a very simple way an AWS for free so that people would buy other services from AWS instead of paying Elastic and the others - who do do the development job - for hosting the databases. This destroyed their business model so they had to change their licenses from Open Source licenses to closed source licenses. So in this case Red Hat is in the same boat as Elastic and they are right that this is a threat to open source companies everywhere.
So, is this something they could have solved using a different licensing strategy? Seems like they should have seen this as a possibility before banking their business strategy off of it.
Normally you start a open source project to scratch your own itch and to share it with other enthusiasts. Only once you decide to make it a business it’s kind of difficult to keep it Open Source and to make money, therefor they make it closed source and everyone is mad like this time with Red Hat.
No, they’re pointing to things in the past like what Amazon was doing to Elastic, MongoDB, Redis, and others where they (legaly) took the others companies code and made it available in a very simple way an AWS for free so that people would buy other services from AWS instead of paying Elastic and the others - who do do the development job - for hosting the databases. This destroyed their business model so they had to change their licenses from Open Source licenses to closed source licenses. So in this case Red Hat is in the same boat as Elastic and they are right that this is a threat to open source companies everywhere.
edit: Some more background info about this problem: https://techcrunch.com/2018/11/29/the-crusade-against-open-source-abuse/
Should be obvious, but I will point it out anyway… “Open source” is a higher priority than “open source companies”.
So, is this something they could have solved using a different licensing strategy? Seems like they should have seen this as a possibility before banking their business strategy off of it.
Normally you start a open source project to scratch your own itch and to share it with other enthusiasts. Only once you decide to make it a business it’s kind of difficult to keep it Open Source and to make money, therefor they make it closed source and everyone is mad like this time with Red Hat.