Both GNU and GrapheneOS have staunch requirements and will accept no compromises.
This is a situation where their requirements don’t align, so they’ll never reach an agreement.
GrapheneOS, for example, is also strictly against making the Fairphone line of phones a little more secure because it doesn’t meet all of their security requirements
In this case GNU won’t certify GrapheneOS as fully open because it includes binaries that aren’t open
The FSF is more along your line of improving the situation where they can
Graphene is totally open source, nothing is stopping fairphone from maintaining a port for their phones
GOS did reach out to them in the past, but they couldn’t reach a mutual understanding for support regarding hardware level patches for the fairphone 3 I believe. There’s a git issue about it
I see no reason the fairphone 5 couldn’t have GOS support, sure it’s missing some of the security requirements, but fair phone could build the branch and make it public
Both GNU and GrapheneOS have staunch requirements and will accept no compromises.
This is a situation where their requirements don’t align, so they’ll never reach an agreement.
GrapheneOS, for example, is also strictly against making the Fairphone line of phones a little more secure because it doesn’t meet all of their security requirements
In this case GNU won’t certify GrapheneOS as fully open because it includes binaries that aren’t open
The FSF is more along your line of improving the situation where they can
Graphene is totally open source, nothing is stopping fairphone from maintaining a port for their phones
GOS did reach out to them in the past, but they couldn’t reach a mutual understanding for support regarding hardware level patches for the fairphone 3 I believe. There’s a git issue about it
I see no reason the fairphone 5 couldn’t have GOS support, sure it’s missing some of the security requirements, but fair phone could build the branch and make it public