@QCCEChris it seems this is going to be a similar situation to what we're already coping with now; that is to say, the updates are available in a timely manner because Graphene has access to them under embargo, but the source code won't be available.
I'm basing this conclusion on the current thread here: https://discuss.grapheneos.org/d/30133-google-will-now-only-release-android-source-code-twice-a-year/3
I'm going to take this opportunity to try life without a smartphone, both for the purpose of avoiding this bullshit and for my personal well-being. I've got time (~9mo) before my Pixel 6 is out of support, anyway.
@prettygood Reminds me of https://web.archive.org/web/20100816225601/http://mail.opensolaris.org/pipermail/opensolaris-discuss/2010-August/059310.html
> We will distribute updates to approved CDDL or other open source-licensed code following full releases of our enterprise Solaris operating system.
And then the promised source releases never happened anyway
🔜FOSDEM
@prettygood In case of Solaris, they're the copyright holders so they can do whatever regardless of the license anyway no?
🔜FOSDEM
@lanodan @prettygood Mhmm, I'd say it's also prime example why you shouldn't give away your copyright (e.g with CLA or the like)
Keeps some leverage in case those things happen
🔜FOSDEM
@lanodan @prettygood Not that doing things through court is easy but hey
🔜FOSDEM
:gondola_head: 🌿
:gondola_head: 🌿