FYI, we are shifting over to use "Hotlist-Metrics" to track bugs for specific metrics, and reserving the "Internals>Metrics" component (and its subcomponents) for core metrics infrastructure work.

This bug has an owner, thus, it's been triaged. Changing status to "assigned".

alemate@ what is this data for? we can assign component based on what it's for?

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Jacob, could you help finding owner for this?

This issue says that we need to be able to collect data about [region=""] VPD data from devices, but chrome statistics is usually not allowed to collect string data for privacy reasons.

We need to find way to solve this issue somehow. Probably we should implement collecting hashes first, look at the statistics data, and decide whether we need anything more.

What's driving this request? It's not clear to me why this is a P1, what we intend to do with this data, or if privacy has been consulted.

Re #10:

this is an old story of https://crbug.com/702508 (which is blocked by this).

Basically we cannot switch locale/keyboard defaults from separate VPD values to "region" because we found devices with incorrect region values.

We've discussed that we need to somehow estimate the number of affected devices. My first attempt to suggest collecting "region" values as UMA metric was not approved by statistics team, as then said that they do not want to collect strings as values. I remember that they were fine with hashes.

So let's try to collect hashes, because otherwise we still do not have this information and cannot switch to single "region" in VPD.

<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!