1. Understand Chromium-Try-Flakes:
   * P0 how it detects flaky tests in CQ:  https://cs.chromium.org/chromium/infra/appengine/chromium_try_flakes/status/cq_status.py?q=fetch_cq_status
   * P1 how it files/updates Monorail bugs of flaky tests
   * Ask stgao@ for docs about CTF
   * The task here is to make CTF report detected flakes to Findit even after CTF hits the limit of bug updates
2. Review the new BQ query to detect flaky tests: https://chromium-review.googlesource.com/c/infra/infra/+/1031017
   * Current query is https://cs.chromium.org/chromium/infra/appengine/findit/services/flake_detection/detect_flakes.py?q=_CQ_FLAKES_QUERY
   * The task here is to define the output schema of the query that are needed to record flake occurrences, find flaky tests, file/update bugs, and show info on UI/bugs, etc.
3. Understand the data model of the new flake detection on Findit side: https://cs.chromium.org/chromium/infra/appengine/findit/cron.yaml?q=detect-cq-flakes
   * The task here is to refine the data model to support multiple projects.
     Besides Chromium, WebRTC team has feature request to support their cases as well. Later we might want to support v8 too.
   * A design doc might be appropriate here.
4. The end goal of this is to have a better & standalone flake detection as a appengine module/service within Findit, and then deprecate CTF.