[roll] Roll fuchsia [governance] Move area descriptions into YAML.

This old structure was kinda confusing, with the descriptions living
in README.md and the metadata living in _areas.yaml. When the
"Graphics" area got semi-accidentally renamed, README.md didn't get
renamed, and so the description simply didn't show up on the API
Council page.

The downside is that the descriptions have to use HTML, rather than
markdown. However, this is already how the glossary works, so that's
not too unusual.

Also adds the API primary/secondary to the description for each area.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/698330
Original-Revision: 8ed58ce39311a8561195f2562dc42df2c558685b
GitOrigin-RevId: b913991d06ba9523ebf1210b4c93ce709ca9fdcf
Change-Id: I0c692eea797414e63327bed9e90d714307e75a01
1 file changed
tree: 6b148a5ba04a1a3f5dd04e3dc01c90b8fb39c896
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.