3 ms·
The article links to an interesting view on how even AOSP is a no-go for Huawei: https://www.xda-developers.com/analysis-huawei-aosp-google-ban/ https://www.xda
by necovek 7y ago
The article links to an interesting view on how even AOSP is a no-go for Huawei: https://www.xda-developers.com/analysis-huawei-aosp-google-ban/ https://www.xda-developers.com/analysis-huawei-aosp-google-b...
What I find interesting is that Apache Licensed software can be relicensed even in proprietary form (as long as you make it a derivative work, with your derivative bits with a proprietary license), thus the easy way out seems to be to have a non-US entity make a proprietary fork of AOSP. I do not see a legal reason why this company would not be able to sell AOSP to Huawei under these conditions.
I am sure plenty of us remember the days when free and open source encryption software was distributed exclusively through non-US servers due to US export restrictions.
IANAL, so I wonder if I am missing something?
As for alternative platforms, I imagine plenty are US based/originating (QNX, webOS from Palm/HP originally, Android), but there are alternatives like Jolla and Ubuntu Touch which aren't.
While I dislike Huawei since they decided to stop sharing unlock codes for their phones, Huawei has one killer app that's not very much reliant on Android: camera.
Getting that camera app on one of the less known platforms and enabling Huawei phones for them would still make them appealing to a large number of customers in eg. Europe.
- fulafel 7y agoIs the article really right in this one? " A country banning its resident companies from engaging in contracts with a specific company breaks how our copyright system works, and as a result, breaks how open source licenses work. -- If Huawei cannot enter into a contract with Google, then they cannot enter into the Apache 2.0 licensing agreement with Google, which means that they would not have a license to distribute the AOSP codebase." If we look at the cited license (https://www.apache.org/licenses/LICENSE-2.0.html https://www.apache.org/licenses/LICENSE-2.0.html) it's just a one sided license from the copyright holder, not a contract between parties, right?
- masklinn 7y agoSoftware licenses are contracts.
- deng 7y ago> Software licenses are contracts. As lawyers usually say: it depends. https://lwn.net/Articles/747563/ https://lwn.net/Articles/747563/
- fulafel 7y agoVery interesting. So if this lawyer is right about the US, we need a new open source license that is explicitly designed to be not contract-like, to defend against Trump?
- rickdeckard 7y ago> Getting that camera app on one of the less known platforms and enabling Huawei phones for them would still make them appealing to a large number of customers in eg. Europe. Except that camera itself is not a killer-app. The major use-case of a mobile camera BY FAR is not just to capture content, but to share the content on social media, also in Europe. So whatever less-known platform the camera-app would be moved to, that platform would still also have to provide a good user-experience for Facebook, Instagram, Snapchat, WhatsApp, etc. So in the end, that less-known platform would need a SocialMedia app-ecosystem comparable to Android just to match the Android-experience for Camera...
- cosarara 7y agoOnce you are completely blocked from doing business, what do you lose by infringing copyright?
- tantalor 7y agoThe article speculates legal judgements & fines for violations. So, lots.
- cosarara 7y agoHow can the US fine Huawei if Huawei is not allowed to operate (and thus doesn't operate) in the US?
- cameronbrown 7y agoAny hope of being unblocked?
- rvp-x 7y agoQNX isn't US based, it's canadian.
- lmm 7y ago> What I find interesting is that Apache Licensed software can be relicensed even in proprietary form (as long as you make it a derivative work, with your derivative bits with a proprietary license), thus the easy way out seems to be to have a non-US entity make a proprietary fork of AOSP. I do not see a legal reason why this company would not be able to sell AOSP to Huawei under these conditions. IANAL, but: any such fork would remain a Derivative Work of AOSP in which Google would hold some copyright. When Huawei came to redistribute it, they would need licenses from all the copyright holders - this company, Google, any other contributors. Normally this does not matter: the Apache license states "each Contributor hereby grants You...", and You is defined as "an individual or Legal Entity exercising permissions granted by this License". No doubt the US government can enforce whatever capricious fines it likes within the US. But I find it hard to imagine a European court finding Huawei guilty of copyright infringement for distributing Google work that came with a clear, simple license granting them permission to distribute. If the US government wants to say that Google can't grant that permission, that's between Google and the USG. And given that the Apache license states that the grant of permission is "perpetual, ..., irrevocable" and came with a copy of AOSP that Huawei has no doubt downloaded and read years before the current crisis, trying to revoke that permission now doesn't work either.
- jeremyjh 7y agoI believe that if Google doesn't license AOSP to Huawei (whether by their own free choice or not), it might be that they are in violation of the Linux kernel GPL2 agreement that they have made with Linus / Linux Foundation.
- tantalor 7y agoElaborate?
- jeremyjh 7y agoUsers of GPL licensed software such as the Linux kernel, are bound by the terms of that license to release modifications under the same license. Android and AOSP incorporates and uses the Linux kernel; this is the entire reason AOSP exists. You cannot pick and choose which users you distribute sources to under the GPL.
- gpm 7y agoAs long as no one distributes it (binary or code) to Huawei I don't think they would be in violation of the license. They aren't personally required to do so. But anyone with access to the binaries (not in the US I guess) is allowed to redistribute it to Huawei, and the GPL then requires google to grant Huawei a license, not doing so would appear to be in violation of the license. > 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided [irrelevant terms here] > 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. IANAL
- vxNsr 7y agoI think that article is taking the wrong approach. If Huawei doesn't have a US presence, which they won't after this, and if they really are an arm of the Chinese espionage complex then what's to stop them from just downloading ASOP source and doing whatever they like with it, based on ARM's reaction is unlikely other western countries are gonna allow Huawei much longer so it really only has access to the Chinese market where it's protected. Now it's role will be more FBI vs CIA.
- chasd00 7y agoThat's my thought, why would Huawei even care about licensing? They've certainly stolen plenty before (Nortel and Cisco). Any discussion about licensing and contracts is meaningless when you're dealing with an entity perfectly ok with just stealing the product.
- taffer 7y agoThis is really interesting and raises further questions from me: - Can open source licenses be unilaterally revoked? - Is Google the sole proprietor of AOSP? - If there are other proprietors of AOSP, do they have a say?
- muyuu 7y agoLock-in through privileges in access to infrastructure, control via default services, "system as a service" etc means OSS licences no longer provide much of a guarantee towards the ownership and control of your own software and hardware. But this has been the case of a long time already. Maybe a consortium of China-backed companies (Huawei, Xiaomi, OnePlus, etc) could create a viable fork of Android and/or put enough weight behind an alternative app store that it could be a viable alternative for the mainstream (say, F-Droid, Aptoide, etc). Thing is, on such short notice they will struggle and it doesn't seem like they have preemptively prepared to a full-blown switch of OS/ecosystem AND also an architecture switch (British ARM also joining the US sanctions).