Google's git hosts need their maintainers' written permission, as Qt's REST API does¶

# research(2026-10). The 2026-10-08 entry admitted android.googlesource.com on its own robots.txt, which leaves git fetching open (RFC 9309 ties a robots.txt to the scheme and authority it is served from, sections 2.3 and 2.3.1.2), and set aside the reading that the review site's Disallow: / expresses the operator's wish about the records themselves. That reading is the stronger one: RFC 9309 says its rules "are not a form of access authorization" (section 1), so compliance with a robots.txt does not settle whether collection is wanted, and Gold and Krinke (EMSE 27, 2022, section 4.2.5) extend a mining study's compliance to a platform's terms and conditions, citing a platform's demand that researchers stop collecting data it had not permitted. The study asked Chromium's infra-dev list on 2026-09-23, mentioning the AOSP data already held, and has had only an automatic reply; AOSP's own maintainers were not asked. So every googlesource git host is refused until its maintainers grant permission in writing: GIT_PERMITTED refuses android, chromium and fuchsia (fuchsia added), and every host's pacing floor now applies whether or not it is permitted.

This sets what "admitted for this use" means in item 1 of the H2 plan above: H2's foreign source is the first of Chromium, Fuchsia and AOSP whose maintainers grant written permission before the first H2 development contrast, in that order whatever order they answer in. Drafts to Fuchsia's discuss list, to AOSP's android-contrib list, and a narrowed follow-up to Chromium's infra-dev list (about 2,000 changes over git each) are with AJ. Data already held from these hosts stays out of every figure until then and is deleted on refusal.