Simply rebuilding code, without adding value or changing it in any way, represents a real threat to open source companies everywhere. This is a real threat to open source…
This is beginning to sound like they’re calling open source piracy.
“Noooo, you can’t copy it. That’s not fair.”
Actually, they’re beginning to sound a lot like Microsoft. It’s their job to complain about FOSS but still contribute.
Hm. Perhaps Red Hat is trying to take Microsoft’s place. In that case…
“Simply ignoring licenses, without acknowledging their terms and dismissing open source practices while still contributing to the FOSS community, represents a threat to closed source companies everywhere. This is a real threat to closed source…”
Yo, Microsoft. Don’t worry about the Activision acquisition. You have new competition to acquire.
Sarcasm aside, this is what we should have expected once they were acquired by IBM. You know, that company which has only ever behaved in an ethical manner for the last… century? Some fun history there. People should read up about it. Especially the '30s and '40s. And then jump to the '80s and '90s where they seem to still be stuck because they’re kind of pulling a “pirates of Silicon Valley” thing here.
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.
This is beginning to sound like they’re calling open source piracy.
“Noooo, you can’t copy it. That’s not fair.”
Actually, they’re beginning to sound a lot like Microsoft. It’s their job to complain about FOSS but still contribute.
Hm. Perhaps Red Hat is trying to take Microsoft’s place. In that case…
“Simply ignoring licenses, without acknowledging their terms and dismissing open source practices while still contributing to the FOSS community, represents a threat to closed source companies everywhere. This is a real threat to closed source…”
Yo, Microsoft. Don’t worry about the Activision acquisition. You have new competition to acquire.
Sarcasm aside, this is what we should have expected once they were acquired by IBM. You know, that company which has only ever behaved in an ethical manner for the last… century? Some fun history there. People should read up about it. Especially the '30s and '40s. And then jump to the '80s and '90s where they seem to still be stuck because they’re kind of pulling a “pirates of Silicon Valley” thing here.
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/
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.