Earlier this year however, I discovered that a well-known company had taken the code - disappeared underground with it for several months, improved upon it, utilized the capability in their advertisements and demos and in the end posted the code utilizing their own source control system, detached from any state of that of the upstream project's. Even to the extent some posters around the web thought libhybris was done by that company itself.
That kind of behavior ruined the initial reason I open sourced libhybris in the first place and I was shocked to the point that I contemplated to by default not open source my hobby projects any more. It's not cool for companies to do things like this, no matter your commercial reasons. It ruins it for all of us who want to strengthen the open source ecosystem. We could have really used your improvements and patches earlier on instead of struggling with some of these issues.
This ladies and gentlemen is the reason for the GPL. This lets you sue the living piss out of people like this.
-What does this mean for Android apps?
-Is it possible to run Android apps without Myriad?
-And is lybhibris built in Sailfish ?
This is not very clear to me. Can someone please elaborate on this?
-What does this mean for Android apps?
-Is it possible to run Android apps without Myriad?
-And is lybhibris built in Sailfish ?
This is not very clear to me. Can someone please elaborate on this?
This ladies and gentlemen is the reason for the GPL. This lets you sue the living piss out of people like this.
No, it doesn't. The GPL does not stop anyone to release the code as a tarball instead of systematic commits to the repository, and you are only obliged to give out the code to users of your program. If it's only shown in demos and used in-house it's legal not to do so. It's bad bad manners anyhow, especially from an open-source company like canonical. I think there was similar behaviour from Apple with khtml/webkit, but they changed, too.