Misleading headline. Instead of public repos, they’ll use source snapshots of each release. It’s technically correct because the development is going private, but the releases will remain open source.
If I understand you correctly, the developmental changes occurring between releases (every little step change/test) won’t be visible to us, just the final results in the form of the release code? (All corrections/clarifications accepted, hell, requested). We’d still be able to compile, but we wouldn’t necessarily have code for those small, incremental changes.
Correct. We will, of course, be able to create diffs between the released versions, for the whole project or for individual files (assuming they haven’t moved around).
Isn’t that sources available, not open source since they aren’t allowing community contributions, or am I misunderstanding that?
Kind of like how greyjay is source available but not open source?
Android is licensed under the Apache license 2.0, which is an open source license. Their Linux kernel modifications are licensed under the GPL v2. https://source.android.com/license
Accepting contributions is not required to be open source.
Google has shared more details on how AOSP will change after it makes Android OS development fully private
TL;DR
- Google has confirmed to Android Authority that the Android team will still review code contributions from external developers.
- The company also shared details on what branch of Android platform developers should work with from now on, as well as what will happen to other AOSP-adjacent projects.
- The details shed light on what exactly will change after Google takes development of the Android OS fully private.
What do they mean “help”? Does this mean that they’re going to have to suffer with the consequences of paying devs?
