Return dpranke to (some) OWNERS files.

This is a partial revert of commit
0dfd069333cc2a29273706402d3c48b5099bd86c
(https://chromium-review.googlesource.com/c/chromium/src/+/3434116).

and returns dpranke to some directories he should still own (mostly
build files but a few scattered Python directories and the code of
conduct as well). It is only a partial revert because he no longer needs
to be an owner of some of the directories he was previously.

Change-Id: I23b3f40068caee55e88837e86fda5d1cb628c8e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3983606
Commit-Queue: Dirk Pranke <dpranke@google.com>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Erik Staab <estaab@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1066096}
NOKEYCHECK=True
GitOrigin-RevId: 8a720cdd501b94ada4df8b36e81aec17d991523d
1 file changed
tree: 30426e6328a1dec21b5a3af9af185ca1ee5feac1
  1. .gitignore
  2. __init__.py
  3. base.css
  4. doc.css
  5. footer.html
  6. gitiles_autolink.py
  7. gitiles_ext_blocks.py
  8. gitiles_smart_quotes.py
  9. header.html
  10. md_browser.py
  11. OWNERS
  12. prettify.css
  13. README.md
  14. update-css.sh
README.md

md_browser

This is a simple tool to render the markdown docs in a chromium checkout locally. It is written in Python and uses the Python ‘markdown’ package, which is checked into src/third_party.

md_browser attempts to emulate the flavor of Markdown implemented by Gitiles.

Gitiles is the source browser running on https://chromium.googlesource.com, and can be run locally, but to do so requires a Java install and a Buck install, which can be slightly annoying to set up on Mac or Windows.

This is a lighterweight solution, which also allows you to preview uncommitted changes (i.e., it just serves files out of the filesystem, and is not a full Git repo browser like Gitiles is).

To run md_browser:

  1. cd to the top of your chromium checkout

  2. run python3 tools/md_browser/md_browser.py

  3. There is no step three.

This will run a local web server on port 8080 that points to the top of the repo. You can specify a different port with the -p flag.