Earlier quoted context omitted.
An incredibly incomplete port without many of the core security features and decent updates is not GrapheneOS. It isn't possible to bring GrapheneOS to Fairphone devices. > It's not as though we're talking about a device with hardware specs locked behind an NDA and drivers that only support outdated kernel versions. Fairphone 5 and earlier have an end-of-life Linux kernel. Fairphone 6 is approaching the same fate. No…
Yes, I realize that the official stance is that it isn't grapheneos without the security features. That doesn't change the fact that someone who won't have the security features either way (and presumably doesn't care because otherwise he would switch to a different piece of hardware) might want the option of using a build of grapheneos that isn't officially condoned by the maintainers. (That's kind of the whole poin…
An OS without the core features and updates of GrapheneOS clearly isn't GrapheneOS. It's not permitted to refer to it as such.
> That's kind of the whole point of FOSS, right?
No, the point of FOSS is that you can take all of our code and use it for other purposes. Calling an incomplete port to another device GrapheneOS is misleading users. It isn't GrapheneOS and must have a unique name.