uhh no, that’s technically not correct. google can not “restrict access to AOSP”. nobody can “restrict access” to an open source project. (at least not read/use access, if that’s what you’re talking about. they can exclude you from contributing your own code changes; for which case forks are the way to go)
They can restrict access to the current form of the Source as they are the Arbiters of who can obtain the Source. When I went to try to get the most recent AOSP some time ago, one of the requirements was agreeing to Google. All projects that stem out of the AOSP agreed to the terms Google laid out for the access to the AOSP. It is only “open source,” insofar as Google allowing one to access it. It is akin to a park that is free to access, so long as you pay the toll booth at the authorized road to get there.
uhh no, that’s technically not correct. google can not “restrict access to AOSP”. nobody can “restrict access” to an open source project. (at least not read/use access, if that’s what you’re talking about. they can exclude you from contributing your own code changes; for which case forks are the way to go)
They can restrict access to the current form of the Source as they are the Arbiters of who can obtain the Source. When I went to try to get the most recent AOSP some time ago, one of the requirements was agreeing to Google. All projects that stem out of the AOSP agreed to the terms Google laid out for the access to the AOSP. It is only “open source,” insofar as Google allowing one to access it. It is akin to a park that is free to access, so long as you pay the toll booth at the authorized road to get there.