To summarize the article: they will deliberately open-source any updates several years later, or whenever they feel like, to ensure Stock Android is the only OS you use and new features available for people who pay Google money, which also includes security updates.
This is not at all a summary of the article. They’re moving to trunk-based dev to reduce merge conflicts coming in from the public on AOSP.
I don’t like it, because those few devs who contribute to AOSP without an agreement currently will have lagging code, but what you describe is just plain wrong. Is it possible? Sure. But it always has been, that doesn’t mean that’s what is happening.
Is it possible? Sure.
Even then, not really. Not legally, anyway. Open source licences require that the user be provided with the source code (if requested) alongside the binaries. If they roll out an update to Android (to code which is under an open source licence), they have to release the code at essentially the same time. Rolling out an update and then withholding the source code for an unnecessarily long time would be against the terms of the licence.
Is it possible? Yes
Is it likely given Corpo take over of civilization? Also yes…
Good clarification. It’s also worth clarifying that choosing hidden trunk based development instead of public trunk based development makes it clear that community contributions aren’t one of their priorities.
Sounds like good news for mobile linux!
Right after Linux on desktop takes off, which is sure to happen any day now.
I don’t need desktop linux to “take off”, I’ve happily used it for a decade. I don’t need mobile linux to become mainstream. I just need it to be a bit better than it currently is.
time to switch to graphene or e/os?
graphene is a fork of stock android, so wouldn’t this affect them?
