The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/24a3674be9f96f6543ffc187cdcda81fd0b5ccdc

commit 24a3674be9f96f6543ffc187cdcda81fd0b5ccdc
Author: Miguel Casas <mcasas@chromium.org>
Date: Thu Dec 20 19:54:38 2018

docs/gpu/vaapi.md: Link TODO to bug

Link TODO to bug

TBR=andrescj@chromium.org

Bug: 917091
Change-Id: I0489ca019a1ca300d198f2c4c1a6717f65ef78eb
Reviewed-on: https://chromium-review.googlesource.com/c/1387392
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#618293}
[modify] https://crrev.com/24a3674be9f96f6543ffc187cdcda81fd0b5ccdc/docs/gpu/vaapi.md

Thank you for working on this!

We also have https://cs.chromium.org/chromium/src/docs/media/gpu/. Given that vaapi code is in media/gpu, I'm wondering if we should perhaps move this there, or alternatively have a stub with a link to the docs/gpu document from docs/media/gpu? WDYT?

#2: I thought about docs/media/gpu, but we're going to be using VaAPI
for non-video cases, e.g. accelerated image decoding or jpeg encoding,
and those are not/ don't have to be media/ ... 

@3: sgtm, thanks!

Hi, I am about to fill-in the TODO. I was wondering if there is any page in https://www.chromium.org/developers/design-documents that refers to docs/gpu/vaapi.md and docs/media/gpu ? i.e. can a reader discover them ? 

I don't see any reference to docs/gpu/vaapi.md after grepping, it would be good to add one, probably in docs/README.md? Also shouldn't this document be in docs/media/gpu/vaapi.md? mcasas@ probably has a more educated opinion than mine on the topic.

#5,6: feel free to link to it from any other documents/ ToCs.

Re. the docs/media/gpu, we already discussed it in #2-#3-#4,
right? Point being that VaAPI extends beyond media/ as it's 
understood in Chrome.