Unsure what you mean by link against it. GPLv3 requires making the entire project it is bundled with GPLv3 as well. GrapheneOS would need to relicense the entire OS and bundled apps as GPLv3 to allow them to use any app with that license.
They mean linking as in [1] against a GPLv3 work to create a derived work. Simply including a GPLv3 application in a aggregation of different works (e.g. an OS image) does not require everything else to be GPLv3.
The GPLv3 only applies to a work and works derived from it, so either if you take an existing GPLv3 project and modify it or if you link against a GPLv3 project. In these cases, the other code needs to be under licenses that are compatible with the GPLv3.
This is clearly described in the GPLv3:
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
Go read the GPLv3 license and/or ask yourself how Linux distributions are able to ship a mix of GPLv3, v2, MIT, BSD, etc licensed software all in the same image.
GrapheneOS may or may not have a policy against shipping GPLv3 software (I don't know), but if they do, it's a political or business decision, not a restriction imposed by GPLv3.
I like Heliboard a lot, but its autocorrect gets stuck in the mud all the time.
It completely falls apart and starts injecting nonsense phrases made up of nonsense misspelled words moment you miss a space ('v' or 'b') or type a really long word it doesn't know.
It also stubbornly incorrects other things like 'a' into "and" if it thinks it knows a phrase fragment. It's always wrong. It just happened to me now twice. Above, "or type a" became "or type and". Also, "it's" became "IRS".
Heliboard would be perfect if it stuck to word-only spellcheck and never split words. Just now again, it tried correcting "heliboard" into "hellenized" and "he lib oars".
This is not a matter of just lowering how aggressive the spellcheck is. It will still generate slop every time. The only real option is to completely turn it off. Futo can have similar problems, but there are a lot more options to tweak and the defaults aren't so bad.
If you are referring to Heliboard as an AOSP board replacement, that cannot work, GrapheneOS cannot use GPLv3 projects.
If you mean it as a user installed app, please disregard.
Could you please elaborate? I wouldn't think this causes an issue unless they need to link against it, which I don't think they do.
Unsure what you mean by link against it. GPLv3 requires making the entire project it is bundled with GPLv3 as well. GrapheneOS would need to relicense the entire OS and bundled apps as GPLv3 to allow them to use any app with that license.
They mean linking as in [1] against a GPLv3 work to create a derived work. Simply including a GPLv3 application in a aggregation of different works (e.g. an OS image) does not require everything else to be GPLv3.
The GPLv3 only applies to a work and works derived from it, so either if you take an existing GPLv3 project and modify it or if you link against a GPLv3 project. In these cases, the other code needs to be under licenses that are compatible with the GPLv3.
This is clearly described in the GPLv3:
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
[1] https://en.wikipedia.org/wiki/Linker_(computing)
Literally none of what you said is true.
Go read the GPLv3 license and/or ask yourself how Linux distributions are able to ship a mix of GPLv3, v2, MIT, BSD, etc licensed software all in the same image.
GrapheneOS may or may not have a policy against shipping GPLv3 software (I don't know), but if they do, it's a political or business decision, not a restriction imposed by GPLv3.
I like Heliboard a lot, but its autocorrect gets stuck in the mud all the time.
It completely falls apart and starts injecting nonsense phrases made up of nonsense misspelled words moment you miss a space ('v' or 'b') or type a really long word it doesn't know.
It also stubbornly incorrects other things like 'a' into "and" if it thinks it knows a phrase fragment. It's always wrong. It just happened to me now twice. Above, "or type a" became "or type and". Also, "it's" became "IRS".
Heliboard would be perfect if it stuck to word-only spellcheck and never split words. Just now again, it tried correcting "heliboard" into "hellenized" and "he lib oars".
This is not a matter of just lowering how aggressive the spellcheck is. It will still generate slop every time. The only real option is to completely turn it off. Futo can have similar problems, but there are a lot more options to tweak and the defaults aren't so bad.
I turn off automatic autocorrect except for "I". I can use it manually when I need it (jot often).
Autosuggestions are nice to have but there is no autocorrection that really works well in my experience regardless of OS.
this was my experience. the autocorrect for heliboard is beyond atrocious and renders the keyboard unusable.
i ended up just using gboard on gos because every other one i tried fell short.
hopefully the stock gos one can be reworked into an actually decent keyboard.