AOSP as RQ2's third organization, and why it can only ever be RQ2's¶

To separate an organization from its codebase family, RQ2 needs several projects per organization in one shared language on both sides. Qt's C++ libraries have that; a second organization with several C++ projects on public Gerrit supplies the other side. AOSP (android-review.googlesource.com) does: seven C++-dominant projects (art, system/core, bionic, frameworks/native, frameworks/av, external/perfetto, system/netd), about 40% of merged changes carrying inline comments in a sample of thirty. It answers residential addresses and refuses datacenter ranges, so it is fetched from a workstation, and fetch --project bounds it and records the restricted query in the snapshot.

Its public review record ends on 2025-03-27. The fetch shows 547 to 753 merged changes a month for these projects through 2025-03, then 2 to 9. Google moved Android development to internal branches that week and made aosp-main read-only (9to5Google, 2025-03-26; Android Authority). AOSP therefore has no dev or test window under RQ1's registered windows and cannot join RQ1. RQ2's client design needs no time split, so its months 2024-11 to 2025-03 serve, extended back to 2024-01 for volume.

The same filters, a different mix of what they drop. Per month AOSP yields about 220 examples against OpenStack's 458 and Qt's 880. The drop profile differs in composition rather than in kind: comments by the change's own author account for 40% of AOSP's drops against 21 to 24% elsewhere, metadata files for 30% against 39 to 55%, unanchored comments for 19% against 12 to 30%. Android reviewers and authors work in the review thread more, which the author filter removes on all three organizations alike.