@divVerent @fireborn @larsmb @semitones @thomas @mpldr @j_j Multiple companies have made it clear that having any GPLv3 code would be a significant barrier to working with them. Their legal departments do not want to have even the possibility of it being included. They want a policy against using it as AOSP has. That's why AOSP has that policy. Google doesn't have that policy themselves elsewhere. They use GPLv3 code in ChromeOS. It's not in AOSP because of what other companies want.
@GrapheneOS @fireborn @larsmb @semitones @thomas @mpldr @j_j Then maybe GrapheneOS has to remain disabled hostile because these companies are, and the solution could be a community spinoff based on GrapheneOS source releases.
Kinda sad though.
@divVerent @larsmb @GrapheneOS @semitones @thomas @mpldr @j_j I'm not sure what companies they are working with, but the companies might not be disabled-hostile, just gplv3 hostile. I'm currently discussing with one of the maintainers in another thread about what's going on, and what could be improved.