TPMs are working with dev teams to add COMPONENT/TEAM information into the owner files in the chromium repo. The goal is to create a mapping from directories to components, and also a mapping from components to teams.

Proposal is https://docs.google.com/document/d/1jty6UsFMW9-SYgpQC-ztEc3lltziOQBBArMkROCSTh0/edit#heading=h.xgjl2srtytjt

We plan to extract such info from all the dispersed owner files into a single file which is also committed into the chromium repo in src/ root directory.
In this way, it would be much easier for tools to leverage the info for bug assignment, etc.

Concrete tasks here:
1. Create a script to extract COMPONENT/TEAM from owner files into a single file.
2. Set up a buildbot cron job to do this periodically and commit that single file into chromium repo. (similar to automatic dep roll)
 

TPMs are working with dev teams to add COMPONENT/TEAM information into the owner files in the chromium repo. The goal is to create mapping from directories to components, and also mapping from components to teams.

Proposal is https://docs.google.com/document/d/1jty6UsFMW9-SYgpQC-ztEc3lltziOQBBArMkROCSTh0/edit#heading=h.xgjl2srtytjt

We plan to extract such info from all the dispersed owner files into a single file which is also committed into the chromium repo in src/ root directory.
In this way, it would be much easier for tools to leverage the info for automatic bug assignment, etc.

Concrete tasks here:
1. Create a script to extract COMPONENT/TEAM from owner files into a single file in a machine-readable format like:
{
  "directory-to-component": {
    "path/to/feature1": "feature1-component",
    "path/to/feature2": "feature2-component",
  },
  "component-to-team": {
    "feature1-component": "feature1-owner@chromium.org",
    "feature2-component": "feature2-owner@chromium.org",
  }
}

2. Set up a buildbot cron job to do this periodically and automatically commit that single file into chromium repo. (similar to automatic dep roll)
 

TPMs are working with dev teams to add COMPONENT/TEAM information into the owner files in the chromium repo. The goal is to create mapping from directories to components, and also mapping from components to teams.

Proposal is https://docs.google.com/document/d/1jty6UsFMW9-SYgpQC-ztEc3lltziOQBBArMkROCSTh0/edit#heading=h.xgjl2srtytjt
Examples: https://cs.chromium.org/search/?q=%22%23+COMPONENT:%22+file:OWNERS

We plan to extract such info from all the dispersed owner files into a single file which is also committed into the chromium repo in src/ root directory.
In this way, it would be much easier for tools to leverage the info for automatic bug assignment, etc.

Concrete tasks here:
1. Create a script to extract COMPONENT/TEAM from owner files into a single file in a machine-readable format like:
{
  "directory-to-component": {
    "path/to/feature1": "feature1-component",
    "path/to/feature2": "feature2-component",
  },
  "component-to-team": {
    "feature1-component": "feature1-owner@chromium.org",
    "feature2-component": "feature2-owner@chromium.org",
  }
}

2. Set up a buildbot cron job to do this periodically and automatically commit that single file into chromium repo. (similar to automatic dep roll)