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)
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)